[Solved] Cache Drive becomes unassigned on reboot


Recommended Posts

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

Link to comment

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.

Link to comment

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

Link to comment

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

Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.