From owner-freebsd-questions Mon Jan 19 23:19:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10664 for questions-outgoing; Mon, 19 Jan 1998 23:19:37 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from ocala.cs.miami.edu (ocala.cs.miami.edu [129.171.34.17]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA10657 for ; Mon, 19 Jan 1998 23:19:32 -0800 (PST) (envelope-from marcus@ocala.cs.miami.edu) Received: from jaguar.ir.miami.edu by ocala.cs.miami.edu via SMTP (950413.SGI.8.6.12/940406.SGI) id CAA09993; Tue, 20 Jan 1998 02:19:31 -0500 Date: Tue, 20 Jan 1998 02:19:31 -0500 (EST) From: "Joe \"Marcus\" Clarke" X-Sender: marcus@jaguar.ir.miami.edu To: Mark Mayo cc: questions@FreeBSD.ORG Subject: Re: oops, removed a scsi disk and now I'm toast.. In-Reply-To: <19980120014645.49932@vmunix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk Get the fixit and boot floppies from FreeBSD (or the boot floppy, and a FreeBSD live filesystem CD). Then boot up, and start a fixit session. You can then edit fstab to reflect the change in drive position. I just recently went through this with IDE drives. Joe Clarke On Tue, 20 Jan 1998, Mark Mayo wrote: > Stupid question of the day.. I removed a SCSI drive that was sitting > in the middle of my SCSI chain. The important fact is that is was > before my FreeBSD disk, so now what used to be sd2 is sd1.. argghh. > > Of course, FreeBSD won't boot cause fstab says everything should > be on /dev/sd2s1x . I just need to get it up so I can compile a > new kernel which expects its root to be on sd1. > > How do I fix this?? Most time when I boot and manually tell the > boot prompt to use 1:(sd1,a)/kernel it just pukes with a panic > after the hardware detect. Other time I get to the point where > I can hit return and get 'sh'. sd1a is now mounted up as > > root_device blah blah / > > according to df. I mounted up /dev/sd1s1h on /usr, and went to > vi the /etc/fstab, but alas, root_device is read-only. Ugh. Trying > to mount it again gives me a device busy error, and trying to > mount -u -o rw / uses fstab and tries to do sd2 again.. > > I'm stuck. What do I do next? :-) > > TIA, > -Mark > > -- > ------------------------------------------------------------------------ > Mark Mayo mark@vmunix.com > RingZero Comp. http://www.vmunix.com/mark > > finger mark@vmunix.com for my PGP key and GCS code > ------------------------------------------------------------------------ > Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to > an an 8 bit operating system originally coded for a 4 bit microprocessor, > written by a 2 bit company that can't stand 1 bit of competition. -UGU >