Jump to content

Talk:Seagate ST1

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Untitled

[edit]

Quoted from the article: All ST1 drives have "For Embedded Application Only" printed on the back of them, which has led some people to think that the CF mode required for use in digital cameras is disabled. This is in fact not true and was most likely put there to remind the user that the drive was not designed for continuous use in a desktop computer. A casual glance at the numerous messageboard questions from users who have had problems getting "For Embedded Application Only" marked drives to work suggests that this text is not correct, or is at least partially incorrect. —Preceding unsigned comment added by 93.97.143.19 (talk) 22:22, 6 May 2010 (UTC)[reply]

ST1 diagnostics

[edit]

Hi, seems a lot of these are failing because of very simple design flaws. One of which is that the 2MB buffer chip can go bad due to electromigration from the heat, if drive is kept cool then it lasts a lot longer. This part can in fact be replaced though more difficult than conventional HDDs as the ST1 is a lot harder to remove the PCB on. Another known fault is failing magnets in the motor and head seek mechanism due to heat build-up but this is difficult to repair: symptoms include excess power usage as the drive tries and fails to seek, clicking etc and eventually failure to spin up. A good way to detect it is measuring power usage over time: any increase suggests imminent failure. This technique incidentally works on any hard drive but monitoring vibrations from the motor can yield valuable information. — Preceding unsigned comment added by 91.190.161.223 (talk) 10:09, 15 February 2020 (UTC) The author is also working on a 5GB drive in external modified CF "flat" reader as it has internal problems already though manufacturer diagnostics seem to suggest any damage is minimal This paper is being published shortly on Hackaday or some other forum as it is considered of general interest under "Fair Use".[reply]