Do I need to fix - Inode 0x40f70 is corrupt. Run ntfsck.

[rkalinka]

Hey there, I am running 3x Asus RT-AC88u's in an AI Mesh config using Merlin FW - one of my nodes runs Samba to share a network drive for backups. I have a windows laptop running Cobian Reflector over the wifi that writes to said Samba drive. Overall the configuration works fine. THat being said, we lost power while one of my backups was running - and thus it errored out. In the syslog, I see errors:


root@AC88U-A640:/tmp/home/root# grep error /tmp/syslog.log
Mar 13 02:34:13 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:13 kernel: tntfs error (device sda3, pid 2207): ntfs_index_lookup_next(): Failed (error 5).
Mar 13 02:34:13 kernel: tntfs error (device sda3, pid 2207): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 02:34:13 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:13 kernel: tntfs error (device sda3, pid 2207): ntfs_index_lookup_next(): Failed (error 5).
Mar 13 02:34:13 kernel: tntfs error (device sda3, pid 2207): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 02:34:13 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:13 kernel: tntfs error (device sda3, pid 2207): ntfs_index_lookup_by_position(): Failed (error 5).
Mar 13 02:34:13 kernel: tntfs error (device sda3, pid 2207): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 02:34:13 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:18 kernel: __ntfs_error: 2478 callbacks suppressed
Mar 13 02:34:18 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:18 kernel: tntfs error (device sda3, pid 2207): ntfs_index_lookup_next(): Failed (error 5).
Mar 13 02:34:18 kernel: tntfs error (device sda3, pid 2207): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 02:34:18 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:18 kernel: tntfs error (device sda3, pid 2207): ntfs_index_lookup_by_position(): Failed (error 5).
Mar 13 02:34:18 kernel: tntfs error (device sda3, pid 2207): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 02:34:18 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:18 kernel: tntfs error (device sda3, pid 2207): ntfs_index_lookup_next(): Failed (error 5).
Mar 13 02:34:18 kernel: tntfs error (device sda3, pid 2207): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 02:34:18 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:23 kernel: __ntfs_error: 168 callbacks suppressed
Mar 13 02:34:23 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:23 kernel: tntfs error (device sda3, pid 2207): ntfs_index_lookup_next(): Failed (error 5).
Mar 13 02:34:23 kernel: tntfs error (device sda3, pid 2207): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 02:34:23 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:23 kernel: tntfs error (device sda3, pid 2207): ntfs_index_lookup_by_position(): Failed (error 5).
Mar 13 02:34:23 kernel: tntfs error (device sda3, pid 2207): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 02:34:23 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:23 kernel: tntfs error (device sda3, pid 2207): ntfs_index_lookup_next(): Failed (error 5).
Mar 13 02:34:23 kernel: tntfs error (device sda3, pid 2207): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 02:34:23 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:28 kernel: __ntfs_error: 354 callbacks suppressed
Mar 13 02:34:28 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:28 kernel: tntfs error (device sda3, pid 2207): ntfs_index_lookup_next(): Failed (error 5).
Mar 13 02:34:28 kernel: tntfs error (device sda3, pid 2207): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 02:34:28 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:28 kernel: tntfs error (device sda3, pid 2207): ntfs_index_lookup_by_position(): Failed (error 5).
Mar 13 02:34:28 kernel: tntfs error (device sda3, pid 2207): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 02:34:29 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 02:34:29 kernel: tntfs error (device sda3, pid 2207): ntfs_index_lookup_next(): Failed (error 5).
Mar 13 02:34:29 kernel: tntfs error (device sda3, pid 2207): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 02:34:29 kernel: tntfs error (device sda3, pid 2207): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 03:23:35 kernel: __ntfs_error: 209 callbacks suppressed
Mar 13 03:23:35 kernel: tntfs error (device sda3, pid 2209): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 03:23:35 kernel: tntfs error (device sda3, pid 2209): ntfs_index_lookup_next(): Failed (error 5).
Mar 13 03:23:35 kernel: tntfs error (device sda3, pid 2209): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).
Mar 13 03:23:35 kernel: tntfs error (device sda3, pid 2209): ntfs_index_descend_into_child_node(): Index record with VCN 0x32 is corrupt (magic is 0x0). Inode 0x40f70 is corrupt. Run ntfsck.
Mar 13 03:23:35 kernel: tntfs error (device sda3, pid 2209): ntfs_index_lookup_by_position(): Failed (error 5).
Mar 13 03:23:35 kernel: tntfs error (device sda3, pid 2209): ntfs_readdir(): Failed to look up index entry with position 0x269 in directory 0x40f70 (error 5).


Obviously this all occurred right around the power outage - so I expect there to be problems. That being said, how to I resolve these issues? (Or do I even need to?) I saw posts about running ntfsk to fix things but that requires the partition to be unmounted (which the router won't let me do.

FYI - i ran "ntfsck /dev/sda3"

 

[ColinTaylor]

Unmount the drive using the option in the router's webUI. Then move the drive to a Windows PC to repair it (or run ntfsck -a /dev/sda3 on the router).

Alternatively (and probably a better option), run amtm and select dc to install a disk check/repair every time the router boots up.

 

[rkalinka]

Colin - I will try this one: (Alternatively (and probably a better option), run amtm and select dc to install a disk check/repair every time the router boots up.) and the restart the node
- as this was my next question - Doesnt' the router check the drive for faults on restart.

 

[ColinTaylor]

- as this was my next question - Doesnt' the router check the drive for faults on restart.

I don't believe the stock firmware fixes faults by default (but that may have changed). I think you have to go to Network Map, select the USB drive and then select Health Scanner. You can then run a manual check or setup a schedule.

IIRC the motivation behind the disk check addon was that the stock Health Scanner was very limited in the types of filesystem it supported.

 

[JGrana]

Anyone installing a USB drive should also install dc right after formatting.

@ColinTaylor and @thelonelycoder , maybe the amtm “fd” command should ask the user to also install dc after formatting. And make it recommended. Small insurance!

 

[rkalinka]

Unmount the drive using the option in the router's webUI. Then move the drive to a Windows PC to repair it (or run ntfsck -a /dev/sda3 on the router).

Alternatively (and probably a better option), run amtm and select dc to install a disk check/repair every time the router boots up.

Installed and rebooted. Checked dcl - but the log was truncated (Truncated log file, size over 300KB). is there a way to allow for a larger log with this utility? Also - I "assume" there were no other issues based on what I could see in the log. It looks to have done some repairs. Thoughts?

 

[rkalinka]

I don't believe the stock firmware fixes faults by default (but that may have changed). I think you have to go to Network Map, select the USB drive and then select Health Scanner. You can then run a manual check or setup a schedule.

IIRC the motivation behind the disk check addon was that the stock Health Scanner was very limited in the types of filesystem it supported.

Well- your earlier suggestion using amtm with dc worked... so I am good with that... just need to keep an eye on things I guess.

 

[rkalinka]

Anyone installing a USB drive should also install dc right after formatting.

@ColinTaylor and @thelonelycoder , maybe the amtm “fd” command should ask the user to also install dc after formatting. And make it recommended. Small insurance!

I like this idea is it does seem to be a best practice regardless.