Pola Posted May 29 Posted May 29 Hi, I tried this to no avail: I had issues stopping the array, but it let me power off. When i powered back on cache drive.. poof! I have been having issues for a while where I can't shutdown my unraid system; it works fine whilst it's on but spazzes out when I try to shut it down sometimes and have to manually power off... not ideal and frustrating, i thought it was plex docker image and tried stopping that before attempting shutdowns but I just don't know at this point. Wondering if the cache drive might need a firmware update? Also, I don't understand why with the cache drive and parity drive (ok it's not a cache pool) I get yellow warnings on my shares (appdata, isos, systems...) that are not on the drives.... Thank you for your time if you have reached this far :) polaflix-syslog-20240528-0944.zip Quote
itimpi Posted May 29 Posted May 29 1 hour ago, Pola said: why with the cache drive and parity drive (ok it's not a cache pool) I get yellow warnings on my shares (appdata, isos, systems...) that are not on the drives.... That is because with a single drive pool the files on the pool drive are not protected. Quote
Pola Posted May 29 Author Posted May 29 1 hour ago, itimpi said: That is because with a single drive pool the files on the pool drive are not protected. That makes sense question, what are the implications of not using a cache drive? I dont think I actually need it... I just have plex on the server and some shares... Currently my docker images have "gone", is there anything I have lost? would I have to set up all shares to "no cache"? My personal shares were not using cache drive. i do think the cache drive is what was causing failures to shutdown properly.... Thanks itimpi Quote
JorgeB Posted May 30 Posted May 30 write time tree block corruption detected This usually means bad RAM, start by running memtest, then post new diags after array start. Quote
Pola Posted May 30 Author Posted May 30 1 hour ago, JorgeB said: write time tree block corruption detected This usually means bad RAM, start by running memtest, then post new diags after array start. Oh dear... i'm not really sure how to run a Memtest? Is it one of the boot options when i power on the server? I usually run headless... Gracias Quote
itimpi Posted May 30 Posted May 30 Just now, Pola said: Is it one of the boot options when i power on the server? yes Quote
Pola Posted June 3 Author Posted June 3 (edited) Hi, seems like 1 error popped up; however, screen has gone black (memtest didn't seem to have finished....) and I can't get the monitor to receive input from the server any longer; should I leave it for a while just in case?¿ Else i will have to power off manually... Not sure why I would have a RAM error, sticks were new with the build Thanks for your help, edit: have powered off manually, launching metest again, tweaked a couple of things in the BIOS settings to see if it makes a difference or not... anyhow! Edited June 3 by Pola Quote
itimpi Posted June 3 Posted June 3 Even 1 failure in memtest means the RAM cannot be trusted and crashes are likely. You may be able to tweak some BIOS settings to improve things. Quote
Pola Posted June 3 Author Posted June 3 8 minutes ago, itimpi said: Even 1 failure in memtest means the RAM cannot be trusted and crashes are likely. You may be able to tweak some BIOS settings to improve things. Questions: would you suggest swapping both sticks or trying to figure which one is the culprit and remove just that one? how about using ECC RAM? i think it's compatible with my mobo. Lastly, can i go on without the cache drive? Just need to reinstall my docker images? Thanks, Quote
JorgeB Posted June 3 Posted June 3 You can re-test with one stick at a time, ECC is always preferable if it's a possibility. You can use the server without cache, obviously anything that was there won't work. Quote
Pola Posted June 3 Author Posted June 3 I'm having an issue where screen turns black during memtest; not sure why, if I blindly press escape and enter it returns to boot menu... weird? thanks Jorge! Quote
Pola Posted June 16 Author Posted June 16 Hi, since i removed (unassigned) the cache drive I have had no issues with the server. I suspect it could be the cache drive causing all the issues... Any suggestions on brand? it's an m.2 Don't really need a cache pool or a cache, I just use plex at the moment. however I without a cache the HDDs will be worn out faster? thank you for your help Quote
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.