[Recover Disk 2.0 Serial Key
Kody Coste
So a while back I had a disk failure, I put a new disk in and parity rebuild started, it was moving really slow and by morning the new disk died as well (second parity disk never kicked in I simply lost the data)
Not going to comment on the recovery process, but I will state that actual disk failures are pretty rare, and based upon your description its more likely to be a cabling or power issue. Sans diagnostics though its impossible to tell...
The link you gave seems to be about recovering from filesystem corruption. If that is your problem, rebuilding the disk is not going to help no matter how many disks you try. You need to fix the filesystem.
So is that rebuilt disk still in the computer? If so, have you checked it for filesystem corruption? A rebuild won't fix filesystem corruption, and filesystem corruption won't prevent a successful rebuild. So it seems to me you may still have issues you don't know about.
attempting to find secondary superblock...
............................................................................................................................................................................................................................................................................................................................................................................................................................Sorry, could not find valid secondary superblock
Exiting now.
Sparkum, it's really important you use the exactly correct command, and it's really important you know exactly what the file system is that you should fix, because if you use the wrong one, you can damage things even worse. All 3 commands you tried above were wrong! This is not the place for trial and error methods. Please, take the time to read the wiki page more thoroughly!
True that, I didn't even look carefully at the other commands used, only at the first, ideally you know which filesystem it is but if not run both in read only mode, xfs_repair was correct, but with reiser use reiserfsck --check only at first.
Are you absolutely certain that both drives were formatted with XFS? I noticed that you used both xfs_repair and reiserfsck, as if you were not sure which file system was in use. Using the wrong tool can both cause additional damage, and result in errors that may look like hardware errors. You need to find previous evidence of the actual file systems, like older syslogs or notes or screen captures, that indicate the correct file system for each.
Once you know which one it is (ReiserFS or XFS), then you can retry on both with the correct tool. And if it is ReiserFS, then you should try the --rebuild-tree option with the scan whole partition option (-S), searches the entire partition for files and folders.
Basically, after the upgrade to FW 6.5.0, the system became unstable: (1) it crashed every few hours; (2) rebooting would often hang with a blinking power button, and I couldn'tg reach my volume; (3) if it did boot all the way, and I could reach my volume, the power button would still keep blinking, and soon the volume would become unreachable.
So I pulled the 2 disks out (configured as RAID-1 and tried re-installing the OS through the boot menu. Now, nothing works. When I re-insert the same two disks, RAIDar is able to detect the chassis, but shows no disks. AND the power button perpetually blinks.
Thus, I've decided that I should give up trying to read the disks in the RN102 and just recover the data from the disks manually using my PC. At no point did I do a factory reset, so all the data should still be on my two disks. How do i recover the data from the 2 RAID-1 disks using my PC?
Sometimes I've found that actually disconnecting the system from power can help with bios device detection, so I thought it worth a try. Most modern electronics are never really off as long as they are powered. But it looks like the system is locking up after the boot. It could be the chassis hardware, something wrong with one of the disks that eventually crashes the SATA bus (or drivers), or something really wrong with the 6.5 upgrade.
Question on the customer support: if I go all the way to a data recovery contract, if I expect that my disks are in perfectly good shape, would the data recovery services produce an image of my disks on a third disk with my file structure and file names fully intact? Or would the recovery be just a dump of all the files w/o any file structure and files named by some some arbitrary recovery sequence? I have some 20k files on these two 4-TB drives, so such a dump of a recovery would be rather useless.
Then you use support again to resolve the lockup problem. Perhaps at that point all your data is intact and mounted, but if the volume were corrupted, you would need a separate data recovery contract.
Regarding the link "Recover HDD data from broken ReadyNAS," it doesn't specify the Windows tools that I might be able to use. I've seen Linux Reader/DistkInternals and R-Linux to referred to elsewhere in these NETGEAR forums. But no guidance on how to use them. I've got on HDD now hooked up to my Windows 10 machine now, and R-Linux is running a scan of it (about 7 hours into that scan). And waiting.
@StephenB @JennC: I've re-inserted by two disks back into the RN102, selected 'Reinstall OS' from the boot menu (being very careful to select Reinstall OS and not default reset), waited 3.5 hours, and power button never stop stopped blinking. Double pressing power didn't shut it down, so I unplugged the AC adapter to power it down. I plugged it back in, and it entered the boot up sequence. RAIDar is able to see that it's in boot up, and then RAIDar says no disks are detected, and it's been this way for 3 hours now.
As far as I can tell both disks should still be good and not corrupted, because before I originally pulled the disks out, I was able to read the volume from Windows Explorer for a minute or two before the RN102 crashed (see original problem up top).
Try powering down the NAS, and removing the power connection. Wait a few minutes and then reseat the two disk trays. Then restart and try again with RAIDar. If the NAS still doesn't see the disks, then contact support.
I am newcomer here but I share your concern and had similar problem. I have a readynas 102 with two one TB HDD in RAID 1 configuration. I had some issues with OS and tried to connect the Ready NAS directly on ethernet crossconnection to PC. Did couple of resets and when i started my ReadyNas was broken it says cant mount volumes. The DATA was ofcourse precious, so I removed the HDDs and connected them to PC extra sata ports. booted the machine in windows, the only software which could show all my files was Reclaime, however to save the showed files it needs a licence of 200 $ which i cant afford as of now. So I am still trying to figure out alternative means. Reclaime shows me all the files and previews for my 10000 plus images. Hope it helps.
And if the file system is corrupted, it might not recover everything anyway. We hear this story over and over. RAID is not enough to keep your data safe, and RAID recovery can be expensive, time consuming, and is not guaranteed.
@landed up on Active @ LiveCD with capability to handle the BTFRS, so .. downloaded the image and made a bootable pen drive. Connected my HDD from NAS through SATA, booted the Active Live CD and VOILA, the partiions automounted and all my data was there in front of me...
Anyway, the outcome of my case is that I paid for an extended warranty/tech support contract for one year since the original 90 day support period had long expired. Tier 2 and Tier 3 identified a firmware or OS corruption that could not be resolved remotely, so I received a replacement NAS unit. After I received the new unit, Tier 3 recovered my data (3 TB) for me onto an external drive.
795a8134c1