From owner-freebsd-questions Sat Aug 15 10:35:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16349 for freebsd-questions-outgoing; Sat, 15 Aug 1998 10:35:12 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from lucy.bedford.net (lucy.bedford.net [206.99.145.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16328 for ; Sat, 15 Aug 1998 10:35:04 -0700 (PDT) (envelope-from listread@lucy.bedford.net) Received: (from listread@localhost) by lucy.bedford.net (8.8.8/8.8.8) id NAA12486; Sat, 15 Aug 1998 13:24:08 -0400 (EDT) (envelope-from listread) Message-Id: <199808151724.NAA12486@lucy.bedford.net> Subject: Re: disk confusion In-Reply-To: <19980816015957.37974@welearn.com.au> from Sue Blake at "Aug 16, 98 01:59:57 am" To: sue@welearn.com.au (Sue Blake) Date: Sat, 15 Aug 1998 13:24:08 -0400 (EDT) Cc: freebsd-questions@FreeBSD.ORG X-no-archive: yes Reply-to: djv@bedford.net From: CyberPeasant X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sue Blake wrote: > To do the installation (from CD) I disabled the IDE (wdc0) and > unplugged sd0, making the working disk take the name sd0 temporarily. > Now of course it's called sd1 again. Ouch. I bet "real" sd1's /etc/fstab is just chock full of references to sd0sX > Yes it booted fine as sd0 before I plugged the first SCSI disk back in. Right, sd0... Repeat last comment, s/bet/really bet/ At this point, I would boot FreeBSD from any but the sd1 system; I would fsck the sd1s1X partitions. Then I would mount the sd1s1a on /mnt, and poke around in /mnt/etc, looking for sd0 [fstab :) ] where it should be sd1. I just went through this drill yesterday, more or less. (I was using a scsi controller trick to accomplish the same as unplugging the drive.) Alas, this stuff arises because of convenience and user friendliness. You have to jump through hoops to get the ancient behavior (the one the gods intended men to use), where SCSI ID 4 becomes sd4, regardless of what other devices are on the SCSI bus. My two drives are ID 0 and ID 2, but show up as sd0 and sd1. If I tell the controller to boot from ID 2, then ID 2 becomes sd0 and ID 0 becomes sd1. This is, of course, user friendly. Grrrr. It's real friendly, until you want to boot the rescue on ID 2. This will be sd0 if old ID 0 has failed due to hardware (can't be detected by the controller) or sd1 if ID 0 is still alive at the SCSI level. The hoops to jump through involve, IIRC, "wiring" the ID to a specific device by configuring yet another new kernel. (Your problem won't require this, I think). Dave -- Confutatis maledictis, flammis acribus addictis. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message