Hi, after a bit of support again!

 

I've moved to a new system - all new hardware (including new raid controllers), but bringing the disks with me.

(Old controller was an Adaptec 51245 in JBOD mode)/ New controllers are H200s, though all disks are connected to only one of them)

 

On the old system, I screenshotted the current array config, stopped the array, disabled 'autostart' & shut down

 

I moved all the disks to the new system, ensured the controllers were configured correctly (IT mode v20) and boot was to the usb drive.

 

unRaid starts up fine, but even though it seems to have correctly identified each disk, it's not allowing me to start the array as there are too many 'wrong' drives.

 

Have I missed out a step?

 

Edited May 9, 20179 yr by extrobe

IIRC, you were using a RAID controller before that you assigned each disk as a JBOD? If that's the case, you probably need to set a new config and reassign the drives, now that unraid can read them directly instead of the RAID controller managing them.

1 minute ago, jonathanm said:

IIRC, you were using a RAID controller before that you assigned each disk as a JBOD? If that's the case, you probably need to set a new config and reassign the drives, now that unraid can read them directly instead of the RAID controller managing them.

 

Correct - I'll give that a go, thanks!

That seems to be doing the job - parity sync has started, and a cursory look through the drives suggests they're intact etc!

 

thanks for the prompt help again!

 

(ps, I'm going to be changing the heatsink - bizarrely, it's too tall for use with my new Lian Li D8000W! Gets in the way of the centre divider which I want to use to mount a fan to cool the controllers)

BTW, unless you have a really good reason to skip drive slots, I wouldn't. It can complicate things, especially with poorly written user addons that assume no empty spots.

Just now, extrobe said:

parity sync has started,

Theoretically you should be able to check the box saying parity is valid on the new config screen and just do a check instead of a full sync.

Just now, jonathanm said:

BTW, unless you have a really good reason to skip drive slots, I wouldn't. It can complicate things, especially with poorly written user addons that assume no empty spots.

 

Just now, jonathanm said:

BTW, unless you have a really good reason to skip drive slots, I wouldn't. It can complicate things, especially with poorly written user addons that assume no empty spots.

 

Not a very good reason - only that I was having odd issues with slot 4 failing (even with different disk in different bays - thought I'd play it safe / try and rule out/confirm a disk issue whilst I built the new system. I'll be adding more drives post parity-sync, so will have a disk 4 again!

1 minute ago, jonathanm said:

Theoretically you should be able to check the box saying parity is valid on the new config screen and just do a check instead of a full sync.

 

That would have probably saved me 24 hours, but I'll just let it get on with it now!

(Plus, unsurprisingly, the new system is running at a much faster pace than the original one!)

Disk "slots" are purely a programming / logic thing. Nothing to do with what is physically connected where.

 

Also, if you already have the drives you want to add and know they are good, you would save time by stopping the sync and just adding them with a new config. Parity WILL need to be rebuilt in that case, but you will save the time of unraid needing to clear them before they can be added to the parity protected array.