SSD partitions? USA error

bazilio113

Member
Joined
Jun 7, 2024
Posts
8
Hi, i got a problem which seems chkdsk can't fix, few days ago after i installed second Samsung SSD and got a freeze of system during opening chrome, i have old 2012 motherboard, so probably sata2 connector didn't work well with it, anyway i fixed it and just changed SSD conneciton to other socket. Freeze gone. But after this case system disc E: with windows 10 seems got corrupted, i checked it with chkdsk with /F and got what doesn't look good: The USA check value, 0x0, at block 0x1 is incorrect.
Then i checked my system SSD disk with Victoria 5.37 tool, but it shows not problems with sectors, all of them are fine. But chkdsk can't fix this specific error looks like, anything i can do without redoing partitions, killing my win 10 system and such bad things? :( System win 10 SSD is pretty new, so i doubt it's hardware problem.

Here is chkdsk with /R key results:
Code:
Checking file system on E:
The type of the file system is NTFS.
Volume label is Новый том.


A disk check has been scheduled.
Windows will now check the disk.                      


Stage 1: Examining basic file system structure ...
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
  4750592 file records processed.                                                    




File verification completed.
 Phase duration (File record verification): 44.71 seconds.
  12761 large file records processed.                                




 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                  




 Phase duration (Bad file record checking): 0.92 milliseconds.


Stage 2: Examining file name linkage ...
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2.
  5041 reparse records processed.                                  




  6199808 index entries processed.                                                    




Index verification completed.
 Phase duration (Index verification): 2.73 minutes.
  0 unindexed files scanned.                                    




 Phase duration (Orphan reconnection): 3.91 minutes.
  0 unindexed files recovered to lost and found.                




 Phase duration (Orphan recovery to lost and found): 2.06 milliseconds.
  5041 reparse records processed.                                  




 Phase duration (Reparse point and Object ID verification): 40.82 milliseconds.


Stage 3: Examining security descriptors ...
Cleaning up 14 unused index entries from index $SII of file 0x9.
Cleaning up 14 unused index entries from index $SDH of file 0x9.
Cleaning up 14 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 73.19 milliseconds.
  724609 data files processed.                                        




 Phase duration (Data attribute verification): 1.03 milliseconds.
CHKDSK is verifying Usn Journal...
  38628696 USN bytes processed.                                                        




Usn Journal verification completed.
 Phase duration (USN journal verification): 238.28 milliseconds.


Stage 4: Looking for bad clusters in user file data ...
  4750576 files processed.                                                            




File data verification completed.
 Phase duration (User file recovery): 59.47 minutes.


Stage 5: Looking for bad, free clusters ...
  105457814 free clusters processed.                                                    




Free space verification is complete.
 Phase duration (Free space recovery): 0.00 milliseconds.


Windows has scanned the file system and found no problems.
No further action is required.


1000098903 KB total disk space.
 572030412 KB in 2989177 files.
   1344664 KB in 724610 indexes.
         0 KB in bad sectors.
   4892571 KB in use by the system.
     65536 KB occupied by the log file.
 421831256 KB available on disk.


      4096 bytes in each allocation unit.
 250024725 total allocation units on disk.
 105457814 allocation units available on disk.
Total duration: 1.11 hours (4012840 ms).

Internal Info:
00 7d 48 00 ff aa 38 00 8b a8 5e 00 00 00 00 00  .}H...8...^.....
83 12 00 00 2e 01 00 00 00 00 00 00 00 00 00 00  ................
Victoria with S.M.A.R.T:
1717752781199.png1717753111208.png
Motherboard Gigabyte GA-X58A-UD3R v2
 
Run Powershell as admin, copy/paste this into it and hit Enter. Repair-WindowsImage -Online -RestoreHealth

Post the result please.

In that same Pwershell window after the RestoreHealth gets finished type sfc /scannow and hit enter.

Post result.
 
Run Powershell as admin, copy/paste this into it and hit Enter. Repair-WindowsImage -Online -RestoreHealth

Post the result please.

In that same Pwershell window after the RestoreHealth gets finished type sfc /scannow and hit enter.

Post result.
It's the first thing which i always do after smth goes wrong with system or ssd/hdd, no errors found, tho thx for trying to help.
Code:
DISM /Online /Cleanup-Image /CheckHealth


DISM system
Version: 10.0.19041.3636


Image version: 10.0.19045.4474


No damage to the component store was detected.
The operation was completed successfully.

sfc /scannow

System scan has started. This process may take some time.

Beginning of the verification stage of a system scan.
Verification is 100% complete.

Windows Resource Protection did not detect any integrity violations.
 
Last edited:
Found some info about this error, i guess i am really unlucky, rofl, no idea how to fix tho.
The USA check value, 0x3aea, at block 0x3 is incorrect.
For internal control of volume integrity, NTFS uses the so-called MFT to record elements. Update Sequence Array (USA). Each MFT element occupies several sectors (2 for a 512-byte sector, which is used de facto on all magnetic devices). With each write (modification) of the MFT, the word at the end of each sector increases by one (when the MFT element is first written, the last word of each sector is 0001, then 0002, etc. the main thing is to control the synchronicity of this word during multi-sector recording).

