G
Gerry
I have had a disk connection problem which seems to relate to failing sata
cables. The BIOS has failed intermittently to detect one or both hard
drives. The problem was more obvious with the master drive so I replaced the
cable 14 days ago and there was no further problem until this morning. The
problem this morning was the slave drive so I have replaced the cable for
that drive. It has now been working for a bit over two hour.
The problem first became apparent a month ago when I found the system would
freeze after it had been running some time. Resetting sometimes worked and
sometimes resulted in a failed boot. Eventually the system would boot but
the problem would happen again some hours later or the next day. Sometimes
there have been Event Viewer reports -mainly ID: 11 referring to the
Controller. Often the problem is unreported. This is probably because the
Error is occurring before Event Viewer starts.
From a friend I got these comments.
"In my view, the SATA 'Connector' is an engineering blunder. A sort-of flat
sleeve slides over a notched part on the edge of the board whereupon sit
some exposed/un-insulated traces. Flat conductors encased within a plastic
bit are slid into contact with them. There is no mechanism but friction to
keep the 'connector' in place. Entirely inadequate. It is not designed for
repeated make/break insertion/removal. If subjected even to a low number of
such operations (design spec is 50), it will fail. (5 000 for an eSATA
connector). If I have to repeatedly disconnect-connect a drive during
testing, I replace the cable as a matter of routine."
I am interested in knowing whether others have encountered this problem and
how common place it is?
TIA
--
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
cables. The BIOS has failed intermittently to detect one or both hard
drives. The problem was more obvious with the master drive so I replaced the
cable 14 days ago and there was no further problem until this morning. The
problem this morning was the slave drive so I have replaced the cable for
that drive. It has now been working for a bit over two hour.
The problem first became apparent a month ago when I found the system would
freeze after it had been running some time. Resetting sometimes worked and
sometimes resulted in a failed boot. Eventually the system would boot but
the problem would happen again some hours later or the next day. Sometimes
there have been Event Viewer reports -mainly ID: 11 referring to the
Controller. Often the problem is unreported. This is probably because the
Error is occurring before Event Viewer starts.
From a friend I got these comments.
"In my view, the SATA 'Connector' is an engineering blunder. A sort-of flat
sleeve slides over a notched part on the edge of the board whereupon sit
some exposed/un-insulated traces. Flat conductors encased within a plastic
bit are slid into contact with them. There is no mechanism but friction to
keep the 'connector' in place. Entirely inadequate. It is not designed for
repeated make/break insertion/removal. If subjected even to a low number of
such operations (design spec is 50), it will fail. (5 000 for an eSATA
connector). If I have to repeatedly disconnect-connect a drive during
testing, I replace the cable as a matter of routine."
I am interested in knowing whether others have encountered this problem and
how common place it is?
TIA
--
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~