Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!wx.gtegsc.com!news.cerf.net!crash!fpm From: fpm@crash.cts.com (Frank Maclachlan) Subject: Re: REPOST: NetBSD 0.8: can't disklabel 2nd IDE Organization: CTS Network Services (crash, ctsnet), El Cajon, CA Date: 29 Jul 93 12:01:18 PDT Message-ID: <1993Jul29.120118.25903@crash> Keywords: disklabel IDE NetBSD References: <1993Jul28.104210.26144@newstand.syr.edu> <1993Jul29.142557.899@mnemosyne.cs.du.edu> Lines: 22 In article <1993Jul29.142557.899@mnemosyne.cs.du.edu> bspengle@nyx.cs.du.edu (Brett Spengler) writes: > >Yeah, I ran into this as well even got newfs to go through. However fsck >coughed on bootup and I ended up with a mess. > >A quick and very dirty work around is to take the 2nd IDE and make it the >1st. Take the 1st out of your machine and shelve it temporarily. GO >through the standard install on the drive that wouldn't disklablel -- >it will disklabel for some reason this way. Move it back to the 2nd >drive and put your first back in. You now have two dislabeled drives that >will work. A brute force method, but effective. > The problem is that the second stage boot, /usr/mdec/bootwd, has non-zero values in the diskabel area. Mount the appropriate install floppy and replace /usr/mdec/bootwd with the file by the same name from the floppy. Cheers, Frank MacLachlan -- UUCP: {hplabs!hp-sdd ucsd nosc}!crash!fpm INET: fpm@crash.cts.com