Ok so I narrowed down to a case that I could repeat - Booting while
connected to a drive that the system can't access while booted. In this
case a corrupt hard drive. In dmesg this kind of device gives me the
errors:
[ 212.201991] ata5: exception Emask 0x10 SAct 0x0 SErr 0x40d0000 action 0xe
frozen
[ 212.201997] ata5: irq_stat 0x00400040, connection status changed
[ 212.202003] ata5: SError: { PHYRdyChg CommWake 10B8B DevExch }
[ 212.202015] ata5: hard resetting link
[ 217.966628] ata5: link is slow to respond, please be patient (ready=0)
[ 222.226432] ata5: COMRESET failed (errno=-16)
[ 222.226442] ata5: hard resetting link
[ 227.990008] ata5: link is slow to respond, please be patient (ready=0)
[ 232.253800] ata5: COMRESET failed (errno=-16)
[ 232.253809] ata5: hard resetting link
[ 238.033490] ata5: link is slow to respond, please be patient (ready=0)
and never works.
So now when I restart with this drive connected the boot process freezes
(after selecting kernel in grub). now with the upstream kernel even with
this defective drive disconnected, the boot failed and I didn't see any
text after grub so no idea what is wrong there.
I don't see how boot should depend on externally connected drives in any
manner if they are not included in fstab or grub.
** Tags removed: kernel-request-3.2.0-20.32 needs-upstream-testing
** Tags added: kernel-unable-to-test-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964810
Title:
boot delay or failure when external drives are connected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/964810/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
