From vger.rutgers.edu!owner-linux-raid-outgoing Thu Oct 14 03:00:56 1999 Return-Path: Received: from nic2.funet.fi(really [128.214.248.46]) by planet via smail with esmtp id for ; Thu, 14 Oct 1999 02:59:26 -0700 (PDT) (Smail-3.2.0.90 1996-Dec-4 #9 built 1996-Dec-8) Received: from vger.rutgers.edu ([128.6.190.2]:16666 "EHLO vger.rutgers.edu") by nic2.funet.fi with ESMTP id ; Thu, 14 Oct 1999 12:51:51 +0300 Received: by vger.rutgers.edu via listexpand id ; Thu, 14 Oct 1999 05:51:20 -0400 Received: by vger.rutgers.edu id ; Thu, 14 Oct 1999 05:51:05 -0400 Received: from ibm6.ftech.net ([212.32.16.76]:47344 "EHLO relay4.ftech.net") by vger.rutgers.edu with ESMTP id ; Thu, 14 Oct 1999 05:49:50 -0400 Received: from ibm9.ftech.net ([212.32.16.79] helo=prior.ftech.co.uk) by relay4.ftech.net with smtp (Exim 3.03-ftechp4 #2) id 11bhOa-0006dc-00; Thu, 14 Oct 1999 10:42:00 +0100 From: "Bruno Prior" To: "Linux-Raid" , "Markus Hofmann" Subject: RE: Lilo and booting with failed first disk Date: Thu, 14 Oct 1999 11:01:16 +0100 Message-ID: <002301bf162b$0e024da0$0201a8c0@prior.ftech.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-linux-raid@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-raid-outgoing Status: RO > My Problem: > First i tried to use root=/boot-hda1 in lilo.conf.hda below. But this > doesn't work. I got the following error from lilo: > Sorry, don't know how to handle device 0x0906 > ... but /boot-hda1 was mounted to /dev/hda1 which is a nonraid ext2 > partition. > o.k. but when i mount /dev/hda1 on /boot lilo works If lilo tells you it can't handle device 0x0906, that means somewhere in lilo.conf you are telling lilo to read from /dev/md6. Do you really mean you used root=/boot-hda1? This would make no sense as you want /boot-hda1 to be your /boot filesystem, not your / filesystem. But your lilo.conf and shell script imply that this is not what you are doing, so I hope this was just a typo. If not, you know where your problem lies. Assuming this was a typo, and you were actually going with a lilo.conf something like: append="console=ttyS1" boot=/dev/hda serial=1,9600n8 vga=normal read-only prompt timeout=50 image = /boot-hda1/vmlinuz root = /dev/md6 label = Linux and this was throwing up the "can't handle device 0x0906" error, then you may find that the problem is the absence of map= and install= lines. If these are not included in your lilo.conf, lilo defaults to map=/boot/map and install=/boot/boot.b. With /dev/hda1 mounted on /boot-hda1, /boot presumably resides on the root filesytem, i.e. /dev/md6. Try adding the lines: map=/boot-hda1/map install=/boot-hda1/boot.b below the boot= line in your lilo.conf and see whether that works. Or better still, do away with /boot-hda1, and leave /dev/hda1 on /boot permanently. Why do you want to have 2 copies of the /boot filesystem on each disk anyway? This means that anytime you make changes to the kernel, you have to copy from /boot to /boot-hda1 before you can run lilo. I can't see what this gets you, apart from extra hassle. > I changed my lilo script and now lilo installs the kernels on /dev/hda1 > and /dev/hdc1 and itself to the master boot record. Both partitions are > marked as active. > Booting from /dev/hda1 works fine. Then I simulated a error and removed my > first disk. In my BIOS i use autodetection for the harddisks. When System > reboots I think he tries to boot from /dev/hdc1, because the computer > doesn't say "no system, press any key to reboot" (or something similiar). > But I only got many alternating 010101010101 scrolling down my screen - > which means that something is wrong with lilo.... > Is there something else to do, that lilo could boot from the second disk? As James says, use a "disk=/dev/hdc bios=0x80" line after your boot= line in lilo.conf.hdc to tell lilo that in the event that you boot from hdc, it will actually be in the bios location of hda. You should be aware that this trick is fine for when /dev/hda blows up so completely that it isn't even identified and /dev/hdc slips to /dev/hda. But in the situation where /dev/hda fails but is still recognized as present, you are stuck until you either pull the disk or use a boot floppy. Cheers, Bruno Prior bruno@prior.ftech.co.uk