NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS Pro 6 Checking root FS
Hi
My ReadyNAS Pro 6, running firmware 6.7.5 was working fine for many months. However, a few days ago, it became inaccessible from web gui and ssh (did not reply to pings) and appeared hung. After powering off and restarting, it came back with the previously formatted dirty disks error. Using the Boot Menu, I tried an OS Reinstall. However, this hangs on the "Checking root FS" message. Rebooting again takes me back to the dirty disks error.
Telneting in, I can see my data raid partitions, and can mount them and copy between them without any issues. My data seems to be intact. However, mounting the /dev/md0 partition fails with an invalid argument error. I'm guessing my 4GB root FS partition is either full or otherwise corrupt? Is there a way to manually wipe this and restore from the flash from within the command line environment?
I'd appreciate any help in getting the OS reinstalled.
As I can see my data, if necessary, I can probably pull it off and do a factory reset. However, I'd prefer not to if at all possible, especially as it seems to be just an issue with the root FS.
Thanks in advance.
Yes that's possible. It should only be considered though if confident that the disks are healthy (you've checked SMART stats) and that the data volume RAID and filesystem are in a good state.
Formatting the root volume wipes the logs etc. off it.
After trying to mount md0 you should check what the error message is by doing e.g.
# dmesg | tail
Depending on what the error is it might be fixable (with a small amount of data loss) without resorting to the drastic step of formatting md0. Greater care needs to be taken with the data volume if that fails to mount.
A read-only btrfsck can provide useful information.
2 Replies
Replies have been turned off for this discussion
Yes that's possible. It should only be considered though if confident that the disks are healthy (you've checked SMART stats) and that the data volume RAID and filesystem are in a good state.
Formatting the root volume wipes the logs etc. off it.
After trying to mount md0 you should check what the error message is by doing e.g.
# dmesg | tail
Depending on what the error is it might be fixable (with a small amount of data loss) without resorting to the drastic step of formatting md0. Greater care needs to be taken with the data volume if that fails to mount.
A read-only btrfsck can provide useful information.
Thanks mdgm. Your PM was also very helpful. I've sent another PM with a small query on which I would be grateful for your input on.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
