Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

handycapp

Members
  • Joined

  • Last visited

Everything posted by handycapp

  1. Hi folks, this issue has taken me an inordinate amount of time to identify. My environment: Unraid OS: 7.2.3 VM Type: UEFI (OVMF) Guest OS: Debian 12 (but issue is hypervisor‑level, not guest‑specific) Hypervisor: KVM/QEMU via libvirt Storage: vdisk1.img on /mnt/user/domains/<vmname>/ UEFI VMs are the default for most modern OSes. Cloning is essential for: staging changes testing upgrades templating disaster recovery snapshot‑style workflows At present, cloning a UEFI VM requires manual intervention in multiple areas of the XML and filesystem, which is error‑prone and not discoverable. Summary of the Problem Cloning a UEFI VM via the Unraid VM Manager produces a VM definition that is not bootable, even when: The vdisk is valid The vdisk path is correct No passthrough devices are assigned No ISO is attached Boot order is correct BIOS type matches the source VM The cloned VM always drops into OVMF BIOS and cannot locate a bootloader. This behaviour is fully reproducible. Root Cause Analysis After detailed inspection of the generated XML and libvirt runtime state, the following issues are present in every clone: 1. Missing NVRAM (VARS) file for the cloned VM The source VM has: Code <nvram>/etc/libvirt/qemu/nvram/<UUID>_VARS-pure-efi.fd</nvram> The cloned VM’s XML references a different UUID, but no corresponding VARS file is created in: Code /etc/libvirt/qemu/nvram/ As a result, OVMF has: no EFI variables no boot entries no BootOrder no saved boot manager state This alone is sufficient to cause a drop into BIOS. Manual fix (works): Code cp /etc/libvirt/qemu/nvram/<sourceUUID>_VARS-pure-efi.fd \ /etc/libvirt/qemu/nvram/<cloneUUID>_VARS-pure-efi.fd Then update the <nvram> path in the clone’s XML. 2. Inherited passthrough <hostdev> blocks The clone inherits all <hostdev> entries from the source VM, including GPU audio functions, USB controllers, NVMe devices, etc. If the source VM is running, the clone cannot start because the PCI devices are already bound to vfio-pci by the source domain. Even when removed in the GUI, the XML may still contain stale <hostdev> blocks. 3. Inherited ISO <disk device='cdrom'> block Even when the GUI shows “None” for OS Install ISO, the cloned XML still contains: Code <disk type='file' device='cdrom'> <source file='/mnt/user/isos/<installer>.iso'/> </disk> This causes QEMU to prioritize the CD-ROM device unless boot order is explicitly overridden. 4. Boot order is not reset The clone inherits the source VM’s boot order, which may prioritize: CD-ROM Network boot Nonexistent devices Combined with missing NVRAM, this guarantees a BIOS drop. 5. vdisk path is correct, but clone still fails to boot Even when pointing the clone directly at the source VM’s known‑good vdisk, the clone still drops into BIOS. This confirms the issue is not related to: vdisk corruption block‑commit snapshot chain copy failure The failure is entirely in the VM definition (XML + missing NVRAM). Steps to Reproduce (Minimal) Create a UEFI VM (OVMF) Shut it down Use Clone in VM Manager Manually copy the vdisk to the clone’s folder Start the cloned VM Result: VM enters OVMF BIOS and cannot boot. Expected Behaviour Cloning a VM should: Generate a new NVRAM (VARS) file Remove passthrough devices unless explicitly selected Remove ISO references Reset boot order to vdisk first Produce a bootable clone without manual XML editing Actual Behaviour Cloning produces a VM that: Has no NVRAM file Contains stale passthrough hostdevs Contains stale ISO references Has incorrect boot order Cannot boot even with a known‑good vdisk Questions for Lime Technology: Is the absence of automatic NVRAM generation for cloned UEFI VMs a known limitation in 7.2.3? Is there an officially supported method to clone UEFI VMs without manual XML/NVRAM intervention? Is automatic NVRAM creation planned for a future 7.x release? Should the VM Manager remove inherited hostdev and ISO blocks when cloning? Is the VM Manager rewrite (mentioned in prior forum posts) expected to address these issues? sagittarius-diagnostics-20260107-2100.zip
  2. Doh!😆Thanks Kilrah very muchly. Thought I was going bananas,cheers😄
  3. Summary: Wordpress not connecting to mariadb, and I'm not getting anywhere yet. Newly installed MariaDB.Official and Wordpress dockers today. Wordpress will not launch from the machine's local network IP address:8080 I've attached logs of both dockers and their configs, as well as diagnostics. I can't see any glaring errors in configs, mariadb log perhaps? Diagnostics file for docker is empty, and other dockers appear to be fully functional. Any help would be greatly appreciated... 2025-10-06 local-logterminal-MariaDB-Official.log.txt 2025-10-06 logterminal-WordPress.log.log.txt sagittarius-diagnostics-20251006-1847.zip
  4. Ah yes 7.2, thanks Jorge. Yes, so far so good. Running long enough now with both drives parity sync, couple of Dockers and VMs running under load. No notifications or errors pertaining to drives whatsover ... (yet). Cheers
  5. Hi Jorge, it seems the cause of USB disconnections and system crashes was a faulty drive (#13). Once that was removed and -> New Config => system appears stable 😀 So haven't gone to 7.1.5 beta yet. Downgrades however weren't available to select?
  6. Yes, the USB driver and resource limitations are not ideal. Yet, I've had the same setup for years with 2 NUC models and never had these issues before, albeit with 4 fewer drives & no drive enclosure. Currently it's a non-critical backup server, it's worth testing it with the beta and may go back versions until stability is evident. Cheers Jorge.
  7. Ok... interesting, it's happened again Jorge. Overnight all drives now with read errors, flash drive unreadable ... diags attached. unsuccessful stop via GUI stop via console -> emcmd cmdStop=Stop -> no indication of array stopping neither from GUI nor console. no option but to powercycle. On rebooting and array start, system seems ok. No read errors, just parity check running ... diags attached. So, the next troubleshooting stage is an upgrade to Unraid 7.2 beta. sagittarius-diagnostics-20250922-1403.zip sagittarius-diagnostics-20250922-1454.zip
  8. Thanks Jorge, @ console nginx stop and start fixes the issue and am monitoring system with Netdata docker to confirm causes. Yes, if it happens again overnight, I'll update from Tools > Update OS after another flash backup and parity disk 2 sync finishes. Very much appreciate the support Jorge😊 Cheers
  9. Interesting development Jorge. The system seemed stable and was rebuilding as expected but overnight the display of Main view is blank and have tested with several devices and browsers, all showing the same thing as per attached screenshot. Other GUI views such as Dashboard, Plugins, Settings etc display as normal, and the Parity rebuilding at the bottom end of Main view (attached) suggests it still running, although system log at time 6:25:40 shows this nginx error: Sep 21 06:25:40 SAGITTARIUS nginx: 2025/09/21 06:25:40 [error] 17238#17238: MEMSTORE:01: force-reaping msg with refcount 1 On searching for this error i found this description and possible causes/solutions: The error MEMSTORE:00: force-reaping msg with refcount 1 typically indicates a memory management issue in Unraid, often related to Nginx or the Nchan module. This can occur when shared memory resources are exhausted or improperly released. Possible Causes Shared Memory Exhaustion: Insufficient memory allocated for Nchan or other shared memory operations. Improper Resource Cleanup: Messages or channels not being properly released, leading to lingering references. High System Load: Excessive traffic or resource usage causing instability. 1. Increase Shared Memory Allocation Adjust the nchan_max_reserved_memory parameter in your Nginx configuration to allocate more memory for Nchan. Example Configuration Update: nchan_max_reserved_memory 256M; Restart Nginx after making changes: /etc/rc.d/rc.nginx restart 2. Debugging and Restarting Services If the issue persists, restart Nginx to clear any lingering memory issues: /etc/rc.d/rc.nginx reload 3. Check System Logs and Resources Monitor system logs (/var/log/nginx/error.log) and resource usage using tools like top or htop to identify bottlenecks. 4. Update Unraid and Plugins Ensure you are running the latest version of Unraid and its plugins, as updates often include bug fixes for such issues. 5. Reduce System Load If high traffic is causing the problem, consider optimizing your configuration or scaling resources. By following these steps, you can address the "force-reaping msg with refcount 1" error and improve system stability. Fix common problems finds nothing of concern. I've attached in-use system drivers' screenshot, Diags, dmesg. log, graphql-api log and system log. Checking the nginx.conf nchan shared memory value -> already set at 256M http { ## # Basic Settings ## # Hide nginx version information. server_tokens off; # Define the MIME types for files. include /etc/nginx/mime.types; default_type application/octet-stream; # Shared memory slab pre-allocated for Nchan. # default is 128M nchan_shared_memory_size 256M; # How long to allow each connection to stay idle; longer values are better # for each individual client, particularly for SSL, but means that worker # connections are tied up longer. (Default: 65) keepalive_timeout 20; Re: Disk 13 was new and as such console> du -h -d 1 /x shows 0 /x sagittarius-diagnostics-20250921-1458.zip sagittarius-syslog-20250921-0505.zip dmesg.txt graphql-api.log
  10. Ok, thanks Jorge. Disk 13 mounted /x and browsable but no data actualy there as it never completed rebuilding the disk in the array due to the usb uasp driver issue. Disk 6 mounted /x and was browsable with data as expected. I will now execute the new config as suggested. Cheers
  11. ~# sgdisk -o -a 8 -n 1:32K:0 /dev/sdj The operation has completed successfully. root@SAGITTARIUS:~# blkid /dev/sdj1 /dev/sdj1: UUID="5bc5fd60-401f-49a2-b8ec-bedab02890f6" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="37e727ec-a367-4c51-a072-9672fff29dbe"
  12. Now if I do /dev/sdg (the new assignment) instead of /dev/sdj (the original assignment) then ~# sgdisk -o -a 8 -n 1:1M:0 /dev/sdg *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. *************************************************************** Warning! Secondary partition table overlaps the last partition by 33 blocks! You will need to delete this partition or resize it in another utility. Non-GPT disk; not saving changes. Use -g to override. The GUID overlaps by 33 blocks. If i use -g override, I don't think it would change the fact it's no longer being recognised as a Seatay device and the wrong drive issue remains. I guess in that scenario would you agree that I then have to do an array reset with Tools>New Config and select "Preserve current assignments: All" ??
  13. Hi Jorge, I've applied the quirks koption but now can't start one of the usb drive enclosures (disk 6) with "wrong disk error" (screenshot attached). It's not being recognised as a Seatay device but the WD drive itself is the same and operational. I tried the workaround from your reply to a post using the correct /dev/sdj assignment as per my screenshot above without any effect on reboot: sgdisk -o -a 8 -n 1:1M:0 /dev/sdj In any case lsusb -vt output follows: ~# lsusb -vt /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 001: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M ID 046d:c52b Logitech, Inc. Unifying Receiver |__ Port 001: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M ID 046d:c52b Logitech, Inc. Unifying Receiver |__ Port 001: Dev 003, If 2, Class=Human Interface Device, Driver=usbhid, 12M ID 046d:c52b Logitech, Inc. Unifying Receiver |__ Port 002: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M ID 413c:2113 Dell Computer Corp. KB216 Wired Keyboard |__ Port 002: Dev 004, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M ID 413c:2113 Dell Computer Corp. KB216 Wired Keyboard /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0626 Genesys Logic, Inc. Hub /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 001: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub |__ Port 001: Dev 005, If 0, Class=Hub, Driver=hub/4p, 480M ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub |__ Port 004: Dev 008, If 0, Class=Hub, Driver=hub/4p, 480M ID 1a40:0801 Terminus Technology Inc. |__ Port 001: Dev 010, If 0, Class=Human Interface Device, Driver=usbhid, 12M ID 27c0:0859 Cadwell Laboratories, Inc. |__ Port 001: Dev 010, If 1, Class=Human Interface Device, Driver=usbhid, 12M ID 27c0:0859 Cadwell Laboratories, Inc. |__ Port 001: Dev 010, If 2, Class=Human Interface Device, Driver=usbhid, 12M ID 27c0:0859 Cadwell Laboratories, Inc. |__ Port 003: Dev 004, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 001: Dev 007, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 002: Dev 009, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 003: Dev 011, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 004: Dev 012, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 004: Dev 006, If 0, Class=Mass Storage, Driver=usb-storage, 480M ID 346d:5678 /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0626 Genesys Logic, Inc. Hub |__ Port 001: Dev 003, If 0, Class=Hub, Driver=hub/4p, 5000M ID 0bda:0411 Realtek Semiconductor Corp. Hub |__ Port 001: Dev 005, If 0, Class=Hub, Driver=hub/4p, 5000M ID 0bda:0411 Realtek Semiconductor Corp. Hub |__ Port 002: Dev 008, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 152d:2590 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge |__ Port 002: Dev 007, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge |__ Port 003: Dev 010, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge |__ Port 004: Dev 012, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge |__ Port 002: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge |__ Port 003: Dev 006, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub |__ Port 001: Dev 009, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub |__ Port 004: Dev 013, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 0bc2:2031 Seagate RSS LLC |__ Port 002: Dev 011, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub |__ Port 001: Dev 015, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 125f:a64a A-DATA Technology Co., Ltd. |__ Port 003: Dev 018, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 0bc2:2037 Seagate RSS LLC |__ Port 004: Dev 019, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 1058:2621 Western Digital Technologies, Inc. |__ Port 003: Dev 014, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub |__ Port 002: Dev 017, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 1058:2627 Western Digital Technologies, Inc. |__ Port 004: Dev 016, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub |__ Port 001: Dev 020, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 1058:2627 Western Digital Technologies, Inc. |__ Port 002: Dev 021, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 0bc2:2031 Seagate RSS LLC /: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 001: Dev 002, If 0, Class=Wireless, Driver=btusb, 480M ID 0e8d:c616 MediaTek Inc. |__ Port 001: Dev 002, If 1, Class=Wireless, Driver=btusb, 480M ID 0e8d:c616 MediaTek Inc. |__ Port 001: Dev 002, If 2, Class=Wireless, Driver=[none], 480M ID 0e8d:c616 MediaTek Inc. /: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/0p, 5000M ID 1d6b:0003 Linux Foundation 3.0 root hub
  14. Thanks Jorge, Posted the lsusb -vt below. FYI this USB connected setup was fully operational for 2 previous Intel NUC server machines with Unraid 6.x and 7.x, and Yottamaster 4-bay external enclosure which uses JMS567 bridge. In any case, I found another 2 posts with similar JMicron bridge issues. https://forums.unraid.net/topic/187956-usb-jbod-drive-mount-issues-after-upgrade-to-70701/ https://forums.unraid.net/topic/170412-unraid-61210-how-to-permanently-add-a-usb-storage-quirk-to-disable-uas/ The newest hardware change was the Minisforum MS-A2 machine in late July 2025 without issues until very recently; perhaps the USB driver was also updated recently? Cheers ~# lsusb -vt /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 001: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M ID 046d:c52b Logitech, Inc. Unifying Receiver |__ Port 001: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M ID 046d:c52b Logitech, Inc. Unifying Receiver |__ Port 001: Dev 003, If 2, Class=Human Interface Device, Driver=usbhid, 12M ID 046d:c52b Logitech, Inc. Unifying Receiver |__ Port 002: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M ID 413c:2113 Dell Computer Corp. KB216 Wired Keyboard |__ Port 002: Dev 004, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M ID 413c:2113 Dell Computer Corp. KB216 Wired Keyboard /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0626 Genesys Logic, Inc. Hub /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 001: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub |__ Port 001: Dev 005, If 0, Class=Hub, Driver=hub/4p, 480M ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub |__ Port 004: Dev 008, If 0, Class=Hub, Driver=hub/4p, 480M ID 1a40:0801 Terminus Technology Inc. |__ Port 001: Dev 010, If 0, Class=Human Interface Device, Driver=usbhid, 12M ID 27c0:0859 Cadwell Laboratories, Inc. |__ Port 001: Dev 010, If 1, Class=Human Interface Device, Driver=usbhid, 12M ID 27c0:0859 Cadwell Laboratories, Inc. |__ Port 001: Dev 010, If 2, Class=Human Interface Device, Driver=usbhid, 12M ID 27c0:0859 Cadwell Laboratories, Inc. |__ Port 003: Dev 004, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 001: Dev 007, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 002: Dev 009, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 003: Dev 011, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 004: Dev 012, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 004: Dev 006, If 0, Class=Mass Storage, Driver=usb-storage, 480M ID 346d:5678 /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0626 Genesys Logic, Inc. Hub |__ Port 001: Dev 003, If 0, Class=Hub, Driver=hub/4p, 5000M ID 0bda:0411 Realtek Semiconductor Corp. Hub |__ Port 001: Dev 005, If 0, Class=Hub, Driver=hub/4p, 5000M ID 0bda:0411 Realtek Semiconductor Corp. Hub |__ Port 002: Dev 007, If 0, Class=Mass Storage, Driver=uas, 5000M ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge |__ Port 003: Dev 009, If 0, Class=Mass Storage, Driver=uas, 5000M ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge |__ Port 004: Dev 011, If 0, Class=Mass Storage, Driver=uas, 5000M ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge |__ Port 002: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge |__ Port 003: Dev 006, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub |__ Port 001: Dev 008, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub |__ Port 004: Dev 012, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 0bc2:2031 Seagate RSS LLC |__ Port 002: Dev 010, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub |__ Port 001: Dev 014, If 0, Class=Mass Storage, Driver=uas, 5000M ID 125f:a64a A-DATA Technology Co., Ltd. |__ Port 003: Dev 016, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 0bc2:2037 Seagate RSS LLC |__ Port 004: Dev 018, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 1058:2621 Western Digital Technologies, Inc. |__ Port 003: Dev 013, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub |__ Port 001: Dev 017, If 0, Class=Mass Storage, Driver=uas, 5000M ID 152d:2590 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge |__ Port 002: Dev 019, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 1058:2627 Western Digital Technologies, Inc. |__ Port 004: Dev 015, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub |__ Port 001: Dev 020, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 1058:2627 Western Digital Technologies, Inc. |__ Port 002: Dev 021, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 0bc2:2031 Seagate RSS LLC /: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 001: Dev 002, If 0, Class=Wireless, Driver=btusb, 480M ID 0e8d:c616 MediaTek Inc. |__ Port 001: Dev 002, If 1, Class=Wireless, Driver=btusb, 480M ID 0e8d:c616 MediaTek Inc. |__ Port 001: Dev 002, If 2, Class=Wireless, Driver=[none], 480M ID 0e8d:c616 MediaTek Inc. /: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/0p, 5000M ID 1d6b:0003 Linux Foundation 3.0 root hub
  15. Hi folks, I've changed USB Flash drives > shutdown and rebooted several times now, and always with the same outcome. Flash drive boots on front USB2.0 port The system hardware is a Mini Forum MS-A2 AMD 9955hx CPU 128Gb 13Tb Array. Parity drives x 2, Array drives x 13 all connected by USB3.0 hub, tried different hubs withy same outcome. USB hubs are connected to 4 x USB3.0 ports. Memtest on reboot finds no errors. The server has been online and offline for more than a week. The server was operating fine until after 7.1.3 -> 7.1.4 update. What's the best method to downgrade versions? sagittarius-diagnostics-20250918-1811.zip
  16. Hi Richard. Just follow the steps 1 to 4 as per pics below, then step 5 - navigate back to MAIN stop the array and reboot. The network configuration file will be auto recreated. I've found the issue often arises when multiple network interfaces are configured. HTH .. Dolf 1. Select the square with diagonal arrow on the far left of the Flash drive 2. Then click on the folder called config 3. Next, select the network.cfg file 4. Finally, rename the file or delete it 5. Stop the array and reboot.
  17. Hi Sanders. I've gone through the topics discussed here and haven't resolved this Network Manager database connection issue with the official MySQL docker image as per the attached screenshot. There's a 32 digit alphanumeric application key and MySQL root password configured. The MySQL database on launching the docker is network_manager. I would very much appreciate any suggestions to identify and resolve this connection issue.
  18. "Folks, my Unraid Version 6.12.8 2024-02-15 server refuses to connect to Unraid Connect Cloud (Socket Closed), and of course no plugin or docker updates are available if this is error is caused by a plugin." SOLVED easily enough by renaming network.cfg in boot flash config folder and rebooting. It would however be good to know which process related to the connect cloud API causes this network configuration issue. Thanks, .. Dolf
  19. Yes, indeed I've been following older documentation on a recommended NAS solution. Thank you folks for your kind assistance. It saved me troubleshooting time and will now reconfigure the array for best practice. Cheers
  20. Hi folks, I'm primarily a Windows user (DOS/3.1x-NT/11) and over the years in IT support I've dabbled in a large number of *nix distros and MacOS so I guess I know enough to get me into trouble. I've just installed an unraid server with a trial license. The install and config was easy enough and love the functionality. However in trying to install unmenu to extend the WebGUI I've come across an issue when running its bash install script. At CLI i can create the /boot/unmenu dir and wget the zip, and unzip so the boot USB is mounted as rw as expected. Then I need to execute the script file unmenu_install so tried to chmod +x and also tried chmod 755 on the rw file but this op fails without error since ls -l unmenu_install shows no change to permissions (same rw as before but no new x permission). Of course if one then cd to /boot/unmenu folder and tried to execute with ./unmenu_install we get the bash: ./unmenu_install: Permission denied error. I've also tried creationg new files and chmodding to +x but the same issue arises. I followed precisely the documented instructions and cannot identify the "root" cause of the problem. It's obviously a permission issue but since I'm logged in as root I should'nt it have the right to chmod anything? I know the OS is Slackware 14.2+ but cannot find any peculiar permission differences from searching various distro support fora. Unraid is version 6.92 with a Trial registration cert. If changed USB drives and installed Unraid on them using the supplied installer, each one works fine but permission issue peresists so it's not hardware. I must be missing something. I've attached the diagnostics for my server install which apart from the above sated issue is working flawlessly as intended. sagittarius-diagnostics-20220411-2019.zip

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.