The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Erik E. Fair" <fair-tuhs@netbsd.org>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Might Have a DMERT SCSI Disk, Need Help Preserving
Date: Fri, 08 Mar 2024 20:22:21 -0800	[thread overview]
Message-ID: <29986.1709958141@cesium.clock.org> (raw)
In-Reply-To: <VTcqXbJu3X-CIAiWc5oEOUTAoCScvv4DGjFDoniGFTo36XFiGP6IlDNOgvRWl64KTB0lx_zx5_-zd-n_M1O1bdwFYCz1TsXxNR58GRzpgZA=@protonmail.com>

A storage device data recovery service that has been around since 1985:

"Drive Savers"


https://drivesaversdatarecovery.com/data-recovery-services/devices-supported/external-drive-data-recovery/

I have never used their services myself, but they advertised handling SCSI drives back in the day, and given their business, I doubt they throw away outmoded gear - can't hurt to call 'em and ask.

I tried that imgur.com link and got a 404 - no image there.

An Ultra320 SCSI drive should have either a 68-pin or 80-pin SCA connector on the back, and will be "low voltage differential" (LVD) - an Ultra80 or Ultra160 SCSI controller should be able to talk to that, i.e., the drive should be able to negotiate the link speed with the controller and downgrade appropriately. I might be able to cobble something together from the junk I keep too much of to try and read the drive if it will spin up and talk, but an outfit like Drive Savers will be much better equipped than I am.

This might also be a job for the restoration folks at the Computer History Museum in Mountain View, CA.

	Erik Fair

  reply	other threads:[~2024-03-09  4:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09  3:59 [TUHS] " segaloco via TUHS
2024-03-09  4:22 ` Erik E. Fair [this message]
2024-03-09  4:29   ` [TUHS] " Warner Losh
2024-03-09  4:27 ` Kevin Bowling

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=29986.1709958141@cesium.clock.org \
    --to=fair-tuhs@netbsd.org \
    --cc=segaloco@protonmail.com \
    --cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).