From owner-freebsd-current Wed May 20 01:44:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19884 for freebsd-current-outgoing; Wed, 20 May 1998 01:44:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19870 for ; Wed, 20 May 1998 01:44:23 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id BAA14336; Wed, 20 May 1998 01:37:33 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd014332; Wed May 20 08:37:26 1998 Date: Wed, 20 May 1998 01:37:23 -0700 (PDT) From: Julian Elischer To: Mike Smith cc: Tom Jackson , FreeBSD Current Subject: Re: slice/devfs problem In-Reply-To: <199805191337.GAA03125@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 May 1998, Mike Smith wrote: > > Neither disklabel, fdisk nor sysinstall work with SLICE. There are new > tools in the pipeline, but until then you will need to stick with using > an install image or non-SLICE kernel. Not STRICTLY true.. you can use fdisk as before, and disklabel -rw if you know what you are doing. julian > > > Since devfs/slice had been added to LINT I adopted it to all > > my boxes. No problem on two with single disk, dangerously > > dedicated. On the the main server box, disklabel says all disk > > end partition and 'c' partition extend past end of disk. > > > > When I tried to use sysinstall to change the slice settings on > > a brand new disk, it hung, sorry I didn't get debug messages. I > > won't go into the file system corruption I got on unrelated fs's > > ( first time ever with FreeBSD ) but the new disk now is not seen > > by /stand/sysinstall. Also fdisk can't find the slices either and > > says it is using dummy parameters 1/1/1 and then it hangs. > > > > I've got the corrupted file systems back by dumping devfs/slice > > on the server and using /stand/sysinstall to delete, bring back > > and newfs the file systems. > > > > BIG question is how do I get fdisk to work with the new disk and > > thus, let me use /stand/sysinstall to set the slice settings. The > > weird thing is msdos lets me put a dos slice on this disk, no problem, > > pfdisk shows the slices, no problem, and a boot floppy picks up the > > disk to allow me to set the slices. > > > > I'm holding off dedicating anything to this disk until I can get it > > to look normal to fdisk. > > > > Thanks for FreeBSD, > > > > Tom > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message