Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!swing.iinet.net.au!news.uoregon.edu!usenet.eel.ufl.edu!pacifier!homer.alpha.net!solaris.cc.vt.edu!news.duke.edu!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: 18 Oct 1995 18:38:56 GMT Organization: Lawrence Berkeley Laboratory Lines: 62 Message-ID: <463hk0$pde@overload.lbl.gov> References: <461btt$34q@overload.lbl.gov> <462cgf$hgc@germany.eu.net> NNTP-Posting-Host: gracie.lbl.gov In article <462cgf$hgc@germany.eu.net>, Bernard Steiner <bs@Germany.EU.net> wrote: > >In article <461btt$34q@overload.lbl.gov>, jin@gracie.lbl.gov (Jin Guojun[ITG]) writes: >|> I had problems using disklabel to label some brand new SCSI disks. >|> I am using 2.1-951005-SNAP. I have not tried it on 2.0.5-RELEASE. >|> >|> # disklabel -r sd2c >|> disklabel: /dev/rsd2c: No such file or directory > >That is fairly obvious, isn't it ? > ># cd /dev; sh MAKEDEV sd2h > >or somesuch. > >CU > Bernard I did not miss this. I won't say I am a guru in O.S. addministration. However, I work on a variaty of O.S. and I didn't remove /dev/rsd2*. If you familiar with FreeBSD, the sd0-3 are made in INSTALLATION time. I do have to MAKEDEV sd4-7 to make 8 disks working. Also, the right syntax for MAKEDEV is : ./MAKEDEV sd[0-9] Thanks for your point. Now, what is fairly obvious is that disklabel is buggy (BSDI has so many problems on disklabel too, and they won't fix them until 2.1 release )-: ). The thing I do not understand is that how the INSTALLATION labels new disks. If the disklabel in INSTALLATION can work. It should not be too hard to fix the regular disklabel program. If something is confusing, I'd like to put more words here even they are not necessary for FreeBSD experts. Two scsi (HAWK) disks are labeled at installation time, and other two are not. So, put two labeled disks (call them l-disk) on sd0 and sd1, and put two other non-labeled disks (call them nl-disk) on sd2 and sd3; then you see above errors. 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. The problem is the disklabel can label a labeled disk, but cannot label a non-labeled disk. So, what I can do right now is either using installation floppy to label the new disks, or using SunOS to label them, then using disklabel progeam relebel the disk again. No problem. You always can find a solution kludge to fix a bug. I awared that almost no body uses a raw-raw disk from manufactories. However, this discovers the problem in disklabel. What happens if the disk label is completely wiped out? Then, how this disk can be relabeled? Is this the disklabel bug, or I miss something? -- /-------------- 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 |