NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Original Infrant ReadyNAS NV powers up but not responding
After a recent power outage, our original Infrant NV seems to turn on but will not respond. It was populated with 3 WD 3 TB drives and has been that way for 6 or 7 years working perfectly. So prefe...
Well I've been rooting around the rabbit hole for a while now and I'm finally up for air. I was trying to use System Rescue CD but that was a dead end as it was too hard for me to add the necessary software without apt-get. I switched and set up a live persistent USB with Mint 18 and was able to access the files. As we speak they are being transfered to another drive. The USB was very easy to setup using Windows software here: https://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
As many here know, the key was to use "fuseext2". Not "fuse-ext2" and not "mount". For those who are reading this without seeing alot of other info the SPARC versions of the ReadyNAS NV with version 4.x firmware use a non-standard 16k block size so fuseext2 is the only one that will play nice-ish. I still could not access the mounting with any GUI applications on Mint and it would lock up the LV if I tried. With my level of knowledge the only way out at that point was a reboot.The following instructions posted elsewhere will work. Just use the right mounter fuseext2 and do not add a dash. That was a huge time waster for me.
(1) sudo su (2) apt-get install fuseext2 (3) apt-get install lvm2 (4) modprobe fuse (5) vgscan (6) vgchange -ay c (7) fuseext2 -o ro /dev/c/c /mnt (7) fuseext2 -o ro -o sync_read /dev/c/c /mnt That’s it!!! You can now see the mounted files in the /mnt directory
While the clues were there, it took a long time for me to put them together. On an unsuccessful mount, Mint gives some advice to check the dmesg using
Code: dmesg | tail where I found this:
Code: EXT3-fs (dm-3): error: bad blocksize 16384
Googling the message found someone with the same issue and that fuseext2 must be used to accommodate the nonstandard block size. With that change, it was off to the races and plodding through authoring the proper rsync and find commands to get what I wanted.
I still like the tool set on the SytemRescueCD and while it can be done, I don't think I am at the level to add the software required to this live CD. It is a shame that it is not easier as there are always new (or old) tools that come along a person might need or want when troubleshooting.
Thank you very much for the time you spent considering my challenge. Just knowing there are knowledgeable people like you willing to help lowered the anxiety greatly.
I was able to connect to the admin page for a short time and managed to download the logs. If this will help anyone to give me some direction, it would be appreciated. I have pasted the most recent entries below from the log page. I would guess disk 3 is on its way out but I would appreciate a second oppinion. I can send the zipped log files if it would help. What would be the best plan of attack from here?
I have the unit shut off right now and will leave it that way until I can get enough backup storage on hand in case I can get reconnected. I was not able to do much during my connection and when I went to the volumes tab, nothing happened and the page bonked.
I'm very nervous as I am being forces to yank the plug to get it to shut down each time and that can't be a good thing.
Fri Mar 23 02:04:22 PDT 2018 System is up. Fri Mar 23 02:00:41 PDT 2018 Reallocated sector count has increased in the last day. Disk 3: Previous count: 9 Current count: 10 Growing SMART errors indicate a disk that may fail soon. If the errors continue to increase, you should be prepared to replace the disk. Fri Mar 23 01:59:01 PDT 2018 RAID sync started on volume C. Fri Mar 23 01:58:52 PDT 2018 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Thu Mar 22 22:09:14 PDT 2018 System is up. Thu Mar 22 22:03:47 PDT 2018 RAID sync started on volume C. Thu Mar 22 22:03:39 PDT 2018 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Thu Mar 22 21:13:36 PDT 2018 System is up. Thu Mar 22 21:08:23 PDT 2018 RAID sync started on volume C. Thu Mar 22 21:05:20 PDT 2018 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Wed Mar 21 20:34:38 PDT 2018 System is up. Wed Mar 21 20:29:47 PDT 2018 RAID sync started on volume C. Wed Mar 21 20:29:23 PDT 2018 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Sun Mar 18 15:01:55 PDT 2018 A SATA reset has been performed on one or more of your disks that may have affected the RAID parity integrity. It is recommended that you perform a RAID volume resync from the RAID Settings tab ( accessible in the Volumes page => Volume tab in FrontView ). The resync process will run in the background, and you can continue to use the ReadyNAS in the meantime. Sun Mar 18 15:01:15 PDT 2018 Access to the disk on channel (??) is producing I/O errors. Although the array is still redundant, please replace this drive as soon as possible, as it is likely to fail soon. Sun Mar 11 04:00:04 PDT 2018 Reallocated sector count has increased in the last day. Disk 3: Previous count: 8 Current count: 9 Growing SMART errors indicate a disk that may fail soon. If the errors continue to increase, you should be prepared to replace the disk. Wed Feb 28 04:00:03 PST 2018 Reallocated sector count has increased in the last day. Disk 3: Previous count: 7 Current count: 8 Growing SMART errors indicate a disk that may fail soon. If the errors continue to increase, you should be prepared to replace the disk. Mon Jan 22 03:55:20 PST 2018 RAID sync finished on volume C. The volume is now fully redundant. Sun Jan 21 19:32:37 PST 2018 System is up. Sun Jan 21 19:27:35 PST 2018 RAID sync started on volume C. Sun Jan 21 19:26:52 PST 2018 Improper shutdown detected. To ensure data integrity, a filesystem check should be performed by rebooting the NAS through Frontview with the volume scan option enabled. Fri Dec 15 04:00:03 PST 2017 Reallocated sector count has increased in the last day. Disk 3: Previous count: 6 Current count: 7 Growing SMART errors indicate a disk that may fail soon. If the errors continue to increase, you should be prepared to replace the disk.
3TB disks aren't supported by the NV so I'd be surprised if you're using those.
This doesn't look like a situation an OS Re-install would help with. An OS Re-install will reset some network settings (ones that may lock you out of the system if configured incorrectly) and the admin password and extract the OS over itself. It won't magically fix a bad disk.
If your backup is not up to date you may wish to contact support. There would be costs involved with this.
You can send me your logs if you like (see the Sending Logs link in my sig), but it does sound like contacting support would be best in your situation.
If your data's important to you then you really should backup that data regularly in future, especially if the primary copy of the data is on a very, very old device.
Troubleshooting would be the same as for the NV+ (v1) except for the lack of a display on the front. So like the Duo you'd have to rely on seeing the LED pattern for using the boot menu etc.
The Duo/NV+ (v1) boot menu is very different to the menu for the v2 so don't look at the wrong boot menu by mistake.It's possible disk cloning may be needed to attempt to recover data, but the logs would need to be reviewed before one could jump to that conclusion.
You are right. It has 3 of 2.0 TB Western Digital WD20EARS. Late night when I was typing and I can't seem to edit the message to correct.
Logs sent.
Last backup is from April 2016.
I am thinking maybe of pulling Drive 3 and tyring to restart. I really don't like having to pull the plug when it locks up.
I will wait for your comments/feedback before taking any further action.
You need better information befoe pulling a drive and re-booting. The re-allocated sector count on Drive 3 is nowhere near the critical level. The ATA error on drive (??) is a lot more troublesome. But unless you can confirm that is also on Drive 3, then you are not ready to pull any drives. If you pull the wrong one and an ATA error occus during the re-sync, all could be lost.
If the info you need isn't in the logs, then testing all the drives on a PC with WD Lifeguard would be a good next step. Just insure you keep the NAS power off all through the testing and you return the drives to their orignal locations.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
