Date: Tue, 01 Feb 2000 04:27:20 -0500 From: "James A. Mutter" <jmutter@ds.net> To: Alfred Perlstein <bright@wintelcom.net> Cc: Mike Morgan <mikemorgan@hfnweb.com>, "'schwenk@math.udel.edu'" <schwenk@math.udel.edu>, "'freebsd-questions@freebsd.org'" <freebsd-questions@FreeBSD.ORG> Subject: Re: Any 'elders' care to help? [Was: wd0 or wd1] Message-ID: <3896A6F8.74FF93DD@ds.net> References: <E3E1A9F2A227D311A1EC00902785C1084C2F3D@UTASVEXG001> <38967EDF.C54B4C51@ds.net> <20000201004941.D24609@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > Ok. At this point you need to end up the following devices: > > rwd0s1a .. rwd0s1h > > wd0s1a .. wd0s1h > > > > Problem is that I'm not the one to tell you how to create them. Under > > other circumstances I might suggest using 'mknod' to accomplish this but > > something tells me it's going to be a bit more complicated this time. > > You _might_ be able to do this with disklabel or sysinstall but I can't > > promise you that they won't destroy the existing data. At this point > > you need the assistance of one of the group elders. > > > > Good luck though and let me know how it works out. > > I'm not sure how you arrived at this problem, however if you can > mount and fetch a recent copy of the MAKEDEV script from src/etc/MAKEDEV > you ought to be able to use it to recreate these device nodes. He got into this when he physically moved the HDD effectively changing wd1 -> wd0. He altered /etc/fstab and his kernel to reflect the changes but still had problems, that's when we noticed that the proper /dev/wd* entries were missing. I wasn't sure if it was as simple as just using MAKEDEV to add the entries. Apparently it is. I was concerned though that this might somehow corrupt the existing data on the drive. - Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3896A6F8.74FF93DD>