Bug#548290: marked as done (linux-image-2.6.30-2-686: 2.6.30 cannot find root file system)
Your message dated Mon, 4 Jan 2010 00:23:29 +0100 with message-id 20100103232329.gc4...@stro.at and subject line Re: missing ROOT uuid link has caused the Debian Bug report #548290, regarding linux-image-2.6.30-2-686: 2.6.30 cannot find root file system to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 548290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Subject: linux-image-2.6.30-2-686: 2.6.30 cannot find root file system Package: linux-image-2.6.30-2-686 Severity: critical Justification: breaks the whole system *** Please type your report below this line *** When I try to boot with linux-image-2.6.30-1-686 the boot up hangs while trying to find the root file system. It freezes for a few minutes and then drops me into the busybox shell. I have tried changing the root parameter in grub's menu.lst from /dev/hda1 (this is the working setting, up to and including 2.6.26) to /dev/sda1 or using the UUID setting. I also try this in the fstab file. The results are always the same. It cannot find the root file system. I don't think this is strictly a 2.6.30 problem because I tried booting with a Sidux live CD (2009-2) which also uses 2.6.30 and the system booted with no problems. It identified my hard disk as /dev/sda1, but as I've said, doing that on the Debian system doesn't help. The specs of my hard disk taken from lshw are as follows: *-disk description: ATA Disk product: ST3200822A vendor: Seagate physical id: 0 bus info: i...@0.0 logical name: /dev/hda version: 3.01 serial: 3LJ3JP6Q size: 186GiB (200GB) capabilities: ata dma lba iordy smart security pm partitioned partitioned:dos configuration: mode=udma5 signature=dc40dc40 smart=on *-volume:0 description: EXT3 volume vendor: Linux physical id: 1 bus info: i...@0.0,1 logical name: /dev/hda1 logical name: / version: 1.0 serial: 27569688-0e33-41be-90f9-f92103c9bbe4 size: 183GiB capacity: 183GiB capabilities: primary bootable journaled large_files recover ext3 ext2 initialized configuration: created=2007-01-11 22:32:41 filesystem=ext3 modified=2009-09-12 07:56:21 mount.fstype=ext3 mount.options=rw,errors=remount-ro,data=ordered mounted=2009-09-12 07:56:21 state=mounted -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.30-2-686 depends on: ii debconf [debconf-2.0]1.5.27 Debian configuration management sy ii initramfs-tools [linux-initr 0.93.4 tools for generating an initramfs ii module-init-tools3.3-pre11-1 tools for managing Linux kernel mo Versions of packages
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 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548290: marked as done (linux-image-2.6.30-2-686: 2.6.30 cannot find root file system)
I have tried changing the root parameter in grub's menu.lst from /dev/hda1 (this is the working setting, up to and including 2.6.26) to /dev/sda1 or using the UUID setting. ^ stable device names do not exist and this is not a kernel bug, but userspace policy. UUID should be stable, no ? So, to close this bug, you must think the bug report is wrong (describing wrong fact, or bad use of UUID, or ...). More input from the submitter seems to be required. Regards, Vincent -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548290: marked as done (linux-image-2.6.30-2-686: 2.6.30 cannot find root file system)
On Mon, Sep 28, 2009 at 19:15:52 +0200, Jonathan Kaye wrote: /pre /blockquote Hi Vincent,br 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.br br 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,br Jonathanbr br /body /html 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 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548290: marked as done (linux-image-2.6.30-2-686: 2.6.30 cannot find root file system)
Your message dated Fri, 25 Sep 2009 16:52:25 +0200 with message-id 20090925145224.gb28...@baikonur.stro.at and subject line Re: linux-image-2.6.30-2-686: 2.6.30 cannot find root file system has caused the Debian Bug report #548290, regarding linux-image-2.6.30-2-686: 2.6.30 cannot find root file system to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 548290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Subject: linux-image-2.6.30-2-686: 2.6.30 cannot find root file system Package: linux-image-2.6.30-2-686 Severity: critical Justification: breaks the whole system *** Please type your report below this line *** When I try to boot with linux-image-2.6.30-1-686 the boot up hangs while trying to find the root file system. It freezes for a few minutes and then drops me into the busybox shell. I have tried changing the root parameter in grub's menu.lst from /dev/hda1 (this is the working setting, up to and including 2.6.26) to /dev/sda1 or using the UUID setting. I also try this in the fstab file. The results are always the same. It cannot find the root file system. I don't think this is strictly a 2.6.30 problem because I tried booting with a Sidux live CD (2009-2) which also uses 2.6.30 and the system booted with no problems. It identified my hard disk as /dev/sda1, but as I've said, doing that on the Debian system doesn't help. The specs of my hard disk taken from lshw are as follows: *-disk description: ATA Disk product: ST3200822A vendor: Seagate physical id: 0 bus info: i...@0.0 logical name: /dev/hda version: 3.01 serial: 3LJ3JP6Q size: 186GiB (200GB) capabilities: ata dma lba iordy smart security pm partitioned partitioned:dos configuration: mode=udma5 signature=dc40dc40 smart=on *-volume:0 description: EXT3 volume vendor: Linux physical id: 1 bus info: i...@0.0,1 logical name: /dev/hda1 logical name: / version: 1.0 serial: 27569688-0e33-41be-90f9-f92103c9bbe4 size: 183GiB capacity: 183GiB capabilities: primary bootable journaled large_files recover ext3 ext2 initialized configuration: created=2007-01-11 22:32:41 filesystem=ext3 modified=2009-09-12 07:56:21 mount.fstype=ext3 mount.options=rw,errors=remount-ro,data=ordered mounted=2009-09-12 07:56:21 state=mounted -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.30-2-686 depends on: ii debconf [debconf-2.0]1.5.27 Debian configuration management sy ii initramfs-tools [linux-initr 0.93.4 tools for generating an initramfs ii module-init-tools3.3-pre11-1 tools for managing Linux
