Mike Tancsa wrote: > I hooked up a Vantec eSata enclosure using a SATA to eSATA cable off the > main motherboard. One small difference I noticed is that camcontrol > does not get the info from the drive like it does on other devices. > Perhaps thats the enclosure messing things up ? > > 0(ich10)# camcontrol identify ada2 > pass2: < > ATA/ATAPI-0 device That's strange. IDENTIFY is a basic ATA command, which must work always. > There was a previous drive connected. We powered off the external > drive, disconnected the cable, hooked up the new drive, powered up the > enclosure and then I did a camcontrol rescan all > > Jul 4 20:19:22 ich10 kernel: (ada2:ahcich2:0:0:0): lost device > Jul 4 20:19:22 ich10 kernel: (ada2:ahcich2:0:0:0): removing device entry > Jul 4 20:19:37 ich10 kernel: (probe0:ahcich2:0:0:0): SIGNATURE: 0000 > Jul 4 20:19:37 ich10 kernel: ada2 at ahcich2 bus 0 target 0 lun 0 > Jul 4 20:19:37 ich10 kernel: ada2: <ST3750330AS SD15> ATA/ATAPI-8 SATA > 1.x device > Jul 4 20:19:37 ich10 kernel: ada2: 150.000MB/s transfers > Jul 4 20:19:37 ich10 kernel: ada2: 715404MB (1465149168 512 byte > sectors: 16H 63S/T 16383C) > Jul 4 20:19:37 ich10 kernel: ada2: Native Command Queueing Enabled Looking to this, it was working. > The drive we connected has some bad sectors, so I wanted to try a secure > wipe as much as possible before RMAing the drive. I also thought it > would be useful to test with the new driver how it handles bad disks > > Is this such an error ? > > Jul 4 20:25:57 ich10 kernel: ahcich2: ahci_ch_intr ERROR is 40000001 cs > 00000004 ss 00000000 rs 00000004 tfd 451 serr 00000000 This is AHCI driver debugging. I've removed it in latest patch. In this case it means that drive signals some command error. -- Alexander MotinReceived on Sun Jul 05 2009 - 04:41:32 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:51 UTC