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!
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!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
