From freebsd-questions Sat Aug 18 22:12:50 2001 From: "Milo Hyson" Date: Sat, 18 Aug 2001 22:12:50 +0000 To: freebsd-questions Subject: RE: Re[2]: Disks moved around -- can't boot -- help!!! X-MARC-Message: https://marc.info/?l=freebsd-questions&m=99817272501418 Yup, that did it. Thanks. Somebody needs to figure out a better way to handle that situation. - Milo Hyson CyberLife Labs, LLC > -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Walter Hop > Sent: Saturday, August 18, 2001 2:33 PM > To: Milo Hyson > Cc: FreeBSD Questions List > Subject: Re[2]: Disks moved around -- can't boot -- help!!! > > > [in reply to milo@cyberlifelabs.com, 18-08-2001] > > > One problem. There are no device nodes for the new slices. The current > > slices are ad0s1a, ad0s1b, ad0s1e and ad0s1f. There are nodes > for ad1, ad1a > > through ad1h and ad1s1 through ad1s4. > > Funny, I had the same problem last week (ad1 moved to ad0). > > After moving a disk to a new machine, boot failed and I could not mount > it read-write because the right devices were missing. I'm sure there is > a better method, but I did the following: > > *] Booted with kern.flp and mfsroot.flp, went to "Fixit" with fixit.flp > *] On the Fixit floppy, in /mnt2/dev/ if I recall correctly, I did > a: sh ./MAKEDEV ad0s1a (the ad0 dev entries were absent) > *] I could now mount the hard drive with: mount -t ufs ./ad0s1a /mnt > *] On the hard drive I remade the devices as well: cd /mnt/dev/; > sh ./MAKEDEV ad0s1a > *] Then edited /etc/fstab to reflect the new drive (ad0 instead of ad1), > and rebooted. > > Hope this helps, > walter > > -- > Walter Hop | +31 6 24290808 | Finger for public key > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message