salvialight

yea i was thinking to get a UPS but it's just gonna be another box to squeeze into where my NAS stands. but yea i'll also look into the terramaster BIOS n see if there's a way to make it auto start

is there a way to make my NAS automatiaclly turn back on after a power outage? its annoying cuz i have to turn it back on physically with the button every time my apt loses power for whatever reasons

you're right i noticed it has not actually created any file. so if my server ip is 10.0.0.153 i just put that for ip address and i can leave the port as is?

OK i just enabled the syslog server. I attached the settings i used to this post as a screen shot. I decided not to mirror to flash, cuz my appdata folder is on my cache drive and it gets backed up daily to the array. so i guess at this point ther's no way for me to find out what happened before that shut down, since syslog was not running? weird that it's not on by default

Last night I was using my NAS remotely thtrough twingate, everything was working perfectly. today i tried to access it again and it wasn't responding. i come home to the apt where the NAS sits and I see it is simply off. All i know is that it started a monthly parity check last night while i was using it to stream plex content. Any thoughts on why it might've gone down? I powered it back up and it says parity check was completed with 0 errors. When i open the logs, it only shows me logs starting from the time that i booted it up. How can i check logs from before it went down?/ update - i just noticed that despite telling me the parity check went all good (after i booted up the nas), the system has started doing a parity check all over again, currnetly at 3%

i actually have been having a similar problem except without even any VMs. i have an intel pentium gold 8505 in a ugreen NAS, running unraid, and my CPU has been going to 90+ when all i'm doing is qbittorrent and sabznbd running/downloading. I've also been experiencing a weird problem where my twingate connector randomly goes offline and i think it may have to do with this CPU overheating. I'm not sure how to fix this, maybe my bios fan settings are messed up but i never changed them.

yup that's exactly what i was planning to do with the appdata back up plugin. but yea that's how i would run mover, cuz i generally want my downloads folder to write to cache and then move to array when mover runs. i guess my main question is, is there some problem with just keeping appdata/system/isos/domain folders permanently on the cache drive (its 1TB)? assuming i do use appdata backup plugin to back it up occasioanlly to the array?

OK so i am on the right track with this set up. My idea is to set it up as cache-preferred and NO secondary storage, so that the appdata/VM stuff is only and always on the SSD. Is that not a good idea? If i set array as secondary, then won't it just move all of the appdata/VM shares on to the array when mover runs, so that would defeat the purpose of putting them on the SSD in the first place

I have been doing research on this a bunch and i have not really been able to figure out a clear answer to my concern. I just set up my unraid server. i have two 8tb HD's, and a 1TB samsung evo nvme. I set up the two HDD's in the array with one for parity, and the SSD i formatted as BTRFS and set it as cache. what i want to know is what is the optimal setting in terms of drive usage for appdata and the other shares? i set appdata, domain, isos, and system to all use cache as primary, with no secondary. the main use of this server will be plex, and i may set up immich for a photo backup and hosting solution. My idea is to make unraid use ONLY the SSD for all docker stuff (and any VMs if i decide to play around with that in the future). as well as set up a media share and download share that will have preferred cache but secondary array (for when i'm downloading something or writing from external disk to speed up the writes). since the SSD will have no mirroring, i'm planning to use the appdata back up plugin to periodically back up the appdata from SSD to the array. Does all of this sound sensible/possible? or am i thinking about this all wrong