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.

Dockers unresponsive and VMs disappear

Featured Replies

Since upgrading to 6.6.x (currently on 6.6.6), I've been getting a weekly problem where my dockers become unresponsive and my VMs disappears completely from the list of VMs in the console.  This always seems to occur on a Monday morning and I usually receive an email similar this:

 

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

 

None of my drives show any errors at this point although the log drive is usually at 100% when I login to the console to see what is going on.  Rebooting UnRaid causes everything to work again for another week.  I've attached my diagnostics but this is after rebooting the server so there may be nothing to see at this point.

 

I see that there are some issues with TRIM working on LSI controllers but as far as I can see I don't have one of those.  I also have TRIM scheduled to run daily so I don't know why it would only have problems one day of the week.

tower-diagnostics-20190107-1419.zip

  • Author

This morning the same thing happened again.  Maybe it is a problem with TRIM?  TRIM is scheduled to run daily at 5am and I received the email at 5:19am which is the same time I received it yesterday.  I've attached the diagnostic files from before I reboot the server.

tower-diagnostics-20190108-0816.zip

  • Community Expert

The problem is that your SSD dropped offline:

 

Jan  8 03:25:24 Tower kernel: ata7: hard resetting link
Jan  8 03:25:34 Tower kernel: ata7: softreset failed (1st FIS failed)
Jan  8 03:25:34 Tower kernel: ata7: hard resetting link
Jan  8 03:25:44 Tower kernel: ata7: softreset failed (1st FIS failed)
Jan  8 03:25:44 Tower kernel: ata7: hard resetting link
Jan  8 03:26:19 Tower kernel: ata7: softreset failed (1st FIS failed)
Jan  8 03:26:19 Tower kernel: ata7: limiting SATA link speed to 3.0 Gbps
Jan  8 03:26:19 Tower kernel: ata7: hard resetting link
Jan  8 03:26:24 Tower kernel: ata7: softreset failed (1st FIS failed)
Jan  8 03:26:24 Tower kernel: ata7: reset failed, giving up
Jan  8 03:26:24 Tower kernel: ata7.00: disabled

Likely the result of a bad SATA cable, replace it.

  • Author

Ok, I've replaced the SATA cable and changed the SATA port it is plugged into for good measure.  Will update if that fixes things.  Thanks for the advice!

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.