NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
LongTimer
Mar 23, 2018Aspirant
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...
- Apr 01, 2018
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.
Hombibi
Mar 25, 2018Guide
Hi Longtimer, sorry to hear about your situation. I have experienced something similar a while ago, and managed to recover everything without too much costs.
In short, I had a dynamic X-RAID array in which disks corrupted one after the other rendering the whole array inaccessible. Your situation is somewhat different but I would take the same approach I ended up recovering my data with:
My first step was securing the data off the disks: figuring the disks were old any could break up any moment now I bought a USB cradle that I connected to another computure, so that I could make exact data images of each disk. I used software that read the disks as a record (sequentially?) so that the platters/heads etc were least stressed. (Repiecing back data structures puts a lot of stress on disks.)
This allowed me to put the "old,fragile,unreliable" disks aside and only use the images to recover the data.
Once I had the images I used a piece of software that could detect dynamic arrays: select all images, and start. After the software recognised the dynamic array I was presented with the original filesystem which easily allowed me to recover/copy all data quickly.
In the end I recovered all my data, setup an automatic backup and simplified my NAS disk configuration.
Here is the sequence of events of my recovery, hopefully it will help you recover your data.
StephenB
Mar 25, 2018Guru - Experienced User
WD-WCAZA2099151 shows a pending sector count of 1452, which is definitely a sign of a failing disk.
Hombibi's link is worth reading through. One correction - XRAID's on-disk format is not proprietary (despite what the recovery folks said). It uses standard linux software raid and the btrfs file system. RTT's tool doesn't support btrfs, but ReclaiMe does.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!