Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!vic.news.telstra.net!act.news.telstra.net!psgrain!reuter.cse.ogi.edu!netnews1.nwnet.net!netnews.nwnet.net!news.u.washington.edu!uw-beaver!uhog.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!news-peer.gsl.net!news.gsl.net!portc01.blue.aol.com!newsstand.cit.cornell.edu!news.acsu.buffalo.edu!news.drenet.dnd.ca!crc-news.doc.ca!nott!bcarh189.bnr.ca!bmerhc5e.bnr.ca!bcrkh13.bnr.ca!n merh207!friedman From: friedman@bnr.ca (Barry Friedman) Subject: Disk confusion Summary: After adding a backup disk nothing works Sender: usenet@bnr.ca ( Usenet System ) Message-ID: <Dy9MFy.LCH@bnr.ca> Date: Wed, 25 Sep 1996 01:50:21 GMT X-Nntp-Posting-Host: nquah6f Reply-To: friedman@bnr.ca Organization: Northern Telecom, Ltd. Lines: 41 I was given a running bsd system with the boot and system residing on partition 1 of the master disk off an IDE controller (wd0). What I tried to do was to reformat the slave disk which was a single dos partition, partition it the same as the master disk, and copy the running system onto it so I would have a backup of this system in case a disk crashed. This all went relatively smoothly except that I noticed that I was getting an error: "wd1: raw partition size != slice size" I was able to mount all the partitions of the new disk and using tar, copy the system data. So far so good. The last thing that I did was to install a bootstrap on wd1 using disklabel. Then the trouble started. I tried to reboot the machine after a power failure and instead of booting wd0, the bootstrap fsck'd wd1 and gave me the message: /dev/wd1a on /: Specified device does not match mounted device. Filesystem mount failed, startup aborted I went into sh and did a df and got root_device on /. An ls of / shows that it is the original wd0a. Then I tried booting "wd(1,a)/kernel" to try and boot the new system. There was an additional message this time: "changing root device to wd1a. This time I got exactly the inverse -- of the boot of wd0, i.e. the boot fsck'ed /dev/rwd0 and gave the message: /dev/wd0a on /: Specified device does not match mounted device. and the root_device is wd1a. One additional piece of data: disklabel wd0 reports "disk: wd1s2" so this system may have originally been built on wd1. In any case, before I trash the entire build and start again from scratch, If there is any way to recover from this (or at least understand what is happening), I would be much obliged to hear about it. Thanks for reading this far. Regards, Barry Friedman