failing disk, or not?

[George Georgalis]

On Mon, Mar 28, 2005 at 07:44:24PM -0800, Matthew Dillon wrote:
>
>:I'm seeing some disk errors in dfly that I cannot reproduce with other
>:OS checking the partition:
>:
>: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
>
>    This doesn't sound like a disk failure to me.  It sounds like a driver
>    problem.
>
>: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
>:ad4: DMA limited to UDMA33, non-ATA66 cable or device
>:ad4: 190782MB <ST3200822AS> [387621/16/63] at ata2-master BIOSDMA
>
>    That's not good.  It can't identify the controller.  It's amazing that
>    it works at all.
>
>    Could you run pciconf -l?

Well no. This morning I did cvsup to "." from DragonFly_Stable and now
I get:

# lspci -l
ELF binary type "0" not known.
Abort
# 

the 1/2 dozen other commands I tried worked...


>:Don't see it in dmesg, but ad4 is a 200Gb Seagate drive, on a nvidia
>:sata controler.  Disk Product Number ST3200822AS, Part Number 9W2854-301
>:
>
>    Update to the latest, just in case recent big fixes might have
>    something to do with the lockup you experienced. 

After serious disk thrashing last night, I was unable to reproduce a
disk error in linux.

I have a cvsup from HEAD this morning and 

cd /usr/src/sys/i386/conf
mkdir -p /root/kernels
cp GENERIC /root/kernels/MYKERNEL   
ln -sf /root/kernels/MYKERNEL
cd /usr/src \
 && make buildworld \
 && make buildkernel KERNCONF=MYKERNEL \
 && make installkernel KERNCONF=MYKERNEL \
 && make preupgrade \
 && make installworld \
 && make upgrade \
 && echo a-okay

. ..
# uname -a
DragonFly . 1.1-CURRENT DragonFly 1.1-CURRENT #5: Tue Mar 29 14:55:45 GMT 2005     root at .:/usr/obj/usr/src/sys/MYKERNEL  i386

This is a Shuttle SN85G4v3 amd64 socket 754
http://global.shuttle.com/Product/Barebone/SN85G4%20V3.asp

not sure what to make of the lspci error.

// George


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