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: Sat, 31 May 2025 09:21:56 +0100 [thread overview]
Message-ID: <13774716.uLZWGnKmhe@rogueboard> (raw)
In-Reply-To: <e322c280-50fb-e3fa-d840-668488ad00ec@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1818 bytes --]
On Friday, 30 May 2025 22:06:03 British Summer Time Dale wrote:
> Michael wrote:
> > You can transfer some data from a tmpfs and measure the speed. If it gets
> > anywhere near 4.8 Gbit/s (600 MB/s) its a SATA 3. The delay in the kernel
> > picking it up at boot may be related to its size, but I have no experience
> > of such large drives to be able to confirm this.
>
> When I started reading your reply, I realized I had that drive in the
> older external enclosure connected to my main rig. I'm not sure if it
> is SATA 3 capable or not. I need to research the specs on that
> enclosure. It works fine for running self tests tho. Anyway, I
> connected it to my NAS box. On it, it reads at speeds that make me
> think it is SATA 3. It's around 250MB/sec with hdparm -t which is
> normal on most all my rigs.
I corrected my statement above, which referred to the max speed of SATA 3
interface rather than the drive itself. As Frank noted in real life the drive
only achieves a fraction of this. Your 250MB/sec read rate is what you can
expect.
[snip ...]
> I'm surprised by the speed of the OS drive tho. It is a SSD drive.
> Anyway, as one can see, some drives are connected at SATA 2 and some at
> SATA3. Now I noticed, the 4 drive set is connected to a PCIe card. The
> three drive set and the OS drive is connected to the mobo itself. This
> makes me wonder, is the mobo ports only SATA 2? I went and looked at
> the manual that shows a block diagram and what is what. Sure enough,
> the mobo ports are SATA 2 or 3GBs/sec. Well, that explains that.
Aha! Yes, that explains it.
> I can't believe that mobo is SATA 2 tho. I could have sworn it was SATA
> 3.
>
> Dale
>
> :-) :-)
I recall mentioning at the start of this thread you should check the MoBo's
SATA port spec. ;-)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-05-31 8:23 UTC|newest]
Thread overview: 28+ 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
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
2025-05-30 13:46 ` Frank Steinmetzger
2025-05-30 1:25 ` Dale
2025-05-30 10:56 ` Michael
2025-05-30 13:47 ` Frank Steinmetzger
2025-05-30 15:10 ` Michael
2025-05-30 21:06 ` Dale
2025-05-31 8:21 ` Michael [this message]
2025-06-01 2:51 ` Dale
2025-06-01 11:02 ` Frank Steinmetzger
2025-06-01 12:20 ` Dale
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=13774716.uLZWGnKmhe@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