-
Posts
40 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by kbnomad
-
-
5 hours ago, SimonF said:
Can you post the XML for the VM. Have you passed the NVME as a PCI device?
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. -
3 hours ago, SimonF said:
You need to install the virtioscsi driver in the guest before you change from sata to scsi
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?
-
On 4/30/2023 at 7:59 PM, Keinden said:
Additional input: I re-installed my Windows VM to use SCSI instead of SATA and can confirm it's butter smooth when gaming
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.
-
On 3/29/2024 at 5:15 AM, JorgeB said:
It depends, but generally any call trace means that there is a problem, hardware or software, though some can be more serious than others.
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 -
1 minute ago, JorgeB said:
Then the call traces would not be about macvlan.
Yes.
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. -
31 minutes ago, JorgeB said:
If you really need macvlan, you can still use, as long as bridging is disabled.
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.
-
2 hours ago, JorgeB said:
That doesn't look like the typical macvlan call trace, but retest with ipvlan, also enable the syslog server, to see if it catches anything else.
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).
-
Hi,
I've had my unraid for about 2 years now (I think), but I've been on ipvlan for the longest time, and switched back to macvlan when 6.11.5 came out and gave the workarounds; also, I couldn't get to my dockers' webgui with ipvlan, as well as WOL doesn't really work with it.
I never really noticed random freezes ever since (at least not that I know of) but I haven't put my unraid server to sleep, until recently when I installed S3 Sleep again, since I have pfsense router fully set up already.
I also changed my flash drive Last October 2023 to Samsung Bar Plus, but recently got faulty about a few days ago (got the "Unable to enumerate USB Device"); so I changed that.but for the last 2 days, I've gotten 3 random crashes/reboot/freezes. Initially I was thought it was the Dynamix S3 Schedule (inactivity) sleep that was crashing my system, but then I saw some call traces on my syslog.
I already ram memtest again since 2 yrs ago, and no errors.
Anyone know if this is the macvlan call trace issue or something else?
I currently switched to ipvlan to monitor it , and let S3 Schedule to put the system to sleep and see if it crashes.I have my diagnostics uploaded for reference as well..
Thanks for any help.
QuoteMar 27 17:51:22 kbnomadserver kernel: Call Trace: Mar 27 17:51:22
kbnomadserver kernel: <TASK> Mar 27 17:51:22
kbnomadserver kernel: \_\_schedule+0x5b2/0x612 Mar 27 17:51:22
kbnomadserver kernel: schedule+0x8e/0xcc Mar 27 17:51:22
kbnomadserver kernel: request\_wait\_answer+0xf7/0x1d3 Mar 27 17:51:22
kbnomadserver kernel: ? \_raw\_spin\_rq\_lock\_irqsave+0x20/0x20 Mar 27 17:51:22 kbnomadserver kernel: fuse\_simple\_request+0x1b0/0x1ef Mar 27 17:51:22
kbnomadserver kernel: fuse\_statfs+0xb0/0x132 Mar 27 17:51:22
kbnomadserver kernel: statfs\_by\_dentry+0x40/0x5e Mar 27 17:51:22
kbnomadserver kernel: vfs\_statfs+0x16/0x93 Mar 27 17:51:22
kbnomadserver kernel: user\_statfs+0x54/0x9f Mar 27 17:51:22
kbnomadserver kernel: \_\_do\_sys\_statfs+0x20/0x50 Mar 27 17:51:22
kbnomadserver kernel: do\_syscall\_64+0x6b/0x81 Mar 27 17:51:22
kbnomadserver kernel: entry\_SYSCALL\_64\_after\_hwframe+0x64/0xce Mar 27 17:51:22 kbnomadserver kernel: RIP: 0033:0x14e42aab6537 Mar 27 17:51:22
kbnomadserver kernel: RSP: 002b:00007ffd64f46fd8 EFLAGS: 00000202 ORIG\_RAX: 0000000000000089 Mar 27 17:51:22
kbnomadserver kernel: RAX: ffffffffffffffda RBX: 00007ffd64f47080 RCX: 000014e42aab6537 Mar 27 17:51:22
kbnomadserver kernel: RDX: 00007ffd64f483e8 RSI: 00007ffd64f46fe0 RDI: 000055814bf371f0 Mar 27 17:51:22
kbnomadserver kernel: RBP: 00007ffd64f46fe0 R08: 00007ffd64f483e8 R09: 000014e42ab9c3e0 Mar 27 17:51:22
kbnomadserver kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffd64f483e0 Mar 27 17:51:22
kbnomadserver kernel: R13: 000055814bf391b0 R14: 00007ffd64f483e8 R15: 000055814bf00800 Mar 27 17:51:22
kbnomadserver kernel: </TASK> -
-
-
Hi,
How are you guys doing?
I'm wondering why I can't seem to access some of my dockers' webUI when it doesn't have the same ip address as my server but the ones with the same ip address as the server + different port, works fine remotely.
How can I work around this so that I can access all my dockers remotely when the necessity arises? -
-
OIC. good to know.
I could agree with the SATA Cable since I just picked this old cable from the office.
I guess I should change the cables with bbrand new ones just to make sure.
Thank you for the info. -
Hi,
I am getting 1 Warning Error on my Parity drive. This is a new WD Gold that I bought a few months ago.
Is this a possible drive failure? -
20 hours ago, Squid said:
Without diagnostics (ideally in a separate thread), not much we can do to help
unfortunately, nothing was logged and I downgraded back to 6.10.3 stable
-
updated to 6.11.0-rc4 , unraid crashed twice in 1 day
-
On 7/19/2022 at 11:29 AM, ljm42 said:
Were you able to resolve your DNS issues?
Yes!
as What @JonathanM mentioned, I changed my Unraid DNS Servers to Cloudflare's 1.1.1.1 while routing all devices through pihole (except unraid).- 1
-
Recently bought 2 WD Gold 16TB. First time I bought HDD in about 10 yrs. All SSD & NVME until I switched to Unraid.
-
Just now, JonathanM said:
except Unraid itself
Gotcha.
I will do that once my Parity Sync is done.
Thanks for the info. -
1 hour ago, JonathanM said:
Why? There is no good reason to do that. Set Unraid's DNS to a reliable external source like 1.1.1.1 or 9.9.9.9, or google's DNS of 8.8.8.8.
That's what I understood from the forums to route everything to pihole and have pihole set the DNS to 1.1.1.1.
I set my Unraid's DNS IP to my Router's then my router's DNS is pointing to pihole which uses the 1.1.1.1 DNS Server.
What would be the best way to go about it? -
On 6/21/2022 at 11:34 AM, ljm42 said:
The optional Remote Access feature provides secure access to the Unraid webgui. No additional client software is needed, just a web browser. And a good root password.
WireGuard is harder to setup, and requires the client to run special software, but is arguably more secure.
Thanks!
I actually have both Remote Access and Wireguard set up.
I guess I could use the my servers for quick connect remotely when I have my VPN turned on, since connecting through wireguard requires me to turn my commercial VPN off and connect to the wireguard tunnel. -
Hi,
I just recently got this My Servers Error Message: "DNS issue, unable to resolve wanip4.unraid.net" but I can remote access actually works.
Not sure why it's saying that, though, I recenlty have set up pihole and set my unraid server's DNS to my Router which points back to pihole's Server, and router's IP as backup, but set router's DNS to point to pihole as well.attaching screenshot for reference.
-
On 7/28/2016 at 1:54 PM, Viaduct said:
Netdata docker is amazing. Simple to install and monitor in webpage.
Sent from my iPhone using Tapatalk
netdata doesn't show any Voltages at all; just a bit more detailed stats that you see on the dashboard
Lousy Performance on GPU Passthrough
in VM Engine (KVM)
Posted
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.