Question Corrupted brand new HDD

Alpha39401

Distinguished
Mar 13, 2015
45
1
18,535
In short, Windows claims the brand new HDD I got is corrupted after a few days of use.

Basically this is the story:
I have bought a Toshiba 2TB 7200RPM HDD (DT01ACA200) to replace my aging WD Green 2TB. I used SeaTools to run S.M.A.R.T. test, Drive Self Test and a Long Generic test on the new drive. All shows as pass. The data transfer went smoothly too.

After everything was done I decided to take the old WD drive out of my PC and leave the Toshiba inside. I also switched the Toshiba to the original location of my WD drive to help with airflow.

Then I am barred by this error (Toshiba drive is T):
T:\ is not accessible
The disk structure is corrupted or unreadable


In Win 10 Disk Management it now shows the drive as RAW.
I tried different SATA wires and SATA power connectors, doesn't work.
Using CHKDSK /f T: returns "The type of file system is NTFS.
Unable to determjne volume version and state. CHKDSK aborted."
Tried reinstalling the device using device manager.

I am thinking to test it on another PC and maybe boot Ubuntu as well.

The new Toshiba drive is barely a week old. Ultimately I can just do a reformat as I have a full copy of all my data on another drive. But since this has happened I don't think it is wise to continue using this drive? What are you guys thoughts?

Edit: The Toshiba drive has always been in the same exact PC from the moment I installed, formatted and used it. It has not been installed in any other PC.

Edit 2: I attempted to fix the partition in Ubuntu with no avail.
____
This is what I get after using ntfsfix:


ubuntu@ubuntu:~$ sudo ntfsfix /dev/sdb
Mounting volume... NTFS signature is missing.
FAILED
Attempting to correct errors... NTFS signature is missing.
FAILED
Failed to startup volume: Invalid argument
NTFS signature is missing.
Trying the alternate boot sector
Unrecoverable error
Volume is corrupt. You should run chkdsk.
ubuntu@ubuntu:~$ sudo ntfsfix /dev/sdb1
Mounting volume... ntfs_mst_post_read_fixup_warn: magic: 0x68da344d size: 1024 usa_ofs: 34667 usa_count: 36853: Invalid argument
Record 0 has no FILE magic (0x68da344d)
Failed to load $MFT: Input/output error
FAILED
Attempting to correct errors... ntfs_mst_post_read_fixup_warn: magic: 0x68da344d size: 1024 usa_ofs: 34667 usa_count: 36853: Invalid argument
Record 0 has no FILE magic (0x68da344d)
Failed to load $MFT: Input/output error
FAILED
Failed to startup volume: Input/output error
Checking for self-located MFT segment... ntfs_mst_post_read_fixup_warn: magic: 0x68da344d size: 1024 usa_ofs: 34667 usa_count: 36853: Invalid argument
OK
Unrecoverable error
Volume is corrupt. You should run chkdsk.
ubuntu@ubuntu:~$
____
This is the error that "Disks" in Ubuntu shows:


ntfs_mst_post_read_fixup_warn: magic: 0x68da344d size: 1024 usa_ofs: 34667 usa_count: 36853: Invalid argument
Record 0 has no FILE magic (0x68da344d)
Failed to load $MFT: Input/output error
Failed to mount '/dev/sdb1': Input/output error
NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
made to NTFS by this software.

Failed to open '/dev/sdb1'.

ntfs_mst_post_read_fixup_warn: magic: 0x68da344d size: 1024 usa_ofs: 34667 usa_count: 36853: Invalid argument
Record 0 has no FILE magic (0x68da344d)
Failed to load $MFT: Input/output error
Failed to mount '/dev/sdb1': Input/output error
NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
made to NTFS by this software.

Unable to read the contents of this file system!
Because of this some operations may be unavailable.
The cause might be a missing software package.
The following list of software packages is required for ntfs file system support: ntfs-3g / ntfsprogs.
 
Last edited:
FYI, you use Seagate's utility on Seagate's drives, not other branded drives. Please include your system's specs like so:
CPU:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Case:
OS:

Include the age of the drives and which ports they were connected to. Also a screenshot of Disk Manager will also help us with understanding your drive structure.
 
I understand that Seagate's tool is designed mainly for their own brand of drives. I don't seem to find Toshiba's own HDD diagnostic tools. I would be happy to know if there are any (Toshiba) alternatives to tools that can conduct various tests like SeaTools and WD's Data Lifeguard.

The Toshiba drive is brand new and under a week old. I doubt if it is related but my old WD drive is a bit over 5 years old. Windows 10 is installed on the SSD (M.2 NVMe). Currently the Toshiba is the only HDD in the system. I tried changing SATA ports but the results are the same.

Here is my system info:
CPU: Ryzen 5 3600
Motherboard: Gigabyte B450M Gaming
Ram: 2x 8GB 3200Mhz DDR4
SSD/HDD: WD SN550 512GB SSD + Toshiba DT01ACA200 2TB HDD (Old one is WD20EZRX)
GPU: RX 480
PSU: Corsair CS550M
Case: Corsair Carbide Spec-01
OS: Windows 10 Pro 2004 19041.508
 
The OP's drive appears to have a missing or corrupt NTFS boot sector. The information in the boot sector points to the $MFT. Since the boot sector is corrupt, then the $MFT is also inaccessible. The system knows that the partition type is NTFS probably because there is an 07 partition ID in the MBR in sector 0.

All of this should be visible in DMDE. It may also be possible to repair the partition with DMDE, but we would need to see the damage before proceeding.

CHKDSK won't do anything if there is no boot sector or $MFT.
 
Thank you for your replies. In the end I decided to bite the bullet and reformat the HDD. Since I have another copy of my data all I need to do now is to put it back into the newly formatted HDD.

However I am still interested in this issue as it has never happened to me. Unfortunately at the time I read fzabkar's post about DMDE I had already reformatted the drive. Thank you though! I did use MiniTool Partition Wizard to rebuild MBR and use the partition recovery tool. It did show it as a 1.8TB NTFS file system and a tiny amount (I don't remember exactly) of ext2 partition. It might be caused by me booting a Live Ubuntu USB.

This is one of the weirdest issue I have ever encountered. All I did was literally unplug and plug the drive and the partition suddenly went bad. The drive seems to be working normally now. Perhaps I will run a few long tests again.