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.

Unraid 7.1.4 USB Flash drives changed because corrupted or offline message, simultaneously several array drives show read errors

Featured Replies

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?

DriveReadErrors.jpg

Flashdrivecorruptionagain.jpg

sagittarius-diagnostics-20250918-1811.zip

Solved by handycapp

  • Community Expert

USB problems: Please note that USB is not recommended for array or pool devices:

Sep 18 14:01:11 SAGITTARIUS kernel: scsi host2: uas_eh_device_reset_handler start

Sep 18 14:01:12 SAGITTARIUS kernel: usb 4-2.1.2: reset SuperSpeed USB device number 7 using xhci_hcd

Sep 18 14:01:12 SAGITTARIUS kernel: usb 4-2.1.2: device firmware changed

Sep 18 14:01:12 SAGITTARIUS kernel: scsi host2: uas_eh_device_reset_handler FAILED err -19

You can try disabling UASP to see if it's more stable; post the output from lsusb -vt

  • Author

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

  • Community Expert

Click on the flash drive, scroll down to the Syslinux configuration section, make sure Menu View is enabled, top-right, and add after /bzroot to the default boot option, the one in green:

usb_storage.quirks=174c:55aa:u,125f:a64a:u,152d:2590:u

It should be added to the same line as /bzroot, just leave a space between that and the kernel option, then reboot and post a new lsusb -vt output to confirm it's no longer using UASP.

  • Author

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

  • Author

This is the screenshot of above wrong disk post

Screenshot 2025-09-19 183020.png

  • Author

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" ??

  • Community Expert
17 minutes ago, handycapp said:

sgdisk -o -a 8 -n 1:1M:0 /dev/sdj

Please NEVER try random commands you see in other posts; this does not apply to you.

Let me read the rest of the post now.

  • Community Expert

That device will use an MBR partition; you just created a GPT partition on top. The only solution now is probably going to be to rebuild it, assuming parity was valid, but before anything else, post new diags to see the current state.

  • Community Expert

Those appear to be the same diags as before.

  • Community Expert

So, if I understand correctly, you ran the partitioning command on /dev/sdg but aborted before doing any changes, so that should still have the original MBR partition, but you also ran the command on /dev/sdj (which is currently disk13)?

If this is correct, post the output from

blkid /dev/sdj1

  • Author

/dev/sdj1: PARTUUID="8f3eb9c1-3c4c-4b5a-a783-078375cb002c"

  • Community Expert

Assuming you didn't reboot yet and disk13 is still /dev/sdj, type:

sgdisk -o -a 8 -n 1:32K:0 /dev/sdj

Then again, the output from

blkid /dev/sdj1

  • Author

~# 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"

  • Community Expert

OK, disk13 should now be back to the correct partition layout, and the XFS signature is now there.

Parity2 and disk13 got disabled due to USB issues, the disks themselves look OK, so the next step is to confirm if disk13 mounts and contents look correct, type:

mkdir /x

mount -o ro /dev/sdj1 /x

Then browse /x, you can use Midnight Commander, for example, (mc on the console) and see if the contents look OK, if they do, unmount the disk and do the same for disk6

umount /x

mount -o ro /dev/sdg1 /x

Now browse disk6, and if the contents look good for both, unmount disk6 with umount /xand the easiest way to resolve this, would be to do a new config (Tools - New config - Keep all - apply) to accept the new disk6 name and re-enable disk13. You can check "parity is already valid" before array start, but then you should run a correcting parity check.

Any issues or doubts, please ask before proceeding.

  • Author
  • Solution

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

  • Community Expert
1 hour ago, handycapp said:

Disk 13 mounted /x and browsable but no data actualy there as it never completed rebuilding

It should still have the old data, assuming you were rebuilding on top, or was this a new disk?

With that disk mounted at /x post the output from

du -h -d 1 /x

  • Author

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

  1. Shared Memory Exhaustion: Insufficient memory allocated for Nchan or other shared memory operations.

  2. Improper Resource Cleanup: Messages or channels not being properly released, leading to lingering references.

  3. 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

Screenshot 2025-09-21 144542.png

FireShot Capture 031 - SAGITTARIUS_SysDrivers - [sagittarius.local].png

FireShot Capture 032 - SAGITTARIUS_Main lower half suggests parity rebuilding- [sagittarius.local].png

FireShot Capture 033 - SAGITTARIUS_Dashboard - [sagittarius.local].png

sagittarius-diagnostics-20250921-1458.zip sagittarius-syslog-20250921-0505.zip dmesg.txt graphql-api.log

Edited by handycapp

  • Community Expert

Rebooting should bring the display back, but if it keeps happening, I recommend upgrading to 7.2.0-beta.3, there are some changes that should help with those issues.

  • Author

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

  • Author

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.

FireShot Capture 034 - SAGITTARIUS_Main - [sagittarius.local].png

FireShot Capture 035 - SAGITTARIUS_Main - [sagittarius.local].png

sagittarius-diagnostics-20250922-1403.zip sagittarius-diagnostics-20250922-1454.zip

  • Community Expert

Sep 22 01:48:51 SAGITTARIUS kernel: xhci_hcd 0000:01:00.4: xHCI host not responding to stop endpoint command

Sep 22 01:48:51 SAGITTARIUS kernel: xhci_hcd 0000:01:00.4: xHCI host controller not responding, assume dead

Sep 22 01:48:51 SAGITTARIUS kernel: xhci_hcd 0000:01:00.4: HC died; cleaning up

Sep 22 01:48:51 SAGITTARIUS kernel: usb 3-2: USB disconnect, device number 2

Sep 22 01:48:51 SAGITTARIUS kernel: usb 3-2.1: USB disconnect, device number 3

Sep 22 01:48:51 SAGITTARIUS kernel: usb 3-2.1.1: USB disconnect, device number 5

Sep 22 01:48:51 SAGITTARIUS kernel: usb 3-2.1.1.4: USB disconnect, device number 8

Sep 22 01:48:51 SAGITTARIUS kernel: usb 3-2.1.1.4.1: USB disconnect, device number 10

Sep 22 01:48:51 SAGITTARIUS kernel: usb 4-2.3.4.1: USB disconnect, device number 20

Sep 22 01:48:51 SAGITTARIUS kernel: usb 4-2.3.3.2: USB disconnect, device number 17

Sep 22 01:48:51 SAGITTARIUS kernel: usb 4-2.3.1.4: USB disconnect, device number 13

Sep 22 01:48:51 SAGITTARIUS kernel: usb 4-2.3.2.1: USB disconnect, device number 15

Sep 22 01:48:51 SAGITTARIUS kernel: usb 4-2.1: USB disconnect, device number 3

Sep 22 01:48:51 SAGITTARIUS kernel: usb 4-2.1.1: USB disconnect, device number 5

Sep 22 01:48:51 SAGITTARIUS kernel: usb 4-2.1.1.2: USB disconnect, device number 8

Sep 22 01:48:51 SAGITTARIUS kernel: usb 4-2: USB disconnect, device number 2

Problem with the USB controller, so all connected USB devices were dropped.

You can try to upgrade (or downgrade) Unraid to see if that controller work better with a different kernel, but using USB for array and pool devices is really a bad idea, they tend to drop a lot, and USB is bad at error handling in general.

  • Author

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.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

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.