Andrew Hesford wrote:
>
> On Fri, Apr 06, 2001 at 10:17:24AM +0200, Jon Molin wrote:
> > The -I option gives the same output:
> > jmo# fdisk -I ad3
> > ******* Working on device /dev/ad3 *******
> > fdisk: invalid fdisk partition table found
> > jmo# disklabel -B -w -r ad3s1 auto
> > disklabel: /dev/ad3s1: Device not configured
> >
> > /jon
>
> [snip]
> Why don't you try this: re-zero the device, just to make sure it's
> clean, then give fdisk another go. If it fails, re-zero it again, and
> try to use Windows fdisk (or even Linux) to partition the drive. If
> neither one succeeds, you know the disk got trashed, and your failure is
> most likely a coincidence. If one *does* succeed, then save the MBR, put
> the disk in your FreeBSD box, and edit the existing MBR with the FreeBSD
> fdisk.
> --
> Andrew Hesford
> [EMAIL PROTECTED]
When i first got the disk it was windows and i was able to mount and get
the data from it. Then i used freebsd fdisk and all 'dispeared'. Then i
used a slackware bootdisk to get fdisk there and was able to make it a
bsd partition, but when i booted back to freebsd and tried to slice it
it didn't work...
And i got the devices there:
# ls /dev/ad3*
/dev/ad3 /dev/ad3e /dev/ad3s1a /dev/ad3s1f
/dev/ad3s4
/dev/ad3a /dev/ad3f /dev/ad3s1b /dev/ad3s1g
/dev/ad3b /dev/ad3g /dev/ad3s1c /dev/ad3s1h
/dev/ad3c /dev/ad3h /dev/ad3s1d /dev/ad3s2
/dev/ad3d /dev/ad3s1 /dev/ad3s1e /dev/ad3s3
/jon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
