NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
1002030001 - 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 one folder to another. Then realized I could no longer add or modify any files anywhere on my shares.
I've made no changes to the system in a while save one: updated the firmware to 6.7.5 last week. I probably didn't add anything to the server in that time until today. That's the only culprit.
Now, I am seeing this:
- Where my group or individual user shares were set correctly, they now appear as "guest" or 'anonymous'.
- I can see all my content but cannot modify it or add or delete it
- I have 4.6TB of about 16TB.
- The logs don't show anything alarming (in the GUI - the downloaded logs is another story)
- The downloaded logs show numerous permissions errors. Access denied. Groups not existing
- Interestingly, I can add new users and groups (with an error, but it creates them).
- I can't assign shares to these new users.
I could use some help. Anyone else seeing this or have a fix that hopefully doesn't include wiping the system and starting over?
Best,
Michael
24 Replies
Replies have been turned off for this discussion
- If there is any data you couldn't copy, you can try 'btrfs restore'.
I'd advise you to inspect the data you copied, to confirm that the files aren't corrupt, etc.Good advice; I've done a lot of spot checking and everything looks intact. Late last year I forgot I made a change to my backups and I actually have everything backed up, luckily about 2 hours before the corruption set in on the 11th. So, I have a full intact set of backup and was able to copy out every file from the NAS yesterday. So I have two copies, really.
The memory test has been running for 9 hours now. All the drive lights are solid green, which from what I can tell is good news. So I'll be resetting the unit today and will begin the process of restoration, checking files again as I go. Particularly the genealogy and photos section (both of which are also backed up in the cloud - yes, very paranoid, hehe).
Really appreciate the help. Not sure why Netgear never officially stepped in. Even if they knew it was doomed - would have been nice to hear it quickly.
- The point of the dbbroker command to enable SSH so you didn't need to go to Tech Support Mode...
I wouldn't have done btrfsck --repair at all. - Good job for having a good backup! I'm glad you didn't lose any (important) data.
Interesting thoughts during recovery:
I decided to try the non-brute-force approach to this.
In a good twist of fate, my last backups ran about two hours before the fault on the 11th. This rarely happens. I unmounted the backup drives from the NAS. Then, I set up my old NAS (Ultra 4) and started copying files over from the problem NAS. I quickly realized a number of my folders were inaccesible. I copied the two (of 10) which i could and then performed a Reinstall OS, as I had read if fixes some security issues on the data volume.
Interestingly, when I rebooted, all of my folders were accessible again. I immediate started a copy of the remaining 8 folders. My optimism was short-lived, though, as, while the length copy took place, several of the folders became inaccessible again. I've managed 3 more folder sets. I'm going to try the OS reinstall again once they complete and see if I can get the remaining folders. If not, I'll rely on backup.
Once the data transfer is done, I'll do a full factory reset on the current NAS and then move some content back in and watch it like a hawk.
Will update so future generations have a path forward.
You can also look at "btrfs restore".
https://btrfs.wiki.kernel.org/index.php/Restore
https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-restore
Look in the log zip at volume.log. Towards the bottom you'll see a section header of === df -h ===
Right below that you'll see something like this:
=== df -h ===
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 3.7G 574M 3.0G 17% /
tmpfs 1009M 0 1009M 0% /dev/shm
tmpfs 1009M 532K 1009M 1% /run
tmpfs 505M 656K 504M 1% /run/lock
tmpfs 1009M 0 1009M 0% /sys/fs/cgroup/dev/md127 927G 20M 925G 1% /data
/dev/md127 927G 20M 925G 1% /home
/dev/md127 927G 20M 925G 1% /appsCan you post those lines from your log?
Surely, here you go. What does that tell you besides the use amount?
=== df -h ===
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 3.7G 1.1G 2.4G 32% /
tmpfs 1009M 0 1009M 0% /dev/shm
tmpfs 1009M 944K 1008M 1% /run
tmpfs 505M 1.1M 504M 1% /run/lock
tmpfs 1009M 0 1009M 0% /sys/fs/cgroup
/dev/md127 17T 12T 4.7T 72% /data
/dev/md127 17T 12T 4.7T 72% /apps
/dev/md127 17T 12T 4.7T 72% /home
/dev/sdf1 3.6T 1.6T 2.1T 44% /media/USB_HDD_2
/dev/sde1 3.6T 633G 3.0T 18% /media/USB_HDD_3It tells me that your OS partition is not full, which rules out one possible cause.
/dev/md0 3.7G 1.1G 2.4G 32% /
This is higher than it normally is (note mine was about 17%) but not anywhere close to full.
I don't have a good next step in mind though. If a Netgear mod requests your logs, it'd be good to provide them for Netgear's analysis.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
