RNDU6000 won't boot - faulty PSU or bricked NAS?

mazerj wrote:
StephenB - I just got off the phone with support and they confirm what you said -- the 316 can NOT read drives formatted under Radiator4.2.x or boot from them. They have no idea what either tech support or mdgm were talking about yesterday.

Well the tech you spoke to today is wrong if he said that. It can boot from it if the array is fine. An x86_64 system (i.e. 300 series, 516 or 716x) can boot 4.2.x. Our head dev has put code in the firmware to handle this situation. We have an internal article on this.

Of course if there is a problem with the array or an issue on the OS partition this will remain when you move the disks across and the NAS will fail to boot.

Do you know what version of OS6 is on the 316?

mazerj wrote:
However, apparently I can pay $200 for their advanced data recovery service and they'll have a tech remote in and recover the data for me so I can copy it off. This seems to indicate OS6 can read ext volumes, but they won't tell me how to do it.

A tech remotely logging in is only necessary if there is a problem with the array and OS6 thus can't boot 4.2.x.

mazerj wrote:

StephenB - I think I'm on the right track now, I booted to OS6 off a spare drive and now I should be able to ssh in and use LVM/mdadm to manually assemble the raid volume. I just need to poke around to figure out the partitions that contain data (vs os) and the right mdadm incantation (I'm a bit rusty there - that's why I'm BUYING nas's and not building them myself anymore..). This would work if the drives weren't redundant since I'd need to get all 6 in there...

If you want to do it that way, you need to do some things e.g.

# systemctl stop readynasd
# systemctl disable readynasd

To make sure the NAS does nothing with the disks from the 4.2.x box. If you break things trying to recover data yourself we may deny support.