Bug#548290: marked as done (linux-image-2.6.30-2-686: 2.6.30 cannot find root file system)
Julien Cristau ha scritto il 28/09/09 23:54:
> On Mon, Sep 28, 2009 at 19:15:52 +0200, Jonathan Kaye wrote:
>
>
>>
>> Hi Vincent,I would be delighted, no overjoyed to give you all the information you
>> want. Please tell me what you need and I'll do my best to supply that
>> information.
>>
>> I did try to use the UUID in the grub root parameter as well as in the
>> fstab file but to no avail.<br>
>> Regards,
> First thing to do is don't use the -quiet email address for the bug
> report, as that won't reach anyone. Next, send plain text mail, not
> html.
> Finally, describe as precisely as you can your setup, what you tried and
> what the result was for each attempt.
>
> Cheers,
> Julien
>
>
Sorry about that. Ok here goes:
1. When linux-image-2.6.30 reached Squeeze I attempted to upgrade the
kernel from 2.6.26 to 2.6.30 exactly as I have been doing for years. I
executed as root:
aptitude install linux-image-2.6.30-1-686
As usual, this created 2 new entries in the menu.lst file and I rebooted
into the "normal" one as I have always done without problems for years..
2. Note that my root parameter in the menu.lst file has always been this:
/boot/vmlinuz-2.6.26-1-686 root=/dev/hda1 ro
aside from changes to the actual kernel version.
3. When booting into the new 2.6.30 kernel the process never got beyond
trying to find the root file system. A script called "Begin" reported
"looking for root file system" or words to that effect. After a few
minutes, it gives up and drops me into the busybox shell.
4. I have tried changing the root= parameter to root=/dev/sda1 and to
the UUID number but the results are always the same. I can never get
beyond the "looking for root file system problem.
5. I posted the hard disk specs as listed by lshw in my original post.
The system settings are also included there. If you cannot access these
I can repost them or send them to you personally.
6. I realise that this is sure not a 2.6.30 bug. I know this because, as
I mentioned previously, I was able to boot from a live Sidux CD that
uses the 2.6.30 kernel and it mounted my hard drive as /dev/sda1 without
any problems. Obviously it was not using that disk as the root file
system but it could find the disk at least.
The bug is related to 2.6.30 in that its symptoms only appear when I try
to boot from that kernel. Every other kernel before it has worked
without any problems. I am currently using the 2.6.26 kernel which has
always found the hard disk and still does. I therefore rule out hardware
malfunction as the source of the problem.
This is all the information I can think of. If you need to know anything
else, please let me know.
Regards,
Jonathan
Reply to: