NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Retired_Member
Jul 11, 20171002030001 - Commit failed when making or checking permissions after firmware 6.7.5 update
My ReadyNAS 214 device has been running very smoothly for months. I use it for backing up and storing a lot of static content on my home network. This morning I noted that I could not copy files from...
Retired_Member
Jul 12, 2017Thanks - I hope they do reply; my backups are not running right now and that makes me twitchy.
jak0lantash
Jul 12, 2017Mentor
Perhaps your data volume is mounted Read-only.
Look for BTRFS messages inside dmesg.log and systemd-journal.log, and for md127 in mounts.log, and paste the beginning of btrfs.log here.
- Retired_MemberJul 12, 2017
Thanks for the reply. Inside dmesg.log, there are a large number of the following lines, about 12 per second:
- [Wed Jul 12 07:43:37 2017] BTRFS critical (device md127): unable to find logical 2595263971328 len 4096
Inside systemd-journal.log, there were 2246 instances of:
Jul 11 07:37:08 [redacted] kernel: BTRFS critical (device md127): unable to find logical 2595263873024 len 4096
Inside mounts.log:
/dev/md127 on /data type btrfs (ro,noatime,nodiratime,nodatasum,nospace_cache,clear_cache,subvolid=5,subvol=/)
/dev/md127 on /apps type btrfs (ro,noatime,nodiratime,nodatasum,nospace_cache,clear_cache,subvolid=257,subvol=/.apps)
/dev/md127 on /home type btrfs (ro,noatime,nodiratime,nodatasum,nospace_cache,clear_cache,subvolid=256,subvol=/home)
/dev/md127 on /run/nfs4/home type btrfs (ro,noatime,nodiratime,nodatasum,nospace_cache,clear_cache,subvolid=256,subvol=/home)Looks like read only if "ro" is an indication
The first segment of the btrfs.log:
Label: '11b7bc56:data' uuid: bfc1ea85-d4ed-4b14-a0dd-357b1b85a202
Total devices 1 FS bytes used 11.72TiB
devid 1 size 16.36TiB used 11.75TiB path /dev/md127=== filesystem /data ===
Data, single: total=11.74TiB, used=11.72TiB
System, DUP: total=8.00MiB, used=1.28MiB
System, single: total=4.00MiB, used=0.00B
Metadata, DUP: total=1.50GiB, used=717.62MiB
Metadata, single: total=8.00MiB, used=0.00B
GlobalReserve, single: total=252.00MiB, used=0.00B
=== subvolume /data ===
=== btrfs dump-super /dev/md127
superblock: bytenr=65536, device=/dev/md127*[redacted] is my modification for server name
Thanks,
Michael
- jak0lantashJul 12, 2017Mentor
Your volume is mounted read-only, which explains the symptoms. In the logs, you should find mention of something like "falling back to read-only". This is because of some BTRFS corruption.
As far as my experience with BTRFS goes, you're better off going for the backup + wipe + restore option, imho.
It seems that this what was done on this occurrence: https://community.netgear.com/t5/Using-your-ReadyNAS/btrfs-search-forward-2d4-error-on-RN204/m-p/1199638#M122268
This will save you huge amount of time. Even if you contact NETGEAR Support, there is a good chance they'll dump the filesystem anyway (I doubt they will fix the filesystem in place).
- Retired_MemberJul 12, 2017
Well, I won't shoot the messenger. But, argh.
I did a search through all the logs using Notepad++ for the terms you suggested. Lots of results for Read-Only file system, but nothing suggesting the cause of the issue, overtly. I don't know enough about each individual log to look for a root cause. I only assume the firmware update instigated it. The only regular activity on this NAS is the nightly backups and they've been going fine.
Fortunately, I kept my old NAS around and can use it for backup/wipe/restore. I'll probably start after work, so if anyone else wants to chime in (hello, Netgear Mod), feel free.
Thanks for the support.
Michael
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!