The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Might Have a DMERT SCSI Disk, Need Help Preserving
Date: Sat, 09 Mar 2024 03:59:28 +0000	[thread overview]
Message-ID: <VTcqXbJu3X-CIAiWc5oEOUTAoCScvv4DGjFDoniGFTo36XFiGP6IlDNOgvRWl64KTB0lx_zx5_-zd-n_M1O1bdwFYCz1TsXxNR58GRzpgZA=@protonmail.com> (raw)

Hello everyone, I reach out in my time of need regarding a potential source of DMERT materials.  I've recently come into possession of a hard disk unit from a 5ESS switch, presumably the 5ESS-2000 variant, part UN 375G:

https://i.imgur.com/yQzY5Hs.jpeg

The actual disk itself appears to be a Ultra320 SCSI disk, which I unfortunately do not have the tools to do anything with myself.  After looking into various solutions, I'm not getting the warm fuzzies about finding the necessary hardware on my first shot, these sorts of hardware specifics are not my strong suit.  The story I got is it is from a working system, so could possibly have artifacts, but at the same time, I've already sunk a little over $1,000 into getting this, I'm hesitant to drop more on hardware I'm not 100% confident is correct for the job.

Does anyone have any recommendations, whether a service, hardware, anything, that I could use to try and get at what is on this disk?  Even if it's just sending it off to someone along with enough storage for them to make me a dd image of the thing, I just feel so close yet so far on finally figuring out if I've managed to land a copy of DMERT.

Thanks in advance for any advice, I'm really hoping that the end of this story is I find DMERT artifacts to get archived and preserved, that would be such a satisfying conclusion to all this 3B20/5ESS study as of late.  I wish I had the resources to see the rest through myself but this is getting into an area I have quite a bit of trepidation regarding.  What I don't want to do is inadvertently damage something by getting it wrong.

- Matt G.

             reply	other threads:[~2024-03-09  3:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09  3:59 segaloco via TUHS [this message]
2024-03-09  4:22 ` [TUHS] " Erik E. Fair
2024-03-09  4:29   ` 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='VTcqXbJu3X-CIAiWc5oEOUTAoCScvv4DGjFDoniGFTo36XFiGP6IlDNOgvRWl64KTB0lx_zx5_-zd-n_M1O1bdwFYCz1TsXxNR58GRzpgZA=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    /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).