ReadyNAS312 move disks to replacement 312 - easy?

---

flattened wrote:

Hello, hopefully a simple question.

 

I have a (months old) 312 unit on OS6.6.1 that is making me sweat with its behaviour (call it UNIT-A). I have an identical NEW 312 unit also on OS6.6.1 and a basic build that has been added to ReadyCloud ( call it UNIT B)

 

 

---

1. Install the same firmware on both systems if they are mismatched.  Do this by upgrading whichever firmware is older.
2. Gracefully shut UNITB down.
3. Remove its disks 2*2TB disks (labeling by slot).
4. Gracefully shut UNITA down.
5. Take UNITA's 2*2TB disks and put them into UNITB (preserving slot order)
6. Start UNITB up.
7. Put UNITB disks into UNITA (preserving slot order)
8. Start UNITA up.

There is no need to factory reset UNITB.  Also there isn't any real need to back up the config of UNITA.  The systems boot from the disks, and the full configuration moves with the disks.  That includes apps, readcloud, users, permissions, the host name, etc.  

The boot process checks the firmware in the flash against the disks, and if they are mismatched it will attempt to upgrade whichever is older (from the other). That's generally a good thing, but can go wrong.  That is why I suggest matching the firmware versions first.

If the issue with UNITA is software-related, it will move with the disks.  If it's hardware-related it won't.  Swapping the disks will hopefully give you some confirmation on where the issue lies.  

Since my adapted migration keeps both systems running, there is no reason to leave ReadyCloud on UNITB first. Although if there are no ReadyCloud users configured for UNITB now, you could leave ReadyCloud if you wish.  It's important to keep the readycloud user home folders backed up, since if those accounts are deleted via ReadyCloud, those folders will be deleted too.  Several people here have lost precious data because the accounts were deleted when they didn't expect them to be.