"cg 0: bad magic number" (used to be Disappointed with version 6.0)

[Peter]

--- "Donald J. O'Neill" <duncan.fbsd at gmail.com> wrote:

> > Ok, I have narrowed down my problem a great deal.  It appears that
> > FreeBSD cannot read the partition table of my 300 GB Seagate
> > Barracuda. My dos diagnostic utility works because it accesses the
> > disk in a different way.
> >
> > I used the entire disk (one slice/partition) and attempted to
> format
> > it.  This is what I get after it reaches the end of the disk:
> >
> > "cg 0: bad magic number"
> >
> > It also slows down significantly about 3/4 through the procedure.
> >
> 
> Are you doing this through sysinstall or are you manually running
> fdisk 
> and bsdlabel.
> 

Through sysinstall.  Both disklabel and fdisk don't work.  The former
gives "input/output error" and output to the latter I gave in my last
post.


> > Now the funny part.  I create two partitions and the newfs output
> is
> > exactly the same as before when I try to format the first
> partition!
> > It tries to format as if there is only one partition and produces
> the
> > same error.
> >
> > If I remove the slice via sysinstall and then try fdisk I get this:
> >
> > # fdisk -vBI ad3
> > ******* Working on device /dev/ad3 *******
> > parameters extracted from in-core disklabel are:
> > cylinders=581421 heads=16 sectors/track=63 (1008 blks/cyl)
> >
> > Figures below won't work with BIOS for partitions not in cyl 1
> > parameters to be used for BIOS calculations are:
> > cylinders=581421 heads=16 sectors/track=63 (1008 blks/cyl)
> >
> > Information from DOS bootblock is:
> > 1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
> >     start 63, size 586072305 (286168 Meg), flag 80 (active)
> >         beg: cyl 0/ head 1/ sector 1;
> >         end: cyl 812/ head 15/ sector 63
> > 2: <UNUSED>
> > 3: <UNUSED>
> > 4: <UNUSED>
> > fdisk: Geom not found


> Is this a brand new disk? Has it ever been used before? Is it still 
> under warrantee? If it is, take it back and get it replaced.


Yeah, I'm leaning that way too.


> Hey, I just saw it. You made Google search.


Huh?


> It looks to me like things just went through the motions and not the 
> actuality of installing ufs on the drive. That's happened to me a 
> couple of times and from what I remember, I had to start the install 
> over from the beginning - and I seem to recall something about having
> 
> to install windows first and reformatting all the hard-drives with 
> NTFS, then I could go back in and install FreeBSD. Otherwise, I 
> couldn't get FreeBSD to install, it just went through the motions, 
> wiping out whatever was on the hard-drives but not putting in
> FreeBSD. 
> Without a CDROM, it's going to be a little bit rough to do.

I don't understand why you mention Windows.  Surely I don't require
Windows to get this drive to work.  As for the cdrom, I can always put
it back to do an install.  It doesn't cause  trouble -just slows down
the boot drive.

--
Peter

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com