cancel
Showing results for 
Search instead for 
Did you mean: 

AXE16000 Error Log with NFTS Kernal

ayayron74
Level 8
I receive this error pattern nonstop all day long. It goes on and on forever with this same set of lines and repeats.

How can this be fixed so it doesn't do this anymore it's the only error message I have everything else is working great.

Feb 25 09:22:05 kernel: __ntfs_error: 12 callbacks suppressed
Feb 25 09:22:05 kernel: tntfs error (device sda1, pid 2638): ntfs_lookup(): ntfs_iget(0x110d7) failed with error code -2.
Feb 25 09:22:05 kernel: tntfs error (device sda1, pid 2638): ntfs_lookup(): ntfs_iget(0x110d7) failed with error code -2.
Feb 25 09:22:05 kernel: tntfs error (device sda1, pid 2638): ntfs_lookup(): ntfs_iget(0x110d7) failed with error code -2.
Feb 25 09:22:05 kernel: tntfs error (device sda1, pid 2638): ntfs_lookup(): ntfs_iget(0x110f8) failed with error code -2.
Feb 25 09:22:05 kernel: tntfs error (device sda1, pid 2638): ntfs_lookup(): ntfs_iget(0x110f8) failed with error code -2.
Feb 25 09:22:05 kernel: tntfs error (device sda1, pid 2638): ntfs_lookup(): ntfs_iget(0x110f8) failed with error code -2.
Feb 25 09:22:05 kernel: tntfs error (device sda1, pid 2638): ntfs_lookup(): ntfs_iget(0x110f8) failed with error code -2.
Feb 25 09:22:05 kernel: tntfs error (device sda1, pid 2638): ntfs_lookup(): ntfs_iget(0x110f2) failed with error code -2.
Feb 25 09:22:05 kernel: tntfs error (device sda1, pid 2638): ntfs_lookup(): ntfs_iget(0x110f2) failed with error code -2.
Feb 25 09:22:05 kernel: tntfs error (device sda1, pid 2638): ntfs_lookup(): ntfs_iget(0x110f2) failed with error code -2.
684 Views
1 REPLY 1

Jiaszzz_ROG
Customer Service Agent
Hello, ayayron74.

May I ask if resetting the ROG Rapture GT-AXE16000 was able to solve the problem?
Please refer to the link below to reset. >> https://www.asus.com/support/FAQ/1039078/

In addition, could you please help confirm if the the ROG Rapture GT-AXE16000 has been updated to the latest version of firmware?
If not, it is recommended that you update and try again.

Thank you.
As the local holiday is ongoing, there may be further delays in responses.
We appreciate your patience in advance.