Re: Dangerous file system / disk problem

2004-06-08 Thread Ben Paley
On Tuesday 08 June 2004 10:38, Malcolm Kay wrote: > On Tuesday 08 June 2004 05:20, Ben Paley wrote: > > But seriously, does any of this suggest a course of action to you? I'm > > planning to try the "set sysid to 0" plan... what if that doesn't work? > > Sounds like an excellent idea. Perhaps wind

Re: Dangerous file system / disk problem

2004-06-08 Thread Ben Paley
On Tuesday 08 June 2004 10:38, Malcolm Kay wrote: > On Tuesday 08 June 2004 05:20, Ben Paley wrote: > > But seriously, does any of this suggest a course of action to you? I'm > > planning to try the "set sysid to 0" plan... what if that doesn't work? > > Sounds like an excellent idea. Perhaps wind

Re: Dangerous file system / disk problem

2004-06-08 Thread Malcolm Kay
On Tuesday 08 June 2004 05:20, Ben Paley wrote: > On Monday 07 June 2004 16:44, Malcolm Kay wrote: > > Notice the size recorded for this slice is zero. > > > > If the "cylinders=155061 heads=16 sectors/track=63" is somewhere > > near the reasonable possible geometry description then virtually > > t

Re: Dangerous file system / disk problem

2004-06-07 Thread Ben Paley
On Monday 07 June 2004 16:44, Malcolm Kay wrote: > > Notice the size recorded for this slice is zero. > > If the "cylinders=155061 heads=16 sectors/track=63" is somewhere > near the reasonable possible geometry description then virtually > the entire disk has been allocated to the FreeBSD slice.

Re: Dangerous file system / disk problem

2004-06-07 Thread Malcolm Kay
On Monday 07 June 2004 04:01, Ben Paley wrote: > su-2.05b# fdisk ad1 > *** Working on device /dev/ad1 *** > parameters extracted from in-core disklabel are: > cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > par

Re: Dangerous file system / disk problem

2004-06-07 Thread Robert Storey
On Mon, 7 Jun 2004 13:10:48 +0100 Ben Paley <[EMAIL PROTECTED]> wrote: > This is very scary, but thanks for the advice. I had some more advice > (not sure if it went to the list or not) to try setting the second > partition as unused (sysid=0), so I might try that first to see > whether I can avo

Re: Dangerous file system / disk problem

2004-06-07 Thread Ben Paley
On Monday 07 June 2004 11:17, Dan Strick wrote: > > Partition 2 (sysid 14, start 156296385) is bogus. I don't have a clue as > to how it might have been created. I *guess* it was the W98 installer - if you boot into DOS and invoke setup.exe it's fairly polite, but if you boot from the cdrom, w

Re: Dangerous file system / disk problem

2004-06-07 Thread Dan Strick
On Sun, 6 Jun 2004 19:31:48 +0100, Ben Paley wrote: >> > ... > > *** Working on device /dev/ad1 *** > parameters extracted from in-core disklabel are: > cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > paramete

Re: Dangerous file system / disk problem

2004-06-06 Thread Ben Paley
On Sunday 06 June 2004 13:04, Dan Strick wrote: > Perhaps something changed the partition type code in the MBR partition > table on your FreeBSD disk. Do "fdisk ad1" to display the MBR partition > table. The FreeBSD slice should say: > > sysid 165,(FreeBSD/NetBSD/386BSD) > > If it says any

Re: Dangerous file system / disk problem

2004-06-06 Thread Dan Strick
On Sun, 6 Jun 2004 12:13:17 +0100, Ben Paley wrote: >> > I wanted to have FreeBSD on my first drive and Win98 on the second, but > of course windows doesn't like being on the second disk, and began > "preparing" my first drive which already had FreeBSD on it! Well, I > swapped the drives over, put

Dangerous file system / disk problem

2004-06-06 Thread Ben Paley
Hello, I wanted to have FreeBSD on my first drive and Win98 on the second, but of course windows doesn't like being on the second disk, and began "preparing" my first drive which already had FreeBSD on it! Well, I swapped the drives over, put W98 on the first one, they both boot fine and I didn