Not sure how grub handles it, but with LILO.... boot=/dev/md1 raid-extra-boot="/dev/sda,/dev/sdb" These two options will do what you need. Very strange.. Linux RAID auto-detect should automatically the partitions up from each device, so every time you reboot they become unsynced/not started? Justin. On Fri, 14 Jul 2006, Michael Menge wrote:

Justin Piszcz wrote:

...

What does cat /proc/mdstat say?

While in /bin/sh

Personalities : [raid1] md0 : active raid1 hda1[0] hdc1[1] 2104384 blocks [2/2] [UU]

unused devices: <none> ----------------------------

Afterwards

------------------------------------

Personalities : [raid1] md2 : active raid1 hda3[0] hdc3[1] 137002240 blocks [2/2] [UU]

md0 : active raid1 hda1[0] hdc1[1] 2104384 blocks [2/2] [UU]

md1 : active raid1 hda2[0] hdc2[1] 20972736 blocks [2/2] [UU]

unused devices: <none>

...

And also df -h.

----------------------

df -h Filesystem Size Used Avail Use% Mounted on /dev/md1 20G 2.9G 18G 15% / udev 112M 200K 112M 1% /dev

---------------------

...

Also /dev/md0 -> boot /dev/md1 -> swap /dev/md2 -> root

Is the recommended config.

yast was able to install the other config an it did start, but after cloning the system it did not start. So Yast did something during installation so that the deviecs for /dev/md1 are found during boottime but i dont know what.

...

On Fri, 14 Jul 2006, Michael Menge wrote:

...

Hi,

I have clonend a System with tar and sfdisk and now i have Problems Booting the System. The Rootfs is on /dev/md1, Swap on /dev/md0

The last lines I see are the following

md: md1 stopped mdadm: no devices found for /dev/md1 Attempting manual resume md: md0 still in use md: md0 still in use mdadm: fail to stop array /dev/md0: Device or resource busy md: md1 stopped mdadm: no devices found for /dev/md1 md: md2 stopped mdadm: no devices found for /dev/md2 Waiting for device /dev/md1 to appear: ok rootfs: major=9 minor=1 devn=2305 /dev/md1: Unknown volume type Invalid root filesystem -- exiting to /bin/sh $

If i start /dev/md1 with mdadm -Ac partitions -m 1 /dev/md1 and exit the /bin/sh the bootingproces is continued, but this hase to be done every time i reboot.

I dont understand why the devieces for /dev/md1 are not found but the devices for /dev/md0 and why they are found on the original system.

--------------------------- /sbin/fdisk -l Disk /dev/md1 doesn't contain a valid partition table Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md2 doesn't contain a valid partition table Disk /dev/hda: 163.9 GB, 163928604672 bytes 255 heads, 63 sectors/track, 19929 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 262 2104483+ fd Linux raid autodetect /dev/hda2 * 263 2873 20972857+ fd Linux raid autodetect /dev/hda3 2874 19929 137002320 fd Linux raid autodetect Disk /dev/hdc: 163.9 GB, 163928604672 bytes 255 heads, 63 sectors/track, 19929 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 1 262 2104483+ fd Linux raid autodetect /dev/hdc2 * 263 2873 20972857+ fd Linux raid autodetect /dev/hdc3 2874 19929 137002320 fd Linux raid autodetect Disk /dev/md1: 21.4 GB, 21476081664 bytes 2 heads, 4 sectors/track, 5243184 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md0: 2154 MB, 2154889216 bytes 2 heads, 4 sectors/track, 526096 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md2: 140.2 GB, 140290293760 bytes 2 heads, 4 sectors/track, 34250560 cylinders Units = cylinders of 8 * 512 = 4096 bytes

--------------------------------------------- /proc/mounts

rootfs / rootfs rw 0 0 udev /dev tmpfs rw 0 0 /dev/md1 / xfs rw,sunit=8,swidth=16 0 0 proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 debugfs /sys/kernel/debug debugfs rw 0 0 devpts /dev/pts devpts rw 0 0 securityfs /sys/kernel/security securityfs rw 0 0 ------------------------------------------------- /bin/ls -la /boot

