Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 30 Jun 2002 14:55:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 30 Jun 2002 14:55:02 -0400 Received: from twinlark.arctic.org ([208.44.199.239]:21453 "EHLO twinlark.arctic.org") by vger.kernel.org with ESMTP id ; Sun, 30 Jun 2002 14:55:01 -0400 Date: Sun, 30 Jun 2002 11:57:26 -0700 (PDT) From: dean gaudet To: Roy Sigurd Karlsbakk cc: linux-raid@vger.rutgers.edu, Kernel mailing list Subject: Re: Can't boot from /dev/md0 (RAID-1) In-Reply-To: <200206301419.26254.roy@karlsbakk.net> Message-ID: X-comment: visit http://arctic.org/~dean/legal for information regarding copyright and disclaimer. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1115 Lines: 39 my system has 4 disks, but /dev/md0 is a RAID1 for /boot. (/dev/md1 is a RAID5 and LVM is on top of it...) anyhow, this is what works for me. i've even pulled out a disk and it still boots. btw, you really don't want to put two drives on an IDE controller. not just for performance reasons -- if a master drive fails it can easily prevent access to the slave... so you'll have a two disk failure on your hands. or maybe this is just urban legend and i'm spreading it further ;) -dean lba32 boot=/dev/md0 root=/dev/arctic/root install=/boot/boot-text.b map=/boot/map prompt timeout=150 raid-extra-boot=/dev/hde,/dev/hdg,/dev/hdi,/dev/hdk password=XXXXXXXX serial=0,38400n8 append="console=tty0 console=ttyS0,38400n8" default=linux image=/boot/vmlinuz initrd=/boot/initrd-lvm-2.4.19-pre3-ac1.gz label=linux restricted read-only - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/