mechling-burgh Posted February 7, 2017 Share Posted February 7, 2017 I have been trying unraid to set up a SageTV server. I downloaded the key set everything up and worked fine with the two dockers I needed. Rebooted the server several times everything was fine. installed the windows 10 vm using the online tutorials again everything seemed fine. But when I rebooted the cache drive disappeared. I read through the forums and it maybe bad ssd or flash drive. I replaced both and reinstalled, waited the 7 hours for the parity drive to rebuild. I then rebooted the server, rebooted fine cache drive was there no problems, Reinstalled the windows 10 vm again tonight rebooted the server came up cache drive was unassigned, and reading as sbd. The ssd is a pony 240 gigs, the parity and data disks are seagate barracudas 3 tb. The version is the newest stable 6.3. It seems to me that it's the vm causing the problem that seems to be when its happening after theinstall of that. Any suggestions on how to get the cache drive to stick. I really like unraid but unless I can get ti to reboot with the cache drive I can't really use it. Thank You Quote Link to comment
limetech Posted February 7, 2017 Share Posted February 7, 2017 When it's in a state where cache drive assignment got lost, please navigate in webGui to Tools/Diagostics and post the diagnostics.zip file. Quote Link to comment
mechling-burgh Posted February 7, 2017 Author Share Posted February 7, 2017 Here is the file you asked for sagetv-diagnostics-20170206-2123.zip Quote Link to comment
mechling-burgh Posted February 7, 2017 Author Share Posted February 7, 2017 Would installing 6.2 fix the problem. I know I would have to do a clean install from scratch but that is better than the cache drive disappearing when I reboot. Quote Link to comment
limetech Posted February 7, 2017 Share Posted February 7, 2017 The only interesting thing in the syslog is that 'appdata' share is set 'cache-only'. In a default install this is set 'prefer'. Maybe you changed it at some point? I don't see anything that explains why cache assignment should get cleared - nothing in unRAID does that on it's own. I suggest you plug flash device into PC and make a backup. Next reformat the flash, re-install unRAID OS and then restore your backup. After first boot, review device assignments and go ahead and assign your ssd to cache. Now Start array. I'm guessing everything should come back online. At that point open telnet/ssh session and type: diagnostics This will create a timestamped zip file in the 'logs' directory on your flash. Then try to remember to type 'diagnostics' periodically as you do things like Stop array or reboot server. The idea is to catch it in a state where the cache disk assignment gets unassigned. Quote Link to comment
JorgeB Posted February 7, 2017 Share Posted February 7, 2017 The idea is to catch it in a state where the cache disk assignment gets unassigned. I'm having a similar issue on my work server, adding a 2nd cache device, and this time using a different browser isn't helping, sometimes changing the cache slots appears to help but also not having luck this time (btw, whatever the issue is started on rc9), attached diags after first assignment and after rebooting, maybe you can see something but the 2nd cache disk is assigned at reboot time and unassigned at next array start. tower8-diagnostics-20170207-1929.zip tower8-diagnostics-20170207-1933.zip Quote Link to comment
BobPhoenix Posted February 7, 2017 Share Posted February 7, 2017 Glad to see it isn't just me. Thought maybe I was doing it incorrectly. I did finally get one of the two cache drives to stay assigned but the second still refuses to stick. I've never posted before because I figured it was me. Now I'm not so sure. But I will try again. I tried with Chrome, Firefox and Edge. Will try another browser besides those as well. Also will try from my windows VMs. Hoping that since I went from 0 out of 2 to 1 out of 2 sticking that I can eventually get the last one to stick. Quote Link to comment
limetech Posted February 8, 2017 Share Posted February 8, 2017 The idea is to catch it in a state where the cache disk assignment gets unassigned. I'm having a similar issue on my work server, adding a 2nd cache device, and this time using a different browser isn't helping, sometimes changing the cache slots appears to help but also not having luck this time (btw, whatever the issue is started on rc9), attached diags after first assignment and after rebooting, maybe you can see something but the 2nd cache disk is assigned at reboot time and unassigned at next array start. Yes I see the issue. Fix coming in 6.3.1. Quote Link to comment
robbot Posted April 19, 2017 Share Posted April 19, 2017 Is this issue fixed? I'm seeing it in 6.3.3. I keep having to add a 2nd slot and assign the 2nd cache drive to it after a reboot. Any idea how to fix this and make the setting persistent? Quote Link to comment
JorgeB Posted April 19, 2017 Share Posted April 19, 2017 10 minutes ago, robbot said: Any idea how to fix this and make the setting persistent? See the FAQ: Quote Link to comment
robbot Posted April 20, 2017 Share Posted April 20, 2017 26 minutes ago, johnnie.black said: See the FAQ: So I tried Safari, then Edge, same issue, finally tried IE and it worked! Weird. Quote Link to comment
Joe Posted June 17, 2017 Share Posted June 17, 2017 Same issue here. Both my cache drive come up unassigned after reboot. Just upgraded to 6.3.5 and no help. Thanks Joe Quote Link to comment
Squid Posted September 6, 2018 Share Posted September 6, 2018 Post your diagnosticsSent from my LG-D852 using Tapatalk Quote Link to comment
theDrell Posted September 8, 2018 Share Posted September 8, 2018 On 9/6/2018 at 6:53 PM, Squid said: Post your diagnostics Sent from my LG-D852 using Tapatalk Moved the discussion over to here, will post diagnostics in a few, have been swamped. Quote Link to comment
Recommended Posts
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.