I've recently installed FreeNAS 9.10 onto a system containing 12 drives (no real data)
MB: A1SAI-2758F/32 GB ECC RAM
LSI (Avago) 9207-8i (P20 Firmware)
Four of the drives are attached to the MB SATA controller and were given /dev names ada0-3
Eight drives are attached to the HBA and were given /dev/da0 thru /dev/da7
All is good!
I noticed that I had accidentally swapped the connectors to the HBA and during boot the configuration from the LSI utility shows disks physically in slots 0-3 are listed as slots 4-7 (and are given names /dev/da4 thru /dev/da7) and disks physically in slots 4-7 show as enclosure slots 0-3 and were given /dev/da0 thru /dev/da3.
No problem! I open the case, and swap the SFF cables and reboot. The LSI listing during boot looks fine but the /dev/hdX names stay the same.
I rearrange the drives in the slots, names stay the same (pretty cool). I pull some of the drives and the designations remap to /dev/da0 thru /dev/daX depending on the number of drives I've left in the system. but whenever I put all the drives back, it goes back to the original designations.
hmm! OK, OS probably has a list of ID's so let's reinstall the FreeNAS. Wipe the boot disk, reinstall, no joy! The drives are given their origin /dev/daX designations.
Now I'm pretty surprised! I guess there's some information written on the partitions. I boot gpartd, wipe the partition table off every drive, reinstall and still the drive designations stays the same.
So my question is what is happening? I get the value of keeping the same name once FreeNAS is installed but I'm really surprised that this is persisting across a partition wipe of all the drives in the system and a reinstall. I'm guessing that the 9207-8i itself is mapping a drive serial number to some manufactured SAS address and that's being passed to the driver. I took a quick look at sas2flash and did a -reset since that seems to be closest to a factory reset. I don't know if that guess is correct so I wasn't about to start erasing memory segments on the HBA to try to fix this.
Question 2: How do I force a rescan and reassignment? Or am I stuck having the physical and logical order forever out of alignment?
Thanks in advance for the help!
Kevin
MB: A1SAI-2758F/32 GB ECC RAM
LSI (Avago) 9207-8i (P20 Firmware)
Four of the drives are attached to the MB SATA controller and were given /dev names ada0-3
Eight drives are attached to the HBA and were given /dev/da0 thru /dev/da7
All is good!
I noticed that I had accidentally swapped the connectors to the HBA and during boot the configuration from the LSI utility shows disks physically in slots 0-3 are listed as slots 4-7 (and are given names /dev/da4 thru /dev/da7) and disks physically in slots 4-7 show as enclosure slots 0-3 and were given /dev/da0 thru /dev/da3.
No problem! I open the case, and swap the SFF cables and reboot. The LSI listing during boot looks fine but the /dev/hdX names stay the same.
I rearrange the drives in the slots, names stay the same (pretty cool). I pull some of the drives and the designations remap to /dev/da0 thru /dev/daX depending on the number of drives I've left in the system. but whenever I put all the drives back, it goes back to the original designations.
hmm! OK, OS probably has a list of ID's so let's reinstall the FreeNAS. Wipe the boot disk, reinstall, no joy! The drives are given their origin /dev/daX designations.
Now I'm pretty surprised! I guess there's some information written on the partitions. I boot gpartd, wipe the partition table off every drive, reinstall and still the drive designations stays the same.
So my question is what is happening? I get the value of keeping the same name once FreeNAS is installed but I'm really surprised that this is persisting across a partition wipe of all the drives in the system and a reinstall. I'm guessing that the 9207-8i itself is mapping a drive serial number to some manufactured SAS address and that's being passed to the driver. I took a quick look at sas2flash and did a -reset since that seems to be closest to a factory reset. I don't know if that guess is correct so I wasn't about to start erasing memory segments on the HBA to try to fix this.
Question 2: How do I force a rescan and reassignment? Or am I stuck having the physical and logical order forever out of alignment?
Thanks in advance for the help!
Kevin