Perhaps I am simply sleep deprived in such a state my google foo is weak... however after my 2 TB WD Green cache drive threw an uncorrectable error resulting in a pending sector that simply would not move I decided to replace the drive with a new Samsung 850 PRO ...  Plus I am not in the habit of keeping any drives that throw smart errors. 

 

I followed https://lime-technology.com/wiki/index.php/Replace_A_Cache_Drive and all looks good... except when I restart the machine, the cache drive does not automount when the array automounts.  I need to stop the autostarted array and assign the cache drive to the now strangely empty cache drive spot and then re-start the array.   As I have an autostart docker on this, the behaviour is a tad irksome.

 

An ideas, or items one would want me to share?

 

thanks crew

Edited March 12, 20179 yr by landS

Boot unraid in safe mode, stop the array, assign the cache drive, start the array, stop the array, shut down and reboot. See if that fixes it.

Thanks Jonathanm... This fixed it!

 

As this computer is not hooked up to a terminal (and is a major pita to do so)... I used the method of booting into safe mode by clicking on Main/Flash/Syslinux Configuration and moved menu default from under the label unRAID OS to label unRAID OS Safe Mode.  Powered back on and it was in safe mode as per the red label on the footer.