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...
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
I actually have been looking at this already, but I'd need access to the shell and every time I try to add that or grant it to any users, I get the original 1002030001 error. I'd also, from what I can tell, need the telnet user name and password in Tech Support mode to be able to get to the shell via PuTTY.
I was actually planning, after the data copy, to try something like this with some info I've found while searching. Though much of it is very old and I suspect the un/pw are different for my model. I'll give it a go before the factory reset.
In any case, I re-installed the OS one more time on the problematic device again and it keeps restoring access long enough for me to copy content out. I suspect by the end of the day I'll have everything out and can get going on the full reset. Hopefully that solves the issue permanently.
Try to access the following URL (put the NAS IP or name instead - try https if not response): http://NAS_IP/dbbroker?start_svc=ssh
Using Tech Support mode isn't that easy, everything must be done manually. But if you want the password, you can find on Internet.
btrfs restore doesn't need the volume to be mounted.
Thanks! The copying is nearly done and I'll give it a whirl afterward. More tomorrow.
Michael
Finally got all the data off and decided to try the repair method. Here's what I did:
1. Started SSH as you described:
http://NAS_IP/dbbroker?start_svc=ssh - Successfully started ssh
2. Restart NAS in Tech Support Mode
3. Used PuTTY to connect:
- port 23
- telnet mode (not ssh)
- IP- login using [redacted]
4. Started issuing commands:
btrfs check --repair /dev/md127 enabling repair mode checksum verify failed on 20187450474496 found AB26D242 wanted 00000000 checksum verify failed on 20187450474496 found AB26D242 wanted 00000000 checksum verify failed on 20187450474496 found AB26D242 wanted 00000000 checksum verify failed on 20187450474496 found AB26D242 wanted 00000000 bytenr mismatch, want=20187450474496, have=0 Couldn't read tree root Couldn't open file system
btrfs check --fix-crc /dev/md127 Fixing bad CRC checksum verify failed on 20187450474496 found AB26D242 wanted 00000000 >> Fixed checksum verify failed on 20187450474496 found AB26D242 wanted 00000000 >> Fixed bytenr mismatch, want=20187450474496, have=0 Couldn't read tree root Couldn't open file system
btrfs check --repair /dev/md127 enabling repair mode bytenr mismatch, want=20187450474496, have=0 Couldn't read tree root Couldn't open file system
From there I have no idea what to do, and the internet is only providing so much. Pretty sure this is a lost cause now, so I'm going to make sure my recovered data is backed up and then start fresh in the morning with a factory reset.
Michael
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
