cd C:\Open Sea Chest (correct the path if necessary)OpenSeaChest_SMART --shortDST --poll -d PD2That's just the way command line is. SeaTools GUI usually works fine on internal HDDs, it's externals where it sucks.
Yes, that's just a cautionary statement saying to format in MBR if you want it recognizable on Windows XP and earlier. If you don't use Windows XP, you should format it with GPT. If it's being used as a Windows OS disk on a UEFI computer, or if it's above 2TB in total capacity, it should be formatted in GPT. Anyways, this isn't relevant to the I/O Device Error topic, as this isn't an error, and the I/O error isn't about GPT or MBR in particular.
It won't change anything, because there is no drive letter until it is formatted. A letter is actually a volume letter, not a drive letter. Drives are numbered, as shown by Task Manager (Disk 0, Disk 1, Disk 2). Letters are for filesystems, which are guests to partitions, which in turn are just guests to an entire disk. The filesystem type, or even the partitioning scheme (MBR/GPT), will have no effect on I/O Device Errors while formatting the disk in entirety.
I made it simpler. Extract the ZIP. Right-click this CMD file and choose Run as Administrator, and a series of openSeaChest tests will be performed without any command line intervention. A popup notification will be displayed when the results are available, so you won't need to look at the Command Prompt.
It looks to be the false warning because a Disk 2 is not present (the ST10000VN004 likely became a different number). Since openSeaChest incorrectly uses Error Code 3 for unavailable disks, when it is supposed to use Error Code 2 for, there isn't a way to fix this issue in this file. Sorry for such an embarrassingly low-quality experience, speaking of low quality. I should of refrained from posting it, since there isn't a way around that bug. I have not made this simple, and have spilled way too much complexity onto your side. Since SeaTools was able to open, you can try testing the ST10000VN004 from there. By the way, Task Manager shows which numbers refer to which disks.
That's the ST8000AS002, not the ST10000VN004.
If there are I/O Device Errors, all software on Windows will be the same. The question is if the I/O Errors are caused by the HDD or something else like the cable. It is probably the HDD. What does SeaTools show for the UDMA CRC Error Count (cable errors)? I think it's under Start Tests > Drive Information. Sorry for the runaround.
Yes, Windows 7 is superior and would have remained leading indefinitely if not for the arbitrary end of support, but how does startup sounds have to do with I/O Device Error? I think this is a Seagate issue, not a Windows 10 issue. Linux would likely have Input/Output Errors as well.
