From: Dale <rdalek1967@gmail.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, 6 May 2025 19:16:37 -0500 [thread overview]
Message-ID: <de53645e-c898-602f-8567-ca6277cc4d21@gmail.com> (raw)
In-Reply-To: <7ed62ad2-c2b1-4f05-ad75-641f951e740d@youngman.org.uk>
Wol wrote:
> On 06/05/2025 21:51, Dale wrote:
>> 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.
>
> Did you ADD that drive to all the others when it came up with that
> message? Is it possible that the drain of that extra drive caused a
> brown-out in the enclosure?
>
> I know I've had systems where the power had trips in to bring the
> drives up with random delays (mini-computers) because the system was
> quite capable of powering running drives, but couldn't provide the
> necessary boot-up surge to all the drives simultaneously.
>
> Cheers,
> Wol
>
> .
>
The other drives are in the safe. The only drives connected are the SSD
for the OS and this one drive. Originally, I was going to use the
external enclosure connected to my main rig to just test the drive.
When I saw the slow data connection speed, I removed it from the
enclosure and hooked it to the NAS box. I wanted to be sure it was the
enclosure causing the slow data connection. It appears that enclosure
is SATA 2 or something. Anyway, it was when I connected to the NAS box
as a bare drive that I noticed the slow to respond message. It may have
been there on my main rig as well but I just didn't notice it. I
usually use tail -f to watch and hit the return key a few times to
separate what I want to watch from the normal logging. It may have done
the same on my main rig and I missed it. I sometimes forget to hit
return a few times.
At this point, I don't know if I should return this drive or keep it as
is. I don't know if this is a problem with this drive or normal for
some drives to be slow to respond at times. I don't recall ever seeing
it before.
Dale
:-) :-)
next prev parent reply other threads:[~2025-05-07 0:17 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
2025-05-06 20:51 ` Dale
2025-05-06 23:08 ` Wol
2025-05-07 0:16 ` Dale [this message]
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=de53645e-c898-602f-8567-ca6277cc4d21@gmail.com \
--to=rdalek1967@gmail.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