NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN214 internal power supply failure
Hi all, My second ReadyNAS (RN214) died recently after five years of always-on use. Same thing that killed my previous one - failure of the internal power supply. I've had some awful problems...
Recovery is now in progress, humming along the LAN to my new QNAP at a blistering 75MB/s, ish. Not sure if that speed limit is due to the resources I allocated to the VM (bridged adapter, 2 CPUs, and 2GB of RAM) or some other limitation happening on the network. But whatever, at least it's working! The VM recognized the raw drives instantly and booted just like real hardware would. Even reverted to my old login credentials.
Sandshark, I have 4 x 8TB Seagate Ironwolf Pros in RAID 5, for 20TB available space. I'd offer a minor tweak to the instructions that you posted:
1) Firstly, Windows users may encounter problems getting vboxmanage.exe to actually mount the raw drives, getting an ACCESS ERROR message (or something like that), as I did at first. This is likely due to a permissions problem with VboxSVC.exe - go into the Properties menu and set it to run as administrator. Run vboxmanage.exe and VirtualBox itself as admin, too. Once I did this it all worked smoothly.
2) Second, the createrawvmdk command has now been deprecated and VirtualBox recommends you don't use it. The new approved method for mounting a raw drive is:
VBoxManage.exe createmedium disk --filename nas1.vmdk --format=VMDK --variant RawDisk --property RawDrive=\\.\PHYSICALDRIVE1
Thanks again for posting your initial guide - I likely wouldn't have my data back without it!
It does sound like the flash image may be corrupt.
I've not run it on VitrualBox >V6, so there may be an additional; setting needed if you are running V7.
Make sure the "flash" image is installed on SATA channel zero and that EFI boot is not enabled.
You should also be able to disconnect the hard drive image and see if it boots and searches for disks.
Note that booting without a drive installed will cause the OS to update to 6.10.10 unless you have the Ethernet settings set such that it cannot see the internet (like Host Only mode). While Netgear has claimed to me that this auto-update is impossible, it absolutely does happen, at least in some cases, with the VM being one of them.
Thanks Sandshark. Fortunately, a helpful YouTuber uploaded the image to Google Drive for me. There's a link in his video description here, if anyone else has this issue: https://www.youtube.com/watch?v=l1wnpyGb4cA
I've successfully booted the VM now and have access to the GUI. I'll make an attempt at connecting the drives for recovery tomorrow (it's 0100 here!). Will update this thread to help out others who may face the same problem as the ReadyNAS hardware that's still out there gets older.
Glad you got it worked out.
How large are your drives? One thing I never did is try to determine if there was a limit to the drive size, just as there is a limit to the number of drives. So let us know if you have success.
Recovery is now in progress, humming along the LAN to my new QNAP at a blistering 75MB/s, ish. Not sure if that speed limit is due to the resources I allocated to the VM (bridged adapter, 2 CPUs, and 2GB of RAM) or some other limitation happening on the network. But whatever, at least it's working! The VM recognized the raw drives instantly and booted just like real hardware would. Even reverted to my old login credentials.
Sandshark, I have 4 x 8TB Seagate Ironwolf Pros in RAID 5, for 20TB available space. I'd offer a minor tweak to the instructions that you posted:
1) Firstly, Windows users may encounter problems getting vboxmanage.exe to actually mount the raw drives, getting an ACCESS ERROR message (or something like that), as I did at first. This is likely due to a permissions problem with VboxSVC.exe - go into the Properties menu and set it to run as administrator. Run vboxmanage.exe and VirtualBox itself as admin, too. Once I did this it all worked smoothly.
2) Second, the createrawvmdk command has now been deprecated and VirtualBox recommends you don't use it. The new approved method for mounting a raw drive is:
VBoxManage.exe createmedium disk --filename nas1.vmdk --format=VMDK --variant RawDisk --property RawDrive=\\.\PHYSICALDRIVE1
Thanks again for posting your initial guide - I likely wouldn't have my data back without it!
I think the slow speed can be attributed to the fact that the drives are still going through the VBox virtual drive interface, though they are in raw mode. But speed isn't the main consideration here, so it sounds like a success.
I assume from the fact that the vboxmanage command has been depreciated that you are running it on VirtualBox V7. Good to know it still works with that, though I had no reason to think it wouldn't.
Whether or not you need to make the permission changes depends on the main security settings you have on your computer. If you have them set to prompt for admin permission, then the changes shoudn't be needed. I likely did run vboxmanage from an admin command prompt and didn't think to specify that.
I thank you for bringing attention back to this free method of data recovery that does not require knowledge of Linux. If a volume is corrupted, it's not going to help, but many may find themselves in your shoes as ReadyNAS get older.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
