Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!news.dacom.co.kr!news.kreonet.re.kr!overload.lbl.gov!gracie.lbl.gov!jin From: jin@gracie.lbl.gov (Jin Guojun[ITG]) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: help on labeling non-labeled new scsi disk Date: 25 Oct 1995 22:37:21 GMT Organization: Lawrence Berkeley Laboratory Lines: 64 Message-ID: <46me71$lvv@overload.lbl.gov> References: <461btt$34q@overload.lbl.gov> <462cgf$hgc@germany.eu.net> <463hk0$pde@overload.lbl.gov> <46akio$ge6@uriah.heep.sax.de> NNTP-Posting-Host: gracie.lbl.gov In article <46akio$ge6@uriah.heep.sax.de>, J Wunsch <j@uriah.heep.sax.de> wrote: >Jin Guojun[ITG] <jin@gracie.lbl.gov> wrote: > >>Also, the right syntax >>for MAKEDEV is : >> ./MAKEDEV sd[0-9] >>Thanks for your point. > >Both are valid, "sh MAKEDEV args..." is also ok. It depends on what args they are. You remember the first part, but forgot the last part. The original syntax was: sh MAKEDEV sd2h Would you beleive that could work? or be an error? >>Now, what is fairly obvious is that disklabel is buggy > >It's fairly obvious that disklabel ain't buggy, and it's as obvious >that you didn't read the slices.hlp file on the boot floppy. :-) > >If something is buggy (or at least, dubious), it's fdisk(8). > >>Now, switch nl-disk to sd0 and sd1, and l-disk to sd2 and sd3; then >you will see > >># disklabel: /dev/rsd0c: No such file or directory >> >>and disklabel -r sd2 will work well. So, don't doubt the system is wrong. > >What's wrong with "disklabel [options] sd2"? Why don't you simply >trust disklabel(8) to find the right device, and try to enforce it >something it cannot access (yet) -- "/dev/rsd0c"? > ...... (omitted number of lines) >FreeBSD bootstrap on it, e.g. with "disklabel -B -r [-w] sd0 ...". You said a quite bit without an example or a solution. I do not want to do any fancy thing on the raw-raw disks. The only thing I needed is to put a label on the disks (no partitions and no slices; or a couple of partitions is the labeling tool has to need them). I only need to use the raw disks, however, the FreeBSD won't do the configuration on unlabled SCSI devices. Before, It just complains that "no magic", but after 2.1-SNAP, I didn't see the complaining. Instead, the devices are not configged. What has been changed? What is the easy way to make system can read raw disk without labeling? or what is the way to label the raw disks? Any help will be appreciated. >Btw., the installer doesn't use disklabel(8) itself; it uses libdisk >which can be found in the src/release/libdisk directory. That is a library, but not a utility tool. -- /-------------- Jin Guojun ------------ v ---- Internet: g_jin@lbl.gov ----\ | Imaging & Distributed Computing | Usenet: ucbvax!g_jin@lbl.gov | | Lawrence Berkeley Laboratory | Bitnet: -- | | 50B-2239, Berkeley, CA 94720 - jin%george.lbl.gov@Csa3.LBL.Gov |