Ok, so I’ve finished populating the JBOD disk tray with 18 600’s and 6 1TB’s and all the pools are up and running as I expect.
However…
The system seems to think that all the disks in the JBOD are somehow not assigned into a pool (only 4 of them should be unassigned (2 hot spare 600s and two new 1TBs today)), plus it seems to think that I have 26 drives available to add, not the 24 max size of the tray.
Anyone know whats the easiest way to correct this? I want to just get it to see the drives are actually in use and correct the values etc. Possibly I could export and re-import all the pools on the back end as the SAS drives in the server seem ok as do the SATA drives in the other array (which is connected as a secondary device to the JBOD’s secondary controller).
Exported and re-imported the pool (set to not destroy data or config to be safe ) and still showing 26 disks.
Note:- If I try to add them it is complaining about non-unique serial numbers… I guess something went awry in the upgrade to E.E. as it’s only been since then…
Pulled one cable out of the back of the JBOD and the fans started screaming for a while (and not in a good way )…
Ok. So, showing 2 drives as being available (the two I just added in today so that’s good) but also 4 drives as being removed and that’s taken down half the pool (the 600GBx18 Zvol)…
right, lets bounce the tray and the server and see what it picks up. Maybe the other drives that have gone missing are being referenced by the now unplugged second controller…
looks like it was that. seems if you have dual controllers on the sas jbod, you can only connect from one of them (so no resiliency) otherwise TNS will read the drives twice. Looks like it might be an E.E revision issue though as it was ok before the upgrade…
) and still showing 26 disks.