> ... but trying my 160 Gbyte Maxtor DiamondMax 16:
> /usr/sbin/smartctl -a /dev/hdd
> returned with an error message and the suggestion
> to try:
> /usr/sbin/smartctl -s on /dev/hdd
> which in turn failed, and suggested adding something
> like "-T permissive". This hung Windows.
Do you remember the error messages, especially the one later ignored by
> ... On rebooting,
> the BIOS failed to detect the Maxtor disk, and it was
> making clicking noises.
> I removed the disk and placed it in an external USB
> enclosure. The clicking noises continued, and neither
> Windows nor Linux can see the disk.
Last year, I had exactly the same failure (clicking, no detection on
next boot) on two Maxtor disks, 4K060H3 and 6Y120P0. There was no
smartctl, SMART BIOS setting or similar involved. (BTW: actually, with
these crashes, my interest in SMART began and eventually leads to the
smartctl windows port).
I tried to connect the disks to several (~8) different PCs.
Surprisingly, the BIOS of some old PIII detected the 60Gb disk. Many
sectors of the disk were damaged, but I was able to save most of the data.
This worked only on this specific PC, I never found out why (different
IDE command sequences during initialization, Power supply voltage
All other PCs did not detect any of the two disks. Sometimes, a "funny"
drive name was shown after power up. The 120Gb disk was only 3 weeks old
and powered on at most 3 hours/day. Maxtor specific problem?
As Bruce already pointed out, it is unlikely that the disk crash is
related to some bug smartctl itself. The windows code was tested
thoroughly on several windows machines. The windows SMART_IOCTL does not
allow to send any possibly dangerous non-SMART IDE commands to the
drive. Only for READ_LOG, another ioctl is used, but this is not used
during "smartctl -s on" (see WARNINGS file).