Re: device name problem after update
Paul E Condon wrote the following on 10.03.2010 19:17 -- snip -- 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? There is a libata transition coming down the road. But AFAIK that transition has been only prepared in experimental until now and not been uploaded to unstable. Which issue are you aware of? -- bye Thilo 4096R/0xC70B1A8F 721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hnbfhc$gq...@dough.gmane.org
Re: device name problem after update
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 pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100310181723.ga4...@big.lan.gnu
Re: device name problem after update
On Wed, Mar 10, 2010 at 8:17 PM, Paul E Condon pecon...@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 pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100310181723.ga4...@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 uuid297ae396-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) uuid297ae396-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+ uuid297ae396-2033-42da-ad3b-640b5f3f01d5 kernel
Re: device name problem after update
On 20100310_204803, Angelin Lalev wrote: On Wed, Mar 10, 2010 at 8:17 PM, Paul E Condon pecon...@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 pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100310181723.ga4...@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 uuid297ae396-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) uuid297ae396-2033-42da-ad3b-640b5f3f01d5 kernel /boot/vmlinuz-2.6.28-11-server root=UUID=297ae396-2033-42da-ad3b-640b5f3f01d5 ro single
Re: device name problem after update
On Wed, Mar 10, 2010 at 9:24 PM, Paul E Condon pecon...@mesanetworks.net wrote: On 20100310_204803, Angelin Lalev wrote: On Wed, Mar 10, 2010 at 8:17 PM, Paul E Condon pecon...@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 pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100310181723.ga4...@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
Re: device name problem after update
On Wed, 10 Mar 2010 15:25:40 -0500 (EST), Angelin Lalev wrote: Well, It probably is something I have done. The installation is at least one year old (so I had the time to screw something up) and I'm not very familiar with linux (BSD fan). I'll think I'll try to put uuids in menu.lst... Good luck. But please trim your posts. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1877566475.18203011268253964942.javamail.r...@md01.wow.synacor.com
device name problem after update
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? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/532b03711003091257g31d63267k3d5be7bbf11ea...@mail.gmail.com
Re: device name problem after update
On 2010-03-09 14:57, 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? That's udev. Does your fstab use /dev/hdX, labels or uuids? -- Ron Johnson, Jr. Jefferson LA USA If God had wanted man to play soccer, he wouldn't have given us arms. Mike Ditka -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b96be06.90...@cox.net
Re: device name problem after update
Ron Johnson wrote: On 2010-03-09 14:57, 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? That's udev. Does your fstab use /dev/hdX, labels or uuids? Whatever it currently uses, you *should* use labels in fstab; and when not possible (fancy fs, whatever), UUIDs. To reference the block device anywhere else, use /dev/disk/by-label/... When not possible or not such a good idea (removable drives,..), there are also subdirectories to reference by disk ID (generated with the model/serial numbers,..), path (physical) or UUID. If you don't want to use these paths, you can generate your own symlinks via custom udev rules. I would *not* recommend renaming the drives with fixed kernel names ([sh]d[a-z]) in order to reorder them. I had some issues trying to do that in the past, and in the end I realized it would only add useless confusion. So, it's not a bug, you should just not rely on these names. -thib -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b96da56.20...@stammed.net