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.

Existing Cache Drive Showing as Unmountable After Reboot

Featured Replies

This morning I received an alert stating that my system was "unable to write to cache" and "unable to write to docker image". After a bit of forum searching, I shut down my server and checked the connections on the cache drive cables. Upon reboot of the server and restart of the array, unraid is telling me that my cache drive is "unmountable: unsupported partition layout". 

 

FWIW, syslog is also throwing out buffer I/O errors like crazy on the cache drive. I've attached the diagnostic log.

 

Is there any way to retrieve the cache drive partition layout and docker container configurations? Any help would be greatly appreciated. I have a new SSD I can use to replace the existing cache drive, but I really don't want to reconfigure my dockers unless I absolutely have to.

tower-diagnostics-20210801-0857.zip

  • Community Expert

Your docker templates are on flash and Previous Apps on the Apps page will reinstall any and all dockers exactly as they were using those templates. But unless you also have appdata for each docker, it will be a new install.

  • Author

Excellent. Thanks for the help, I will try these options. 

  • Community Expert

Cache device dropped offline, this is a hardware issue:

 

Aug  1 08:28:28 Tower kernel: ata6: link is slow to respond, please be patient (ready=0)
Aug  1 08:28:33 Tower kernel: ata6: COMRESET failed (errno=-16)
Aug  1 08:28:38 Tower kernel: ata6: link is slow to respond, please be patient (ready=0)
Aug  1 08:28:43 Tower kernel: ata6: COMRESET failed (errno=-16)
Aug  1 08:28:48 Tower kernel: ata6: link is slow to respond, please be patient (ready=0)
Aug  1 08:29:18 Tower kernel: ata6: COMRESET failed (errno=-16)
Aug  1 08:29:18 Tower kernel: ata6: limiting SATA link speed to 1.5 Gbps
Aug  1 08:29:23 Tower kernel: ata6: COMRESET failed (errno=-16)
Aug  1 08:29:23 Tower kernel: ata6: reset failed, giving up
Aug  1 08:29:23 Tower kernel: ata6.00: disabled

 

See if new cables help.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

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.