I connected the Seagate internally to my secondary PC and booted into Ubunto. I used the instructions here to get it mounted:
https://www.synology.com/en-us/knowledg ... using_a_PC
I used the instructions here to run fsck:
https://smallbusiness.chron.com/run-chk ... 54071.html
This is the results:
Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext5 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsc -b 8193 <device>
e2fsck -b 32768 <device>
Next I installed and ran TestDisk. I haven't been able to figure out where the log file is for that scan but I did take some screenshots. Some of the message I got were:
Here are the screenshots:Bad sector count.
The harddisk (4000 GB / 3726 GiB) seems too small! (< 5078 GB / 4730 GiB)
Check the harddisk size: HD jumpers settings, BIOS detection...
The following partitions can't be recovered
Not sure of what to do next, I tried Seagate's bootable USB SeaTools. The program boots and starts loading but then the screen just goes black and does nothing else while loading extensions. This is the last thing I see before it goes black:
I don't care about recovering what was on the drive. It's all secondary backup stuff that isn't important. I just want to get the drive functional so I can put it back in the NAS.
So I guess my main question is: is there actually anything physically wrong with the Seagate? If not, how do I get it back in a condition to be useful.
By the way, after doing stuff with fsck and TestDisk on the Western Digital drive, it appeared to be fine. I put it in the NAS and run both quick and extended SMART scans and it passed with no problems at all.