Bug#490959: marked as done (linux-image-2.6.25-2-amd64: upgrade from 2.6.24 to 2.6.25 changes drive identities)
Your message dated Tue, 15 Jul 2008 17:52:30 +0200
with message-id <20080715155230.GF4183@baikonur.stro.at>
and subject line Re: Bug#490959: linux-image-2.6.25-2-amd64: upgrade from 2.6.24 to 2.6.25 changes drive identities
has caused the Debian Bug report #490959,
regarding linux-image-2.6.25-2-amd64: upgrade from 2.6.24 to 2.6.25 changes drive identities
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 owner@bugs.debian.org
immediately.)
--
490959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490959
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.25-2-amd64
Version: 2.6.25-6
Severity: important
When upgrading to 2.6.25, the linux kernel re-assigns drive letters with respect to how it is done in 2.6.24.
In my particular case, /dev/sdc is swapped with /dev/sdb. This will make a remote reboot unreliable and/or impossible, parameters
used by the boot loader and fstab must be updated and even then the system keeps complaining about special
devices which should be normal devices.
This also happened, in reverse order, when upgrading from 2.6.18 to above.
Nothing is changed in the BIOS. Booting into 2.6.24 says the root file system is on /dev/sdc, booting into 2.6.25
says the root file system is on /dev/sdb.
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.25-2-amd64 depends on:
ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92e tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
linux-image-2.6.25-2-amd64 recommends no packages.
-- debconf information:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.25-2-amd64/preinst/abort-overwrite-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/prerm/removing-running-kernel-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/postinst/old-initrd-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/postinst/create-kimage-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/failed-to-move-modules-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/preinst/abort-install-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/postinst/kimage-is-a-directory:
linux-image-2.6.25-2-amd64/postinst/depmod-error-2.6.25-2-amd64: false
linux-image-2.6.25-2-amd64/postinst/bootloader-test-error-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/postinst/old-system-map-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/prerm/would-invalidate-boot-loader-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/overwriting-modules-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/postinst/depmod-error-initrd-2.6.25-2-amd64: false
linux-image-2.6.25-2-amd64/postinst/old-dir-initrd-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/elilo-initrd-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/postinst/bootloader-error-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/preinst/lilo-initrd-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/lilo-has-ramdisk:
linux-image-2.6.25-2-amd64/preinst/initrd-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/preinst/bootloader-initrd-2.6.25-2-amd64: true
--- End Message ---
--- Begin Message ---
On Tue, Jul 15, 2008 at 05:22:15PM +0200, Rutger ter Borg wrote:
> Package: linux-image-2.6.25-2-amd64
> Version: 2.6.25-6
> Severity: important
>
>
> When upgrading to 2.6.25, the linux kernel re-assigns drive letters with respect to how it is done in 2.6.24.
> In my particular case, /dev/sdc is swapped with /dev/sdb. This will make a remote reboot unreliable and/or impossible, parameters
> used by the boot loader and fstab must be updated and even then the system keeps complaining about special
> devices which should be normal devices.
>
> This also happened, in reverse order, when upgrading from 2.6.18 to above.
>
> Nothing is changed in the BIOS. Booting into 2.6.24 says the root file system is on /dev/sdc, booting into 2.6.25
> says the root file system is on /dev/sdb.
right device names are userspace policy never guaranteed to stay stable.
use UUID to prevent that.
grub by default now uses UUID. just mv menu.lst and regenerate it with
update-grub.
sorry for the trouble, but known fact and errata of d-i.
best regards
--
maks
--- End Message ---
Reply to: