Date: Thu, 13 Apr 2006 12:14:19 -0700 From: Oliver Iberien <oliver-mailinglist@charter.net> To: freebsd-questions@freebsd.org Cc: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> Subject: Re: sysinstall won't write fs to new disk, bad magic number Message-ID: <200604131214.20271.oliver-mailinglist@charter.net> In-Reply-To: <448xq9y4oj.fsf@be-well.ilk.org> References: <200604102018.57042.oliver-mailinglist@charter.net> <200604120829.35428.oliver-mailinglist@charter.net> <448xq9y4oj.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 13 April 2006 06:40, Lowell Gilbert wrote:
> Oliver Iberien <oliver-mailinglist@charter.net> writes:
> > On Wednesday 12 April 2006 04:18, Lowell Gilbert wrote:
> > > Oliver Iberien <oliver-mailinglist@charter.net> writes:
> > > > There was a thread about this a while ago, but it did not seem to end
> > > > in a solution... In any case, I have a 160GB Seagate drive that I was
> > > > trying to mount a partition on as /disk2. I went through the
> > > > instructions in the Handbook under "Formatting Media for Use With
> > > > FreeBSD." No formatting seemed to be happening, though. When I added
> > > > it to fstab, something in KDE found it and then failed to open it.
> > > > mount shows that it has not been mounted, and if I try to mount it:
> > > >
> > > > bsd# mount -u /dev/ad1s2c /disk2
> > > > mount: /dev/ad1s2c on /disk2: specified device does not match mounted
> > > > device bsd# mount /dev/ad1s2c /disk2
> > > > mount: /dev/ad1s2c: Input/output error
> > > >
> > > > I looked at the previous thread and then tried:
> > > >
> > > > bsd# newfs /dev/ad1s2c
> > > > /dev/ad1s2c: 52627.0MB (107780084 sectors) block size 16384, fragment
> > > > size 2048
> > > > using 287 cylinder groups of 183.77MB, 11761 blks, 23552
> > > > inodes. super-block backups (for fsck -b #) at:
> > > > 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624,
> > > > 3010976, ...
> > > > 107260480, 107636832
> > > > cg 0: bad magic number
> > > >
> > > > I had two partitions on it, one to be used for linux later on. I
> > > > tried swapping them out, but no difference.
> > > >
> > > > This drive worked under linux. Any ideas?
> > >
> > > Sounds like you didn't write a disklabel on it.
> > > That's covered in the tutorial you mentioned...
> >
> > I used the disklabel tool in sysinstall. But it did not seem to do
> > anything...
>
> Try doing the disklabel from the command line, so you can show an
> exact transcript.
Here is what I have. Sorry it is not too helpful:
bsd# fdisk ad1
******* Working on device /dev/ad1 *******
parameters extracted from in-core disklabel are:
cylinders=4961616 heads=1 sectors/track=63 (63 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=4961616 heads=1 sectors/track=63 (63 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 102398247 (49999 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
sysid 131 (0x83),(Linux native)
start 102398310, size 210178395 (102626 Meg), flag 0
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
bsd# disklabel -B -w -r ad1s1 auto
disklabel: /dev/ad1s1 read: Input/output error
bsd# disklabel ad1
disklabel: /dev/ad1 read: Input/output error
I don't know why there are two partitions after the ones I meant to create.
The disklabel command comes from 17.3.2.1 of the handbook.
I saw the thread about DMA errors. When I have this new drive attached, I get
this (from dmesg) repeated many times:
ad1: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63
ad1: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED>
LBA=63
Could this problem be related?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200604131214.20271.oliver-mailinglist>