Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Getting IO errors

Featured Replies

Not sure what happened, but I have been overseas and the server was working fine for more than a month and all of a sudden errors occured. Could not access my Plex and OpenVPN etc. Lots of errors while viewing the log.

 

I'm also getting errors like this:

fstrim: /etc/libvirt: FITRIM ioctl failed: Input/output error
fstrim: /var/lib/docker: FITRIM ioctl failed: Input/output error

 

 

Did something died or got corrupted? What should be my next move?

 

 

tower-diagnostics-20200124-0143.zip

  • Community Expert

NVMe cache device stopped responding:

Jan 17 14:26:44 Tower kernel: nvme nvme0: I/O 991 QID 13 timeout, aborting
Jan 17 14:26:44 Tower kernel: nvme nvme0: I/O 992 QID 13 timeout, aborting
Jan 17 14:26:44 Tower kernel: nvme nvme0: I/O 993 QID 13 timeout, aborting
Jan 17 14:26:44 Tower kernel: nvme nvme0: I/O 994 QID 13 timeout, aborting
Jan 17 14:26:45 Tower kernel: nvme nvme0: I/O 827 QID 5 timeout, aborting
Jan 17 14:26:45 Tower kernel: nvme nvme0: I/O 406 QID 10 timeout, aborting
Jan 17 14:26:45 Tower kernel: nvme nvme0: I/O 407 QID 10 timeout, aborting
Jan 17 14:26:45 Tower kernel: nvme nvme0: I/O 408 QID 10 timeout, aborting
Jan 17 14:27:14 Tower kernel: nvme nvme0: I/O 991 QID 13 timeout, reset controller
Jan 17 14:27:45 Tower kernel: nvme nvme0: I/O 8 QID 0 timeout, reset controller
Jan 17 14:28:48 Tower kernel: nvme nvme0: Device not ready; aborting reset
Jan 17 14:28:48 Tower kernel: nvme nvme0: Abort status: 0x7
### [PREVIOUS LINE REPEATED 7 TIMES] ###
Jan 17 14:29:18 Tower kernel: nvme nvme0: Device not ready; aborting reset
Jan 17 14:29:18 Tower kernel: nvme nvme0: Removing after probe failure status: -19
Jan 17 14:29:18 Tower kernel: nvme nvme0: Device not ready; aborting reset
Jan 17 14:29:18 Tower kernel: print_req_error: I/O error, dev nvme0n1, sector 500361306

 

Reboot or power/cycle to see if comes back online.

  • Author

image.thumb.png.7e67ea77065bb96fab212c05415c8900.png

 

I think you are right, I rebooted and it is no longer being detected..

image.thumb.png.0c9de2fec35986ccaf8e328f26919dc2.png

I will shutdown and see if the bios can detect it... I hope it didn't died because its pretty new

  • Author

Not sure what happened but it’s working now. I reboot it, Bios detected the nvme, but I updated the bios just in case. Works fine now. Appreciate your help!

  • Community Expert

If it happens again you can try disabling power states, some devices have issues with those and linux, don't have the procedure at hand but post back here if needed. 

 

 

  • Author

Ok I will keep that in mind, will update again if this issue persists in the future... thank you!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.