March 1, 20251 yr Okay so I have actually read another post or 2 saying that this is a know bug in Unraid 7 due to a storage driver change. I have actually already tried the fix that was posted for this that is supposed to keep the hardware IDs from changing: Edit my boot line to this: kernel /bzimage append initrd=/bzroot usb_storage.quirks=2109:0715:u USB IDs: Bus 001 Device 001 Port 1-0ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001 Port 2-0ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002 Port 2-1ID 2109:0822 VIA Labs, Inc. USB3.1 Hub Bus 002 Device 003 Port 2-1.2ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor Bus 002 Device 004 Port 2-1.3ID 2109:0822 VIA Labs, Inc. USB3.1 Hub Bus 002 Device 005 Port 2-1.3.1ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor Bus 002 Device 006 Port 2-1.3.3ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor Bus 003 Device 001 Port 3-0ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002 Port 3-2ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS Bus 003 Device 003 Port 3-3ID 10c4:8a2a Silicon Labs HubZ Smart Home Controller Bus 003 Device 004 Port 3-4ID 2109:2822 VIA Labs, Inc. USB2.0 Hub Bus 003 Device 005 Port 3-10ID 8087:0032 Intel Corp. AX210 Bluetooth Bus 003 Device 006 Port 3-4.3ID 2109:2822 VIA Labs, Inc. USB2.0 Hub Bus 004 Device 001 Port 4-0ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 002 Port 4-1ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive JBOD: Bus 002 Device 005 Port 2-1.3.1ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor Hardware: MINISFORUM MS-01 Yottamaster 5 Bay RAID Hard Drive Enclosure in JBOD mode
March 1, 20251 yr Author Also just noticed my Shares keep disappearing since the 7.0 update. They come back after a reboot. If I need to reboot and attach a new diagnotics let me know. I am also having an issue with one of my NVME drives dropping off after a reboot and only way to bring it back is a complete power off of the server and manual power on lsusb -vt /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/3p, 20000M/x2 ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 10000M ID 2109:0822 VIA Labs, Inc. |__ Port 002: Dev 003, If 0, Class=Mass Storage, Driver=usb-storage, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor |__ Port 003: Dev 004, If 0, Class=Hub, Driver=hub/4p, 10000M ID 2109:0822 VIA Labs, Inc. |__ Port 001: Dev 005, If 0, Class=Mass Storage, Driver=usb-storage, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor |__ Port 003: Dev 006, If 0, Class=Mass Storage, Driver=usb-storage, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=[none], 12M ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS |__ Port 003: Dev 003, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M ID 10c4:8a2a Silicon Labs |__ Port 003: Dev 003, If 1, Class=Vendor Specific Class, Driver=cp210x, 12M ID 10c4:8a2a Silicon Labs |__ Port 004: Dev 004, If 0, Class=Hub, Driver=hub/4p, 480M ID 2109:2822 VIA Labs, Inc. |__ Port 003: Dev 006, If 0, Class=Hub, Driver=hub/4p, 480M ID 2109:2822 VIA Labs, Inc. |__ Port 010: Dev 005, If 0, Class=Wireless, Driver=btusb, 12M ID 8087:0032 Intel Corp. AX210 Bluetooth |__ Port 010: Dev 005, If 1, Class=Wireless, Driver=btusb, 12M ID 8087:0032 Intel Corp. AX210 Bluetooth /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive syslog-previous tower-diagnostics-20250301-1107.zip Edited March 1, 20251 yr by ech0chamber
March 2, 20251 yr Community Expert All disks were detected correctly on this boot, if it happens again post new diags There appears to be a container constantly restarting, see if you can find which by looking at their uptimes. Regarding the other issues, post dags after it happens.
March 3, 20251 yr Author On 3/2/2025 at 4:26 AM, JorgeB said: All disks were detected correctly on this boot, if it happens again post new diags There appears to be a container constantly restarting, see if you can find which by looking at their uptimes. Regarding the other issues, post dags after it happens. Thanks I'll pull fresh logs here in little bit. Rebooting the server a couple times so I can get the issues to appear. It's pretty consistent
March 4, 20251 yr Author Haven't gotten the drive IDs to change yet which is weird cause it usually does it every 2-3 reboots. But here is diagnostics after the shares disappeared tower-diagnostics-20250304-1102.zip
March 5, 20251 yr Community Expert Syslog is full of spam like this: client: 192.168.1.230, server: tower.tail57dd0.ts.net, request: "GET /login HTTP/2.0", host: "192.168.1.2", referrer: "https://192.168.1.2/Settings/AB.Main" Do you know which computer is 192.168.1.230? Still not seeing anything about shares, do you know the approximate time they stopped working?
March 5, 20251 yr Author 13 hours ago, JorgeB said: Syslog is full of spam like this: client: 192.168.1.230, server: tower.tail57dd0.ts.net, request: "GET /login HTTP/2.0", host: "192.168.1.2", referrer: "https://192.168.1.2/Settings/AB.Main" Do you know which computer is 192.168.1.230? Still not seeing anything about shares, do you know the approximate time they stopped working? The .230 is my Desktop PC I don't sorry. Here's another log with the shares dropping again. I just rebooted the server again. They seem to drop every 12 hours or so. It's 5p EST here I'll check again in the morning and if it's dropped off that'll give us a general idea tower-diagnostics-20250305-1621.zip Edited March 5, 20251 yr by ech0chamber
March 6, 20251 yr Community Expert There's still a lot of spam in the logs, errors related to the UPS and there appears to be a container constantly restating, see if you can find which by looking at their uptimes.
March 6, 20251 yr Author Okay here's another log where shares dropped off middle of the night. I'll look for the container and I may disconnect the UPS tonight so I can give you cleaner logs tomorrow tower-diagnostics-20250306-0855.zip
March 6, 20251 yr Community Expert I would recommend fixing the container issues, since a constantly restarting container can cause stability issues.
March 7, 20251 yr Author On 3/6/2025 at 10:57 AM, JorgeB said: I would recommend fixing the container issues, since a constantly restarting container can cause stability issues. Just fixed the container issue. It was Mellisearch that was continuously crashing. Will keep an eye on the system and see if I have any issues. For some reason my Disk IDs have not changed since I created this post despite editing my boot grub line days before making this post. But I'll take the win
March 8, 20251 yr Community Expert Log is still being spammed with UPS related errors, but I think I see the issue now, or at least, an issue, the second-cache NVMe device is dropping offline: Mar 8 00:05:19 Tower kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Mar 8 00:05:19 Tower kernel: nvme nvme0: Disabling device after reset failure: -19 Mar 8 00:05:19 Tower kernel: XFS (nvme0n1p1): metadata I/O error in "xfs_btree_read_buf_block.constprop.0+0x83/0xd0" at daddr 0x13bbe3a60 len 8 error 5 Mar 8 00:05:19 Tower kernel: XFS (nvme0n1p1): Block device removal (0x20) detected at fs_bdev_mark_dead+0x4b/0x5f (fs/xfs/xfs_super.c:1177). Shutting down filesystem. Mar 8 00:05:19 Tower kernel: XFS (nvme0n1p1): Please unmount the filesystem and rectify the problem(s) Try this, on the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off Reboot and see if it makes a difference.
March 10, 20251 yr Author On 3/8/2025 at 10:27 AM, JorgeB said: Log is still being spammed with UPS related errors, but I think I see the issue now, or at least, an issue, the second-cache NVMe device is dropping offline: Mar 8 00:05:19 Tower kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Mar 8 00:05:19 Tower kernel: nvme nvme0: Disabling device after reset failure: -19 Mar 8 00:05:19 Tower kernel: XFS (nvme0n1p1): metadata I/O error in "xfs_btree_read_buf_block.constprop.0+0x83/0xd0" at daddr 0x13bbe3a60 len 8 error 5 Mar 8 00:05:19 Tower kernel: XFS (nvme0n1p1): Block device removal (0x20) detected at fs_bdev_mark_dead+0x4b/0x5f (fs/xfs/xfs_super.c:1177). Shutting down filesystem. Mar 8 00:05:19 Tower kernel: XFS (nvme0n1p1): Please unmount the filesystem and rectify the problem(s) Try this, on the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off Reboot and see if it makes a difference. Funny you mention this. This just occurred to me the drive was dropping offline as I have noticed for a couple months now whenever I reboot the server, the drive would not mount and only fix is to completely poweroff the server and power back on. Frustrating as this is a brand new drive I bought in November but I think the drive is known to have Firmware issues. It is a HP FX900 Pro 4TB and only reason I bought it is cause I got it for $215. I'll try this fix and see if it fixes it but if not I am replacing the drive. Already have a Samsung Evo Plus 4TB ordered for $249 and should arrive tomorrow. My Temp fix atm the moment is a user script I wrote that tries to write a text file to one of my shares and remove it every 15 minutes and it fails, reboot the server. Edited March 10, 20251 yr by ech0chamber
March 24, 20251 yr Author Okay so swapping the drive to a 990 Pro solved my issues with the system crashing and shares disappearing. Still haven't fixed the drive ID issue but since my uptime has skyrocketed and the issue resolves itself after a reboot I can live with that for now.
December 25, 2025Dec 25 Hello @JorgeB,Would it be fine if I also ask for your help? I'm fairly new to the forums and consider myself to only have surface knowledge in Unraid so please bear with me. In a way I'm kinda running in the same situation with OP and I've been trying to fix this situation for almost 2 days now. For context, I have my setup with an HP Elite mini 600 and a 2-bay enclosure with a total of 3 drives and 2 NVMes. A couple of weeks ago, the enclosure crashed/gave up causing one of the drives connected to the 2-bay to become emulated. I found that it was the main reason cause connecting any one of the two would cause the drives to run, but connecting them both would not even let the server recognize any. So I had to buy a new enclosure which is Yottamaster DF4RU3, I can't remember the exact model but it has the no-raid configuration. In addition to that, I also bought a new drive to be my parity cause, although the current drives I had are really old(more than 4years now), I'm quite sure they are still fine, well, at least until before the 2-bay gave up.Now I was able to make it work for at least a day by adding the usb_storage.quirks= flag to the syslinux with the correct device, but I still had my doubts since the name of the disks are still External_USB3.0_0000007788FC-0:1 and such. I ignored it at first since I tried rebooting the server and the disks did not change locations so I thought it was fine. After a day or less, all of the disks would continuously report SMART errors uncorrect 40, I know its a failing disk error, but it fixes itself after just a few seconds and even the new drive would also report the same thing so I thought it was just the JBOD acting up.Last night, I had to install a Home Assistant VM and I tried to pass the sound device to the VM via iommu, rebooted the server and then the problem started. The whole JBOD would now disconnect a few seconds after starting the server, it would report that only one of the drives(one of the old drives) is disabled and emulated, but the whole JBOD is disconnected as I see from the system device. Stopping the array, and turning the JBOD on and off would fix the situation with the reported drive disabled. I'd have to create a new configuration, see that the drives are fine with their contents right, and then situation would loop all over again if I start the array.I'm just frustrated now since I don't know if its the old drives or the JBOD that's the issue so I'm kinda desperate now. The logs and diagnostics are attached below. Thank you! sefserver-syslog-20251225-2045.zip sefserver-diagnostics-20251226-0500.zip
December 26, 2025Dec 26 Community Expert 10 hours ago, Sef Sagun said:Stopping the array, and turning the JBOD on and off would fix the situation with the reported drive disabled.Not sure I follow. Were the drives wrong/missing or disabled? When a drive is really disabled, reconnecting it won't 'change anything; it needs to be rebuilt. Post a screenshot of the main showing what you mean.
December 26, 2025Dec 26 2 minutes ago, JorgeB said:Not sure I follow. Were the drives wrong/missing or disabled? When a drive is really disabled, reconnecting it won't 'change anything; it needs to be rebuilt. Post a screenshot of the main showing what you mean.It looks like thisFirst, it will report that disk 1 is disabled, but in reality the whole JBOD would be disconnected, resulting in all of the devices to be missing. So when I turn the JBOD on and off, the disks will be back like what the screenshot shows with the disabled device recognizable.EDIT: To add context, I look at System Devices to confirm that the whole JBOD is disconnected. So do you reckon I have to rebuild the disk by unassigning and reassigning it back? I'm quite terrified to do that actually cause it might ruin the disk/s if it again disconnects the JBOD if I start the array. Edited December 26, 2025Dec 26 by Sef Sagun
December 26, 2025Dec 26 Community Expert Disk1 is really disabled, that will not happen just because the drives were missing at boot. There must have a been a write error in the past. The first step is to rebuild disk1Start the array with disk1 unassigned and post new diags to see if the emulated disk is mounting.
December 26, 2025Dec 26 1 minute ago, JorgeB said:Start the array with disk1 unassigned and post new diags to see if the emulated disk is mounting.This is what it looks like after unassigning the device and starting the array. Also attached are the new diags. I've stopped the array since and tried reassigning the drive but it wont mount, so let me know what should I do next. sefserver-diagnostics-20251226-1640.zip Edited December 26, 2025Dec 26 by Sef Sagun
December 26, 2025Dec 26 Community Expert You have a really dangerous external USB compartment there!It automatically generates "disk names", UNRAID needs them to find back the drives after a reboot.But your box seems to throw a dice every power on (actually I would more think it just renumbers them in the sequence they spin up), this is a sure source for desaster sooner or later (and repeatingly).Get rid of that thing and get something real!
December 26, 2025Dec 26 Okay, so I think I've found out why the unassigned device is not mounting. As you can see in the screenshot I sent above, it clearly says its one of the 4tb disks. But when I check the identity of the device, its the 2tb disk. So this goes back to the issue of the disk ids changing. The JBOD also disconnected, I think, since the mount location changed from sde, sdb, sdd to sdf, sdg, sdh.I do have the usb_storage.quirks= set in the syslinux as seen below, but yeah. I dunno why it keeps disconnecting or what.
December 26, 2025Dec 26 9 minutes ago, MAM59 said:You have a really dangerous external USB compartment there!It automatically generates "disk names", UNRAID needs them to find back the drives after a reboot.But your box seems to throw a dice every power on (actually I would more think it just renumbers them in the sequence they spin up), this is a sure source for desaster sooner or later (and repeatingly).Get rid of that thing and get something real!I would if I could, but unfortunately I can't afford to buy something real since, I just bought this brand new and I don't have the budget to buy a good one.Hence I posted on this topic specifically cause I've seen not just from Unraid forums that usb_storage.quirks should allow checking the device IDs instead of disk names.
December 26, 2025Dec 26 Community Expert The quirks are correctly applied; and none of the USB devices is using the UAS driver, so the issue is not that. It's just a USB enclosure that won't work correctly with Unraid, if you really need USB, I'm afraid you will need to try using a different enclosure.
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.