Hi Steffen again, alternatively, you could also use the udev symbolic block device names instead of LABEL=xxx mount points (works also with initramfstools):
[EMAIL PROTECTED]:~$ ls -l /dev/disk/by-label/ insgesamt 0 lrwxrwxrwx 1 root root 10 2007-12-01 23:24 boot -> ../../sda2 lrwxrwxrwx 1 root root 10 2007-12-01 23:23 home -> ../../sdb1 lrwxrwxrwx 1 root root 10 2007-12-01 23:23 root -> ../../sdb2 lrwxrwxrwx 1 root root 10 2007-12-01 23:23 swap -> ../../sdb4 lrwxrwxrwx 1 root root 10 2007-12-01 23:23 var -> ../../sdb3 So a kernel command line could be: 0:2/vmlinuz ro initrd=/initrd.img root=/dev/disk/by-label/root ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [EMAIL PROTECTED] > -----Original Message----- > From: Uwe Schindler [mailto:[EMAIL PROTECTED] > Sent: Friday, January 18, 2008 9:50 AM > To: [EMAIL PROTECTED]; debian-alpha@lists.debian.org > Subject: RE: Change the order of scsi Controller > > Hi Steffen, > > as Etch uses udev for managing hardware, why not use symbolic names for > your > partitions (based on the file system label)? This works even in initrd, if > you use initramfstools, it does not work with yaird! > > On my Alphastation I have the following kernel bootlines in aboot.conf: > > [EMAIL PROTECTED]:/boot$ cat etc/aboot.conf > # > # aboot default configurations > # > 0:2/vmlinuz ro initrd=/initrd.img root=LABEL=root > 1:2/vmlinuz.old ro initrd=/initrd.img.old root=LABEL=root > > And the following fstab: > [EMAIL PROTECTED]:~$ cat /etc/fstab > # /etc/fstab: static file system information. > # > # <file system> <mount point> <type> <options> <dump> <pass> > proc /proc proc defaults 0 0 > LABEL=root / ext3 defaults,errors=remount-ro 0 > 0 > LABEL=boot /boot ext2 defaults,noatime,nodiratime 0 > 0 > LABEL=var /var ext3 defaults 0 0 > LABEL=home /home ext3 defaults 0 0 > LABEL=swap none swap sw 0 0 > > The labels were assigned to all partitions e2label and for swap by mkswap. > That was it. Works stable and I can change my hardware configuration > whatever I like (because sometimes the order changes with every reboot > when > parallel searching for new devices is enabled). > > I use this style for all my machines (not only the alpha one). > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: [EMAIL PROTECTED] > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Friday, January 18, 2008 9:13 AM > > To: debian-alpha@lists.debian.org > > Subject: Change the order of scsi Controller > > > > Hello, > > > > I have 2 AlphaServer 4100 (Rawhide) running Debian/Etch and a Digital > Raid > > Array (RA3000) connected. > > > > I have installed debian on the Server with the RA3000 switched off > running > > the generic alphaserver kernel. > > > > Now everything is installed on /dev/sda: > > > > /dev/sda3 / ext3 defaults,errors=remount-ro > 0 > > 1 > > /dev/sda2 /boot ext2 defaults 0 2 > > /dev/sda4 none swap sw 0 0 > > > > /dev/sda is the first scsi- disk plugged into the local servers SCSI- > > Container. > > > > > > Now, if I switch on the raid array and boot the server, the module of > the > > scsi controller (QLogic qla1280) > > has the raid array connected seems to be loaded before the module of the > > controller (sym53c8xx) for local disks. > > > > Thats why my disks order is changed completely. > > > > The first disk in the raid controller becomes /dev/sda and the disks on > > the local controller will be added > > after the last disk in the raid array. > > > > My question is, if the reason for that is really the module- load order > > how can I change it easily? > > > > The scsi- modules are loaded via initrd. > > > > I already read this article: > > > > http://ubuntuforums.org/showthread.php?t=219600 > > > > but my > > > > /etc/initramfs-tools/module > > > > file is empty, and I don't know what modules are loaded with initrd. > > > > Any suggestions? > > > > PS: > > Compiling a new kernel is no optiion for now. > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > > [EMAIL PROTECTED] > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
