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.

[Solved] Cache Drive becomes unassigned on reboot

Featured Replies

I just reformatted my flash drive and did a clean install of Unraid 6.1.7.  So I am completely stock and have not installed any plugins, dockers or VMs.  The only changes I have made is to the networking section to setup a static IP and changed my workgroup name in the SMB settings.

 

I went through and assigned all of my drives including my cache drive and started the array.  Everything was fine.  I then rebooted the array and when the main screen came up in the webgui...the cache drive slot showed as unassigned.  When I looked at the syslog is says no device...see attached diagnostics.

 

The second diagnostic is after I reassigned the cache drive and started the array.

 

It just seems weird to me that the cache drive is not staying assigned???

tower-diagnostics-20160125-0730.zip

tower-diagnostics-20160125-0744.zip

  • Community Expert

Something in your syslog I don't recall seeing before. Your flash is sda, but

Jan 25 07:43:48 Tower emhttp: get_device_size: open: No medium found
Jan 25 07:43:48 Tower emhttp: device /dev/sdb problem getting size
Jan 25 07:43:48 Tower emhttp: get_device_size: open: No medium found
Jan 25 07:43:48 Tower emhttp: device /dev/sdc problem getting size
Jan 25 07:43:48 Tower emhttp: get_device_size: open: No medium found
Jan 25 07:43:48 Tower emhttp: device /dev/sdd problem getting size

what are sdb,sdc,sdd? Then your actual drives start at sde.

  • Community Expert

If you are using chrome, do it with another browser, the whole process, assign cache, start array, stop array and reboot, if it sticks you can go back to chrome.

  • Community Expert

what are sdb,sdc,sdd? Then your actual drives start at sde.

 

Probably a cardreader

  • Author

Definitely a card reader.  This is a clean install and I have a card reader plugged into a PCIe USB card that I normally passthrough to a VM and did not set my pci-stub in the syslinux.cfg file yet. 

 

I am using chrome...so I will try with another browser.

 

Attached are screenshots with all drives assigned and array running then second is after a reboot.

unraid_started_all_assigned.JPG.a4ef58e895748c8edf6ebe6ad979546c.JPG

unraid_after_reboot.JPG.0c81bff0808d242189a27022f35d8849.JPG

  • Author

Johnie.Black,

 

I followed your suggestion and used firefox and everything works as it should.  The cache drive stays assigned.  I have tested a reboot cycle as well as a powerdown then restart.  Do you know why this happens with Chrome?  I dont remember seeing any warnings about this on the forums.

 

Thanks for your help!

 

Dan

  • Community Expert

I don’t know the reason, I know it always happens to me (and no, it’s not an ad-blocker).

  • Author

Marking this thread as solved...not sure I understand why...but Johnie.black's suggestion of using another browser has definitely worked.

 

Thanks Johnie!

 

Dan

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.