public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Seagate hard drives with dual actuators.
Date: Thu, 14 Nov 2024 10:48:56 -0600	[thread overview]
Message-ID: <90cde15f-5ed8-ca09-2f16-8782d129df9f@gmail.com> (raw)
In-Reply-To: <2a0a3dca-67b8-47a6-9331-d6f2899267fb@youngman.org.uk>

Wols Lists wrote:
> On 13/11/2024 23:10, Dale wrote:
>> 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.
>
> I think this technology has actually been out for a long time. I'm
> sure I've heard of it ages ago.
>
> Thing is, it's probably one of those things that's been available in
> high-end drives for years, but the cost-benefit ratio has been low so
> few people bought them. Now presumably the economics have changed.
>
> If the actuators are mounted opposite each other, then they can't
> collide, and presumably can operate completely independent of each
> other. The costs of two of them were presumably just deemed not worth it.
>
> An opposite niche (and rather apposite for you) was when I started
> buying disk drives. I think my first was a 2GB Bigfoot, followed by a
> 6GB, and I bought several 18GBs for work. They were "old tech", 5.25"
> 5200rpm in an era of 3.5" 7500rpm, but their capacities were huge and
> cheap. If all you wanted was storage, they were great. Most people
> thought the size and speed of the smaller drives was better value,
> even if it cost more per meg.
>
> Cheers,
> Wol
>
>


It may have been available for really expensive hard drives.  Those far
above what I'd be willing to pay and wouldn't look for.  I do find it
interesting tho.  Why not have three actuators?  Or four?  If they can
all fit in there and not hit each other, it does give the heads more
opportunities to be over needed data.  Then the port between drive and
controller, SATA or maybe SAS, likely becomes a bottle neck.  Of course,
you can only fit so many in there.  Two may be the limit.  Drives are
fairly small already.  Plus there is the heat problem. 

I remember seeing old drives that had I think 14" platters.  They had
large motors to spin them.  The controller was a separate thing too.  I
think their capacity was like 30 or 40MBs or so.  It usually took two
people to move one of those things.  The company I worked for upgraded
systems twice in the five years I worked for them.  Their fastest one
ran at a blazingly fast 25MHz.  It was RISC based, I think I spelled
that right.  It was a NCR system.  We used old Wyse terminals but that
new system was really fast.  Except when two or more of those Genicom
line printers were running.  I think they were the model 4440 or
something.  The printhead didn't move.  It was as wide as the page and
printed a whole line at a time, hence the name line printer.  They could
print far faster than a person could read.  Still, those systems are
nothing compared to what we have today.  Heck, my old video card in my
current rig likely has more computing power than the NCR system back
then, which could handle 200 to 300 users at a time.  How far we have
came. 

Those were the days tho. 

Dale

:-)  :-) 


  reply	other threads:[~2024-11-14 16:49 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
2024-11-14 13:05   ` Dale
2024-11-14  7:55 ` Wols Lists
2024-11-14 16:48   ` Dale [this message]
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=90cde15f-5ed8-ca09-2f16-8782d129df9f@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