I have a similar problem with a Seagate ST3146854LC.
The Adaptec 39320A-R SCSI card, when interrogating this drive, stops with a message:
Backup you data, the drive exceeds SMART threshold parameters, imminent failure may occur.
First time I’ve ever seen this from an HBA.
I then extensively tested the drive, with Seagate diagnostic tools, and professional SCSI software.
None of the test revealed, even a slightest error condition, with the drive’s mechanical components, or SMART parameters.
Like you, I also manually hit enter to continue with the boot sequence; a total unresolved mystery.
The only possible connection I’ve found is that the drive’s firmware is proprietary for a Linux operating system: Originally used for asynchronous data transfer:
I reformatted the drive for windows and modified transfer for U320 interface, possibly producing a false positive errors with the HBA.
If your drive is attached to a regular SCSI controller, make sure, aside from the drive's ID jumper, that additional pins are inserted on the drive creating conflicts between the HBA and drive.
Current SCSI controllers have a section in the BIOS to control parameters previously modified with jumper-pins on the drives: termination, spin-up, interface etc.
Verify the SCSI controller parameters are properly set in BIOS, and no additional jumpers are present on the drive.
Chipstone
525 Posts
0
August 25th, 2006 18:00
The Adaptec 39320A-R SCSI card, when interrogating this drive, stops with a message:
Backup you data, the drive exceeds SMART threshold parameters, imminent failure may occur.
First time I’ve ever seen this from an HBA.
I then extensively tested the drive, with Seagate diagnostic tools, and professional SCSI software.
None of the test revealed, even a slightest error condition, with the drive’s mechanical components, or SMART parameters.
Like you, I also manually hit enter to continue with the boot sequence; a total unresolved mystery.
The only possible connection I’ve found is that the drive’s firmware is proprietary for a Linux operating system: Originally used for asynchronous data transfer:
I reformatted the drive for windows and modified transfer for U320 interface, possibly producing a false positive errors with the HBA.
If your drive is attached to a regular SCSI controller, make sure, aside from the drive's ID jumper, that additional pins are inserted on the drive creating conflicts between the HBA and drive.
Current SCSI controllers have a section in the BIOS to control parameters previously modified with jumper-pins on the drives: termination, spin-up, interface etc.
Verify the SCSI controller parameters are properly set in BIOS, and no additional jumpers are present on the drive.