|
System suddenly changing disk order from BIOS order
When I first installed F12 I had as follows:
BIOS Drive udev assigned
SATA0 WD500AAKS /dev/sda
SATA1 ST3500630AS /dev/sdb
SATA2 ST3500410AS /dev/sdc
SATA3 ST3500418AS /dev/sdd
sda has 2 primary partitions, sda1 300MB /boot ext4, sda2 rest of drive as the first VG in LV with full encryption (LUKS). The VG is subdivided with 9 LVs including the first of 2 swap files, swap01 which is additionally encrypted.
sdb has 1 primary partition setup as a 2nd VG and LUKS, using the full 500GB I had created 3 LVs, again one is swap02 and also additionally encrypted.
sdc has 1 primary partition setup as a 3rd VG and LUKS and 1 LV using the full 500GB of the drive.
I had decided that I wanted to move VG3 to a new 1TB. I removed /dev/sdc from LVM (vgremove, lvremove, and pvremove) leaving it as just a LUKS volume. My intent is to reuse it by expanding VG2 to use both sdb and sdc. The 1TB (WD1001FALS) is sdd and the 500GB that was sdd now is sde on a different host adapter. For some reason, all of a sudden sdb and sdc seem to have flip-flopped. What I have now is:
BIOS Drive udev assigned
SATA0 WD500AAKS /dev/sda
SATA1 ST3500630AS /dev/sdc
SATA2 ST3500410AS /dev/sdb
SATA3 WD1001FALS /dev/sdd
SATA4 ST3500418AS /dev/sde
I have tried sapping the cables around, but only the BIOS sees the change, F12 still puts the 630AS drive as sdb and the 410AS drive as sdc. What gives? I don't want to attempt the expanding of the LUKS/LVM VG2 from what was sdb to include sdc if it's backwards.
|
