NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Shares now Read Only after Updating to 6.7.1
I have an RN526X as my primary server and use a RN314 as a backup server. Yesterday, I upgraded both systems to OS 6.7.1
Each night at 10:00, the RN 526 sends an incremental backup to a folder on the RN314. At midnight, the daily snapshots are taken and those snapshots are also sent to the correspending share on the 314 (the Music share on the 526 is sent to the MusicDR share on the 314, etc.) This has been working fine for a couple of months.
Last night, after the OS upgrade, the backup worked fine but the ReadyDR on the 526 failed and the logs have the following errors.
| Sun May 7 2017 0:00:40 | ReadyDR: ReadyDR job failure: Read-only file system [VideosDR] | |
| Sun May 7 2017 0:00:37 | ReadyDR: ReadyDR job failure: Read-only file system [SoftwareDR] | |
| Sun May 7 2017 0:00:35 | ReadyDR: ReadyDR job failure: Read-only file system [SharedDR] | |
| Sun May 7 2017 0:00:32 | ReadyDR: ReadyDR job failure: Input/output error [PicturesDR] | |
| Sun May 7 2017 0:00:28 | ReadyDR: ReadyDR job failure: Input/output error [DocumentsDR] | |
| Sun May 7 2017 0:00:26 | ReadyDR: ReadyDR job failure: Input/output error [DavidDR] |
In checking the shares on the 314 I found that all of the DR shares are not shown a Read-Only. There is no box to change them to Read/Write and if I go into the Share settings, the File Access tab is grayed out and I cannot change the access.
If I try to create a new Share I get an error message that says:
Failed to craete Share. Please be sure Share name is valid and unique. Code 1013050001
It would seem that the voume is locked. Is there any way to correct this?
Thanks,
David
18 Replies
Replies have been turned off for this discussion
Please send in your logs (see the Sending Logs link in my sig)
Logs have been sent.
I have exactly this issue since I upgraded to 6.7.0 and subsequently to 6.7.1 betas and final. I have ReadyDR backups to an Ultra 6 plus from a 316.
Thread is here:
I have needed to reset the unit 4 times in the last few weeks. I am now not using ReadyDR and the problem has not recurred.
The logs were full of errors which I was told was related to filesystem corruption - these errors made the system force a change to read only
The disks are all OK after thorough testing and the NAS memory is fine.
I will eventually restart ReadyDR and I suspect the problem will recur when I do.
Perhaps have a look at your logs - system journal particularly , to see if you have similar errors, although I would be interested to see what mdgm has to say after looking at your logs.
Since this server is only used for backup I decided to restore it to factory default and I can now create new folder and have read/write access again. I have recreated the backup job from the 526 to the 314 and it appears to be running successfully (it is still running).
I am trying to re-set-up the Ready DR jobs but I cannot upload the Access Key from the 526 to the 314. I download the key without issue but when I try to upload it to the 314 I get an error box. There is no description or code, it just says error.
As I recall there is nothing special about uploading the key. Am I missing a step in stting this up?
Thanks,
David
See your logs, all disks have below errors, please check volume.log file
Reallocated Sectors: 2
Reallocation Events: 2and btrfs filesyste has errors, then volume force to readonly, please check systemd-journal.log
Could do you please backup your data on NAS? then format all disk,
I suggest you had better replace all disks because all disks have reallocated errors.
May 07 00:00:21 ReadyNAS314 replisync[7577]: MusicDR: receiver: Receiving from ReadyNAS526 (2fe6e954): /data/MusicDR/.snapshots/182
May 07 00:00:22 ReadyNAS314 kernel: BTRFS error (device md127): parent transid verify failed on 635994112 wanted 8866 found 8926
May 07 00:00:22 ReadyNAS314 kernel: BTRFS error (device md127): parent transid verify failed on 635994112 wanted 8866 found 8926
May 07 00:00:22 ReadyNAS314 kernel: BTRFS error (device md127): parent transid verify failed on 635994112 wanted 8866 found 8926
May 07 00:00:22 ReadyNAS314 kernel: BTRFS warning (device md127): Skipping commit of aborted transaction.
May 07 00:00:22 ReadyNAS314 kernel: ------------[ cut here ]------------
May 07 00:00:22 ReadyNAS314 kernel: WARNING: CPU: 1 PID: 7598 at fs/btrfs/transaction.c:1853 cleanup_transaction+0x82/0x270()
May 07 00:00:22 ReadyNAS314 kernel: BTRFS: Transaction aborted (error -5)
May 07 00:00:22 ReadyNAS314 kernel: Modules linked in: vpd(PO)
May 07 00:00:22 ReadyNAS314 kernel: CPU: 1 PID: 7598 Comm: btrfs Tainted: P O 4.4.62.x86_64.1 #1
May 07 00:00:22 ReadyNAS314 kernel: Hardware name: NETGEAR ReadyNAS 314/To be filled by O.E.M., BIOS 4.6.5 11/05/2013
May 07 00:00:22 ReadyNAS314 kernel: 0000000000000000 ffff880010ab7a80 ffffffff883cf3c8 ffff880010ab7ac8
May 07 00:00:22 ReadyNAS314 kernel: ffffffff88cec0b7 ffff880010ab7ab8 ffffffff8806b25c ffff88006ab14f30
May 07 00:00:22 ReadyNAS314 kernel: ffff88007bb5e000 ffff88007c351390 00000000fffffffb ffff88007bb5e000
May 07 00:00:22 ReadyNAS314 kernel: Call Trace:
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff883cf3c8>] dump_stack+0x4d/0x65
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff8806b25c>] warn_slowpath_common+0x7c/0xb0
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff8806b2d7>] warn_slowpath_fmt+0x47/0x50
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff882ea962>] cleanup_transaction+0x82/0x270
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff8809f680>] ? wait_woken+0x80/0x80
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff882ecb34>] btrfs_commit_transaction+0x964/0xa30
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff883203f7>] btrfs_mksubvol+0x537/0x550
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff8809f680>] ? wait_woken+0x80/0x80
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff8832059c>] btrfs_ioctl_snap_create_transid+0x18c/0x1a0
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff88320742>] btrfs_ioctl_snap_create_v2+0x102/0x150
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff883253df>] btrfs_ioctl+0x133f/0x2d30
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff8814958d>] ? do_filp_open+0x8d/0xd0
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff88172a04>] ? fsnotify+0x384/0x470
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff8814b745>] do_vfs_ioctl+0x2b5/0x480
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff8814881f>] ? putname+0x4f/0x60
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff8814b984>] SyS_ioctl+0x74/0x80
May 07 00:00:22 ReadyNAS314 kernel: [<ffffffff88a4b717>] entry_SYSCALL_64_fastpath+0x12/0x6a
May 07 00:00:22 ReadyNAS314 kernel: ---[ end trace f5649e008d2444b5 ]---
May 07 00:00:22 ReadyNAS314 kernel: BTRFS: error (device md127) in cleanup_transaction:1853: errno=-5 IO failure
May 07 00:00:22 ReadyNAS314 kernel: BTRFS info (device md127): forced readonly
- Thanks for your note. Please see my follow up post directly above yours.
I did do a factory reset of the NAS (twice) and now do have read/write access. That said, it looks like there is still an issue with the file system as it will not allow me to upload the access key for the ReadyDR function.
I have also tried another manual install of the 6.7.1 firmware but that did not change anything.
Other than that, it seems like the NAS is running correctly again.
A screen shot if the error is included above.
Thoughts?Thanks for your reply. Clearing the browser in Chrome did not help but switching to the Safari (Mac) browser did allow mew to upload the Access Key.
That said, after uploading the key to the 413, I re-setup the ReadyDR shares on the 314 but all of the ReadyDR jobs failed. In checking the history there is sometimes a message that says Broken Pipe. Most of the times the ReadyDR jobs just say Running but never complete and nothing is written to the 314, and I have to cancel the jobs manually.
I know the 314 is on the network and visible to the 526 because a Backup job backing up the entire data volume to a Share on the 314 continues to run fine every night at 10:00 PM.
Any ideas what I am doing wrong?
Regards,
David
I have the same problem since 6.7.1.
root@Io:~# mount | grep -v snapshot | grep '(ro' tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) /dev/mapper/Io-0 on /Io type btrfs (ro,noatime,nodiratime,nospace_cache,subvolid=5,subvol=/) /dev/mapper/Io-0 on /apps type btrfs (ro,noatime,nodiratime,nospace_cache,subvolid=259,subvol=/.apps) /dev/mapper/Io-0 on /home type btrfs (ro,noatime,nodiratime,nospace_cache,subvolid=260,subvol=/home)
All my snapshots are readonly too.
I tried :
- Restart
- Update to 6.7.4
- Check the ro property with btrfs :
root@Io:~# btrfs property get -ts /Io ro=false
Nothing worked
What can i do ?
Thanks in advance
Apparently I spoke too soon when I reported that things were now working correctly.
As I reported yesterday, it appeared that upgrading to 6.7.4 resolved the issue as I was able to complete a manual DR backup job and it automatic DR jobs worked perfectly for two (maybe three) days. This morning, when I opened my email, I was surprised to find a string of messages from the 526X stating that all of the ReadyDR jobs failed because there was a Read-only file system or there was an input output error. Here are the actual error messages:
ReadyDR job failure: Read-only file system [VideosDR] ReadyDR job failure: Read-only file system [SoftwareDR] ReadyDR job failure: Read-only file system [SharedDR] ReadyDR job failure: Input/output error [PicturesDR] ReadyDR job failure: Input/output error [DocumentsDR] ReadyDR job failure: Input/output error [DavidDR] I have not changed anything on the 314 and haven't even added any new data to the 526X since rebuilding the ReadyDR jobs last weekend. This has happened spontaniously.
Any idea why this is happening and how to corrct it?
Regards,
David
I don't have an answer for you but I have posted about this problem several times before and never got an answer.
This is one of the threads:
I have factory defaulted my unit several times as this seem the only way to clear the read-only file sytem error.
I have pretty much isolated the cause to ReadyDR -the unit ran normally for 2 months recently and within 10 days of activating ReadyDR jobs I have the dreaded read-only filesytem error. I have run memory tests and extended disk tests on all disks.
Interestingly once the error appears I can delete the ReadyDR jobs, but not the ReadyDR shares - I get a "failed due to snapshot deletion failure "error
I am running OS 6 Ready DR on a legacy unit which may be why I haven't had much interest from Netgear, perhaps now that there are others with similar issues on newer machines we may get an answer.
I have logs if anyone interested.
Another factory default coming up and I'm abandoning ReadyDR.
It would be good if you could send in logs.
Support has got a case that they suspect might be related (though something that appears to be related at first glance may prove to be quite different).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
