Michael wrote:
> On Tuesday, 6 May 2025 13:59:16 British Summer Time Dale wrote:
>> Michael wrote:
>>> Initially I'd be suspecting the SATA cable/port, but if you tried another
>>> MoBo did you also try a different SATA cable?
>>>
>>> Were the ports you connected to compatible with SATA 3 revision capable of
>>> 6Gb/s?  Notwithstanding the warnings and errors you'd want the highest
>>> transfer speed you can get on a new drive.
>> I think the speed issue might be that external enclosure I used.  I've
>> got two of those I think.  The other external enclosures work at full
>> speed tho.  
> Try one of your SATA 3 enclosures.
>
> Try a different SATA/eSATA cable depending on connecting the drive internally/
> externally.

I was only using the enclosure to test the drive while connected to my
main rig.  I'm not planning to leave it in there once the testing is
done.  I'm not one to buy a drive and put data on it right away.  I test
first then once it is proven to be good, then I put data on it.  When I
saw the slow data speed connection, I suspected the enclosure, never
used it to test a drive before, so I moved the drive to my NAS box rig
where I could connect it directly and remove any doubt about something
in the middle causing problems.  When I put it on the NAS box, I used
the same power cable and data cable that I use to update my backups and
it works without error.  I don't see how it can be the data cable, power
or mobo in this case.  All those work fine when doing backups.  It
powers 4 hard drives in that setup.  Soon to be 5 drives. 

>
>> The concern I have mostly is the slow part when hooked to the NAS mobo
>> directly.  I have a good size power supply for that old thing.  It
>> likely runs at about a 20% load most of the time.  The most excitement
>> it sees is when I do OS updates and backup updates at the same time. 
>> LOL  I included that first error just in case it may be relevant to the
>> one from the NAS box about being slow. 
> I think the messages you received show the drive is slow to initialize, which 
> could be an issue with low power, or poor cable connection.
>
>
>> When I did some searches for that error, I never found a real answer to
>> the question.  Is that normal for some drives or a sign of future
>> failure?  It's a 20TB Seagate EXOS Enterprise drive.  Maybe it has a
>> extra platter which takes longer to spin up or something and it is
>> normal.  Then again, maybe it is a weak motor that is about to fail. 
>> Some stuff I found claimed it was a kernel error.  I've never seen that
>> on either of my systems and I been using those same kernels for a long
>> time.  As most know, I have quite a few large drives here. o_O
>>
>> As far as I know, all my rigs are SATA 3 ready. 
> If you connect a SATA 3 capable drive to a SATA 3 controller you should get 
> SATA 3 speeds.  In the messages you shared I SATA 1 and SATA 2 speeds only.  
> If you've tried different cables and the SATA ports are definitely SATA 3, 
> then the problem must be related to the drive.
>
> You could try disconnecting all other spinning drives from the MoBo, connect 
> ST20000NM007D and boot with the latest adminCD to see what messages you get.


The only other drive connected is a SSD for the OS.  As mentioned above,
this is what I use to connect a 4 drive setup for my backups.  I even
use the same power connector.  I also used one of the same data cables. 
I might add, I just tested a 16TB drive and it worked without error of
any kind.  It's in the safe while I figure out which drive, 16TB or
20TB, is going to be added to my backup drives and which will be added
to my main rig. 

So far, this is the first drive I've ever seen this 'slow to respond'
message with before.  Since I've never seen it before, curious as to
what it means exactly and is it normal?  Searching didn't help.  Some
claim kernel, others claim something else. 

As soon as this test completes, another few hours to go yet, I'm going
to power cycle the drive again to see what it does.  I may cycle it a
few times to see if it is a consistent problem as well. 

Dale

:-)  :-) 

Reply via email to