Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Apr 2006 11:07:47 -0400 (EDT)
From:      Jerry McAllister <jerrymc@clunix.cl.msu.edu>
To:        freebsd-questions@freebsd.org
Cc:        justin@pcmedicsite.com
Subject:   Re: newfs fails on 300GB HDD
Message-ID:  <200604111507.k3BF7lGl019703@clunix.cl.msu.edu>
In-Reply-To: <441ww4gpht.fsf@be-well.ilk.org>

next in thread | previous in thread | raw e-mail | index | archive | help

"Justin P. Michel" <justin@pcmedicsite.com> writes:

> I'm having a slight problem with a 300GB IDE (Maxtor) HDD.  Basically, I've
> run the drive on the system through a complete low-level format and test
> with the PowerMAX tools, which passed fine.  The BIOS recognizes and
> auto-detects the drive okay as well.
> 
> However, in trying to install FreeBSD 6.0, it goes through the partition
> section okay, and then the slice section okay (trying to use a full slice on
> the drive as /dumpdata), the mount fails, and on the alternate screen it
> shows newfs failing.
> 
> Is there a special way to get this drive to work?  Does someone have
> experience with a similar setup that may shed some light my way?  I feel
> like a beginner all over again. : P

Presuming it is a brand new disk and is addressed as the second one (eg ad1), 
>From root (su-ed to root) try this:

     dd if=/dev/zero of=/dev/ad1 bs=512 count=64

     fdisk -BI ad1

     bsdlabel -w -B ad1s1

     bsdlabel -e ad1s1

If you do not want it bootable, then skip the -B switches.

When you do the  bsdlabel -e it will put you in an editor session
with the base settings in the file.   Modify it slightly as follows.
Make the top line look something like:

  a:     *     *    4.2BSD     2048 16384    94   # (Cyl.    0 - 32*)

The '94' may be different.  If it suggests something else, then take that.

Then write/quit from the editor and it will write the label.

Then do the newfs:
    newfs -U /dev/rad1s1a

If newfs gets an error, write it down specifically.

If no error, try mounting:
    mount /dev/ad1s1a /dumpdata

Presumably you have made the directory /dumpdata?    That may seem
to simple to mention, but I have made that mistake more than once
and went nuts wondering why things (in a script) didn't work.

Good luck,

////jerry




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200604111507.k3BF7lGl019703>