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.

Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

Featured Replies

Thanks for the report. I can reproduce this: on 7.3.3 and 7.4.0-rc.1, Unassigned Devices shows only a Format button for an NVMe device that already has a partition. On 7.3.2 the same device mounts normally.

This is a compatibility issue between Unassigned Devices and a udev change in 7.3.3. Your data is fine, but don't click Format. Until it's fixed, you can stay on or go back to 7.3.2.

Non-NVMe devices are not affected; I've reported it to LT and hopefully it will be fixed soon.

  • Replies 11.9k
  • Views 2.2m
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • It's that self healing feature I built into UD.  It just fixes itself.

  • New release of UD.  Changes: When changing the mount point (which is also the share name), the mount point is checked for a duplicate of a user share or another UD device.  Samba cannot handle

  • Major new release of UD: "Where are the switches?"  The "Pass Through", "Read Only", "Automount", and "Share" switches have been moved to a new Edit Settings dialog.  This is also where the sc

Posted Images

1 hour ago, JorgeB said:

Thanks for the report. I can reproduce this: on 7.3.3 and 7.4.0-rc.1, Unassigned Devices shows only a Format button for an NVMe device that already has a partition. On 7.3.2 the same device mounts normally.

This is a compatibility issue between Unassigned Devices and a udev change in 7.3.3. Your data is fine, but don't click Format. Until it's fixed, you can stay on or go back to 7.3.2.

Non-NVMe devices are not affected; I've reported it to LT and hopefully it will be fixed soon.

I've been debugging this too. Seems like it's a multiple alias problem:

The Unassigned Devices plugin has a weakness in its discovery logic:

  1. It chooses one alias for the disk.

  2. It independently chooses an alias for the partition.

  3. It assumes their names match.

When they don't, the plugin incorrectly concludes that the disk has no partitions.

Patched like this:

cp /usr/local/emhttp/plugins/unassigned.devices/include/lib.php /tmp/ud-lib.php.before-alias-fix

sed -i '3595c\ $partitions = array_values(array_filter($devicePaths, function($alias, $real) use ($path) { return (bool) preg_match("#^".preg_quote($path, "#")."p?[0-9]+$#", $real); }, ARRAY_FILTER_USE_BOTH));' /usr/local/emhttp/plugins/unassigned.devices/include/lib.php

php -l /usr/local/emhttp/plugins/unassigned.devices/include/lib.php

And persisted the patch across reboots with this script

mkdir -p /boot/config/custom

cat > /boot/config/custom/ud-nvme-hotfix.sh <<'EOF'

#!/bin/bash

set -euo pipefail

lib=/usr/local/emhttp/plugins/unassigned.devices/include/lib.php

backup=/tmp/ud-lib-before-hotfix.php

# Wait for Unassigned Devices to be installed.

for i in {1..60}; do

[[ -f "$lib" ]] && break

sleep 1

done

[[ -f "$lib" ]] || exit 1

cp "$lib" "$backup"

# Fix NVMe parent device identification.

sed -i 's/MiscUD::base_device($matches\[1\]\[0\])/MiscUD::base_device($partition["device"])/' "$lib"

# Match partitions by real device path, not aliases.

sed -i '/\$partitions = array_values(preg_grep(/c\ $partitions = array_values(array_filter($devicePaths, function($alias, $real) use ($path) { return (bool) preg_match("#^".preg_quote($path, "#")."p?[0-9]+$#", $real); }, ARRAY_FILTER_USE_BOTH));' "$lib"

# Verify both fixes and PHP syntax; roll back on failure.

if ! grep -Fq 'MiscUD::base_device($partition["device"])' "$lib" ||

! grep -Fq 'array_values(array_filter($devicePaths' "$lib" ||

! php -l "$lib" >/dev/null; then

cp "$backup" "$lib"

logger -t ud-nvme-hotfix "Hotfix failed or plugin changed"

exit 1

fi

logger -t ud-nvme-hotfix "NVMe hotfix applied/verified"

EOF

chmod 755 /boot/config/custom/ud-nvme-hotfix.sh

