lcadmedia

Just noticed this last night. Had to restart unraid 3x, to no avail. every time I try run the win11 VM, it just gets stuck there trying to load, but I can browse all other menu/pages except the VM page/section. every after restart, I get the unclean shutdown notification and the correcting parity starts, even though I went through Unraid's restart procedure. my unraid has been running stable 24/7 for several months, until this latest version I guess. I tried deleting the VM and recreated, same issue.

I just realized this as well, as not having to run my win11 VM for at least 2 months, now, i've restarted my unraid 7.0.1 3x in 1 night, prior to that, it's been 24/7 for several months. I didn't notice this until now. unraid isn't crashing completely, I could open on incognito or another server and still browse the dashboard, main, settings, except VM. when I restart/reboot, I get the uncleaned shutdown error notification and parity starts.

same here

okay, parity check done last night, no errors; but this morning, the array becomes inaccessible again. like the unraid gui is still accessible I can browse through different menus, CPU usage and UPS shows data but my array is offline, and it seems like I can't restart nor shutdown unraid because of the array not accessible. it looks like it's just running on RAM.

hmmm.. what could be the call trace issue from? I have set it to ipvlan, and before that the macvlan was working stable for over a year until I got a unifi switch and pfsense router, so I had to set to ipvlan to set my vlans. someone from reddit suggested to change the power mode (which was a new thing to me) to performance mode, and that helped finish the rebuilding of array and was running good for a few days, until tonight while I was playing dota 2 on win 11 VM, all of a sudden it just froze, but I suspect my GPU (6900 XT SE) was the issue as it didn't POST with the GPU light error; currently running the unclean shutdown parity check.

Hi guys, I've had my unraid stable running 24/7 for over a year, but recently I've had crashes after upgrading to Unraid 7 beta 4, downgraded back to 6.12.4 but it seems like I'm still getting crashes and has destroyed my arrary. I'm currently trying to rebuild it a few times now but it randomly freezes or the gui is inaccessible while still being able to ping the unraid IP. I am not sure what's going on recently. I am not sure if the instability happens while idle but it has mostly been freezing when idle, and while array is rebuiling around 50%. Can you guys take a look on what seems to be the issue? I've attached both the diagnostics and the syslog. lcadmediaserver-diagnostics-20241102-1327.zip syslog-127.0.0.1.log

Tried this but my windows boot up just takes forever with all CPU cores/threads at 100%; macOS doesn't boot at all, just stuck at 100% cpu usage, and seem to be stuck at booting midway.

Yes, I originally have passed the NVME PCIe controller for macOS but I recently just swapped the OSes and their storages, so I"m using the NVME for Win11 right now, and noticed it rather disappointing especially for Dota 2. Cyberpunk is good though. I think it stutters on Dx11 games with high CPU bound. Also, just realized, I was asking the SCSI for my Sata SSD drive when I first posted it, not for the NVME as you don't to choose a Bus on that.

Gotcha. does it also apply if I passed through the nvme controller? also just to confirm, I dont need to reinstall using scsi, and can just switch the xml from sata to scsi, right?

I can't seem to install windows using SCSI Bus, it wouldn't detect the dedicated SSD Drive. I have to install using sata bus, then when I tried to change it to SCSI after installing, it just wouldn't boot.

Oddly enough, haven't had call traces since then; Also, didn't have crashing issues until today, but I suspect it's because of the S3 Sleep auto inactivity scheduling, even though I'm running win 11 VM and copying files. It doesn't crash when there's no VM running and it goes to sleep, but it tries to go to sleep even when the VM is running, prolly because I have the NVME Controller and/or SSD Drive passed through. So it might be the culprit.

just switched back to macvlan, and the system froze again as soon as the S3 sleep plugin triggered for inactivity. prior to switching (macvlan), the S3 sleep plugin triggered for inactivity twice, and was able to WOL twice, no problem; even went to sleep while the macOS VM was on (not ideal) but system didn't freeze. Will try to use ipvlan a couple more days and see if it freezes or not, then switch back to macvlan. Also, experienced the crashes/freezes after updating to 6.12.9

Thank you. So the instability isn't about macvlan. so Call traces that isn't macvlan is fine? I will try to switch back to macvlan and monitor the sleep activities. hopefully, it was just the faulty flash drive which I had to change.

Yes, Bridging was disabled when I used macvlan, and tried both bonding enabled/disabled. Just enabled bridging today as I have to switch to ipvlan for monitoring; so far, left the server inactive, and S3 triggered the sleep schedule, woke it up through pfsense no problem twice. Though, it might be too little of a time to conclude yet but I got 3 crashes in 2 days, and just so happened when I updated to 6.12.9, might be coincidence, IDK. Just to clarify, disabled Bridging is the setting under "Settings > Network Settings > Enable Bridging = No; Enable Bonding = Yes" , right? Because that's what I've been using for months, though, the Docker Delugevpn, is still set to bridge mode as that is the only option that works properly.

Interesting. Thanks for the info. ipvlan doesn't have call traces on the syslog, does it? I mean does the call trace only show when there's an issue? my syslog server has always been enable way back when switch to ipvlan in 6.10. so you think the instabality might be something else? I really want the macvlan to work because I like to be able to access my dockers while I'm out of town (remote).