I running into a failure booting S9 XFCE x86_64 from a USB. The boot sequence is getting stuck while searching for the cdrom. Here's a transcription of the console output:
>> Loading modules :: <List of modules loaded> >> Activating iSCSI via iBFT iscsistart: transport class version 2.0-870. iscsid version 2.0-872. Could not get boot entry >> Making tmpfs for /newroot >> Looking for the cdrom >> Attempting to mount media: /dev/sr0 >> Attempting to mount media: /dev/sda1 >> Attempting to mount media: /dev/sda2 >> Attempting to mount media: /dev/sda3 >> Attempting to mount media: /dev/sda4 /dev/sda4 is an extended partition. # fdisk -l /dev/sda Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x0000a378 Device Boot Start End Blocks Id System /dev/sda1 * 2048 2099199 1048576 83 Linux /dev/sda2 2099200 52430847 25165824 83 Linux /dev/sda3 52430848 102762495 25165824 83 Linux /dev/sda4 102762496 976773167 437005336 5 Extended /dev/sda5 102764544 153096191 25165824 83 Linux /dev/sda6 153098240 186652671 16777216 83 Linux /dev/sda7 186654720 253763583 33554432 83 Linux /dev/sda8 253765632 257959935 2097152 82 Linux swap / Solaris /dev/sda9 257961984 976773167 359405592 83 Linux The drive is a 500GB SATA Seagate Barracuda ST500DM002-1BD14 KC45 PQ I have a similarly configured 500GB Western Digital SATA which will also get stuck on the extended partition if I unplug the Seagate and boot with just the WD as the /dev/sda drive. I installed a Sabayon DAILY XFCE (Sabayon_Linux_DAILY_amd64_Xfce.iso dated May 27) during the pre-S9 testing period from the same USB, and didn't have problems. At that time, the /dev/sda drive was new and un-partitioned, but the /dev/sdb drive was my Western Digital that is now failing to boot the S9 USB final. I will re-install Sabayon_Linux_DAILY_amd64_Xfce.iso from May 27th to confirm it can still boot in this configuration or not, and that may give us a partial bisect on this issue.
