I've seen a similar problem in my testing, and the problem seems to be inconsistent values in the superblock that cause lilo to get confused and give up. You can use mdctl to both look at the superblock and to fix it by reconstructing the raid configuration. Probably the Total Disks field has been set to something less than the configured "Raid disks" field. Probably md needs to have safeguards added to prevent superblock errors like this. Andy Cress -----Original Message----- From: Mark Nellemann [mailto:mark@netgroup.dk] Sent: Tuesday, February 26, 2002 7:52 AM To: linux-raid@vger.kernel.org Subject: Lilo problem with RAID1 Hi, I've just upgraded the kernel on a box and was about to update the boot-loader (as i've done many times before), but this time I got an error saying: Fatal: map file must be on the boot RAID partition As you can see below, the map file (/boot/map) is on the root-raid partition. Any ideas? (root) dbnode1: ~ > mount /dev/md1 on / type ext3 (rw,errors=remount-ro,errors=remount-ro) (root) dbnode1: ~ > lilo -V LILO version 22.2 (root) dbnode1: ~ > cat /etc/lilo.conf boot = /dev/md1 install = /boot/boot.b map = /boot/map prompt timeout=100 append="bootfs=ext3" image=/vmlinuz root=/dev/md1 label=Linux read-only (root) dbnode1: ~ > cat /proc/mdstat Personalities : [raid0] [raid1] [raid5] read_ahead 1024 sectors md2 : active raid1 hdc2[1] hda2[0] 2097536 blocks [2/2] [UU] md1 : active raid1 hdc1[1] hda1[0] 95588032 blocks [2/2] [UU] -- Mark Nellemann <mark@netgroup.dk> - Systems Developer NetGroup A/S, St. Kongensgade 40H, DK-1264 København K, Denmark Phone: +45 3370 1537 - Fax: +45 3313 0066 - Web: www.netgroup.dk GPG: C027 8CEB 4410 47D2 481B 5937 96D2 BB27 A2D5 002D - 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 - 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
