At bootup I end up in busybox and I see the following message on the top of the screen "Gave up waiting for root device"
Actually I think that my hard drive "falls asleep" just after leaving grub. When I'm in the busybox I need to unplug my hard drive (serial ata) and to plug it again so that I can hear that it's restarting. After doing that I type exit in the busybox and the boot process restarts normally.
Dmesg shows me that:
[ 9.672007] ata3: link is slow to respond, please be patient (ready=0)
[ 14.320007] ata3: COMRESET failed (errno=-16)
[ 19.680006] ata3: link is slow to respond, please be patient (ready=0)
[ 24.328007] ata3: COMRESET failed (errno=-16)
[ 29.688007] ata3: link is slow to respond, please be patient (ready=0)
[ 59.092004] ata3: COMRESET failed (errno=-16)
[ 59.092004] ata3: limiting SATA link speed to 1.5 Gbps
[ 59.688009] ata3: SATA link down (SStatus 0 SControl 310)
[ 60.164017] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 60.196367] ata4.00: HPA detected: current 160834367, native 160836480
[ 60.196371] ata4.00: ATA-6: HDS722580VLSA80, V32OA6MA, max UDMA/100
[ 60.196373] ata4.00: 160834367 sectors, multi 16: LBA48
The COMRESET thing continues as far as I don't unplug and plug again my hard drive.
I'm not sure this bug concerns only Ubuntu because I tried recently other distributions with the same kernel and I get the same error (Debian and pmagic liveCD) So I think this bug is concerning the kernel 2.6.26 but I don't know how to report this bug upstream.
I also have to tell you that it's a SATA II hard drive (3gbps) on a (nforce 3) SATA I controller (1.5gbps). And it appears that the controller does not fully support the hard drive (or the SATA I retro-compatibility of the hard drive is malfunctioning I don't know) But with older kernel it did always work without any problem.
I'm running intrepid ibex up-to-date, kernel 2.6.26-5-generic
Please tell me if I should attach the entire dmesg or anything.
Thanks
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e . I have classified this bug as a bug in linux. /wiki.ubuntu. com/ReportingBu gs.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https:/
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https:/ /wiki.ubuntu. com/KernelTeamB ugPolicies Thanks in advance!