From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New hard drive. Is this normal? It looks like a connect problem.
Date: Tue, 06 May 2025 15:31:51 +0100 [thread overview]
Message-ID: <2003865.PYKUYFuaPT@rogueboard> (raw)
In-Reply-To: <348d3e3c-1084-013e-1a29-0cf1668c5b7e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2309 bytes --]
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.
> 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.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-05-06 14:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 21:15 [gentoo-user] New hard drive. Is this normal? It looks like a connect problem Dale
2025-05-06 12:12 ` Michael
2025-05-06 12:59 ` Dale
2025-05-06 14:31 ` Michael [this message]
2025-05-06 20:51 ` Dale
2025-05-06 23:08 ` Wol
2025-05-07 0:16 ` Dale
2025-05-06 23:30 ` Dale
2025-05-07 8:18 ` Michael
2025-05-07 15:13 ` Dale
2025-05-10 15:53 ` Dale
2025-05-10 18:52 ` Michael
2025-05-12 8:11 ` Dale
2025-05-12 11:14 ` Michael
2025-05-13 6:30 ` Dale
2025-05-12 22:34 ` Frank Steinmetzger
2025-05-13 6:05 ` Dale
2025-05-13 8:30 ` Michael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2003865.PYKUYFuaPT@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox