I noticed something else interesting.
I tried loading to a SSD with MBR.
I follow the same steps above. On boot It started, but errored out.
I put another drive in to satisfy the sdb1 that didn't exist by putting the GPT drive back in. It booted up without problem.
There are two slots. The left one is labeled CON1 on the motherboard and CON2 on the left. It seems like it will only label a disk in the right side sdb.
When I put the SSD in the left side, it starts fine.
So it will boot to either slot, but will always call the Right slot sdb.
I tried loading to a SSD with MBR.
I follow the same steps above. On boot It started, but errored out.
[ 13.554904] ata1: SATA max UDMA/133 irq 21 [ 13.559023] ata2: SATA max UDMA/133 irq 21 [ 13.904743] ata1: SATA link down (SStatus 0 SControl F300) [ 14.414742] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300) [ 14.454771] ata2.00: ATA-8: KINGSTON SV300S37A120G, 506ABBF0, max UDMA/133 [ 14.461684] ata2.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 14.504772] ata2.00: configured for UDMA/133 [ 14.509493] scsi 1:0:0:0: Direct-Access ATA KINGSTON SV300S3 506A PQ: 0 ANSI: 5 [ 14.544927] sd 1:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB) [ 14.553869] sd 1:0:0:0: [sda] Write Protect is off [ 14.558860] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 14.572024] sda: sda1 [ 14.576272] sd 1:0:0:0: [sda] Attached SCSI disk [ 14.592745] sd 1:0:0:0: Attached scsi generic sg0 type 0 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Waiting for root file system ... done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/sdb1 does not exist. Dropping to a shell! modprobe: module i8042 not found in modules.dep
I put another drive in to satisfy the sdb1 that didn't exist by putting the GPT drive back in. It booted up without problem.
There are two slots. The left one is labeled CON1 on the motherboard and CON2 on the left. It seems like it will only label a disk in the right side sdb.
When I put the SSD in the left side, it starts fine.
So it will boot to either slot, but will always call the Right slot sdb.