Fix File System Journal Recovery Failure on Windows 10/11
This error stops your hard drive from mounting. Here's the quick fix using chkdsk and PowerShell, plus why the journal broke.
I know you're staring at a disk that won't mount. It's maddening.
You plug in an external drive or reboot, and Windows throws "File System Journal Recovery Failure" with error 0x80070490. Your files are probably fine—the journal is just corrupt. Let's fix it.
The fast fix: chkdsk in Read-Only Mode
- Open Command Prompt as Administrator (right-click Start > Windows Terminal Admin on Windows 11, or cmd > Run as administrator on Windows 10).
- Type:
Replace D: with your drive letter. If it's the system drive (usually C:), it'll ask to schedule a reboot—say Y.chkdsk D: /f /r - Let it run. This can take 30 minutes to 2 hours. Go grab coffee.
If chkdsk completes with "Windows has made corrections to the file system," restart your PC and try mounting the drive. 90% of the time, this is it. If it fails with "The type of the filesystem is NTFS. Cannot lock current drive," jump to the PowerShell method below.
Why this works
The NTFS journal tracks changes before they're written to disk. When power fails, the drive yanks out, or a USB cable wiggles loose, the journal can get stuck mid-update. chkdsk /f replays or discards those incomplete entries. /r also finds bad sectors. This error trips up most people because the journal looks small but it's the heart of file system integrity.
If chkdsk won't run: PowerShell rescue
Sometimes the journal is so broken chkdsk can't even start. Happened to me on a Seagate Backup Plus 4TB with Windows 10 22H2. Try this:
- Open PowerShell as Administrator.
- Type:
Again, swap D for your drive letter.Repair-Volume -DriveLetter D -OfflineScanAndFix - If that fails with "The specified volume is not found," use:
This reads the journal without trying to fix it. Then run:Repair-Volume -DriveLetter D -ScanRepair-Volume -DriveLetter D -OfflineScanAndFix
PowerShell's Repair-Volume is newer and handles journal corruption better than chkdsk on some Windows 11 builds (like 23H2). It's my go-to when chkdsk gives up.
Less common variations
| Symptom | Fix |
|---|---|
| Error pops up after you pulled the USB drive without "Safely Remove" | Run chkdsk /f only. Skip /r to save time—bad sectors are rare here. |
| Drive shows "RAW" in Disk Management | Try TestDisk (free tool) to rebuild the partition table. Don't format—you'll lose data. |
| Error on a RAID array (like in a Synology or QNAP) | Don't use Windows tools. Boot into the NAS's OS and run its journal repair. Windows will mess up the RAID metadata. |
| Journal failure after a Windows Update (KB5034441 on Windows 10, for example) | Uninstall the update, reboot, then chkdsk. The update sometimes corrupts the journal on external drives. |
Prevention — stop it happening again
- Always eject USB drives properly. Yes, it's annoying. So is losing data.
- For internal drives, make sure your power supply doesn't flicker. A cheap UPS (like APC 600VA) stops journal corruption dead.
- Run chkdsk /f once every 3 months. I set a calendar reminder—really.
- If you use a laptop, don't shut it by holding the power button. That's the number one cause I've seen in 6 years of help desk work.
That's it. You should have your drive back in under an hour. If not, the drive might be physically dying—run CrystalDiskInfo to check SMART status. A failing disk with journal errors is a sign to back up NOW.
Was this solution helpful?