uspec Posted June 10 Share Posted June 10 HI, i use OS 6.12.10 i set all shares (appdata, system, isos, domain) to use cache pool (as my unraid is still in buildup configuration phase) So no share is targeting array as primary (only as secondary pool the array is getting targeted, but my primary cache disk has enough free space atm). Everything is MOVEd to cache atm. (so i guess starting a my pihole docker oder HA VM shoud also only target cache) my array contains 1 parity and 2 disks, which are all specifically set to spin down after 30 mins. but they never spinned down. any ideas for helping me letting them getting a rest? thanks! Quote Link to comment
itimpi Posted June 10 Share Posted June 10 You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog. Quote Link to comment
uspec Posted June 11 Author Share Posted June 11 ok, providing em attached now. PS.: your diagnostic link links to reset password page, you could use this link instead: https://docs.unraid.net/unraid-os/troubleshooting/diagnostics-information/ core-diagnostics-20240611-1630.zip Quote Link to comment
itimpi Posted June 11 Share Posted June 11 1 hour ago, uspec said: PS.: your diagnostic link links to reset password page, you could use this link instead: https://docs.unraid.net/unraid-os/troubleshooting/diagnostics-information/ It was an issue at the Limetech end that I thought had been fixed. It appears to be true, but apparently is not retroactive to when the wrong link was being generated but should be OK going forward. Quote Link to comment
uspec Posted June 12 Author Share Posted June 12 i hope someone can hlpe here, with my provided diagnostics. i guess i just did a noob mistake, as thats what im doing here with my first unraid Futro Quote Link to comment
itimpi Posted June 12 Share Posted June 12 According to the diagnostics there is no ‘cache’ pool being mounted which would explain why your shares are not visible. Are you sure the array has been started (in normal mode) as I do not see it being started in the syslog that is part of the diagnostics. Quote Link to comment
uspec Posted June 15 Author Share Posted June 15 here we go again a new try for diagnostic power. i started the server. i started the array. i worked a little with HACS with new integrations. nothing spinned down even that everything should have only touched the cache disk. i also attached screenshots from main and shares. core-diagnostics-20240615-2152.zip Quote Link to comment
uspec Posted June 19 Author Share Posted June 19 im really sad, i have biought 3 disks with 2 TB each, which are all empty. i cannot use them and the unraid system, until i have a positive spin down test my unraid server is turned off until some can tell me the trick please... Quote Link to comment
Solution JorgeB Posted June 20 Solution Share Posted June 20 You are using USB disks, besides not being generally recommended for other reasons, some USB bridges have issues with spin down, recommend using SATA. 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.