Re: device name problem after update
On 20100310_204803, Angelin Lalev wrote:
> On Wed, Mar 10, 2010 at 8:17 PM, Paul E Condon
> <pecondon@mesanetworks.net> wrote:
> > On 20100309_225735, Angelin Lalev wrote:
> >> After almost each update of my debian lenny kernel I have my IDE disk
> >> name changed. Once it's hda1 then is hdc1 and keeps flip-flopping. Is
> >> it a known problem?
> >>
> >
> > I'm aware of an issue with naming devices in Squeeze, but you say
> > Lenny. Are you sure you are using Lenny, i.e. stable, as opposed to
> > Squeeze, i.e. testing?
> >
> > --
> > Paul E Condon
> > pecondon@mesanetworks.net
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> > Archive: [🔎] 20100310181723.GA4159@big.lan.gnu">http://lists.debian.org/[🔎] 20100310181723.GA4159@big.lan.gnu
> >
> >
>
> Thanks for the information. Now I know what's doing it and how to fix
> it. But I will send some more information just in case it's a bug. I
> use lenny and never touched the fstab of that machine manually. But I
> run xen which loads it's own "xenified" kernel.
>
> My /boot/grub/menu.lst (I run debian and ubuntu virtual machines on
> their own real partitions)
> I use the first row always (currently Xen 3.2-1-i386)
> ===========================================
>
> server:~# cat /boot/grub/menu.lst | grep -v \# | grep -v ^$
> default 0
> timeout 30
> color cyan/blue white/blue
> title Xen 3.2-1-i386 / Debian GNU/Linux, kernel 2.6.26-2-xen-686
> root (hd0,0)
> kernel /boot/xen-3.2-1-i386.gz
> module /boot/vmlinuz-2.6.26-2-xen-686 root=/dev/hdc1 ro console=tty0
> module /boot/initrd.img-2.6.26-2-xen-686
> title Xen 3.2-1-i386 / Debian GNU/Linux, kernel 2.6.26-1-xen-686
> root (hd0,0)
> kernel /boot/xen-3.2-1-i386.gz
> module /boot/vmlinuz-2.6.26-1-xen-686 root=/dev/hdc1 ro console=tty0
> module /boot/initrd.img-2.6.26-1-xen-686
> title Debian GNU/Linux, kernel 2.6.28.9-al1
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.28.9-al1 root=/dev/hdc1 ro quiet
> initrd /boot/initrd.img-2.6.28.9-al1
> title Debian GNU/Linux, kernel 2.6.28.9-al1 (single-user mode)
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.28.9-al1 root=/dev/hdc1 ro single
> initrd /boot/initrd.img-2.6.28.9-al1
> title Debian GNU/Linux, kernel 2.6.28-11-server
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.28-11-server root=/dev/hdc1 ro quiet
> initrd /boot/initrd.img-2.6.28-11-server
> title Debian GNU/Linux, kernel 2.6.28-11-server (single-user mode)
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.28-11-server root=/dev/hdc1 ro single
> initrd /boot/initrd.img-2.6.28-11-server
> title Debian GNU/Linux, kernel 2.6.26-2-xen-686
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.26-2-xen-686 root=/dev/hdc1 ro quiet
> initrd /boot/initrd.img-2.6.26-2-xen-686
> title Debian GNU/Linux, kernel 2.6.26-2-xen-686 (single-user mode)
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.26-2-xen-686 root=/dev/hdc1 ro single
> initrd /boot/initrd.img-2.6.26-2-xen-686
> title Debian GNU/Linux, kernel 2.6.26-2-686
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.26-2-686 root=/dev/hdc1 ro quiet
> initrd /boot/initrd.img-2.6.26-2-686
> title Debian GNU/Linux, kernel 2.6.26-2-686 (single-user mode)
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.26-2-686 root=/dev/hdc1 ro single
> initrd /boot/initrd.img-2.6.26-2-686
> title Debian GNU/Linux, kernel 2.6.26-1-xen-686
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.26-1-xen-686 root=/dev/hdc1 ro quiet
> initrd /boot/initrd.img-2.6.26-1-xen-686
> title Debian GNU/Linux, kernel 2.6.26-1-xen-686 (single-user mode)
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.26-1-xen-686 root=/dev/hdc1 ro single
> initrd /boot/initrd.img-2.6.26-1-xen-686
> title Debian GNU/Linux, kernel 2.6.26-1-686
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/hdc1 ro quiet
> initrd /boot/initrd.img-2.6.26-1-686
> title Debian GNU/Linux, kernel 2.6.26-1-686 (single-user mode)
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/hdc1 ro single
> initrd /boot/initrd.img-2.6.26-1-686
> title Other operating systems
> title Ubuntu 9.04, kernel 2.6.28-11-server
> uuid 297ae396-2033-42da-ad3b-640b5f3f01d5
> kernel /boot/vmlinuz-2.6.28-11-server
> root=UUID=297ae396-2033-42da-ad3b-640b5f3f01d5 ro quiet splash
> initrd /boot/initrd.img-2.6.28-11-server
> quiet
> title Ubuntu 9.04, kernel 2.6.28-11-server (recovery mode)
> uuid 297ae396-2033-42da-ad3b-640b5f3f01d5
> kernel /boot/vmlinuz-2.6.28-11-server
> root=UUID=297ae396-2033-42da-ad3b-640b5f3f01d5 ro single
> initrd /boot/initrd.img-2.6.28-11-server
> title Ubuntu 9.04, memtest86+
> uuid 297ae396-2033-42da-ad3b-640b5f3f01d5
> kernel /boot/memtest86+.bin
> quiet
>
> My current fstab (I never changed it manually)
> ==================================
>
> # /etc/fstab: static file system information.
> #
> # <file system> <mount point> <type> <options> <dump> <pass>
> proc /proc proc defaults 0 0
> /dev/hda1 / ext3 errors=remount-ro 0 1
> /dev/hda5 none swap sw 0 0
> #/dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
> #/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
>
> To make the things work, after the last flip-flop of the names, I must
> just update my menu.lst and just replace every instance of hdc1 with
> hda1. And it will work probably up to the next time I update the
> kernel.
>
> I will try with UUIDs though, if they are supported in lenny.
>
Thanks, Angelin
I'm curious about your problem. It appears that you have a
'work-around', but not a solution. Like I said earlier, I'm aware of
there being a naming problem in squeeze, but I'm surprised and
somewhat alarmed to here evidence of it having leaked into lenny. Are
you using any backports? The kernel version numbers that you are
running seem to be appropriate for lenny, but can you also tell me the
contents of /etc/debian-version ? Lenny is supposed to be "stable" and
should not suffer from undocumented "upgrades", which this appears to
be.
I am having a number of issues in squeeze, and was on the verge of
reverting a computer from squeeze to lenny when I read you post. Now
I wonder if that would be any help for my problems.
--
Paul E Condon
pecondon@mesanetworks.net
Reply to: