Ah yes. The 2383. Love the sound of that thing.
Some questions to start diagnosing:
Does it boot? Can you load the SCSI and access it in DOS? If yes, what does FDISK see? What is the SCSI ID? Mine has issues being "seen" if not ID0. Could be my drive, though. (also out of the scrap heap).
I've never had mine working in Windows XP because it would crash the computer when I clicked on it in disk management. I could access it in My Computer, though... that's how I got the stuff on it. It was formatted in DOS originally with the 6.22 install disks then into the "modern" computer for the games.

The way I go about old SCSI HDDs is Core2Duo machine with modern Debian and AHA-2940UW(2) controller. Run cat /dev/sdb > hdd.bin and then you can fdisk/mount the resulting bin file as you wish without risking overwriting the HDD. Or use sg_dd with io options if there are bad sectors that cat can't deal with. Point is Linux will work with way more partition types then Windows and there is no need to run any weird M$ tools and alter the HDD just to read it. You have full sector by sector dump for preservation purposes.

Deunan wrote on 2025-01-23, 01:17:

The way I go about old SCSI HDDs is Core2Duo machine with modern Debian and AHA-2940UW(2) controller. Run cat /dev/sdb > hdd.bin and then you can fdisk/mount the resulting bin file as you wish without risking overwriting the HDD. Or use sg_dd with io options if there are bad sectors that cat can't deal with. Point is Linux will work with way more partition types then Windows and there is no need to run any weird M$ tools and alter the HDD just to read it. You have full sector by sector dump for preservation purposes.

That worked. Although the partition shows there's 1.38MB used, but it doesn't show the files. The command "cat /dev/sdb > hdd.bin" (yes I did double check where's the partition for this seagate) gives me permission denied on mint 17.3.

Major Jackyl wrote on 2025-01-23, 00:05:

Ah yes. The 2383. Love the sound of that thing. Some questions to start diagnosing: Does it boot? Can you load the SCSI and acc […]
Show full quote

Ah yes. The 2383. Love the sound of that thing.
Some questions to start diagnosing:
Does it boot? Can you load the SCSI and access it in DOS? If yes, what does FDISK see? What is the SCSI ID? Mine has issues being "seen" if not ID0. Could be my drive, though. (also out of the scrap heap).
I've never had mine working in Windows XP because it would crash the computer when I clicked on it in disk management. I could access it in My Computer, though... that's how I got the stuff on it. It was formatted in DOS originally with the 6.22 install disks then into the "modern" computer for the games.

Nope, the st2383n is not accesible in DOS. FDISK sees it but I have no idea how to assign a letter to it.

kotel wrote on 2025-01-23, 07:48:

That worked. Although the partition shows there's 1.38MB used, but it doesn't show the files. The command "cat /dev/sdb > hdd.bin" (yes I did double check where's the partition for this seagate) gives me permission denied on mint 17.3.

There's probably some udev rules that can be made to allow user to access the device(s) directly but I just use root or sudo for these commands. I'm old-fashioned and lazy like that. On most *nix systems the /dev stuff is not even readable for normal users.

Once you have the file it can be compressed and archived for later use (and copies made), no need to trouble the original HDD anymore. That's the nice thing about it. fdisk will work on the file if you run it "fdisk hdd.bin" just as if it was a block device. Usually mounting the partitions requires knowing where they start, so if it is PC-compatible partition table that fdisk can show just write down the starting LBA/sector of each partition. After that it can be mounted with "mount -o ro,offset=X hdd.bin /mnt/hdd" where X is the LBA/sector * 512 (or whatever the actual block size is in case of SCSI HDDs).

If the partition seems empty but not all space is available then perhaps it was not cleanly shut down and has bogus cluster links in FAT area. fsck should take care of it if you need it repaired, though obviously there is little reason to repair the archived image, unless it prevents you from reading any files on it. If you are sure the drive never worked with Win9x, just DOS, it's probably better to use -t msdos as mount option as well, because otherwise the default is vfat which also supports long names and access timestamps. Note some "DOS" partitions are not MS-DOS and might not be readable in pure DOS on a PC, even if Linux can deal with those.

Welp I tried easeus partition master 5.0.1 and it found nothing, so then I just formatted the drive and checked for bad sectors.
Thanks for the ideas!

Note: These drives like to have their black capacitors short themselves, so be aware