total 21692 drwxr-xr-x 3 root root 4096 Jul 14 09:31 . drwxr-xr-x 22 root root 4096 Jul 14 09:32 .. -rw-r--r-- 1 root root 676109 May 3 12:27 System.map-2.6.16.13-4-default -rw-r--r-- 1 root root 682064 May 3 12:19 System.map-2.6.16.13-4-xen -rw------- 1 root root 512 May 15 15:27 backup_mbr lrwxrwxrwx 1 root root 1 Jul 14 09:13 boot -> . -rw-r--r-- 1 root root 68246 May 3 12:41 config-2.6.16.13-4-default -rw-r--r-- 1 root root 61528 May 3 12:24 config-2.6.16.13-4-xen drwxr-xr-x 2 root root 4096 Jul 14 09:27 grub lrwxrwxrwx 1 root root 26 Jul 14 09:31 initrd -> initrd-2.6.16.13-4-default -rw-r--r-- 1 root root 2377887 Jul 14 09:31 initrd-2.6.16.13-4-default -rw-r--r-- 1 root root 2469652 Jul 14 09:31 initrd-2.6.16.13-4-xen lrwxrwxrwx 1 root root 22 Jul 14 09:13 initrd-xen -> initrd-2.6.16.13-4-xen -rw-r--r-- 1 root root 98320 May 3 12:44 symsets-2.6.16.13-4-default.tar.gz -rw-r--r-- 1 root root 101074 May 3 12:25 symsets-2.6.16.13-4-xen.tar.gz -rw-r--r-- 1 root root 334861 May 3 12:44 symtypes-2.6.16.13-4-default.gz -rw-r--r-- 1 root root 328326 May 3 12:25 symtypes-2.6.16.13-4-xen.gz -rw-r--r-- 1 root root 92204 May 3 12:43 symvers-2.6.16.13-4-default.gz -rw-r--r-- 1 root root 90194 May 3 12:25 symvers-2.6.16.13-4-xen.gz -rwxr-xr-x 1 root root 1498867 May 3 12:40 vmlinux-2.6.16.13-4-default.gz -rwxr-xr-x 1 root root 1684324 May 3 12:24 vmlinux-2.6.16.13-4-xen.gz lrwxrwxrwx 1 root root 27 Jul 14 09:13 vmlinuz -> vmlinuz-2.6.16.13-4-default -rw-r--r-- 1 root root 1237785 May 3 12:27 vmlinuz-2.6.16.13-4-default -rw-r--r-- 1 root root 1399962 May 3 12:19 vmlinuz-2.6.16.13-4-xen lrwxrwxrwx 1 root root 23 Jul 14 09:13 vmlinuz-xen -> vmlinuz-2.6.16.13-4-xen -rw-r--r-- 1 root root 219535 May 2 12:15 xen-3.0.2_09656-4.gz lrwxrwxrwx 1 root root 20 Jul 14 09:13 xen-3.0.gz -> xen-3.0.2_09656-4.gz lrwxrwxrwx 1 root root 20 Jul 14 09:13 xen-3.gz -> xen-3.0.2_09656-4.gz -rw-r--r-- 1 root root 267418 May 2 12:12 xen-dbg-3.0.2_09656-4.gz lrwxrwxrwx 1 root root 24 Jul 14 09:13 xen-dbg-3.0.gz -> xen-dbg-3.0.2_09656-4.gz lrwxrwxrwx 1 root root 24 Jul 14 09:13 xen-dbg-3.gz -> xen-dbg-3.0.2_09656-4.gz lrwxrwxrwx 1 root root 24 Jul 14 09:13 xen-dbg.gz -> xen-dbg-3.0.2_09656-4.gz -rw-r--r-- 1 root root 241057 May 2 12:14 xen-pae-3.0.2_09656-4.gz lrwxrwxrwx 1 root root 24 Jul 14 09:13 xen-pae-3.0.gz -> xen-pae-3.0.2_09656-4.gz lrwxrwxrwx 1 root root 24 Jul 14 09:13 xen-pae-3.gz -> xen-pae-3.0.2_09656-4.gz lrwxrwxrwx 1 root root 24 Jul 14 09:13 xen-pae.gz -> xen-pae-3.0.2_09656-4.gz lrwxrwxrwx 1 root root 22 Jul 14 09:13 xen-syms -> xen-syms-3.0.2_09656-4 -rw-r--r-- 1 root root 2607969 May 2 12:15 xen-syms-3.0.2_09656-4 lrwxrwxrwx 1 root root 26 Jul 14 09:13 xen-syms-dbg -> xen-syms-dbg-3.0.2_09656-4 -rw-r--r-- 1 root root 2847879 May 2 12:12 xen-syms-dbg-3.0.2_09656-4 lrwxrwxrwx 1 root root 26 Jul 14 09:13 xen-syms-pae -> xen-syms-pae-3.0.2_09656-4 -rw-r--r-- 1 root root 2762204 May 2 12:14 xen-syms-pae-3.0.2_09656-4 lrwxrwxrwx 1 root root 20 Jul 14 09:13 xen.gz -> xen-3.0.2_09656-4.gz ------------------------------------------------------------------------- /boot/grub/menu.lst

