From owner-freebsd-current Sun Jan 17 11:51:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20029 for freebsd-current-outgoing; Sun, 17 Jan 1999 11:51:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20023 for ; Sun, 17 Jan 1999 11:51:22 -0800 (PST) (envelope-from veldy@visi.com) Received: from rover (h-178-251.mn.mediaone.net [209.32.178.251]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id OAA16771 for ; Sun, 17 Jan 1999 14:51:16 -0500 (EST) From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: /boot/loader and booting off of second IDE Date: Sun, 17 Jan 1999 13:52:15 -0600 Message-ID: <000001be4252$e2562340$0264a8c0@rover.mn.mediaone.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01BE4220.97C35460" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0001_01BE4220.97C35460 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit OK. I have tried to figure out how to boot off of my second IDE drive and I am close, but I still haven't got it. I need to boot wd2s1a. Here is what I have done. Booting off of a floppy with the old boot blocks: 1:wd(2,a)/boot/loader I get to the prompt and type: set currdev=disk2s1a set rootdev=disk2s1a when I type show, I see loaddev=disk2s1a:, but there does not seem to be any documentation on this. Anybody know if this is significant? Anyway, I then do: boot -rootdev And the kernel proceeds to boot and it actually mounts the correct root (wd2s1a). It shows the all the drives are clean and then it fails, stating that it can't mount wd2s1a because the device is incompatible (or something like that - I am running from memory, as I have blown my system with fdisk (DOS) and am rebuilding) and then drops to a single user shell with / mounted read-only. It seems to me that it is having a problem going from root as a read-only filesystem to a read-write filesystem. I have tried many combinations without success. If it mounts root, it always fails during the remount (fstab). If I don't pass rootdev as an argument to the kernel, it tries to mount wd1s1 and then it panics, obviously because there is no [UFS] filesystem there. Any ideas what else to try? Tom Veldhouse veldy@visi.com ------=_NextPart_000_0001_01BE4220.97C35460 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
OK.  I have tried to figure out how to boot off of my = second IDE=20 drive and I am close, but I still haven't got it.  I need to boot=20 wd2s1a.  Here is what I have done.
 
Booting off of a floppy with the old boot = blocks:
 
    1:wd(2,a)/boot/loader
 
    I get to the prompt and = type:
 
    set currdev=3Ddisk2s1a
    set rootdev=3Ddisk2s1a
 
    when I type show, I see loaddev=3Ddisk2s1a:, = but there=20 does not seem to be any documentation on this.  Anybody know if = this is=20 significant?  Anyway,  I then do:
 
    boot -rootdev
 
And=20 the kernel proceeds to boot and it actually mounts the correct root=20 (wd2s1a).  It shows the all the drives are clean and then it fails, = stating=20 that it can't mount wd2s1a because the device is incompatible (or = something like=20 that - I am running from memory, as I have blown my system with fdisk = (DOS) and=20 am rebuilding) and then drops to a single user shell with / mounted=20 read-only.  It seems to me that it is having a problem going from = root as a=20 read-only filesystem to a read-write filesystem.  I have tried many = combinations without success.  If it mounts root, it always fails = during=20 the remount (fstab).  If I don't pass rootdev as an argument to the = kernel,=20 it tries to mount wd1s1 and then it panics, obviously because there is = no [UFS]=20 filesystem there.
 
Any=20 ideas what else to try?
 
Tom=20 Veldhouse
veldy@visi.com
------=_NextPart_000_0001_01BE4220.97C35460-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message