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 07:59:16 -0500 [thread overview]
Message-ID: <348d3e3c-1084-013e-1a29-0cf1668c5b7e@gmail.com> (raw)
In-Reply-To: <4981413.GXAFRqVoOG@rogueboard>
Michael wrote:
> On Monday, 5 May 2025 22:15:52 British Summer Time Dale wrote:
>> Howdy,
>>
>> I ran up on a couple deals. I first bought a 16TB drive which worked
>> fine. Then I saw a deal on a 20TB drive. I first put it in a external
>> enclosure and connected it by eSATA cable to my new rig. I got this in
>> messages.
>>
>>
>> May 5 15:41:31 Gentoo-1 kernel: ata4: found unknown device (class 0)
>> May 5 15:41:40 Gentoo-1 kernel: ata4: softreset failed (1st FIS failed)
>> May 5 15:41:41 Gentoo-1 kernel: ata4: found unknown device (class 0)
>> May 5 15:41:50 Gentoo-1 kernel: ata4: softreset failed (1st FIS failed)
>> May 5 15:41:51 Gentoo-1 kernel: ata4: found unknown device (class 0)
>> May 5 15:41:59 Gentoo-1 kernel: ata4: found unknown device (class 0)
>> May 5 15:41:59 Gentoo-1 kernel: ata4: SATA link up 1.5 Gbps (SStatus
>> 113 SControl 300)
>> May 5 15:41:59 Gentoo-1 kernel: ata4: link online but 1 devices
>> misclassified, retrying
>> May 5 15:41:59 Gentoo-1 kernel: ata4: reset failed (errno=-11),
>> retrying in 27 secs
>> May 5 15:42:26 Gentoo-1 kernel: ata4: SATA link up 1.5 Gbps (SStatus
>> 113 SControl 300)
>> May 5 15:42:26 Gentoo-1 kernel: ata4.00: ATA-11: ST20000NM007D-3DJ103,
>> SN05, max UDMA/133
>> May 5 15:42:26 Gentoo-1 kernel: ata4.00: 39063650304 sectors, multi 16:
>> LBA48 NCQ (depth 32), AA
>> May 5 15:42:26 Gentoo-1 kernel: ata4.00: Features: NCQ-sndrcv
>> May 5 15:42:26 Gentoo-1 kernel: ata4.00: configured for UDMA/133
>> May 5 15:42:26 Gentoo-1 kernel: scsi 3:0:0:0: Direct-Access
>> ATA ST20000NM007D-3D SN05 PQ: 0 ANSI: 5
>> May 5 15:42:26 Gentoo-1 kernel: sd 3:0:0:0: Attached scsi generic sg2
>> type 0
>> May 5 15:42:26 Gentoo-1 kernel: sd 3:0:0:0: [sdk] 39063650304 512-byte
>> logical blocks: (20.0 TB/18.2 TiB)
>> May 5 15:42:26 Gentoo-1 kernel: sd 3:0:0:0: [sdk] 4096-byte physical blocks
>> May 5 15:42:26 Gentoo-1 kernel: sd 3:0:0:0: [sdk] Write Protect is off
>> May 5 15:42:26 Gentoo-1 kernel: sd 3:0:0:0: [sdk] Mode Sense: 00 3a 00 00
>> May 5 15:42:26 Gentoo-1 kernel: sd 3:0:0:0: [sdk] Write cache: enabled,
>> read cache: enabled, doesn't support DPO or FUA
>> May 5 15:42:26 Gentoo-1 kernel: sd 3:0:0:0: [sdk] Preferred minimum I/O
>> size 4096 bytes
>> May 5 15:42:26 Gentoo-1 kernel: sd 3:0:0:0: [sdk] Attached SCSI disk
>>
>>
>> I thought it might be the enclosure so I booted up my NAS box, removed
>> the drive from the enclosure and connected it bare by SATA cable to the
>> NAS box mobo SATA connector. This is what NAS box shows.
>>
>>
>> May 5 16:00:20 nas kernel: ata4: link is slow to respond, please be
>> patient (ready=0)
>> May 5 16:00:24 nas kernel: ata4: found unknown device (class 0)
>> May 5 16:00:24 nas last message buffered 1 times
>> May 5 16:00:24 nas kernel: ata4: SATA link up 3.0 Gbps (SStatus 123
>> SControl 300)
>> May 5 16:00:24 nas kernel: ata4: link online but 1 devices
>> misclassified, retrying
>> May 5 16:00:30 nas kernel: ata4: link is slow to respond, please be
>> patient (ready=0)
>> May 5 16:00:34 nas kernel: ata4: found unknown device (class 0)
>> May 5 16:00:34 nas last message buffered 1 times
>> May 5 16:00:34 nas kernel: ata4: SATA link up 3.0 Gbps (SStatus 123
>> SControl 300)
>> May 5 16:00:34 nas kernel: ata4: link online but 1 devices
>> misclassified, retrying
>> May 5 16:00:40 nas kernel: ata4: link is slow to respond, please be
>> patient (ready=0)
>> May 5 16:00:42 nas kernel: ata4: SATA link up 3.0 Gbps (SStatus 123
>> SControl 300)
>> May 5 16:00:42 nas kernel: ata4.00: ATA-11: ST20000NM007D-3DJ103, SN05,
>> max UDMA/133
>> May 5 16:00:42 nas kernel: ata4.00: 39063650304 sectors, multi 16:
>> LBA48 NCQ (depth 32), AA
>> May 5 16:00:42 nas kernel: ata4.00: Features: NCQ-sndrcv
>> May 5 16:00:42 nas kernel: ata4.00: configured for UDMA/133
>> May 5 16:00:42 nas kernel: scsi 3:0:0:0: Direct-Access ATA
>> ST20000NM007D-3D SN05 PQ: 0 ANSI: 5
>> May 5 16:00:42 nas kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0
>> May 5 16:00:42 nas kernel: sd 3:0:0:0: [sdb] 39063650304 512-byte
>> logical blocks: (20.0 TB/18.2 TiB)
>> May 5 16:00:42 nas kernel: sd 3:0:0:0: [sdb] 4096-byte physical blocks
>> May 5 16:00:42 nas kernel: sd 3:0:0:0: [sdb] Write Protect is off
>> May 5 16:00:42 nas kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read
>> cache: enabled, doesn't support DPO or FUA
>> May 5 16:00:42 nas kernel: sd 3:0:0:0: [sdb] Preferred minimum I/O size
>> 4096 bytes
>> May 5 16:00:42 nas kernel: sd 3:0:0:0: [sdb] Attached SCSI removable disk
>>
>>
>> Connected directly, no external enclosure, it connects at normal speed.
>> Maybe the enclosure limits the speed??? What concerns me with the NAS
>> box info, the first part about slow to respond. Is that normal? Also,
>> is it likely since it works on the NAS box at full speed that the
>> enclosure is causing the slow down or is that slow to respond a possible
>> cause?
>>
>> I ran the conveyance and short test and it passed both tests. I'm about
>> to start the long test. I figure that will take a couple days, or close
>> to it. Looking for thoughts on whether this drive has issues. I might
>> add, the company I buy from packages their drives to survive about
>> anything. Drive is put in a tough plastic bubble wrap made just for
>> hard drives and that is placed in a box. They then wrap that box in
>> large bubble wrap, like any of us can buy, and put that in a large
>> second box. I can't imagine the drive being damaged in shipping.
>>
>> Oh, when I get a new drive, I first watch messages to see how it
>> connects. Then I run conveyance test, short test and then long test.
>> If it passes all that, I then add it to a LVM drive set or use in some
>> other way. I'm thinking about buying another spare 20TB. Good deal at
>> just over $200 and current drive has only 2 run hours. O_O
>>
>> Thoughts on the above info? Anyone seen this before? Is this drive
>> perfectly fine? Need to return?
>>
>> Thanks.
>>
>> Dale
>>
>> :-) :-)
> 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. They a lot newer model. The thing I like about the one I
used, I just open a door, slide the drive in, close the door and it's
ready to go. My newer type enclosures require me to disassemble them to
put the drive in. They are nice enclosures when you plan to leave a
drive in them for a while.
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.
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.
Dale
:-) :-)
next prev parent reply other threads:[~2025-05-06 13:00 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 [this message]
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
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=348d3e3c-1084-013e-1a29-0cf1668c5b7e@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