td123

Reporting back. I was able to find and see how the system share had docker and libvirt.img on both the cache and the array. I stopped the VM's, dockers, turned it off in settings, manually ran the mover, and then re-enabled VM's/docker, started them back up, and now the system and domains are only on the Cache, everything works as it did before (no data or functionality loss). All seemingly worked without issue and fixed my problem. Thank you itimpi! Side note: USB manager wouldn't let me shut down HAOS VM (it kept immediately restarting it), so I just unplugged my zigbee and z-wave dongles and then I was able to shut it down in unraid.

Thank you so much for looking in to this for me. I'll follow your instructions! Thanks again.

Thank you for the guidance - I've attached the diagnostics here. diagnostics2025.zip

Hi - I'm rather new to this and trying to fumble my way through. I've decided my HAOS VM is most likely preventing my storage drives from spinning down. I purchased a 4TB SSD and am using it as a cache drive. My thought was I could put the HAOS VM on the cache drive so it's persistently active state wouldn't keep my drives spinning. However, it does not seem to have fixed the problem and I'm trying to troubleshoot. A few questions: 1. Does anyone know if this logic is solid? It should just utilize the cache if done right and leave the spinning disks idle right? Would the cache being pinged spin up the storage drives for some reason (and can I stop that)?. 2. Why I think HAOS VM is the problem: When I shut down the VM my drives do seem to behave appropriate and spin down based on the settings I've chosen. When the VM is active the drives never spin down (going on 1yr of no spin down now :(). 3. Did I actually move the HAOS VM to the Cache properly? I feel like I messed this up and must be doing something wrong here as I am a noob. Thanks in advance, I appreciate any help as I've been working on this but just don't have as much time as I used to to figure this stuff out. Setup is below but 1 4tb cache ssd, 1 12tb storage, 1 12tb parity.

Hm. My HDD are getting pretty hot ~60 degrees without an external floor fan pointing at the nas, so I wonder if the CPU is overheating under long load times. I was wondering if I could get away with this old Terramaster, looks like probably not. I have a full size PC, will just move everything over to that and ditch the little nas box. Ty.

I might be doing this wrong - just running diagnostics under tools and downloading that. If it's a different one I'm supposed to be running please let me know. spire-diagnostics-20231116-0931.zip

Thank you! Something is definitely going wrong. I ended up installing the fix common problems tool and a machine check event error detected hardware errors and is asking me to post here with my diagnostics for assistance. Any help is appreciated, thank you!

Hello! I'm new to unraid (only used terramaster nas software in the past) so I apologize in advance if this is pretty basic stuff! Yesterday I installed unraid (Version: 6.12.4) on my terramaster F2-221 (2-bay, Intel J3355 2.0ghz, 2gb ram) and added an extra 8gb stick of ram (10gb total). I put one drive (12TB) as parity and one 12TB as the array. I installed 2 docker containers: Omada controller and Plex Media Server. No cache, installed on mnt/user/appdata. Someone was watching a plex stream in my house as I was transferring ~700gb to the array from my networked windows PC. About 600gb into the transfer I got an error stating "not enough memory" and the file transfer stopped and I had to "skip all" the rest of the files (forgot to screenshot the exact error). I did a ~1TB transfer overnight with no issues, so I'm assuming it has to do with the plex stream running. I had my server dashboard open and ram usage was 27%. I think I only have ~2tb/12tb on it right now so lots of storage space left. Looking at my dashboard I'm wondering if the system can only access 2gb of the 10? It says "System - Memory: 2 GiB", and below it usable size 9.4GB. It never seems to go above 27% usage though, so that's why I think the system is not able to access the full 10gb and that's what led to the error. mcelog errors around the time the transfer are attached. I have Plex hostpath 2: as /tmp so plex uses the ram to transcode, not sure if that matters. spire-diagnostics-20231115-1255.zip