color white/blue black/light-gray default 1 timeout 8 title SUSE Linux 10.1 kernel (hd0,1)/boot/vmlinuz root=/dev/md1 resume=/dev/md0 splash=silent showopts initrd (hd0,1)/boot/initrd title XEN kernel (hd0,1)/boot/xen.gz module (hd0,1)/boot/vmlinuz-xen root=/dev/md1 resume=/dev/md0 splash=silent showopts module (hd0,1)/boot/initrd-xen title Diskette chainloader (fd0)+1 title Failsafe -- SUSE Linux 10.1 kernel (hd0,1)/boot/vmlinuz root=/dev/md1 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3 initrd (hd0,1)/boot/initrd

-------------------------------------------------------------------------------

/boot/grub/device.map

(fd0) /dev/fd0 (hd1) /dev/hdc (hd0) /dev/hda

-------------------------------------------------------------------------------

/etc/grub.conf

root (hd0,1) install --stage2=/boot/grub/stage2 /boot/grub/stage1 d (hd0) /boot/grub/stage2 0x8000 (hd0,1)/boot/grub/menu.lst quit

--

-------------------------------------------------------------------------------- M.Menge Tel.: (49) 7071/29-70316 Universitaet Tuebingen Fax.: (49) 7071/29-5912 Zentrum fuer Datenverarbeitung mail: menge@zdv.uni-tuebingen.de Waechterstrasse 76 72074 Tuebingen

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-- -------------------------------------------------------------------------------- M.Menge Tel.: (49) 7071/29-70316 Universitaet Tuebingen Fax.: (49) 7071/29-5912 Zentrum fuer Datenverarbeitung mail: menge@zdv.uni-tuebingen.de Waechterstrasse 76 72074 Tuebingen

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

I found the problem the /etc/mdadm.conf had the wrong UUIDs echo "DEVICES partitions" > /etc/mdadm.conf mdadm -Ebsc partitions >> /etc/mdadm.conf mkinitrd solved the problem Quoting Joachim Schrod :

Michael Menge wrote:

...

I have clonend a System with tar and sfdisk and now i have Problems Booting the System. The Rootfs is on /dev/md1, Swap on /dev/md0 [...] I dont understand why the devieces for /dev/md1 are not found but the devices for /dev/md0 and why they are found on the original system.

For safety you might want to remove the resume=/dev/md0 boot parameter from grub/menu.lst while you're debugging the problem. The "attempting manual resume" message looks suspicious to me, that might invoke a relict from your cloning. (Resuming from a mirrored swap disk didn't work for me anyhow in 10.0; I didn't try it in 10.1 yet.)

Furthermore, you might want to check with mdadm --detail /dev/md1 and mdadm --examine on the disks that are part of that meta-device that the UUIDs of the md and the disks are the same and that they match the entry in /etc/mdadm.conf.

I don't know exactly how the bootup code (i.e., madam --assemble --scan) determines which partition belongs into the which md; but I read that the UUIDs have something to do with it. At least they are recorded in the md superblock, and mdadm.conf lists them as the only information -- so what else is used for scanning and assembling? (That might be wrong, though.)

Best, Joachim

-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-- -------------------------------------------------------------------------------- M.Menge Tel.: (49) 7071/29-70316 Universitaet Tuebingen Fax.: (49) 7071/29-5912 Zentrum fuer Datenverarbeitung mail: menge@zdv.uni-tuebingen.de Waechterstrasse 76 72074 Tuebingen