and updated go file

cp -p /boot/config/go /boot/config/go.pre-ud-hotfix

grep -Fxq '/boot/config/custom/ud-nvme-hotfix.sh' /boot/config/go || \

sed -i '/^\/usr\/local\/sbin\/emhttp$/i /boot/config/custom/ud-nvme-hotfix.sh' /boot/config/go

grep -B2 -A2 '/usr/local/sbin/emhttp' /boot/config/go

Edited by martindell

I also have a problem after upgrading from 7.3.2 to 7.3.3 - I have three backup disks which run a device script when connected.

Now after upgrading, my disks are not recognized but listed under a different serial number, see attached screenshot.

How can I fix that?


Screenshot 2026-10-12 115720.png

Click settings, assign the same script, set to automount.

52 minutes ago, Kilrah said:

Click settings, assign the same script, set to automount.

Thanks, but I'd consider that a workaround rather than a fix. But Dan "dlandon" is already looking into it, so I guess there will be a fix soon.

1 hour ago, motophil said:

Thanks, but I'd consider that a workaround rather than a fix. But Dan "dlandon" is already looking into it, so I guess there will be a fix soon.

It seems something e.g kernel is now able to extract the real identifiers from usb drives instead of the enclosure identification, which is actually great and worth having to do manual changes.

dlandon is also not involved with the standard UD plugins this thread refers to anymore.

Edited by Kilrah

Hi, I have a minor annoyance. I'm using a NVME drive via USB as a torrentbox. Configured and correctly "unassigned". Yet, I cannot see its utilization on the dashboard: image.png
Disc is formatted XFS. Is there a way to show its actual utilization percentage? And, since I'm here, maybe change the "Dev 1" name as well?

Here's the same drive on the Main page:
image.png

Thanks in advance!

EDIT: so, diandon himself wrote to me and suggested me to use the Unassigned Devices - Next version. After uninstalling my old UD version (once I stopped Docker, unmounted all shares and disks to be extra safe, then uninstalled the old plugin), I installed the Next version. All the settings and my previously mounted disks were there, ready to be mounted once again. It all works extremely well, as always, but with the benefit of a wonderful, new dashboard tile! Thanks again diandon!

image.png

Edited by fra-pipboy

  • 2 weeks later...

Hello, how can I fix an SSD that is now showing "(RO)". It may have been an unclean shutdown that triggered it. I'm not sure how to resolve it so that I can write to it again. Any help is greatly appreciated.

Thanks

Screenshot 2026-10-24 at 1.58.38 PM.png

Screenshot 2026-10-24 at 1.30.45 PM.png

Screenshot 2026-10-24 at 1.30.17 PM.png

tower-diagnostics-20261024-1401.zip

14 hours ago, TekDRu said:

Hello, how can I fix an SSD that is now showing "(RO)". It may have been an unclean shutdown that triggered it. I'm not sure how to resolve it so that I can write to it again. Any help is greatly appreciated.

Pretty sure UD supports read-only for HFS+.

On 10/25/2026 at 5:32 AM, JorgeB said:

Pretty sure UD supports read-only for HFS+.

I have used this drive as a share and saved files to it already. It was working fine as read and write. I'm not sure when the change took place.

9 hours ago, TekDRu said:

I have used this drive as a share and saved files to it already. It was working fine as read and write. I'm not sure when the change took place.

Recommend using a different filesystem; if you need Linux, Mac and Windows compatibility, you can use extFAT

On 10/24/2026 at 8:32 PM, TekDRu said:

Hello, how can I fix an SSD that is now showing "(RO)". It may have been an unclean shutdown that triggered it. I'm not sure how to resolve it so that I can write to it again. Any help is greatly appreciated.

Probably similar to NTFS, linux can read and write but if e.g. it's disconnected unexpectedly without properly unmounting the "dirty, needs filesystem check" flag gets set and that check needs to be done on an actual Windows machine. So try connecting the drive to your mac and do a filesystem check/repair there.

Thanks @JorgeB and @Kilrah. Since this format can experience these issue, I'll change to a safer filesystem.

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.