Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!news.alpha.net!news.mathworks.com!uhog.mit.edu!bloom-beacon.mit.edu!gatech!newsxfer.itd.umich.edu!zip.eecs.umich.edu!caen!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions Subject: Re: disklabel -B has no effect. Date: 9 Dec 1994 16:41:56 GMT Organization: Montana State University, Bozeman Montana Lines: 31 Message-ID: <3ca1ck$50n@pdq.coe.montana.edu> References: <3c98u0$4st@whitbeck.ncl.ac.uk> NNTP-Posting-Host: bsd.coe.montana.edu In article <3c98u0$4st@whitbeck.ncl.ac.uk>, A.M. Zanker <A.M.Zanker@ncl.ac.uk> wrote: >I have a strange problem with the FreeBSD 2.0R disklabel utility. I >installed the system on my 2nd IDE drive (a 170MB IBM model) and decided >to edit the bootblocks to allow default booting from this drive. Having >successfully edited and recompiled bootwd and wdboot I proceeded to >install them with "disklabel -B wd1". However, the boot blocks on the >disk were completely unaffected by this (as od -c /dev/rwd1c revealed). >I tried a number of other incantations of the disklabel command without >success. I'll bet the boot blocks on wd1 were affected by this, but since DOS only allows booting from the 1st disk, it wouldn't do you any good. There are boot managers which recognize the partitions on the second drive and allow you to boot from them, but they over-write the MBR on the first drive. >I eventually solved the problem by copying wdboot and bootwd to >/stand/sdboot and /stand/bootsd (yes, SD) and running the sysinstall >utility to write the MBR/disklabel for my 2nd drive. I suspect that it wrote to the first drive. Nate -- nate@bsd.coe.montana.edu | FreeBSD dude and all around tech. nate@cs.montana.edu | weenie. work #: (406) 994-5980 | Unemployed, looking for permanant work in home #: (406) 586-0579 | CS/EE field.