The following reply was made to PR kern/31003; it has been noted by GNATS.

From: Carl Brewer <carl@bl.echidna.id.au>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/31003
Date: Thu, 13 Apr 2006 16:58:00 +1000

 for what it's worth, I still see random total machine
 hangs with the same hardware - ViPower and 160GB IDE HDD
 and swapped hardware, but the same - just new disk drives and caddies
 etc) on 3.0/i386
 
 dmesg shows :
 
 umass0 at uhub4 port 3 configuration 1 interface 0
 umass0: ViPowER, Inc. ViPowER USB2.0 Storage Device, rev 2.00/0.01, addr 2
 umass0: using SCSI over Bulk-Only
 scsibus0 at umass0: 2 targets, 1 lun per target
 sd0 at scsibus0 target 0 lun 0: <ST316002, 1A, 0\0000> disk fixed
 sd0: 149 GB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808 sectors
 
 It shows a lot of this in dmesg :
 
 sd0: dos partition I/O error
 sd0(umass0:0:0:0):  Check Condition on CDB: 0x28 00 00 00 00 00 00 00 01 00
      SENSE KEY:  Aborted Command
       ASC/ASCQ:  Logical Unit Communication CRC Error
 
 sd0(umass0:0:0:0):  Check Condition on CDB: 0x28 00 00 00 00 00 00 00 01 00
      SENSE KEY:  Aborted Command
       ASC/ASCQ:  Logical Unit Communication CRC Error
 
 sd0(umass0:0:0:0):  Check Condition on CDB: 0x28 00 00 00 00 00 00 00 01 00
      SENSE KEY:  Aborted Command
       ASC/ASCQ:  Logical Unit Communication CRC Error
 
 sd0(umass0:0:0:0):  Check Condition on CDB: 0x28 00 00 00 00 00 00 00 01 00
      SENSE KEY:  Aborted Command
       ASC/ASCQ:  Logical Unit Communication CRC Error
 
 sd0(umass0:0:0:0):  Check Condition on CDB: 0x28 00 00 00 00 00 00 00 01 00
      SENSE KEY:  Aborted Command
       ASC/ASCQ:  Logical Unit Communication CRC Error
 
 Does the above suggest a hardware problem or a problem with
 the umass driver?
 
 
 Is anyone looking at this or doing anything similar?  I'm
 trying (but having no luck!) to use these removable HDDs
 for backup devices, by mounting them, dumping the FS, and
 umounting so the users at the site can take the HDD home as
 an offsite backup.