zanzu
Members-
Posts
25 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
zanzu's Achievements
Noob (1/14)
2
Reputation
-
Main and Shares tabs rendering wrongly with 6.12 and 6.12.1 in Chrome
zanzu replied to Kedryn's topic in General Support
Turned out to be my web proxy server blocking something from the Main Menu. -
Main and Shares tabs rendering wrongly with 6.12 and 6.12.1 in Chrome
zanzu replied to Kedryn's topic in General Support
Today this happened to me as well. Main menu doesn't show the drives under Google Chrome. However, in Safari, no issue; Web GUI shows all disks and details of each drive. I'm using 6.12.2. -
Thanks. I found which docker container is causing the segfault. As for the randon power down, I notice the server will power off when we're playing a video game in Windows10 VM. I've stopped the VM to see how long the server will remain up. Running memtest is a good suggestion - thank you.
-
Recently, my server started having these random shutdowns (power offs). I've enabled syslog logging and noticed a constant stream of segfaults. It's too early to conclude these segfaults are causing the server to power off but does Anyhow know what could be causing these segfaults? Dec 7 22:45:28 XXXXX kernel: library[10406]: segfault at 200000030 ip 000014f8a2165166 sp 000014f89f05d2b0 error 4 in libwebsockets.so.19[14f8a2158000+3b000] Dec 7 22:45:28 XXXXX kernel: Code: 30 48 85 ff 75 21 ba ff 00 00 00 48 8d 35 63 0e 03 00 4c 89 f7 e8 da 2f ff ff 48 83 44 24 30 0d 48 8d 2d 3d cf 04 00 44 89 e0 <23> 45 30 0f 84 6b 01 00 00 ba 00 01 00 00 48 8d 35 c5 d0 04 00 44 Dec 7 22:45:33 XXXXX kernel: library[10730]: segfault at f9a4 ip 0000150bb5198166 sp 0000150bb296f2b0 error 4 in libwebsockets.so.19[150bb518b000+3b000] Dec 7 22:45:33 XXXXXX kernel: Code: 30 48 85 ff 75 21 ba ff 00 00 00 48 8d 35 63 0e 03 00 4c 89 f7 e8 da 2f ff ff 48 83 44 24 30 0d 48 8d 2d 3d cf 04 00 44 89 e0 <23> 45 30 0f 84 6b 01 00 00 ba 00 01 00 00 48 8d 35 c5 d0 04 00 44 Dec 7 22:45:44 XXXXXX kernel: library[11488]: segfault at 1a0000001b2 ip 000014642e198166 sp 000014642b9842b0 error 4 in libwebsockets.so.19[14642e18b000+3b000] Dec 7 22:45:44 XXXXX kernel: Code: 30 48 85 ff 75 21 ba ff 00 00 00 48 8d 35 63 0e 03 00 4c 89 f7 e8 da 2f ff ff 48 83 44 24 30 0d 48 8d 2d 3d cf 04 00 44 89 e0 <23> 45 30 0f 84 6b 01 00 00 ba 00 01 00 00 48 8d 35 c5 d0 04 00 44 Dec 7 22:45:49 XXXXXX kernel: traps: library[11867] trap stack segment ip:14b491f6a166 sp:14b48f71a2b0 error:0 in libwebsockets.so.19[14b491f5d000+3b000] Dec 7 22:45:55 XXXXX kernel: traps: library[12193] trap stack segment ip:14a11236a166 sp:14a10fb1a2b0 error:0 in libwebsockets.so.19[14a11235d000+3b000] Dec 7 22:46:00 XXXXX kernel: traps: library[12563] trap stack segment ip:147589cea166 sp:147586bf42b0 error:0 in libwebsockets.so.19[147589cdd000+3b000] Dec 7 22:46:07 XXXXXX kernel: player[13448]: segfault at 14a4468b18ac ip 000014a449373ae8 sp 000014a44698d2d8 error 4 in libwebsockets.so.19[14a44935d000+3b000] Dec 7 22:46:07 XXXXXX kernel: Code: 02 00 00 64 48 2b 0c 25 28 00 00 00 74 05 e8 2f a2 fe ff 48 81 c4 e8 02 00 00 c3 0f be b7 bd 04 00 00 48 8b 3f e9 91 be fe ff <f6> 87 cc 07 00 00 08 75 6a 55 31 ed 53 48 89 fb 52 e8 92 a5 fe ff Dec 7 22:46:12 XXXXXX kernel: traps: library[13489] trap stack segment ip:153f1ad1d166 sp:153f184d02b0 error:0 in libwebsockets.so.19[153f1ad10000+3b000] Dec 7 22:46:19 XXXXXX kernel: player[14291]: segfault at 14e069e1885c ip 000014e06d16eae8 sp 000014e069edb2d8 error 4 in libwebsockets.so.19[14e06d158000+3b000] Dec 7 22:46:19 XXXXXX kernel: Code: 02 00 00 64 48 2b 0c 25 28 00 00 00 74 05 e8 2f a2 fe ff 48 81 c4
-
HighPoint RocketStor 6418s. Fans won’t spin?
zanzu replied to TheCarlough's topic in Storage Devices and Controllers
Has anyone figured out how to control the fan speed? I populated the bottom half of the enclosure with new drives and started receiving temperature warning beeps; The drives are around 55+C. When I opened the enclosure, I notice Highpoint had connected both fans to one of the molex. Interesting... So since I already had the enclosure open, I replaced the fans and connected one fan to each of the molex connectors. Nothing changed.. The fans initially spin-up when the unit is powered on but still only 1 fan comes on. I'm incline to split the power molex to one of the drive bays and have the fans on all the time. But wanted to confirm with this group if anyone had success controlling the fans or know the conditions when they both will come on? -
Thanks. I visited Dortania.github.io and it seems the AMD 6600 is an unsupported GPU. However, the 6600XT is supported and requires the Lilu and WhateverGreen kexts. https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/amd-gpu.html#navi-2x I do have the AMD 6600 working in the VM but as a generic display (System information shows 'Graphics Display 31MB'. I'm going to try installing those kext and see if it makes any difference. Here's the output from System Report -> Graphics/Displays: Display: Type: GPU Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 31 MB Vendor: AMD (0x1002) Device ID: 0x73ff Revision ID: 0x00c7 Kernel Extension Info: No Kext Loaded Displays: Display: Resolution: 3840 x 2160 (2160p/4K UHD 1 - Ultra High Definition) UI Looks like: 3840 x 2160 Framebuffer Depth: 24-Bit Color (ARGB8888) Main Display: Yes Mirror: Off Online: Yes Automatically Adjust Brightness: Yes
-
Hi, I've managed to get the AMD Radeon RX6600 passthrough to a Monterey VM on UnRaid 6.9.2. However, the GPU name is not listed in the System Information or "About This Mac". I understand the RX6600 is natively supported in Monterey; Is there anything I need to modify to get the name displayed properly? Any suggestion is appreciated.
-
I also have unresponsive shares on MacOS Monterey and Big Sur) when using 6.10 rc1 or rc2. For now, I revert back to 6.9.2 .
-
zanzu started following BigSur VM cannot mount Samba shares under 6.10-rc1
-
I have a BigSur VM mounting two Unraid Samba shares (Music and Videos) with a passthrough Asus 10Gb nic. Under 6.9.2, the shares mount without any issues for a couple months. Recently, I upgraded to 6.10-rc1 but under the release candidate, the mounts hang and the VM becomes unusable until I stop exporting the shares via Unraid. I have the shares automount upon login. To confirm the problem is related to 6.10-rc1, I downgraded to 6.9.2 and started the VM; Shares mounted without any problems. I upgraded the Unraid server to 6.10-rc1 and started the VM, problem returned; The VM cannot mount the shares. I've even tried to mount the shares manually but the system still hangs. I'll compare the smb configurations later but wanted to bring this issue to the forum and see if anyone else experience a similar or same problem.
-
Big Sur 11.6 VM+NVME boot when GPU Passthrough -> PXE Boot
zanzu replied to zanzu's topic in VM Engine (KVM)
Thank you! This is very helpful!! -
Big Sur 11.6 VM+NVME boot when GPU Passthrough -> PXE Boot
zanzu replied to zanzu's topic in VM Engine (KVM)
Yeah, I checked. I'll hold off for the moment. Does anyone know of a cheaper card that's supported by Big Sur and VFIO (supports FLR)? -
Big Sur 11.6 VM+NVME boot when GPU Passthrough -> PXE Boot
zanzu replied to zanzu's topic in VM Engine (KVM)
Quick update: I removed the 5500XT due to instability with the server; The system would reboot whenever I try to shutdown the VM. After some research, it seems the AMD reset bug is fixed in the 6000 series cards and the patch/module approach for the 5000 series card is not working for me. Best solution is to remove the card from the system and purchase a 6800 GPU.