greetz this what ive been doing with grub + mdadm
-install the system with the normal yast installation, creating the raid partitions etc -after it has finnished installing, i reboot with knoppix - in knoppix, i mount the first partition (/boot) to /mnt and cd /mnt - there i reconfigure with the grub, entering root (hd0,0) setup (hd0) root (hd1,0) setup (hd1) -after that i unmount the /mnt - i reboot the system and suse would boot fine after that without probs the problem you are most propably facing is that the device names have changed and that way mdadm and grub are not recongizing the partitions to boot, so start with that, boot with knoppix and see as what devices the drives are visible as, then make sure that mdadm arrays and grub match, if not correct. good luck On 1/22/07, S Glasoe <[EMAIL PROTECTED]> wrote:
On Sunday 21 January 2007 17:02, Bo Jacobsen wrote: > I have done a: > > grub root (hd0,1) > >setup (hd0) > > on the harddisk so it should be OK. Besides the 2.19.1 kernel on the > system boots without any problems. > Both kernels are defined in /boot/grub/menu.lst: > .. > title Linux 2.6.19.1 # This always works, no matter > the hardware. > root (hd0,1) > kernel /boot/boot.2.19 root=/dev/md1 > > title Default OpenSuSE 10.2 # Do not work, but if harddisk is > attached to MS Virtual PC then it works !? > root (hd0,1) > kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/md1 > initrd /boot/initrd-2.6.18.2-34-default > > When booting the default SuSE kernel, the following is written to the > screen: > Loading liniar > md: Liniar personality registered for level1 > Loading JBD > Loading mbcache > Loading ext3 > md: MD1: No device found for /dev/md1 > Waiting for device /dev/md1 to appear: OK > /dev/md1: Unknown volume type > Invalid boot file system - exiting to /bin/sh. > .. > And then the boot stops. > > The same harddisk mounted on a MS Virtual PC and booted with the same > Grub bootline, > boots as expected, and makes the following lines in boot.msg: > .. > Loading liniar > Loading mbcache > Loading ext3 > mdadm: /dev/md0 has been started with 1 drive (out of 2). > mdadm: /dev/md1 has been started with 1 drive (out of 2). > ... > /Bo Since the data is still intact and you have 2 different methods of booting this RAID array I think its something very basic that you are overlooking. Been there done that myself. Are you sure of the grub parameters on the raid array? You're showing us your selected lines of /boot/grub/menu.lst and not the whole thing so we can't spot any potential errors/differences. Is there an initrd line for the boot-2.19 kernel? What other params are we not seeing? One nit to pick also. Why put /swap on the RAID array? I'd advocate having two separate non-RAID /swap files on the bare metal. But then, that's just me. /swap is slow enough compared to main memory but then you also want to write that transient data again to another drive and slow the rest of the system down, again? Sure modern systems are fast but I look at it as unneeded wear and tear. Stan Stan -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