USA is an array of real words written at sector boundaries (occupied by synchronization words). NTFS, when reading an MFT element and checking synchronization, immediately substitutes USA for sector boundaries in its internal representation.

When the NTFS driver detects a synchronization failure in an MFT element, it changes its type to bad (BAAD label at the beginning of the MFT element) and does not use it further.

This can happen in two cases:
1) sudden shutdown of the machine in the middle of a multi-sector write operation (almost unrealistic, since the drive can almost always complete the operation).
2) the hard drive is falling apart (almost certainly).
 
Last edited:
I don't see where you mentioned if you need to keep the data or have a backup. If you need the data, I suggest making an image of the drive.

You could try some of the various methods of refreshing Windows. I've never had much luck with the built in Windows Refresh methods.

Create the installation media​

First, create the installation media that you'll use to reinstall Windows 11.

  1. Make sure you've backed up any files on your device that you wish to save onto an external storage device such as a USB drive, SD card, or external hard drive, or upload your files to OneDrive.
    Note: If you use an external storage device to back up files, make sure it’s a different one than the one you’ll be using to download Windows 10 installation media.
  2. Download the Windows 11 installation media to a separate external storage device that has at least 8GB of available space. Everything on this drive will be deleted to complete the download, so make sure it’s empty before you proceed. Here's how:
    1. On a working PC, go to the Microsoft software download website and select Download tool now.
    2. When the download is complete, open the tool from your desktop, and then select Yes when asked if you’d like to allow the app to make changes to your device.
    3. When the Windows 11 Setup guide appears, accept the license terms and agreements.
    4. Select Create installation media (USB flash drive, DVD, or ISO file) for another PC, and then select Next.
    5. Choose a language, edition, and architecture (64-bit or 32-bit), and then select Next.
    6. Select USB flash drive, and then select Next.
    7. Follow the steps to create installation media, and then select Finish.

Use the installation media to reinstall Windows 11​

Connect the installation media you created to your PC and reinstall Windows 11.

  1. Open File Explorer and select the drive with the installation media.
  2. From the root directory of the drive, double-click setup.exe, and then select Yes when asked if you’d like to allow the app to make changes to your device.
  3. Select Change to determine what to keep: Select one of the following options, and then select Next:
    • Keep personal files and apps – This will preserve your personal data, apps, and settings.
    • Keep personal files only – This will preserve your personal data and settings, but all your apps will be removed.
    • Keep nothing – This will remove all personal data, settings, and apps.
    • Warning: You cannot undo a reinstallation of Windows 10. Be sure to back up your files first if you choose the Keep nothing option.
  4. To finish, select Install to start reinstalling Windows 11 on your PC.
Your PC will restart several times during the reinstallation.


SOURCE
 
Thanks, tho windows itself is fine, seems MFT partition itself is damaged, i mean i don't see any problems except this errors during disk scanning itself. Ofc it's better to keep data, i am trying to find way which won't require disc cleanup, recreating partitions and windows reinstall, it's too much time consuming to restore all i have. There is a nice tool AOMEI Backupper i am using to make my drives backups, but i guess if i will do backup now it will probably will copy damaged MFT elements to it too into backup, so i am not sure about a way to make it nice without actually killing whole SSD drive data with partitions and reinstall all from 0.
 
Last edited:
AOMEI Backupper i am using to make my drives backups, but i guess if i will do backup now it will probably will copy damaged MFT elements to it too into backup
Yes.

How far back do your backups go?

Or choose this when following the above instructions.

  • Keep personal files and apps – This will preserve your personal data, apps, and settings.
 
Yes.

How far back do your backups go?
Not quite enough, thats a problem... ofc there is a way to manually copy all things and such with recreating partitions... reinstall all things i missed from backup, but it's always a risk to leave yourself without any working pc at all, y know and is this error so deadly killing so nobody have any idea how to deal with it a bit easier way... maybe some tool for drives to fix damaged MFT and errors like this.
 
Ye, /fixmbr is good when y have probs with master boot record, but seems it's not where it is actually damaged, in the beginning of partion or smth like, i tried testdisk-7.1, it has in advanced option to fix boot MBR, but seems it's also only working if problems with booting disc at all and after comparing it with mirror boot record on ssd it says that it's fine.

I will wait a day or two and will go hard way sadly with restoring drive backup and all i am missing manually, if no ideas will appear in this thread.
 
Last edited:
So... i did low level formatting of ssd, converted it to gpt, than back to mbr and tried to deploy the backup... but failed to fix error.

Seems backup was also damaged at some moment earlier than i thought, otherwise hard to explain this things, it was done before freeze, but for some reason had other mistakes during chkdsk and same shit error. :(

Also tried to check filesystem with paragon disk manager (it said there are some mistakes, but not relevant) and restore mbr with minitool partition wizard... no effect. Sad to say, but seems i have to live with this error.

I can't use gpt on this windows ssd and convert it cause have motherboard without uefi support, so this option also closed for me.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top