AC68U Health Scanner running long on my USB-2 external drive

[wahoowad]

I have my older 500GB Seagate drive hanging off my AC68U and do my home backups to it across the network. I have it shared out as \\freeagent\backup and all that has been working fine for over a year.

Today I notice my nightly backup job has been failing so I let the AC68U run it's Health Scanner on the USB drive. It seemed to be running long so I dug into the running log file it is producing and see these errors repeating at least 3 times, but it is still running and has been for a good 30 minutes (noticed it maxing out the CPU's too)

Actual VCN (0x0) of index buffer is different from expected VCN (0x2a) in inode 0x115db.
Checking directory structure second time ...
Corrupt directory found, inode=71131 (0x115db)

Actual VCN (0x0) of index buffer is different from expected VCN (0x13) in inode 0x11564.
Repairing corrupt directories completed.
Corrupt directory found, inode=71012 (0x11564)

Can I trust the Health Scanner feature? Is it reliable enough to let it fix these supposed drive issues?

 

[wahoowad]

The system remounted the drive and I can access it across the network from my File Explorer, so I assume it is finished. Yet the Health Scanner says this:

Done NTFS checking and repair on device '/dev/sda1'.
Syncing device ...


I can't tell if it ever finished. My backup software is still having a problem updating the existing archive log. I verified all the permissions are still correct and active.

 

[wouterv]

Here is the result of a completed scan of a USB memory device in my RT-AC68U:

And all the related System Log messages:

After the scan the USB icon shows a blue halo, as follows:

It shows quite clear when it finished and what it has done (in the past I have seen repairs listed).

 

[skeal]

I formatted my additional drives as ext4 and ext2. Since then I've had no more drive errors and the test runs like the fatchk above. Everything clean. Using Linux format and directory structure is not as hard as one thinks. Mine works best as a private music server my amplifier recognizes my routera media server and connects lists and plays files normally. I'm never running Windows ntfs on this linux based router again.

 

[wahoowad]

Mine ran to completion, just took longer than I expected. After it 'fixed' those issues my backup program still could not update the backup index file so I gave it a new directory to write to and started a new full/incremental backup set. Now my backups work fine again.

But running the Health Scanner keeps finding/fixing 'corrupt directories' even though I seem to be able to browse and open files pretty much everywhere. So are these actually corrupt directories or is the Health Scanner finding non-issues? Is it possible my external drive is finally failing or are bad sectors common and I just haven't scanned it in awhile to mark them as unavailable?

ntfsck 3014.5.21
Checking NTFS Superblock ...
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 500105216512 bytes (500106 MB)
Current device size: 500105217024 bytes (500106 MB)
Checking for bad sectors ...
Scanning $MFT ...
Actual VCN (0x0) of index buffer is different from expected VCN (0x9) in inode 0x87ec6.
Checking directory structure ...
Corrupt directory found, inode=556742 (0x87ec6)
Repairing corrupt directories started.
0.00 percent completed
0.01 percent completed
...
99.99 percent completed
100.00 percent completed
Actual VCN (0x0) of index buffer is different from expected VCN (0xe) in inode 0x9b549.
Repairing corrupt directories completed.
Corrupt directory found, inode=636233 (0x9b549)
Repairing corrupt directories started.
0.00 percent completed
0.01 percent completed

 

[swetoast]

running a windows proprietary file system on a linux platform expects a limited hardware with minimal ram to fix issues.. simple solution ext4 run native file systems is always preferable.