#1 - rootdelay set to 120 and 300, neither changes the results.
#2 not an IDE, its a SATA HDD issue.
#3 there are no unused SATA ports. Disconnected all but the root dirve, turned off as recommended, still having the same error.
#4 Bios updated prior to my install, its the latest.
Is there a way to capture the boot messages from the failed boot? I only get as far as the busybox (initrdfs I think) load after things time out and there are no sdN devices found.
Thanks.
#1 - rootdelay set to 120 and 300, neither changes the results.
#2 not an IDE, its a SATA HDD issue.
#3 there are no unused SATA ports. Disconnected all but the root dirve, turned off as recommended, still having the same error.
#4 Bios updated prior to my install, its the latest.
Is there a way to capture the boot messages from the failed boot? I only get as far as the busybox (initrdfs I think) load after things time out and there are no sdN devices found.
> This seems related to bug 220706. Just curious if you could try some of /bugs.edge. launchpad. net/ubuntu/ +source/ linux/+ bug/220706/ comments/ 51 /bugs.edge. launchpad. net/ubuntu/ +source/ linux/+ bug/220706/ comments/ 2 /bugs.edge. launchpad. net/ubuntu/ +source/ linux/+ bug/220706/ comments/ 42 /bugs.edge. launchpad. net/ubuntu/ +source/ linux/+ bug/220706/ comments/ 43
> the workarounds listed there and let us know your results:
>
> 1) "Yes. I already tried settings the rootdelay=120 and it boots after
> the drive has been discovered." -
> https:/
>
> 2) "I fixed the problem by turning my drives to cable select and re-
> plugging my ide cables in the proper direction." -
> https:/
>
> 3) "I turned off all my unused sata ports in BIOS, by changing 'Extended
> IDE Drive' to none." -
> https:/
> and
> https:/
>
> 4) You may also want to try a BIOS update if there is one available for
> you system