thus Urban Boquist spake:
> Timo> please add this quirk for another this, the Seagate ST3160023A
> Timo> (160GByte, 7.200rpm, 8MByte Cache).
> 
> Timo> before applying the patch the machine crashed when builing
> Timo> RAIDframe, with patch applied (i did it for 2.0.2-RELEASE, too)
> Timo> it runs fine.
> 
> Are you sure that it really is the drive that is the problem?

think so -- a few days before another Seagate showed this problem. the
machine runs well for me, i'll give it another try on a different
controller, if this were of any help.

> Maybe
> that quirk is just masquerading some other problem with your
> system. Did you try the drive in some other machine?

i have a few HP Visualize X-Class machines (one of them with the
problem); those are my only x86 machines, and i only bought them to
replace some sparc64 machines i'm about to sell. so the only thing i can
do is to test on another controller :/

> I'm asking because I have been running a "ST3160023AS" for a long time
> without any problems at all. Yes, I know it's not identical, but
> still... ;-) 

weird (at least to me), i don't think that Seagate writes a new firmware
for every model they release. and as some of the other models show
problems...

> Best regards,
> 
>         -- Urban
> 

thanks & regards,

timo

> 
> Timo> --- wd.c 2005-06-20 12:53:48.000000000 +0200
> Timo> +++ wd.c.orig 2005-06-20 12:05:46.000000000 +0200
> Timo> @@ -235,8 +235,6 @@
> Timo> * (aka LBA48_THRESHOLD) in LBA mode. The workaround is to force
> Timo> * LBA48
> Timo>          */
> Timo> - { "ST3160023A",
> Timo> - WD_QUIRK_FORCE_LBA48 },
> Timo>         { "ST3200822A",
> Timo>           WD_QUIRK_FORCE_LBA48 },
> Timo>         { "ST3200822AS",
> 
> 
> Timo> thanks,
> 
> Timo> timo
> 
> Timo> ps: filed kern/30563 for this, just to make sure.