Date: Sat, 11 Jul 1998 22:50:44 -0400 From: Dan Swartzendruber <dswartz@druber.com> To: Doug White <dwhite@resnet.uoregon.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: can't access new disks? Message-ID: <3.0.5.32.19980711225044.00939240@mail.kersur.net> In-Reply-To: <Pine.BSF.3.96.980711194055.3277F-100000@resnet.uoregon.edu > References: <3.0.5.32.19980708073736.0094da40@mail.kersur.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 07:41 PM 7/11/98 -0700, Doug White wrote: >On Wed, 8 Jul 1998, Dan Swartzendruber wrote: > >> >> * The boot-time probe is finding the new drives, yet when I try to do >> >> * anything with them (such as labeling them), I get this: >> >> >> >> # disklabel -r -w da16s1c auto >> >> disklabel: /dev/rda16s1c: Device not configured >> >> >> >> * Any ideas? >> > >> >Does da16 have an fdisk table? >> >> Doubt it. Brand new disk (literally). In any event, I can't even copy >> from the drive (or to it), using slice 'c'. > >You can't access slices if you don't have an fdisk table to define the >slices wih. Try /dev/rda16c. I'm confused. I have no such devices. Nor will MAKEDEV create anything that looks like that (e.g. a diskname ending with 'c'). 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?3.0.5.32.19980711225044.00939240>