On Monday February 4, andrew.r.cress@intel.com wrote: > My RAID-1 root mirror seems to be ok, except that the second disk (/dev/sdb) > doesn't get tagged when I run lilo. I've never seen this before, and I > wondered how to fix it? > > I'm running kernel 2.4.16 and a RH7.1 base distro. > I did do an "mdctl --examine" on it also, results below. ... > /dev/sda1: > Magic : a92b4efc > Version : 00.90.00 > UUID : d7557de6:363404e9:468308b6:5a33c779 > Creation Time : Tue Aug 28 17:32:29 2001 > Raid Level : raid1 > Size : 72192 > Raid Disks : 2 > Total Disks : 1 > Preferred Minor : 1 > > Update Time : Mon Feb 4 16:18:39 2002 > State : dirty, no-errors > Active Drives : 2 > Working Drives : 2 > Failed Drives : -1 > Spare Drives : 1 > Checksum : cf58c674 - correct > Events : 0.204 > Note the "Total Disks" field and the "Failed Drives" field! Several of these fields are not really very well defined, and lilo gets confused (and I cannot say that I blame it). If you remake your boot array with: mdctl --stop /dev/md1 mdctl --create /dev/md1 --level=1 -n 2 /dev/sda1 /dev/sdb1 you should then be able to run lilo successfully. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
