DragonFly BSD
DragonFly bugs List (threaded) for 2005-03
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: failing disk, or not?


From: "George Georgalis" <george@xxxxxxxxx>
Date: Tue, 29 Mar 2005 11:48:29 -0500
Mail-followup-to: bugs@crater.dragonflybsd.org

On Tue, Mar 29, 2005 at 12:25:04PM +0800, Bill Hacker wrote:

>>agp0: <NVIDIA Generic AGP Controller> mem 0xe0000000-0xe3ffffff at device 
>>0.0 on pci0
>>agp0: Unable to find NVIDIA Memory Controller 1.
>
>Unable? That's odd ?

At first I thought because video memory is shared with main memory,
but this board doesn't have onboard video, the add on card is NVIDIA
(like most of the components) so that doesn't make it any easier to
figure out. maybe onboard video was removed from this board, but not
completely... I've not setup x yet.

>>device_probe_and_attach: agp0 attach returned 19
>>isab0: <PCI to ISA bridge (vendor=10de device=00e0)> at device 1.0 on pci0
>>isa0: <ISA bus> on isab0
>>pci0: <unknown card> (vendor=0x10de, dev=0x00e4) at 1.1 irq 10
>
>NVIDIA  - nForce3 250 SMBus Controller ?

Was wondering about that too... maybe it has something to do with
the flash Memory Card Reader -- which I might be taking out because
it takes up a hd slot. This is a Shuttle SN85G4v3 AMD64 socket 754
http://global.shuttle.com/Product/Barebone/SN85G4%20V3.asp


>>atapci0: <Generic PCI ATA controller> port 0xf000-0xf00f at device 8.0 on 
>>pci0
>>ata0: at 0x1f0 irq 14 on atapci0
>>installed MI handler for int 14
>
>>ata1: at 0x170 irq 15 on atapci0
>>installed MI handler for int 15
>>atapci1: <Generic PCI ATA controller> port 
>>0xec00-0xec7f,0xeb00-0xeb0f,0xb70-0xb73,0x970-0x977,0xbf0-0xbf3,0x9f0-0x9f7 irq 11 at device 10.0 on pci0
>
>>ata2: at 0x9f0 on atapci1
>>installed MI handler for int 11
>
>>ata3: at 0x970 on atapci1
>
>*snip*
>
>>ad0: 58644MB <Maxtor 6Y060L0> [119150/16/63] at ata0-master BIOSDMA
>
>>ad4: DMA limited to UDMA33, non-ATA66 cable or device
>>ad4: 190782MB <ST3200822AS> [387621/16/63] at ata2-master BIOSDMA
>
>I'm puzzled:
>
>- ata0-master claims /dev/ad0
>
>- ata1-master claims /dev/acd0
>
>- ata2-master claims /dev/ad4
>
>- ata3 seems empty...
>
>So how do we skip /dev/ad1, /dev/ad2, and /dev/ad3 to arive at /dev/ad4?

there is a cdrom drive on one of the primary or secondary ide channels,
an ata disk hanging outside (on the other channel) and the primary
disk is on an sata controler, the flash memory slots appear as drives
(without media) as well. The ordering in bios is default. if that helps
make any sense of it.



>>Mounting root from ufs:/dev/ad4s3a
>
>>ad4: UDMA ICRC error writing fsbn 249842603 of 110387664-110387679 (ad4 bn 
>>249842603; cn 15551 tn 250 sn 38) retrying
>>ad4: UDMA ICRC error writing fsbn 249842603 of 110387664-110387679 (ad4 bn 
>>249842603; cn 15551 tn 250 sn 38) retrying
>>ad4: UDMA ICRC error writing fsbn 249842603 of 110387664-110387679 (ad4 bn 
>>249842603; cn 15551 tn 250 sn 38) retrying
>>ad4: UDMA ICRC error writing fsbn 488278315 of 229605520-229605535 (ad4 bn 
>>488278315; cn 30393 tn 234 sn 28) retrying
>>ad4: UDMA ICRC error writing fsbn 488278315 of 229605520-229605535 (ad4 bn 
>>488278315; cn 30393 tn 234 sn 28) retrying
>>ad4: UDMA ICRC error writing fsbn 488278443 of 229605584-229605599 (ad4 bn 
>>488278443; cn 30393 tn 236 sn 30) retrying
>>
>>
>You are on slice2, presumably well up in the cylinder count.
>Might the areas above be a geometry mapping conflict?

well, slice 3 if you count from 1, I'm never completely sure.
Thanks for the comments, more followup to Matt's post shortly.

// George


-- 
George Georgalis, systems architect, administrator Linux BSD IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:george@xxxxxxxxx



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]