Re: [ILUG] mirroring on a running system On Tue, Aug 13, 2002 at 04:10:57PM +0100, John P. Looney mentioned: > > I think this procedure is described in the RAID HOWTO for installing a > > new system, but it applies just as well to a running system. >  >  Just double checking (I'd be pissed if I just wiped my installation!)...  Well, this mostly worked, despite Colm saying that "you want the "failed-disk" *instead* of the second "raid-disk", not in addition to it".  I suppose that means instead of: > raiddev /dev/md0 >         raid-level      1 >         nr-raid-disks   2 >         nr-spare-disks  0 >         chunk-size     4 >         persistent-superblock 1 >         device          /dev/hdg3 >         raid-disk       0 >         device          /dev/hda5 >         raid-disk       1 >  >         failed-disk     1  I should have had: > raiddev /dev/md0 >         raid-level      1 >         nr-raid-disks   2 >         nr-spare-disks  0 >         chunk-size     4 >         persistent-superblock 1 >         device          /dev/hdg3 >         raid-disk       0 >         device          /dev/hda5 >         failed-disk     1  It likely means that I was just lucky I put the failed-disk directive after the raid-disk one :)  Anyway. It's doesn't quite boot right, with /=/dev/md0 in fstab. On boot, I see: Partition check:  hda: [PTBL] [2482/255/63] hda1 hda2 hda3 hda4 < hda5 >  hdg: [PTBL] [2434/255/63] hdg1 hdg2 hdg3 floppy0: no floppy controllers found RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize ide-floppy driver 0.99.newide md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: Autodetecting RAID arrays.  [events: 00000000] md: invalid raid superblock magic on hda2 md: hda2 has invalid sb, not importing! md: could not import hda2!  [events: 00000004]  [events: 00000002]  [events: 00000004] md: autorun ... md: considering hdg3 ... md:  adding hdg3 ... md:  adding hda5 ... md: created md0 md: bind md: bind md: running:  md: hdg3's event counter: 00000004 md: hda5's event counter: 00000004 md: RAID level 1 does not need chunksize! Continuing anyway. kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 md: personality 3 is not loaded! md :do_md_run() returned -22 md: md0 stopped. md: unbind md: export_rdev(hdg3) md: unbind md: export_rdev(hda5) md: considering hdg1 ... md:  adding hdg1 ... md: created md1 md: bind md: running:  md: hdg1's event counter: 00000002 md: RAID level 1 does not need chunksize! Continuing anyway. kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 md: personality 3 is not loaded! md :do_md_run() returned -22 md: md1 stopped. md: unbind md: export_rdev(hdg1) md: ... autorun DONE.  Any ideas why ?  My suspicion is that I've a lack of knowledge about how initrd works, so I'm not sure it's loading it. For a start, the / filesystem is being mounted as ext2, at first, not ext3. It does seem mounted as ext3 after the fsck is done - but that means that it's mounted as ext2 read only, fsck'ed and then remounted ext3. Losing the point of it.  Given I can't pass the kernel parameters (I think), how then can I get it to load the initrd ? Kate --  Irish Linux Users' Group: ilug@linux.ie http://www.linux.ie/mailman/listinfo/ilug for (un)subscription information. List maintainer: listmaster@linux.ie