-
USB WLAN/BT Adapter stuck in CDROM mode
Stopping the VM, adding the WLAN adapter as optional, then starting the VM worked. It was taken out of CDROM mode and assigned a new ID. I repeated the above steps with the new ID and removed the old ID completely from the VM. The VM sees it with the new ID as a BT adapter as it did before. lsusb on the host shows the adapter is no longer in CDROM mode and has a new ID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 003 Device 005: ID 154b:00ee PNY USB 2.0 FD Bus 003 Device 006: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 007: ID 1d6b:0104 Linux Foundation Multifunction Composite Gadget Bus 003 Device 009: ID 0bda:c820 Realtek Semiconductor Corp. 802.11ac NIC Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubI also updated to 7.3.4 again. After the update and reboot, the WLAN adapter did not go back to CDROM mode this time and kept the same ID. I will keep this in mind for future updates/restarts just it case it acts up again. Thank you very much for your help! Edit to add more info: I stopped the VM once more and unplugged the adapter, then plugged it back in. This caused it to go back into CDROM mode with old ID from before, but adding it back and starting the VM got it out of that mode again. Previously, I was removing the old CDROM mode device from the VM, however, I am going to leave it assigned to the VM as optional even though it is "missing". I'm hoping this will help it recover automatically if unplugged or reset from the host.
-
USB WLAN/BT Adapter stuck in CDROM mode
I did downgrade back to 7.3.3 because I have a SONOFF Zigbee hub that also stopped working correctly. Not entirely sure what the correlation is there, if any. The Zigbee adapter is working again, but the WLAN adapter is still stuck in CDROM mode. I have attached diagnostics from before and after the downgrade. node304-diagnostics-20261101_1730.zip node304-diagnostics-20261101-1808.zip
-
USB WLAN/BT Adapter stuck in CDROM mode
Ah, that does explain it. I would have needed to take down the VM to do the 7.3.4 update. I do recall that Unraid did not show it being in CDROM mode previously though. It may have been due to making the device required in the VM rather than optional. At any rate, I was able to get it to show as a storage device, but can't get it to eject. Running the first two commands gave this output [0:0:0:0] disk ATA HGST HUH721212AL T9U0 /dev/sdb [1:0:0:0] disk ATA HGST HUH721212AL T9U0 /dev/sdc [2:0:0:0] disk ATA HGST HUH721212AL T9U0 /dev/sdd [3:0:0:0] disk ATA HGST HUH721212AL T9U0 /dev/sde [7:0:0:0] disk PNY USB 2.0 FD PMAP /dev/sda [8:0:0:0] cd/dvd Realtek Driver Storage 1.00 /dev/sr0 [N:0:1:1] disk Patriot M.2 P300 256GB__1 /dev/nvme0n1 [N:1:1:1] disk Patriot M.2 P300 256GB__1 /dev/nvme1n1The eject command on /dev/sr0 gives either this or no output and the drive remained in CDROM mode. It also takes like 20-30 seconds for the command to finish, almost like it gets hung up. I even tried with the -F and -r flags, but it still won't actually eject. eject: cannot open /dev/sr0: Device or resource busyRunning eject with the -v flag gives this and takes a few minutes. eject: device name is `/dev/sr0' eject: /dev/sr0: not mounted eject: /dev/sr0: is whole-disk device eject: /dev/sr0: trying to eject using CD-ROM eject command eject: CD-ROM eject command succeededI got the same output as above when running lsscsi again after the eject. lsusb still shows the same ID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 003 Device 003: ID 1d6b:0104 Linux Foundation Multifunction Composite Gadget Bus 003 Device 004: ID 154b:00ee PNY USB 2.0 FD Bus 003 Device 005: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 016: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter (Driver CDROM Mode) Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub I do have the Unassigned Devices plugin installed, but this device does not show up anywhere in Unraid as a storage device. I also no longer have it mapped to the VM, so it isn't being used there either. Running lsblk does confirm that it is not mounted anywhere on the system. NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 765.9M 1 loop /usr loop1 7:1 0 316.6M 1 loop /lib/firmware loop2 7:2 0 1G 0 loop /etc/libvirt sda 8:0 1 28.9G 0 disk └─sda1 8:1 1 28.9G 0 part /boot sdb 8:16 0 10.9T 0 disk └─sdb1 8:17 0 10.9T 0 part sdc 8:32 0 10.9T 0 disk └─sdc1 8:33 0 10.9T 0 part sdd 8:48 0 10.9T 0 disk └─sdd1 8:49 0 10.9T 0 part sde 8:64 0 10.9T 0 disk └─sde1 8:65 0 10.9T 0 part md1p1 9:1 0 10.9T 0 md /mnt/disk1 md2p1 9:2 0 10.9T 0 md /mnt/disk2 sr0 11:0 1 7.8M 1 rom zram0 252:0 0 0B 0 disk nvme0n1 259:0 0 238.5G 0 disk └─nvme0n1p1 259:1 0 238.5G 0 part nvme1n1 259:2 0 238.5G 0 disk └─nvme1n1p1 259:3 0 238.5G 0 part /var/lib/docker /mnt/m2pool The other really strange thing is that when I plug this adapter into my laptop running Fedora, it comes up as a network adapter without issue, so I know the adapter works fine. Like you said, it's likely because Unraid doesn't automatically eject it like my laptop must be doing.
-
USB WLAN/BT Adapter stuck in CDROM mode
I do want it passed to a VM, that is correct. It was working previously perfectly fine and I was able to use it as desired. The VM saw it and was able to use it correctly. The adapter is unbranded unfortunately. I have attached the new diagnostics with the adapter attached. If the diagnostics say it was working on 7.3.3, then that would be the last version. I don't think I have diagnostics from that version. Here is the output of the commands: lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 003 Device 003: ID 1d6b:0104 Linux Foundation Multifunction Composite Gadget Bus 003 Device 004: ID 154b:00ee PNY USB 2.0 FD Bus 003 Device 005: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 011: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter (Driver CDROM Mode) Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hublsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 20000M/x2 /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 003: Dev 002, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M |__ Port 004: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 004: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 004: Dev 003, If 2, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 004: Dev 003, If 3, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 004: Dev 003, If 4, Class=Audio, Driver=snd-usb-audio, 480M |__ Port 004: Dev 003, If 5, Class=Audio, Driver=snd-usb-audio, 480M |__ Port 004: Dev 003, If 6, Class=Mass Storage, Driver=usb-storage, 480M |__ Port 006: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 480M |__ Port 007: Dev 005, If 0, Class=Human Interface Device, Driver=usbfs, 12M |__ Port 008: Dev 011, If 0, Class=Mass Storage, Driver=[none], 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M command -v usb_modeswitch none node304-diagnostics-20261031-1204.zip
-
USB WLAN/BT Adapter stuck in CDROM mode
Here you are node304-diagnostics-20261030-1114.zip
-
USB WLAN/BT Adapter stuck in CDROM mode
I have what reports as a Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter that is now showing it is in "Driver CDROM Mode". It was previously working prior to updating to 7.3.3 and updating to 7.3.4 did not resolve the issue. I have scoured around and cannot seem to come up with a way to get it out of this mode in Unraid. When using it on other Linux devices, it presents as a WLAN/BT adapter as expected.
-
cordlord started following Error When using Authentik as my OIDC provider and USB WLAN/BT Adapter stuck in CDROM mode
-
Error When using Authentik as my OIDC provider
Well, I guess nevermind cause another update came through and this issue was resolved.
-
Error When using Authentik as my OIDC provider
I'm on Unraid v7.1.4 and the Unraid Connect plugin is on v2025.09.03.1929. I have Authentik setup as an OIDC provider and am receiving these errors when trying to sign in with it: [15:09:54 ERROR OidcTokenExchangeService]: Token exchange failed {"apiVersion":"4.18.2+5d89682","logger":"OidcTokenExchangeService","context":"OidcTokenExchangeService"} [15:09:54 ERROR OidcTokenExchangeService]: Error type: ClientError {"apiVersion":"4.18.2+5d89682","logger":"OidcTokenExchangeService","context":"OidcTokenExchangeService"} [15:09:54 ERROR OidcTokenExchangeService]: Error message: invalid response encountered {"apiVersion":"4.18.2+5d89682","logger":"OidcTokenExchangeService","context":"OidcTokenExchangeService"} [15:09:54 ERROR OidcTokenExchangeService]: Error code: OAUTH_INVALID_RESPONSE {"apiVersion":"4.18.2+5d89682","logger":"OidcTokenExchangeService","context":"OidcTokenExchangeService"} [15:09:54 ERROR OidcTokenExchangeService]: Error cause chain: {"apiVersion":"4.18.2+5d89682","logger":"OidcTokenExchangeService","context":"OidcTokenExchangeService"} [15:09:54 ERROR OidcTokenExchangeService]: [Cause 1] OperationProcessingError: unexpected "iss" (issuer) response parameter value {"apiVersion":"4.18.2+5d89682","logger":"OidcTokenExchangeService","context":"OidcTokenExchangeService"} [15:09:54 ERROR OidcTokenExchangeService]: [Cause 1] Code: OAUTH_INVALID_RESPONSE {"apiVersion":"4.18.2+5d89682","logger":"OidcTokenExchangeService","context":"OidcTokenExchangeService"} [15:09:54 ERROR OidcTokenExchangeService]: [Cause 2] object: [object Object] {"apiVersion":"4.18.2+5d89682","logger":"OidcTokenExchangeService","context":"OidcTokenExchangeService"} [15:09:54 ERROR OidcService]: OAuth callback error: invalid response encountered {"apiVersion":"4.18.2+5d89682","logger":"OidcService","context":"OidcService"} [15:09:54 ERROR OidcRestController]: OIDC callback error: UnauthorizedException: Authentication failed {"apiVersion":"4.18.2+5d89682","logger":"OidcRestController","context":"OidcRestController"}I have double, triple checked that all of my settings are correct both on the plugin and in Authentik. I also have Unraid.net setup and that works perfectly with 0 errors. When I save the OIDC settings, the logs show successful discovery of all the endpoints and gives no errors, so I'm confident that the config is all correct. Edit: I should also mention that Authentik uses the issuer URL as https://auth.domain.com/application/o/unraid/ WITH the trailing '/'. Even though the Unraid docs and error message state to NOT include that, the discovery will error out unless it is included. When I inspect the JWT data, the value for the iss claim also includes the trailing '/'. This seems like an issue somewhere in Unraid where it's getting slightly different data than it's expecting.
-
Disable User/Password login (for specific IP-Ranges) when OIDC is configured
Just my two cents, I'd like a whitelist and a blacklist of client IPs where I can/can't see the username/password prompt. The main way I'd use this is to just whitelist my local and VPN subnets so I can get in on my own network should my OIDC be down, while everywhere else would only see the OIDC providers. Another way that may be easier or require less config, would be to restrict it by url. I have a reverse proxy and domain, so I'd preferably only like to see the OIDC when accessing from there, but would still like to see the username/password field if accessing Unraid through the IP address. It would also be sweet to have auto-signin if I'm already signed in with my OIDC provider.
-
Low-power 2023+ Intel N & U series boards (all form factors) + info on turnkey solutions
Next time I'm able to take my server down, I would be happy to test this out. The only fan I have connected to the motherboard is the cpu fan, but I would be comfortable disconnecting that as the heat sinks should handle the cpu at idle. Good tip about the power measurements. I'll find another way and come back with more concrete numbers, both loaded and unloaded. On the Aliexpress page, they claim the board should sit around 18-23 watts completely bare. We'll see if my numbers are similar.
-
Low-power 2023+ Intel N & U series boards (all form factors) + info on turnkey solutions
Alright, so I finally received the board and got it installed. I've had it running for about 4 days now. In summary, I do not regret this upgrade at all. This new board is MILES ahead of the N5105. Absolutely worth the extra money. Full Overview: Note: When using the term "idle" in my case, this means one drive spun up and no special processes running outside of Unraid, containers and VMS. I posted all the specs in the last post and they all seem to be correct. One correction, I believe is, that this is a CWWK board. I'm not completely savvy to how resellers work, but I got it from the Aliexpress link provided. The board arrived intact and passed all of my testing. It booted, runs the same American Mega Trends bios all of these boards run, and has been running my server perfectly. Both of the boards support automatic power on after power loss. The USB 3.0 header on the N305 board is a very nice addition. The biggest benefit for this board over other N305 boards specifically, is that the 2nd M.2 slot and the PCIe x4 expansion slot are SEPARATE, meaning they can both be used AT THE SAME TIME. On other N305 boards, these are shared, meaning you can only have one or the other active. With the size constraints of this board, you will need to use a riser cable with the PCIe x4 expansion slot if you're also using any of the SATA ports as they will interfere with each other, but this is a small price to pay in my opinion. I indeed am running a single Crucial DDR5 32GB 5200MHz RAM clocked down to the max supported 4800MHz with 0 issues whatsoever. Memtest passed a full 13 passes with 0 issues. Unraid sees all 32GB and has not had any issues. The Noctua NH L12S cooler I ordered mounted right over the included copper heat-sink with no problems at all. It keeps this CPU very happy at 17C at "idle". I've never seen it jump higher than 30C under load. I don't see myself ever worrying about overheating. Note: This is in an unheated room during winter where ambient temp is around 4.5C, so your temps may be a little higher. I have the fan running about half speed if the temps get over 20C, then jump to full speed at 40C. This is configurable through the bios. As for actual performance for Unraid, this thing is a beast. It booted right up after swapping the motherboard and has no issues whatsoever. No changes or special configs were necessary to get anything working, c-states, network ports, etc. I'm running about 30 docker containers, pihole, full media stack and full Nextcloud AIO install, and a Home Assistant VM, 3cpus 6GB ram, and it barely breaks a sweat. I rarely see it go over 10% usage unless I'm doing something intensive or doing a big file transfer. Even then, it can handle a ton and I still have yet to actually get it to 100% usage outside of a benchmark test. My favorite part, there has been no significant power draw changes during normal usage. I have a UPS that tells me the total power draw and the numbers are exactly the same as they were with the old board. Overall, with 2 NVMe drives, 4 7200RPM SATA drives, and the new motherboard, I'm running about 30 watts at "idle" and up to 50 watts or so during something like a parity sync. This is with a PSU that isn't even super efficient at this power draw. Again, all out of the box with no time spent tinkering with the bios or special configs. All in all, if you're looking for a low-power, small form factor, yet powerful, modern and flexible CPU, I would highly recommend this motherboard for the price. I paid right around $300 for the board and cooler. If you have any other questions about the board, my setup, or want me to run any tests, just let me know.
-
Low-power 2023+ Intel N & U series boards (all form factors) + info on turnkey solutions
Just stumbled upon these boards only a month after I bought an N5105 board. https://www.aliexpress.us/item/3256807243287509.html?spm=a2g0o.order_list.order_list_main.5.21ef180247OG2P&gatewayAdapt=glo2usa#nav-specification Edit: It appears to be the same board as this: https://cwwk.net/products/cwwk-12th-gen-i3-n305-n100-2-intel-i226-v-2-5g-nas-motherboard-6-sata3-0-6-bay-soft-rout-1-ddr5-4800mhz-firewall-itx-mainboard?_pos=21&_sid=f0793905f&_ss=r&variant=46326552625384 Not sure if anyone else has seen them. It's a Topton i3-N305 board, but it's different from the others I've seen. It's got 2x M.2 on PCIe x1, 6x SATA 3.0 on PCIe x1, only 2x 2.5 GB eth, a 1x PCIe x4 slot, a USB3 header, and support for Intel 115x coolers. All this at only 18W. The pcb is also purple instead of green or black. This board fixes all the issues I was seeing with the N5105. I only need 2 eth instead of 4 and wanted a little more power than 4 cores. 8 is plenty for me. My least favorite was the cooler support, which was non existent. With the N305 board, you can use coolers like the Noctua NH L12S. Having the ability to add a graphics card for transcoding, a 10 GB eth, or more SATA ports is also great for future proofing. The one downside is the single channel RAM, but, the way I see it, I really don't dual channel for a small server application. Especially since it supports DDR5 4800MHz, nearly double the speed of the N5105. So, needless to say, mine is on it's way and will be immediately replacing the old board. I can post an update once it's in if anyone is interested.
-
[Plugin] Snapshots
Thanks for this. It would be most helpful to have this info built in to the system help. And really any other amount of help information for that matter. This plugin is severely lacking in that area.
cordlord
Members
-
Joined
-
Last visited