NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FSCK Fails after expansion on NVX case# 20304759
I have an NVX that has given me some FSCK problems lately. It started with an expansion months ago that caused FSCK failures, so all the data was backed up, the NVX reset and rebuilt, and then all the data restored.
Subsequently, new online FSCK failues were found. Rebooting with FSCK enabled took the data volume offline and tech support was unable to fix the problem. I managed to mount the volume read-only and back the data up and reinitialize again.
In my latest attempts to reset and rebuild the box, I decided to be extra paranoid. After the initial 4T volume was built, I was informed that a volume expansion would take place on the next reboot (expected). So I decided to force an FSCK on reboot. That one came back clean. After the additional 1TB of space was added to the volume (Bringing the volume to a 5099GB size), I was informed again that a volume expansion would take place on the next reboot (expected). I forced an FSCK on reboot and rebooted the NVX. Now it's come back with errors and the data volume is offline. FSCK errors with a memory allocation failure. I'm somewhat convinced that something in 4.2.22 is misbehaving when expanding the volume, corrupting large numbers of inodes to the point that it exhausts all memory on the system.
Also note that I've run the boot menu's Test Disks without any issues.
Anyone have any ideas on how to resolve this? The fact that an empty data volume is coming back with FSCK errors is rather impressive.
Subsequently, new online FSCK failues were found. Rebooting with FSCK enabled took the data volume offline and tech support was unable to fix the problem. I managed to mount the volume read-only and back the data up and reinitialize again.
In my latest attempts to reset and rebuild the box, I decided to be extra paranoid. After the initial 4T volume was built, I was informed that a volume expansion would take place on the next reboot (expected). So I decided to force an FSCK on reboot. That one came back clean. After the additional 1TB of space was added to the volume (Bringing the volume to a 5099GB size), I was informed again that a volume expansion would take place on the next reboot (expected). I forced an FSCK on reboot and rebooted the NVX. Now it's come back with errors and the data volume is offline. FSCK errors with a memory allocation failure. I'm somewhat convinced that something in 4.2.22 is misbehaving when expanding the volume, corrupting large numbers of inodes to the point that it exhausts all memory on the system.
Also note that I've run the boot menu's Test Disks without any issues.
Anyone have any ideas on how to resolve this? The fact that an empty data volume is coming back with FSCK errors is rather impressive.
22 Replies
Replies have been turned off for this discussion
- That permutation failed, so I tried 4.2.19 with a factory reset. So far so good, FSCK is coming back clean after the first expansion!
- Full rebuild on 4.2.19 worked. Post rebuild upgrade to 4.2.22 and a reboot w/FSCK worked too. There must be a bug/issue in the expansion tools or process in 4.2.22 (and possibly earlier versions).
- I'm going to do 2 more things to verify that my system is going to stay stable:
- RAID Scrub
- Online FSCK
If both of those run and don't completely corrupt everything, then I'll be comfortable restoring the unit. - Note these all worked. Supposedly 4.2.23 will fix the expansion problem
- Which begs the question "Any news on 4.2.23 Release date"? :)
horshack wrote: Note these all worked. Supposedly 4.2.23 will fix the expansion problem
Thank you for your efforts, again! At least, my volume expanded using 4.2.22 did not die the last weeks and checking the md5sums of all files shows no silent data corruption.- I'm almost certainly facing the same issue on my NVX. What were the steps you took to resolve it? A manual run of fsck, seemingly, from what I'm reading elsewhere on the forums, but I'd like to check first.
- Since I had a recent backup, I did a factory reset and after all the expansions I rebooted with the volume scan boot option set until the fsck errors went away. However, downgrading to 4.2.19 before factory reset would have been much safer! Perhaps 4.2.23 does not only destroys the file system while expanding but kills the underlying RAID. Then, I might lose data that I copy to the NAS silently just by hitting the corrupted RAID sections.
See this thread: viewtopic.php?f=66&t=69366 - Any updates here guys? I'm now stuck on the same issue.... will a reboot with FSCK bring my volume back to a writeable stable state?
Everything was working, I rebooted and ran fsck, after seeing almost no progress I rebooted again... and now I can't mount /dev/c/c
Any ideas on how to bring it back? - You should open a NetGear support case (see Online Submission link in my sig) and post your case number.
I have been informed that NetGear is looking into this issue at the moment. Any solution provided in 4.2.23 though would be if possible to prevent users who have yet to run into this issue (i.e. have not yet expanded their volume on affected firmware) from running into this issue.
It is a good precaution to backup your data regularly, and particularly before doing things like expanding your data volume.
Keep an eye on the 4.2.23 beta thread: http://www.readynas.com/forum/viewtopic.php?f=51&t=70385
NetGear has already resolved a number of other issues with 4.2.22 in the 4.2.23 beta builds available so far.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
