What's new

kernel: __ntfs_error: 58 callbacks suppressed

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Indi

Occasional Visitor
My log is FULL of this error code.
Should I be worried?
Rebooting now to see if it still occurs...............

Asus FW 3.0.0.4.388_24329-g5906523 for now as trying to help asus fix their online scheduling bug



Aug 10 10:19:42 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x31be) failed with error code -2.
Aug 10 10:19:42 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x31c0) failed with error code -2.
Aug 10 10:19:42 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x2f) failed with error code -2.
Aug 10 10:19:42 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x31c6) failed with error code -2.
Aug 10 10:19:42 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x3c) failed with error code -2.
Aug 10 10:19:42 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x27) failed with error code -2.
Aug 10 10:19:42 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x39) failed with error code -2.
Aug 10 10:19:42 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x38) failed with error code -2.
Aug 10 10:19:42 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x3d) failed with error code -2.
Aug 10 10:19:42 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x2a) failed with error code -2.
Aug 10 10:20:03 roamast: sta[12:E6:31:20:50:C3] on ap[08:BF:B8:8E:77:D4], rcpi is 58 and rssi is -81
Aug 10 10:20:12 kernel: __ntfs_error: 58 callbacks suppressed
Aug 10 10:20:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x31be) failed with error code -2.
Aug 10 10:20:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x31c0) failed with error code -2.
Aug 10 10:20:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x2f) failed with error code -2.
Aug 10 10:20:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x31c6) failed with error code -2.
Aug 10 10:20:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x3c) failed with error code -2.
Aug 10 10:20:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x27) failed with error code -2.
Aug 10 10:20:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x39) failed with error code -2.
Aug 10 10:20:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x38) failed with error code -2.
Aug 10 10:20:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x3d) failed with error code -2.
Aug 10 10:20:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x2a) failed with error code -2.
Aug 10 10:21:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x31be) failed with error code -2.
Aug 10 10:21:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x31c0) failed with error code -2.
Aug 10 10:21:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x2f) failed with error code -2.
Aug 10 10:21:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x31c6) failed with error code -2.
Aug 10 10:21:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x3c) failed with error code -2.
Aug 10 10:21:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x27) failed with error code -2.
Aug 10 10:21:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x39) failed with error code -2.
Aug 10 10:21:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x38) failed with error code -2.
Aug 10 10:21:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x3d) failed with error code -2.
Aug 10 10:21:12 kernel: tntfs error (device sda1, pid 2694): ntfs_lookup(): ntfs_iget(0x2a) failed with error code -2.


It's related to the USB memory stick I had plugged in.
Unplugged it and no more error messages.....

Aug 10 10:45:45 kernel: __ntfs_error: 24 callbacks suppressed
Aug 10 10:45:45 kernel: tntfs error (device sda1, pid 5728): ntfs_write_mst_block(): I/O error while writing ntfs record buffer (inode 5, attribute type 0xa0, page index 4, page offset 0, block 2055397, block size 4096)! Unmount and run ntfsck.
Aug 10 10:45:45 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Aug 10 10:45:45 hotplug[6394]: USB partition unmounted from /tmp/mnt/RouterUSB
Aug 10 10:45:45 rc_service: hotplug 6394:notify_rc restart_nasapps
Aug 10 10:45:45 rc_service: hotplug 6406:notify_rc restart_nasapps
Aug 10 10:45:45 rc_service: waitting "restart_nasapps" via ...
Aug 10 10:45:45 iTunes: daemon is stoped
Aug 10 10:45:45 FTP Server: daemon is stopped
Aug 10 10:45:45 Samba Server: smb daemon is stopped
Aug 10 10:45:47 Timemachine: daemon is stoped
Aug 10 10:45:47 avahi-daemon[6417]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Aug 10 10:45:48 avahi-daemon[6417]: Alias name "GT-AXE16000" successfully established.
Aug 10 10:45:48 iTunes: daemon is stoped
Aug 10 10:45:48 FTP Server: daemon is stopped
Aug 10 10:45:48 Samba Server: smb daemon is stopped
Aug 10 10:45:50 Timemachine: daemon is stoped
Aug 10 10:45:50 avahi-daemon[6431]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Aug 10 10:45:51 avahi-daemon[6431]: Alias name "GT-AXE16000" successfully established.
 
Last edited:
Do you have a USB hard drive attached (it appears you do) and do you have either iTunes Server and or UPnP Media Server enabled under General > USB Application > Media Server? Seems it may be related to Media Server:

If either of the Media Server options are enabled, maybe try disabling it to see if the messages stop. Or try cycling the service by stopping the services, hit the apply button, reboot the router, then re-enable the services, hit the apply button, and see if the messages continue. Could also be an issue with the USB drive (device sda1, pid 2694) attached to the router. Check the USB drive for errors.
 
Do you have a USB hard drive attached (it appears you do) and do you have either iTunes Server and or UPnP Media Server enabled under General > USB Application > Media Server? Seems it may be related to Media Server:

If either of the Media Server options are enabled, maybe try disabling it to see if the messages stop. Or try cycling the service by stopping the services, hit the apply button, reboot the router, then re-enable the services, hit the apply button, and see if the messages continue. Could also be an issue with the USB drive (device sda1, pid 2694) attached to the router. Check the USB drive for errors.

Indeed it was,was editing my post as you were posting this :)
Had upnp media server enabled,disabling made no difference although tbf hadn't set it all up properly as yet.
Removed usb stick and no more errrors.

Thanks
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top