From owner-freebsd-hackers Tue Mar 28 23:28:42 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA11046 for hackers-outgoing; Tue, 28 Mar 1995 23:28:42 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA11040 for ; Tue, 28 Mar 1995 23:28:41 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id XAA07489; Tue, 28 Mar 1995 23:28:31 -0800 From: Poul-Henning Kamp Message-Id: <199503290728.XAA07489@ref.tfs.com> Subject: Re: mounting msdos, invalid fdisk partitions? To: mmead@goof.com (matthew c. mead) Date: Tue, 28 Mar 1995 23:28:31 -0800 (PST) Cc: hackers@FreeBSD.org In-Reply-To: <199503290720.CAA00284@goof.com> from "matthew c. mead" at Mar 29, 95 02:20:11 am Content-Type: text Content-Length: 783 Sender: hackers-owner@FreeBSD.org Precedence: bulk > I didn't notice any functional difference until I tried to mount the msdos > partition on my second hard drive this evening. I still get the problems > at boot when the drives are first accessed and partitions are "rejected" for > not residing entirely within the freebsd slice. For some reason this is now > preventing me from mounting /dev/sd1e (which used to work). Anyhow, if anyone > knows what's up, please let me know. Thanks! The slice code. Try to mount one of these as your msdos fs: /dev/sd1s1, /dev/sd1s2, /dev/sd1s2, /dev/sd1s3 You may have to run a "MAKEDEV sd1" in /dev... -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'