Not sure this is timely info as the Seagate ST336753LW has been around a while, but wanted to share a recent experience because this forum has helped me in the past:
Had a new spare pair of ST336753LW drives on the shelf for several years. Finally installed them as Drive 0/1 this week RAID1 in a workstation with an onboard AIC-7901 controller.
First boot after installation was fine, but subsequently Drive 1 gave sense key 02h, code 04h, qual 02h (not spinning up).
Searched extensively online for suggestions. Had a problem with a different drive last year and knew about
Hydata but didn't buy because of high cost. Plus, not sure those tools would have worked on last year's problem drive or the current one.
Frustrated by the fact that the drive did work for a short time and then quit, and that it might be out of warranty having been purchased a while back though not yet used, tried several things over the course of many hours.
What finally worked was to temporarily make the problem drive Drive 0 and the remaining good RAID1 member Drive 1 (J6 jumper block). Also temporarily rearranged the SCSI bus (cable) so that the problem Drive 0 was at the end, with the terminator.
Then went into the SCSI configuration area (for this controller, CTRL+A) and looked at the RAID1 drives. Because they were now reversed, both were listed as members but both had ID 1. Obviously not correct. Came to the tentative conclusion that the RAID management utility cannot dynamically update when drive IDs are changed. Didn't proceed further.
Put drives back to original Drive 0/Drive 1 configuration and rebooted. All drives spun up during the SCSI bus scan. (In addition to the RAID1 drive pair, there is a 3rd SCSI drive in this system.)
Went back into the SCSI RAID configuration area and found everything back to normal, except Drive 1 showing as degraded which was expected.
Repaired the array and we've been good to go (so far).