Bug#417172: marked as done (linux-image-2.6.18-4-686: failure to mount root fs if usb drive plugged in (-486 not affected, tho))
Your message dated Sun, 1 Apr 2007 21:00:39 +0200
with message-id <20070401190039.GL16041@baikonur.stro.at>
and subject line Bug#417172: linux-image-2.6.18-4-686: failure to mount root fs if usb drive plugged in (-486 not affected, tho)
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-12
Severity: important
If a usb drive is plugged in and operational during boot of the -686 kernel I get a failure to
mount root filesystem. The usb drive becomes /dev/sda and the 3ware raid becomes /dev/sdb.
Oddly enough, the -486 kernel does not have this problem. The 3ware module being used is
"3w_xxxx" and the card is a 3ware 8006-2LP two channel sata.
I tried configuring initramfs.conf to use MODULES=dep, then purged and reinstalled
linux-image-2.6.18-4.686, but the behavior is still the same.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.18-4-686 depends on:
ii coreutils 5.97-5.3 The GNU core utilities
ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii initramfs-tools [linux-initra 0.85f tools for generating an initramfs
ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.18-4-686 recommends:
ii libc6-i686 2.3.6.ds1-13 GNU C Library: Shared libraries [i
-- debconf information:
linux-image-2.6.18-4-686/preinst/failed-to-move-modules-2.6.18-4-686:
linux-image-2.6.18-4-686/preinst/lilo-initrd-2.6.18-4-686: true
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.18-4-686/preinst/elilo-initrd-2.6.18-4-686: true
linux-image-2.6.18-4-686/preinst/overwriting-modules-2.6.18-4-686: true
linux-image-2.6.18-4-686/prerm/removing-running-kernel-2.6.18-4-686: true
linux-image-2.6.18-4-686/prerm/would-invalidate-boot-loader-2.6.18-4-686: true
linux-image-2.6.18-4-686/postinst/bootloader-test-error-2.6.18-4-686:
linux-image-2.6.18-4-686/preinst/abort-overwrite-2.6.18-4-686:
linux-image-2.6.18-4-686/postinst/old-system-map-link-2.6.18-4-686: true
linux-image-2.6.18-4-686/postinst/depmod-error-2.6.18-4-686: false
linux-image-2.6.18-4-686/preinst/abort-install-2.6.18-4-686:
linux-image-2.6.18-4-686/preinst/lilo-has-ramdisk:
linux-image-2.6.18-4-686/postinst/bootloader-error-2.6.18-4-686:
linux-image-2.6.18-4-686/postinst/depmod-error-initrd-2.6.18-4-686: false
linux-image-2.6.18-4-686/postinst/old-initrd-link-2.6.18-4-686: true
linux-image-2.6.18-4-686/preinst/bootloader-initrd-2.6.18-4-686: true
linux-image-2.6.18-4-686/preinst/already-running-this-2.6.18-4-686:
linux-image-2.6.18-4-686/preinst/initrd-2.6.18-4-686:
linux-image-2.6.18-4-686/postinst/create-kimage-link-2.6.18-4-686: true
linux-image-2.6.18-4-686/postinst/old-dir-initrd-link-2.6.18-4-686: true
linux-image-2.6.18-4-686/postinst/kimage-is-a-directory:
--- End Message ---
--- Begin Message ---
On Sun, Apr 01, 2007 at 02:32:52PM -0400, noahdain@gmail.com wrote:
>
> If a usb drive is plugged in and operational during boot of the -686
> kernel I get a failure to mount root filesystem. The usb drive
> becomes /dev/sda and the 3ware raid becomes /dev/sdb. Oddly enough,
> the -486 kernel does not have this problem. The 3ware module being
> used is "3w_xxxx" and the card is a 3ware 8006-2LP two channel sata.
> I tried configuring initramfs.conf to use MODULES=dep, then purged and
> reinstalled linux-image-2.6.18-4.686, but the behavior is still the
> same.
the kernel never guarantees device ordering.
that is an userspace policy.
use uuid if you want to be on the safe side:
http://michael-prokop.at/blog/2006/08/11/stable-root-device-aka-uuid/
closing
--
maks
--- End Message ---
Reply to: