From: Matt Jolly <kangie@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Seagate hard drives with dual actuators.
Date: Thu, 14 Nov 2024 10:46:03 +1000 [thread overview]
Message-ID: <1e394615-819f-4740-9a91-3f80a7fa64e2@gentoo.org> (raw)
In-Reply-To: <f296f4b3-19a1-08e6-5ff0-32d1dccc1daa@gmail.com>
Hi Dale,
> My question is this. Given they cost about $20 more, from what I've
> found anyway, is it worth it? Is there a downside to this new set of
> heads being added? I'm thinking a higher failure rate, more risk to
> data or something like that. I think this is a fairly new thing, last
> couple years or so maybe. We all know how some new things don't work out.
At least one vendor has been trying to sell me on these recently,
claiming higher bandwidth and better ability to seek. I have not yet
actually used these.
> Just looking for thoughts and opinions, facts if someone has some.
> Failure rate compared to single actuator drives if there is such data.
> My searched didn't help me find anything useful.
There's no reason to suspect that these are going to be terrible, they
appear to be the next step on the Seagate roadmap before HAMR drives
hit the market in the coming years.
I haven't seen much on the reliability side of things, however I
wouldn't be too concerned, assuming that there's proper backup in place
- Any other drive (including SSDs) could "just die" for a multitude of
reasons.
> P. S. My greens are growing like weeds. Usually they ready to pick by
> now but having to wait for the tree to be cut down and cut up delayed
> that. Should be ready by Christmas, I hope. Oh, planted oats, clover,
> kale and some other extra seeds I had in open area. I saw a LARGE buck
> deer the other night snacking on the oats. My neighbor would rather see
> it in his freezer tho. o_0
Hopefully there's some left for you!
Cheers,
Matt
next prev parent reply other threads:[~2024-11-14 0:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 23:10 [gentoo-user] Seagate hard drives with dual actuators Dale
2024-11-14 0:46 ` Matt Jolly [this message]
2024-11-14 13:05 ` Dale
2024-11-14 7:55 ` Wols Lists
2024-11-14 16:48 ` Dale
2024-11-15 0:18 ` [OT] " Peter Humphrey
2024-11-15 8:41 ` [gentoo-user] Hollerith (was: Seagate hard drives with dual actuators) karl
2024-11-15 9:51 ` [OT] Re: [gentoo-user] Seagate hard drives with dual actuators Wols Lists
2024-11-14 11:21 ` Michael
2024-11-14 17:00 ` Dale
2024-11-14 19:12 ` Michael
2024-11-14 19:51 ` Frank Steinmetzger
2024-11-14 19:55 ` Frank Steinmetzger
2024-11-14 23:14 ` Peter Humphrey
2024-11-14 20:33 ` Dale
2024-11-14 20:57 ` Rich Freeman
2024-11-14 23:10 ` Dale
2024-11-15 0:59 ` Rich Freeman
2024-11-15 5:53 ` Dale
2024-11-15 10:09 ` Michael
2024-11-15 11:59 ` Dale
2024-11-15 15:35 ` Michael
2024-11-15 16:36 ` Dale
2024-11-15 22:13 ` Rich Freeman
2024-11-16 11:02 ` Michael
2024-11-16 14:36 ` Rich Freeman
2024-11-16 19:47 ` Michael
2024-11-16 20:13 ` Rich Freeman
2024-11-16 23:21 ` Wol
2024-11-17 11:22 ` Michael
2024-11-17 21:26 ` Rich Freeman
2024-11-17 23:04 ` Jack
2024-11-18 0:23 ` Rich Freeman
2024-11-18 2:32 ` Matt Jolly
2024-11-15 10:38 ` Frank Steinmetzger
2024-11-15 12:19 ` Dale
2024-11-14 22:38 ` Wols Lists
2024-11-15 9:35 ` 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=1e394615-819f-4740-9a91-3f80a7fa64e2@gentoo.org \
--to=kangie@gentoo.org \
--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