One challenge in migrating from Sparc architecture products, to Intel or other (Arm), is that the Linux file system on sparc was built with a 4k block size, rather than 512.
On Intel linux, if you set up your disks, you can mount them with some incantations and special procedures. Not sure how the Readynas Linux handles that problem, but there is a link showing it.
I had a bad disk and some problems with the data recovery firmware on a REadynas NV+ some years ago and got the support group to help me get around it. In the mean time, I had mounted the 4 drives on an Intel linux system I'd built up and had recovered most of the data.
Copy of article for archival:
This articles outlines the necessary steps to access data on disks from ReadyNAS units running RAIDiator on ReadyNAS OS 6 units.
Due to differences in CPU architecture and operating system between RAIDiator and ReadyNAS OS 6, it may be necessary to take additional steps once the disks are moved to an OS 6 chassis.
If your ReadyNAS running RAIDiator is still functional, and you can access the data, we recommended you first backup the data to another location
If you can no longer access the data using your legacy ReadyNAS and you wish to access the data using your ReadyNAS OS 6 device, booting may not be as easy. Depending on which legacy model the disks come from, and which ReadyNAS OS 6 you posses the steps differ to make the data accessible.
After initially moving the disks from the legacy ReadyNAS to the ReadyNAS OS 6 model please be aware of the following items;
- Do not attempt an OS reinstall
- Do not attemp a factory reset
- The RAID must be healthy i.e. if the RAID was broken on the legacy NAS it will not always be possible to access the data on the ReadyNAS OS 6 - an example of this would be 2 failed disks in a 4 disk RAID 5.
- ReadyNAS OS 6 model must have at least the same amount of drive bays as the legacy ReadyNAS
- Logging a ticket with Technical Support may be required
- Purchasing a data recovery contract may be required
- You may require one additional spare blank disk
- You may require an external location to where you can recover your data to i.e. external USB HD, network share, other NAS storage.
- ReadyNAS OS 6
- ReadyNAS 100 series (RN102, RN104)
- ReadyNAS 200 series (RN202, RN204)
- ReadyNAS 210 series (RN212, RN214)
- ReadyNAS 2120 (RN2120)
- ReadyNAS 300 series (RN312, RN314, RN316)
- ReadyNAS 500 series (RN516)
- ReadyNAS 700 series (RN716X)
- ReadyNAS 3130 (RN3130)
- ReadyNAS 3138 (RN3138)
- ReadyNAS 3220 (RN3220)
- ReadyNAS 4220 (RN4220)
- RAIDiator 4.1 (sparc)
- ReadyNAS Duo (RND2XXX)
- ReadyNAS NV+ (RND4XXX)
- ReadyNAS 1100 (RNR4XXX)
- Follow the instructions at ReadyNAS: Migrating disks from RAIDiator 4.1 or RAIDiator 5.3 to ReadyNAS OS 6
- RAIDiator 4.1 (sparc)
- RAIDiator 4.2 (x86)
- ReadyNAS NVX, NVX Pioneer (RNDX4XXX, RNDX4XXE)
- ReadyNAS Pro Series, Pro Pioneer, Pro Business (RNDP2000, RNDP4XXX , RNDP6XXX, RNDPXXXXE)
- ReadyNAS Ultra Series (RNDU2XXX, RNDU4XXX , RNDU6XXX)
- ReadyNAS Ultra Plus series (RNDP2XXU, RNDP4XXU, RNDP6XXU)
- ReadyNAS 1500 (RNRX4000)
- ReadyNAS 2100 (RNRX4000)
- ReadyNAS 3100 (RNRP4000)
- ReadyNAS 3200 (RN12PXXXX)
- ReadyNAS 4200 (RN12TXXXX, RN12GXXXX, RN12SXXXX)
- Follow the instructions at ReadyNAS: Migrating disks from RAIDiator 4.2 to ReadyNAS OS 6 (x86)
- RAIDiator 5.3 (ARM)
- ReadyNAS Duo v2 (RND2XXXv2)
- ReadyNAS NV+ v2 (RND4XXXv2)