Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.eng.convex.com!newshost.convex.com!newsgate.duke.edu!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Help: FreeBSD 2.1 'mount' fails on a 2.0 SCSI partition Date: 13 Jul 1996 11:27:23 GMT Organization: Private BSD site, Dresden Lines: 44 Message-ID: <4s816r$n33@uriah.heep.sax.de> References: <Hc3d6BAgq$4xEwMa@icrt.demon.co.uk> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E "Lars G. Erlandsen" <lerland@icrt.demon.co.uk> wrote: > [This mail was recently sent to questions@free_bsd.org as well] Unless you've actually sent it to questions@freebsd.org (without the underscore), it would have never arrived. :) > FreeBSD 2.1 was installed from CD-ROM without problems on the new IDE > drive. However, shock horror, it gets into fits when I'm manually trying > to mount the SCSI disk, complaining about overlapping partitions, in > particular '/dev/sd1s1d' (yes, I've got two SCSI disks as well, now!). > =============================================================== > sd1s1: rejecting partition in BSD label: it isn't entirely within the > slice > sd1s1: start 32, end 1435647, size 1435616 > sd1s1d: start 0, end 2110811, size 2110812 > =============================================================== The `d' metapartition is no longer supported since the advent of the `slice' code (i.e. FreeBSD 2.0.5). It used to cover the entire disk (as opposed to `c' which covers the BSD slice only, and is still supported), but that's no longer necessary now since there are other device nodes that can be used to handle an entire disk. > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > a: 61440 0 4.2BSD 1024 8192 16 # (Cyl. 0 - > 29) > b: 163840 61440 4.2BSD 1024 8192 16 # (Cyl. 30 - > 109) > c: 1435616 0 unused 0 0 # (Cyl. 0 - > 700*) > e: 1210336 225280 4.2BSD 1024 8192 16 # (Cyl. 110 - > 700*) This one looks right though. I assume this is the in-core label? If this were the on-disk label, i cannot see why it would fail. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)