I've got a problem assigning a replacement cache drive, and it appears to have gotten worse under 6.4.0-rc6.

 

The problem started back when I was on 6.3.  When I upgraded to a new Ryzen system, I replaced my Samsung 840 SSD with a Samsung 960 M.2 drive.  Unfortunately, the cache assignment would not stick, reverting back to unassigned (or the old cache drive if I had it installed) on every reboot.  I tried to make the assignment using Chrome, Firefox, and IE, as the FAQ indicates that this is a known problem - but nothing worked to make it permanent.

 

At the time, I found I could simply stop the array, assign the cache drive, and restart, and everything was fine until the next reboot.

 

Then I upgraded to 6.4.0-rc6 right when it came out, and just now noticed that Mover is broken.  Here's the specific symptoms:

 

A)  As before, every time I boot up, the cache drive is unassigned (unless I install the old SSD, then the old SSD boots up assigned)

B)  Looking in the disk.cfg file, I see the old SSD still being referenced (cacheId="Samsung_SSD_840_EVO_1TB_S1D9NSAF627019H")

C)  Stopping the array, assigning the cache drive, and restarting the array appears to partially fix the problem, as now caching and VM's work.

D)  Under 6.4.0-rc6, the drive Identification is ugly: "eui.0025385c61b08640 - 1 TB (nvme0n1)", back on 6.3.x it seems like it was pretty, something like "Samsung 960 1TB (nvme0n1)"

E)  I can browse to \\TOWER\cache and see my files, and "cache" shows up in the DISK SHARES list on the Shares tab, so both of those seem good

F)  But Mover is broken, always logging the issue "root: cache not enabled, exit", both on manual and scheduled runs

G) Looking at the backlog of files to move, Mover has not worked in a month (June 25 is oldest file) - appears to be when I upgraded from 6.3.x to 6.4.0.-rc6

 

I believe Mover was working on 6.3, even with the cache drive assignment issues.

 

Diagnostics are attached.

 

On a side note, I noticed that on Firefox the checkboxes are invisible with 6.4.0-rc6.  For example, on the Main page, the checkbox for "Yes I want to do this" when stopping the array is invisible, but I can tell it is clicked because the "Stop" button becomes enabled.  The same issue is on the anonymize diagnostics checkbox - impossible to tell if it is clicked.  I can see the checkboxes with Chrome, Edge and IE, just not Firefox.

 

Paul

tower-diagnostics-20170727-1016.zip

20 minutes ago, Pauven said:

On a side note, I noticed that on Firefox the checkboxes are invisible with 6.4.0-rc6.  For example, on the Main page, the checkbox for "Yes I want to do this" when stopping the array is invisible, but I can tell it is clicked because the "Stop" button becomes enabled.  The same issue is on the anonymize diagnostics checkbox - impossible to tell if it is clicked.  I can see the checkboxes with Chrome, Edge and IE, just not Firefox.

This is nothing to do with unRAID.   It is a known FireFox issue where the latest release does not handle checkbox's correctly.

2 minutes ago, itimpi said:

This is nothing to do with unRAID.   It is a known FireFox issue where the latest release does not handle checkbox's correctly.

 

Thanks, I didn't know that.  Perhaps it was mentioned earlier and I just didn't see it.

I read on a post that you can highlight where the checkbox would be and it will show up and then you can check it. 

5 hours ago, Frank1940 said:

I read on a post that you can highlight where the checkbox would be and it will show up and then you can check it. 

 

I had already tried that trick.  For whatever reason, it doesn't work.

 

And before someone asks here (since I was asked in another thread) I've tried booting into safe mode to assign the cache drive, and that doesn't work either.

2 hours ago, Pauven said:

 

I had already tried that trick.  For whatever reason, it doesn't work.

 

And before someone asks here (since I was asked in another thread) I've tried booting into safe mode to assign the cache drive, and that doesn't work either.

 

Please try -rc7a, probably will solve these issues for you.

11 hours ago, limetech said:

 

Please try -rc7a, probably will solve these issues for you.

 

So ultimately -rc7a did resolve the issue, though not without some headaches along the way (including a Kernel Panic).

 

Posted details here: 

 

Thanks for all your help!

Paul