Everything posted by joelones
-
Array does not start on manual invocation 7.3.1
it appeared to be the usb_manager plugin causing the array not starting, closing.
-
Array does not start on manual invocation 7.3.1
Sorry by what is your question? I'd like to stop the array manually to test something and then bring it up manually. The problem is that it doesn't come up. That's the problem. There's no indication in the log why the array could not come up. It's terrible from a user experience perspective that there's no warning or visible error. I'm spinning in circles with this now.
-
Array does not start on manual invocation 7.3.1
I will try but what would booting in safe mode confirm? Does it have something to do with this error? No internal boot setup detected. Launch Internal Boot to configure one. Would this prevent the array from starting once I stop the array ? If so why is this happening? And why would the array come up fine on reboot?
-
Array does not start on manual invocation 7.3.1
Running 7.3.1 and it appears that while stopping and then starting the array manually, the array does not come up. Seems fine on a complete reboot. I see this in the log. Thoughts on what might be going on here? emhttpd: cmdStart: already starting clarabell-diagnostics-20260603-1136.zip Maybe this go be the culprit? I also see a stale reference to vm directory, not sure how to remove this reference, is it in the img file? 2026-06-03 15:26:54.398+0000: 14020: info : libvirt version: 12.2.0 2026-06-03 15:26:54.398+0000: 14020: info : hostname: clarabell 2026-06-03 15:26:54.398+0000: 14020: error : virDirOpenInternal:3163 : cannot open directory '/mnt/user/kvm/domains/windows7': No such file or directory 2026-06-03 15:26:54.398+0000: 14020: error : storageDriverAutostartCallback:213 : internal error: Failed to autostart storage pool 'windows7': cannot open directory '/mnt/user/kvm/domains/windows7': No such file or directory 2026-06-03 15:26:56.705+0000: 14020: warning : qemuDomainObjTaintMsg:5727 : Domain id=1 name='windows10' uuid=589b80db-794f-9069-8df3-49347dab4887 is tainted: high-privileges
-
Dockers missing IP addresses link goes to about:blank#blocked
Thanks. But what you're saying is to rollback to a previous version of my containers exhibiting this issue? But the problem seems unraid / GUI related, no? Not sure sure I want to rollback my containers., interesting though, I'm having problems with some binhex containers too but they did communicate with each other despite the GUI anomaly
-
Dockers missing IP addresses link goes to about:blank#blocked
Thank you for your help anyway.
-
Dockers missing IP addresses link goes to about:blank#blocked
Thanks for the help. tried recreating / removing the custom network a bunch of times, whenever I set the driver to macvlan it doesn't appear in the gui...why it does it for some dockers on the same custom network and not others is a real mystery
-
Dockers missing IP addresses link goes to about:blank#blocked
How does one recreate the custom network? I think my 192.168.10.1/25 network br1.10 was automatically created when I created a bridge on eth1 with a specific VLAN. I tried using the UI to uncheck the docker network (restarted) and then recreate it, not sure if this is the right way (see screenshot) but it did not change anything.
-
Dockers missing IP addresses link goes to about:blank#blocked
No they don't. Makes no sense to me. I did a normal downgrade via the UI, no dice. Then I actually took a backup of the USB before I started and overwrote the UNRAID USB and still the same. So confused
-
about:blank#blocked for all WebUI links
I'm also experiencing this after installing 6.12.11 for some reason: help?
-
Dockers missing IP addresses link goes to about:blank#blocked
Just upgraded to 6.12.11 and now some of my IPs for docker on a custom network don't show in the GUI and link goes to about:blank#blocked. Can someone please shed some light here? Why it is all of a sudden happening to some but not all customer IP containers ? Deleting the docker.img and containers does nothing.
-
6.12.6 Fails to load Windows VM and Onboard Intel GPU
I'm still on 6.12.3 and would like to upgrade but facing multiple issues upon trying 6.12.6. Any guidance would be appreciated. The Intel GPU CometLake-S GT2 [UHD Graphics 630] fails to load upon bootup thus the Jellyfin docker fails to start as it is used for gpu transcoding My Windows 10 VM with a pass-through nvdia quadro fails to start All is fine on 6.12.3. Thoughts? clarabell-diagnostics-20231206-1504.zip
-
[Support] Linuxserver.io - Unifi-Controller
I'm trying to the new UniFi Network Application container and getting a tomcat 404 error using a custom bridge setup. Previous container works well with this setup. Can anyone please advise (unraid 6.12.3)
-
intel gpu drivers for jellyfin
Just tried it again today, same issue same call trace
-
intel gpu drivers for jellyfin
No I reverted back to 6.12.3 which is working fine. I would add this as the following: mkdir -p /boot/config/modprobe.d echo "options i915 enable_fbc=1 enable_guc=3" > /boot/config/modprobe.d/i915.conf mkdir -p /boot/config/modprobe.d echo "options i915 enable_dc=0" > /boot/config/modprobe.d/i915.conf what does this do? for 6.12.3, no need to add the modprobe lines, it just works. odd
-
intel gpu drivers for jellyfin
Apparently `/dev/dri/*` which I pass into the jellyfin docker does not exist. root@clarabell:/boot/config# intel_gpu_top -L No GPU devices found Tried this, but modprobe just hangs: mkdir -p /boot/config/modprobe.d echo "options i915 enable_fbc=1 enable_guc=3" > /boot/config/modprobe.d/i915.conf Here is the diagnostics: root@clarabell:~# lsmod | grep intel intel_rapl_msr 16384 0 intel_rapl_common 24576 1 intel_rapl_msr intel_powerclamp 16384 0 kvm_intel 282624 4 iosf_mbi 20480 2 i915,intel_rapl_common kvm 983040 1 kvm_intel crc32c_intel 24576 2 ghash_clmulni_intel 16384 0 aesni_intel 393216 0 crypto_simd 16384 1 aesni_intel cryptd 24576 2 crypto_simd,ghash_clmulni_intel intel_cstate 20480 0 intel_gtt 24576 1 i915 agpgart 40960 2 intel_gtt,ttm intel_uncore 200704 0 intel_pmc_core 49152 0 clarabell-diagnostics-20230912-1149.zip
-
Add Intel iGPU QSV Quick Sync Encoding to Official Plex-Media-Server the easy way.
Are users having problems loading the intel quick sync drivers with 6.12.4? I seem to have to revert back to .3 to get intel quick sync working in my container.
-
intel gpu drivers for jellyfin
Just install 6.12.4 and can't start jellyfin due to what i think is missing intel drivers??!! Is there a package app for this now with 6.12.4? .3 didn't have this problem
-
quad nice settings gone
Seems like a power cycle brought back the nic's activities LEDs, not sure what happened. could be I'm on an old (currently overloaded) UPS so maybe power issues, i hope not hardware.
-
quad nice settings gone
Here's a picture of the nics, the right one is passthroughed to pfsense and the left one is all of a sudden giving me a problem.
-
quad nice settings gone
you're right, didn't help. here's my zip. did my quad nic just die? i see activity on the quad leds, only the green led is on. i still have the onboard nic which it now thinks is eth0...
-
quad nice settings gone
Before doing that, I only see a network-rules.cfg.old and don't see another. The file seems to have the valid network settings. I copied it to network-rules.cfg and will try a reboot
-
quad nice settings gone
Can someone please help!!! Having a major crisis. Just updated to 6.12.4 and the settings for my quad nic are gone, I can no longer see the other eth1-3 interfaces Tried downgrading to 6.12.3 with the same issue Please help
-
VLANs on a single NIC
I'm currenlty using a second Intel Quad NIC to allocate separate VLANs to a couple of my dockers. Basically port 1 is untagged (host), and port 2 and 3 are configured as separate VLANs (attached image) and I use these bridges for certain dockers. I believe I did because I had problems with inter-docker networking with other dockers bridged (to the host) and to the same parent interface. Could I do away with this NIC and use the onboard Intel NIC on the motherboard and set up VLAN using a parent interface but will I have MacVLAN problems like inter-docker communication with the unRAID box and VLANs?
-
Upgrade old build and migration process
Hello, Although hardware related, I'm posting my question here as I will need to upgrade on older AMD system to an Intel 11th gen based system and I'm not sure how easy it is to migrate to a new motherboard + CPU combo (while keeping the disks and HBA). Will unRAID be smart to work with the existing configuration? Requirements: As many PCI-E slots as possible without going to server motherboards. GPU, HBA, and possibly two Intel Quad NICs. One for a VM and one for VLANs allocated to dockers. Run a maximum of two VMs; one for pfSense (passing in an Intel Quad NIC), and another VM for a basic Windows box for slicing models for my 3D printers. Intel iGPU using quicksync for Jellyfin hardware acceleration This is what I have come up with. Thoughts? Proposed hardware: ASUS Z590-A Prime 11700k or 11600k or even i7-10700 G.SKILL Ripjaws V Series 32GB (2 x 16GB) 288-Pin PC RAM DDR4 3200 (PC4 25600) I already have a Rosewill RSV-L4500U server case but I take it I will need a new low profile heatsink for the CPU? The one I'm using for the old AMD 8350 surely might not work, right? Corsair TX750 from existing box (assuming this will still work?) Questions: Hardware specs seem ok for what I need? Is migrating to a new motherboard + CPU combo easy? I'm using a second Intel Quad NIC to allocate separate VLANs to a couple of my dockers. Could I do away with a second NIC and use the onboard Intel NIC on the motherboard and set up VLANs? Will have MacVLAN problems like inter-docker communication with the unRAID box and VLANs?