NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Ken_C1's avatar
Ken_C1
Aspirant
Oct 21, 2014

ReadyNAS Pro 4 fsck failing

I've got a ReadyNAS Pro 4 (recent rma for an NVX). When I installed the drives from the NVX in it, it booted just fine. I elected to upgrade it to 4.2.27 (or whatever the latest one is).

After that, it gave me an error about the on line filesystem check finding errors and needing to run the check on reboot. OK, fine...

At the same time, I installed the root ssh enabled plugin (of course!)

Anyway, on reboot, the check ran up to 64%, sat there for awhile, then flipped to Booting.... and sat there all night.

I finally tried sshing in with the IP, and I was able to get in and see that /c was not mounted. I tried to run a manual fsck -fy on /dev/c/c. That seemed to work, until it ran out of memory and gave me a sigterm 9. Since then, I've been able to mount /c manually (either by mount -a or mount /dev/c/c /c) and restart Frontview, so I am able to get into it. However, every time I reboot it, it goes back into the fsck.

What are my options at this point? Is my best choice to rsync the data off to another device and reformat this one? I tried contacting support, but my warranty only covers hardware at this point (boo, hiss).

10 Replies

Replies have been turned off for this discussion
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    My guess is that something actually is corrupted in the file system. So rsyncing the data to another device is a good first step. Of course it might fail when it gets to whatever files are at the 64% point.

    After that you could continue to repair the file system, or do a factory reset and rebuild from scratch.
  • Yeah, I'm sure it's running out of memory, but I'm at a loss as to how to troubleshoot it. But you're probably right (sigh).
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    Perhaps you could send me your logs zip file (see the link in my sig)?
  • Will do, if I can get it up far enough. I've been toying with some crazy ideas like plugging in a USB stick and putting a swap volume on it to give it enough memory to get away with the fsck. Watching top, I can see it filling up the ram, then the swap, and then the kernel kills it. But we'll see.
  • 1977 root 20 0 515m 498m 540 R 98 50.4 5:30.19 fsck.ext4

    About ready to die...

    Ah wait, I lie, this is a 1GB unit.

    Maybe that's the problem... the swap size doesn't match the ram size. Hrm...
  • Sent you the logs, but they were 146MB, so I don't know if they're going to make it.
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    Try removing the backup job logs and sending them again.
  • It's actually the fs_check.log! Uncompressed it's 624MB!

    Something weird there...

    Seems to be this:
    /dev/c/c: Multiply-claimed block(s) in inode 44696921: 715161705
    /dev/c/c: Multiply-claimed block(s) in inode 44696922: 727269183
    /dev/c/c: Multiply-claimed block(s) in inode 44696923: 1257472 <massive list of numbers>

    I'll try cutting out just one section of this which should hopefully compress well and go through.
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    Definitely sounds like big issues with the filesystem.

    If you can't backup your data you may wish to consider paid support options.
  • Heh... I've got a 3.7PB NAS system at work that I administer. I imagine I can find some space for my 3.3TB of ReadyNAS data.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More