NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
recovery
13 Topics
RN104 shares lost after OS reinstall, Data still intact, how can i rescue it?
RN-104 Admin Password was lost, performed OS Reinstall from boot menu as instructed by forum users.Admin password is now recovered but all shares have dissapeared from Readynas, The disks still show the same percentage usage so im guessing the data is still intact on disk but all shares are lost, when i try recreating s share with the same name and path as one i previously had i get an error message saying it could not be created, howver if i try and create a share with a name i never previously used it works fine. Also readycloud service is degraded and will not connect. How can i go about rescuing my Data from the drives ? 4x2TB drives formatted in a JBOD array. Readynas Firmware Version: 6.8.1 Many thanks in advance !Solved1.7KViews0likes2Comments
Think twice before committing to X-RAID or RAID-5. What is your recovery plan?
TL;DR: Because I chose RAID-1 over X-RAID, I easily survived a disk failure. I'm back to having a working RAID-1 array, with no loss of data, no support contract, no data recovery fees, no proprietary programs, no shipping drives across the country, and my only cost (besides the replacement drive, of course) was a single SATA-to-USB device ($30). What worked? Boot up with Active@ LiveCD (http://www.livecd.com/) and use the File Manager. 5 years ago, when I bought my ReadyNAS, I engaged in these forums a debate between RAID-1 and X-RAID. My #1 priority was ability to recover data after a failure, while other people focused on maximizing disk space. Well, finally, one of my disks failed recently. No warning ahead of time, no SMART data indicating a disk might fail, just "Disk failure detected" in the logs after it was too late. My shares or volumes were inaccessible via normal Windows networking, and not available in RAIDiator either. There was no indication whether my data was still intact or not. Because I was using RAID-1, I believed that the good disk should still be OK, the hard part was figuring out how to read it. I connected the working drive to my laptop using a SATA-to-USB converter. Many software ideas did not work because the RAID data volume is seen as RAW and not Ext4, so Ext4 readers in Windows don't work. In the end it was one of the simplest options: I booted up using the Active@ LiveCD with the drive already attached. Once booted, the simple Linux File Manager ("Dolphin") was able to see and read all my files perfectly. I did NOT need any of the proprietary software on the CD, just the simple File Manager. And of course, it was possible to plug in a portable drive and copy everything from the source drive to the portable backup. Easy and Free. (I will also note that the basic file manager on the UFS Explorer emergency CD worked as well, although I found Dolphin slightly easier to use) (Later, I also found out that the volumes and shares were all available directly from the NAS after removing the failed drive. In other words, when the good drive was by itself without a failed mirror drive, the NAS made all the data and files available again, with an "unprotected" warning. So essentially, you don't even need a LiveCD... but the biggest advantage is being able to copy data at USB3 speed) Finally, restoring the NAS to RAID-1 was incredibly easy. I put the good drive back into its original slot on the ReadyNAS, ordered a replacement drive (same make and model as the failed drive), and popped it in. The ReadyNAS immediately began copying everything, it had a percentage indicator on the front panel, and only took about 10 hours to mirror 2.7 GB of data. Contrast this with the restoration of an X-RAID array. Start with trying to connect 3 drives to a laptop, plus a portable backup drive. You can easily run out of ports (especially at USB3 speed) or power outlets to plug everything in. Sure you can overcvome this but you're paying for SATA-to-USB enclosures, USB hubs, power strips, etc. Now, is there a definitive guide to restoring an XRAID array to read its data? Not from Netgear. There are some helpful tips and recommendations in these forums but certainly nothing that is foolproof or easy. There is a good chance you'll need to learn to use mdadm. And if it isn't working, is it because the array is not set up correctly, or the data itself is corrupted. Assuming you aren't a full time data recovery expert, how would you tell? There are many more reports of destroyed, overwritten and lost data, or expensive support contracts, than there are of successful DIY recoveries. And if it isn't DIY, it's certainly going to be expensive and often require you to send the physical drives somewhere. Bottom line: after going through this process, I am more convinced than ever that RAID-1 is superior to any other RAID option, unless your data is disposable or 100% backed up in real-time. RAID-1 is not failsafe of course (fire, theft, deleting/overwriting a file, etc), but it is just as compatible with any other backup methods (2nd NAS, drive-swapping, portable backup drives, rsync, cloud storage) as any other RAID type, PLUS you get the benefit of the easiest and fastest recovery process in the case of a drive failure. I would also like to thank StephenB for participating in the initial debate. His ability to see the pros and cons of both methods was appreciated.
Recovering files from ReadyNAS+
Hi, I started looking at ways to be able to access my old ReadyNAS NV+ and windows 10. Everything started going downhill from there. Could not even get to frontview any more. So I go and install DISKINTERNALS and low and behold it looks like its working. I am able to copy across files and save them. But some of the shares say there are no files. Wouldn't you guess they are the important ones :) I am looking at the diskinternals raid recovery, but I was wondering if anyone had a similar problem and a solution. I also tried reclaime (trial) and it keep abendingSolved2.4KViews0likes2CommentsCan't view subfolders/files within shares in Share section in the admin page. OS 6.6.1 Using AD.
ReadyNAS 314 running on 6.6.1 and using Active Directory The issue that I'm having is that when I attempt to drill down into shares in the Share section of of the admin page, nothing happens aside from the progress bar moving temporarily and then disappearing. When viewing the files in Windows explorer, I am not having any of these issues. This behavior is happening in both the current Shares view as well as the recovery view. It is happening with all shares. I am logging into the admin page with the ReadyNAS built-in admin account. This wouldn't be a problem aside from removing my ability to be able to recover specific files and folders within each share. I noticed this last week, but it could have been an existing issue since we moved over to active directory a couple of months ago. It seems like it might be an AD permissions issue, but I'm not sure. What do you guys think? Thanks in advance for any assistance you can provide.2.6KViews0likes2CommentsRN10200 Unable to Boot or reset or reinstall OS
My ReadyNAS is invisible to raidAIR and doesn't even show up under my routers connected devices list. I've tried several times to factory reset and it doesn't seem to work. I tried upgrading firmware back sometime in the winter and since then the readyNAS got put away in a box. Recently went to use it again and remembered why it ended up in the box... I've tried an OS reinstall just now with 2 different USB sticks, both times the process goes about it's thing very quickly, but then nothing happens. Is the readyNAS toast or should I just keep trying with other USB drives? Also, the unit is unresponsive to the power button and passed the memory test. I'm kind of stumped.5.1KViews0likes14CommentsReadyNAS Pro Pioneer - Solutions Please - Bad controller?
Ah the most dreaded topic. I've gotten a bit complacent since it's been so reliable, I double back up but not everything :( and of course I need it sigh. So I shut my pro pioneer down to replace the battery in the UPS it was connected too. Now it won't power up! I figure no big deal, I have a 550w power supply lying around, I'll just plug it all together to get it running again. I get the wiring all sorted out and the power supply keeps tripping out. I tested no drives plugged and it still trips out. I tested with the 3 molex disconnected and it looks like it boots ok (I didn't bother going very far with it) I tested individual molex and it looks like only the top one is ok that doesn't trip the system. the bottom two make power supply trip out or something. I guess bad controller? Anything else I should try? what are my options? Thank you for your timeSolved5.4KViews0likes20CommentsReadyNAS NVX Drive failure and replacement options
I have an NVX with 4x 2TB Seagate drives, configured as a single volume using X-RAID2. It reports Online, X-RAID2, 4 disks, 37% of 5548 GB used. Earlier today I got " Thu Sep 1 00:01:42 MDT 2016 Disk failure detected. Following a power supply problem a few months ago I acquired a 2nd NVX to use as backup. I has 4x 1TB Seagate drives. It's so far unused. By Coincidence today amazon delivered 4x 2TB Seagate drives for the backup NVX and I was going to set-up rsync to backup one to the other. So, short term I can take one of the proposed backup drives and plug it into the primary and buy another 2TB drive. Alternatively, since I don't need the full 5TB capacity, it occurs to me I could ut a 1TB drive in the primary NVX; then build the backup NVX with 1x 1TB and 3x 2TB and be left with a spare 3x 1TB and 1x 2TB drive ready for future drive failure. Make sense or am I missing something important? Both NVX are already running the latest/last RAIDiator-x86 Version: 4.2.28Solved2.9KViews0likes2Comments
ReadyNAS NV - New power supply Power LED 3 fast flash
I've had the power supply on my readynas NV die twice now, but that's to be expected I think when it's around 12 years old. This last round I got the new PWS and installed it. Now when the device tries to boot I get all 4 disk drive LEDs lit, and then the power button does this 3 quick flash then pause, 3 quick flash, pause, etc. Just loops. Not able to find it in Raidar. It's clearly having an issue booting but I'm not sure how to recover. The LED PDF suggested to re-seat the ram. Going to do that next, then it suggested doing a reset of nand. I'm worrid that my old raid is going to disappear and I'll still lose all my data. Any thoughts? Will an Nand recovery lose my raid config? Am I out of luck? Is the 3 flash something else? Thanks!2.5KViews0likes3CommentsSnapshot recovery mode does not give destination pop-up
As per OS 6.4.1 Software Manual and Knowledge Base (http://kb.netgear.com/app/answers/detail/a_id/23403), restoring individual files and folders should prompt for destination. I am not getting the destination pop-up, but the system is doing *something* immediately, as I do get this pop-up: The selected file is being restored now. ...and then this alert: File restore from snapshot has completed Why no destination pop-up, and where is the file being restored to?! ReadyNAS 104 firmware: 6.4.22.5KViews0likes4CommentsSuspect Disk scrubbing followed by fsck TRASHES filesystem. Now what?
I'm starting to suspect that the issue described in the community post titled "Disk scrubbing followed by fsck TRASHES filesystem?" just happened to me. https://community.netgear.com/t5/ReadyNAS-in-Business/Disk-scrubbing-followed-by-fsck-TRASHES-filesystem/m-p/848158#M1202 Wondering if anyone has any ideas as to what else I can try to recover the content. So far: I am running RAIDiator 4.2.28 on a ReadyNAS Ultra 6 Plus [X-RAID2] with 6 2TB drives in X-RAID2 with dual redundancy. The NAS disk check reports tons of errors, and the NAS can't seem to see anything on the data volumes, though the operating file system seems fine. I've plugged the 6 disks into another computer via USB3 and run a slew of recovery software on them. Only two seem to recognize the raid pattern: ReclaimMe Free Raid Recovery and UFS Explorer Pro (though they each report a slightly different configuration, they both detect RAID 6 and seem to be happy about it. ReclaimMe took about 2 hours to detect it by trial and error and only detected 1 raid pattern for the entire disk, UFS Explorer Pro found the raid parameters for 3 partitions (4GB, 2GB, and 7.27TB) instantly. The 4GB partition opens fine with UFS Explorer Pro, can be exported to an image, and I can recover any file I want from this file system image using rlinux from rtt. Just to see how bad things were, I started with the 4GB partition for the operating system. I've saved an image of the un-RAIDed 4GB OS partition, which is mirrored of each of the 6 drives. After trial and error with ReclaimMe, GetDataBack, RStudio, I found that UFS Explorer Pro (trial edition) was the only package that was helpful in detecting this 6x mirrored partition configuration and exporting the diskimage. However, it was rlinux (free) from rtt that allowed me to scan the partition and export the contents. So this partition seems to be intact, which make sense because RAIDiator is still running when I boot the NAS. I compared the unRAIDed image to a few of the mirror individually, and they seem fine, with only a few issues with how symbolic links and duplilcate (probably deleted versions) filenames are handled. Not so lucky with the data volume So then using ReclaimMe Free Raid Recovery, and the parameters it autodetected, I have saved a destriped image of the volume partition of the array, 7,27TB. It took me about 50 hours to write via USB3. I've scanned the destriped image with several recovery programs, so far, only rlinux or rstudio seems to find the EXT filesystem (after 20 hours) or so. ReclaiMe, GetDataBack and UFS File Explorer can find a bunch of file fragments, and ghosts of dozens of FAT and NTFS file systems that seem to belong to disk images and virtual hard drives and backups that I was storing, but no EXT partitions. in rlinux, the file system directory appears remarkably intact, with about 823000 files totaling about 4.44 TB. I can easily extract any one I want. However,it is aggrevating when I am able to recover some of these file and inspect them, that small files (a few kilobytes, probably within one RAID block) are almost always ok, image files like JPG often have ok previews but when opened are corrupt after about 10%-20% of the image, and longer music/video files play fine end to end, but with 'static' / 'corruption' in the stream. 7z/gz/zip/iso files will not open, and I haven't tried any binary files or office documents. So it seems to me like perhaps one of the blocks in the striping pattern got destroyed, and based on my logs, it fits with the known issue (albeit from before version 4.2.20) of 'file system gets trashed after raid scrubbing and fsck' described above. Questions - Please help! Any suggestions on what I can try next, or is the file system 'trashed' as described in the post referenced above? One more thing I thought to try is to export the disk image from UFS Explorer Pro to see if perhaps the reclaimme destriping is to blame for some of the corruption, and then try to recover the file system again using rlinux. That will take around 70 to 80 hours. Any chance that would succeed any better than the reclaime export? is there a better tool to 'destripe' the RAIDX2 to a disk image that I should use instead? Once I have the image, is rlinux the best way to detect the EXT file system, or are there others? Are there any that can repair it? Are there any on-device things I should try on the NAS to recover the file system? Recent system logs These seem to show how this started happening right after a raid scrubbing followed by a fsck on Jan 22. There was also a disk failure during a raid scrubbing on Jan 5, but there was at least one successful fsck on jan 18 that seemed to be ok after the rebuild on Jan 11. Fri Jan 22 16:42:28 EST 2016 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. vault media documents public content webroot common backup addons-config Fri Jan 22 16:40:13 EST 2016 Volume scan found errors that it could not easily correct. Please ensure that you have current backups of all valuable data before performing a full volume scan by rebooting the NAS through Frontview with the volume scan option enabled. Wed Jan 20 11:33:27 EST 2016 RAID scrubbing finished on volume C. Tue Jan 19 01:00:26 EST 2016 RAID scrubbing started on volume C. Mon Jan 18 01:08:08 EST 2016 The on-line filesystem consistency check completed without errors for Volume C. Mon Jan 18 01:00:02 EST 2016 The on-line filesystem consistency check has started for Volume C. Tue Jan 12 08:29:16 EST 2016 RAID sync finished on volume C. Mon Jan 11 19:42:18 EST 2016 RAID sync started on volume C. Mon Jan 11 19:41:51 EST 2016 Data volume will be rebuilt with disk 6. Mon Jan 11 19:39:41 EST 2016 New disk detected. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time. [Disk 6] Mon Jan 11 01:13:34 EST 2016 The on-line filesystem consistency check completed without errors for Volume C. Mon Jan 11 01:00:01 EST 2016 The on-line filesystem consistency check has started for Volume C. Tue Jan 5 14:42:01 EST 2016 A disk was removed from the ReadyNAS. For full protection of your data volume, please add a replacement disk as soon as possible. Tue Jan 5 14:42:01 EST 2016 Disk removal detected. [Disk 6] Tue Jan 5 08:42:20 EST 2016 RAID scrubbing finished on volume C. Tue Jan 5 08:42:14 EST 2016 If the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead. If this disk is a part of a RAID 6 volume, your volume is still protected if this is your first failure. A 2nd disk failure will make your volume unprotected. If this disk is a part of a RAID 10 volume, a failure of this disk's mirror partner will render the volume dead. It is recommended that you replace the failed disk as soon as possible to maintain optimal protection of your volume. Tue Jan 5 08:42:13 EST 2016 Disk failure detected. Tue Jan 5 08:35:37 EST 2016 Detected increasing spin retry count[540701285] on disk 6 [WDC WD20EZRX-00D8PB0, WD-WCC4M1521546]. This often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy. Tue Jan 5 01:00:33 EST 2016 RAID scrubbing started on volume C.Solved3.9KViews0likes6Comments
