Cable or Dead Hard Disk

[Mailing Lists Catcher]

Why not try changing out the cable and see if the problem persists?

Also Maxtor has a nice drive testing utility that runs from a bootable
floppy.  And they work for all drive types...I use them on my WD and IBM
drives when I suspect trouble or before I bring an old HD out of
retirement.

Jason

On Sun, 2003-10-12 at 19:50, Rus Foster wrote:
> Hi All,
> I got the following on a new server with vinum. Is this a cabling issue or
> a DOA hard disk
> 
> 
> Mounting root from ufs:/dev/vinum/root
> ad3s1e: UDMA ICRC error reading fsbn 721 of 329-344 (ad3s1 bn 721; cn 0 tn
> 11 sn                                               28) retrying
> ad3s1e: UDMA ICRC error reading fsbn 721 of 329-344 (ad3s1 bn 721; cn 0 tn
> 11 sn                                               28) retrying
> ad3s1e: UDMA ICRC error reading fsbn 721 of 329-344 (ad3s1 bn 721; cn 0 tn
> 11 sn                                               28) retrying
> ad3s1e: UDMA ICRC error reading fsbn 721 of 329-344 (ad3s1 bn 721; cn 0 tn
> 11 sn                                               28) falling back to
> PIO mode
> vinum: usr.p1.s0 is up by force
> vinum: usr.p1 is up
> vinum: usr.p1.s0 is up
> ad3: WRITE command timeout tag=0 serv=0 - resetting
> ata1: resetting devices ..
> ad3: removed from configuration
> done
> vinum: root.p1.s0 is stale by force
> vinum: root.p1 is faulty
> fatal :root.p1.s0 write error, block 90473 for 8192 bytes
> root.p1.s0: user buffer block 90208 for 8192 bytes
> root2: fatal drive I/O error, block 90473 for 8192 bytes
> vinum: drive root2 is down
> vinum: Can't write config to /dev/ad3s1f, error 6
> vinum: drive usr2 is down
> vinum: usr.p1.s0 is crashed
> vinum: usr.p1 is faulty
> vinum: Can't write config to /dev/ad3s1g, error 6
> vinum: drive home2 is down
> vinum: home.p1.s0 is crashed
> vinum: usr.p1.s0 is stale by force
> vinum: home.p1.s0 is stale by force
> 
> Thanks
> 
> Rus
>