Here yo go, doh!

Thanks

unraid-spare-diagnostics-20260510-0020.zip

***Update***

The version provided by the dev seemed to address my issue, here:

dlandon/unassigned.devices-next: Continued private development of the Unraid Unassigned Devices plugins by dlandon.

Also, same issue on both unRAID instances, Prod and Spare.

Nothing I have tried addresses the issue. Lastly, I have no unRAID array, just ZFS pools.

Thanks

Edited May 10May 10 by Govnah

i not sure if remote samba connections are an unassigned devices plugin or part of unraid OS side

i did request on the unraid features... but if its part of the unassigned devices

its for Auto Retry Mounting Remote Share

if the server that you remote connect to is down at the time it wont mount.. but a feature to a user specific time like 30 seconds 1 min 5 min etc to then retry again to remount /remote location be good so it reconnect… as sometimes if you reboot servers the one server will boot up before the main server or what not and cant connect.. so there should be an auto reconnect retry to keep trying

Edited May 15May 15 by comet424

Now with 7.3 and internal boot could we please get an option to permanently hide a licensing-only USB drive? Kinda annoying to always have it show in UD.

7 minutes ago, Kilrah said:

Now with 7.3 and internal boot could we please get an option to permanently hide a licensing-only USB drive? Kinda annoying to always have it show in UD.

How does it show in UD? Screen shot?

Hello,

I am running Unraid 7.3.1 with the latest version of Unassigned Devices.

I have a Brother DS-940DW mobile scanner configured to save scans directly to its internal SD card. When the scanner is connected to the Unraid server via USB, it is detected correctly by Unassigned Devices:

- Device: Brother DS-940DW

- Size: 8.04 GB

- Filesystem: vfat

- Label: SCANSTOR

However, no "Mount" button is offered. Instead, Unassigned Devices only shows a button labeled "PARTITION".

From the command line, the device appears as "/dev/sdd".

"lsblk -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT" shows:

sdd 7.5G vfat SCANSTOR

"blkid /dev/sdd" returns:

/dev/sdd: LABEL_FATBOOT="SCANSTOR" LABEL="SCANSTOR" UUID="154D-61BC" TYPE="vfat"

"file -s /dev/sdd" returns:

DOS/MBR boot sector

OEM-ID "MSWIN4.1"

FAT (32 bit)

label: "SCANSTOR"

"fdisk -l" shows something unusual:

Disk /dev/sdd: 7.49 GiB

Disk model: DS-940DW

Device Boot Start End Sectors Size Id Type

/dev/sdd1 4109694196 8219388391 4109694196 1.9T f4 SpeedStor

/dev/sdd2 4109694196 8219388391 4109694196 1.9T f4 SpeedStor

/dev/sdd3 4109694196 8219388391 4109694196 1.9T f4 SpeedStor

/dev/sdd4 4109694196 8219388391 4109694196 1.9T f4 SpeedStor

These partition entries appear to be invalid and do not match the actual device size.

The SD card itself is known to be healthy and can be read normally on macOS. The scanner is also correctly detected by Linux and the filesystem is recognized as FAT32/VFAT.

Also, I had this working a few weeks ago.

Has anyone seen a device where the filesystem exists directly on the disk ("/dev/sdd") rather than on a partition ("/dev/sdd1"), causing Unassigned Devices to refuse mounting it?

Is there a known workaround or configuration option to force mounting such a device?

Any help would be appreciated.

2 hours ago, amix said:

Has anyone seen a device where the filesystem exists directly on the disk ("/dev/sdd") rather than on a partition ("/dev/sdd1"), causing Unassigned Devices to refuse mounting it?

Is there a known workaround or configuration option to force mounting such a device?

Yes. Just reformat it and make sure a partition was made, most OSes should do that. Maybe it was formatted in the device and that doesn't make a partition.

is there a script i can make that auto retrys remote share mounting when it cant establish? so if it doesnt mount wait 30 seconds then re try

so when the server or comp your trying to mount in the remote share will retry till it is mounted

Unassigned Drive is now showing my USB SSD external drive as grayed out REBOOT.

I have rebooted the entire server once already and it came back online.

But now I see it is showing grayed out REBOOT again. This is my back up drive.

The drive works fine when connected to my Windows 11 PC.

Is Unraid saying the drive is going bad?

3 hours ago, RaidPC said:

Unassigned Drive is now showing my USB SSD external drive as grayed out REBOOT.

This typically happens if you unplug the drive without unmounting it first.

Thank you, but now another new 4TB USB external drive is coming up with a REBOOT, just after I ran a rsync script to copy files to it. Two different drives, different USB cables and different USB ports.

Something changed. Only recent environmental change was upgrading the UnRaid OS.

Going to opt for now to not use the plugin and copy the files over my LAN with Syncback SE. Slower, but I maybe able to get more insight into the issue by doing so.

Looks like every time I run the script below, my drives hits the "Reboot" dialog box. I have no clue why. The scripts used to run fine. Using Syncback SE worked fine. But attaching the drive to an USB port on my Unraid server is faster.

#!/bin/bash

rsync -avh --delete --progress /mnt/disk3/Photos/backups /mnt/disks/Backup_4TB/Immich

rsync -avh --delete --progress /mnt/disk3/Photos/encoded-video /mnt/disks/Backup_4TB/Immich

rsync -avh --delete --progress /mnt/disk3/Photos/library /mnt/disks/Backup_4TB/Immich

10 hours ago, RaidPC said:

I have no clue why.

Check syslog to see if maybe the drive unexpectedly disconnects from USB during the process.

Edited June 2Jun 2 by Kilrah

10 hours ago, RaidPC said:

Looks like every time I run the script below, my drives hits the "Reboot" dialog box. I have no clue why.

Reboot to clear the logs, run the script, and post the diagnostics if you see the same.

I'll make a note of these suggestions.

Late last night I hooked up another WD drive, Easystore, only this one has the regular 3.5 hard and power adapter. Everything wrote to it with the same script with no issues.

I then hooked up the one 'problematic' MyPassport "REBOOT" earlier drive, and ran the same script on my second UnRaid box, reversing the order. No issues reading from the MyPassport (no external power supply) drive to the internal hard disk.

Then this morning a ran a WD sector by sector scan of the "problematic" drive (MyPassport). Two hours later, no SMART Thresholds tripped or diagnostic failures.

For now I have a working solution. I'll make a note to follow the suggestions above if I venture to hook up the previous drives again.

Trying to get azure classic storage mounted but it keeps timing out.

un 26 08:26:46 unRaid unassigned.devices: Mounting Remote Share '//xxxxxxxxx.FILE.CORE.WINDOWS.NET/storage'...

Jun 26 08:26:46 unRaid unassigned.devices: Mount SMB share '//XXXXXXXXX.FILE.CORE.WINDOWS.NET/storage' using SMB default protocol.

Jun 26 08:26:46 unRaid unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,hard,relatime,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,retrans=3,actimeo=10,rsize=1048576,wsize=1048576,closetimeo=30,credentials='/tmp/unassigned.devices/credentials_xxxxxxxxx.FILE.CORE.WINDOWS.NET_storage' '//XXXXXXXXX.FILE.CORE.WINDOWS.NET/storage' '/mnt/remotes/xxxxxxxxx.FILE.CORE.WINDOWS.NET_storage'

Jun 26 08:26:47 unRaid kernel: Key type dns_resolver registered

Jun 26 08:26:47 unRaid kernel: Key type cifs.idmap registered

Jun 26 08:26:47 unRaid kernel: CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.

Jun 26 08:26:47 unRaid kernel: CIFS: enabling forceuid mount option implicitly because uid= option is specified

Jun 26 08:26:47 unRaid kernel: CIFS: enabling forcegid mount option implicitly because gid= option is specified

Jun 26 08:26:47 unRaid kernel: CIFS: Attempting to mount //xxxxxxxx.FILE.CORE.WINDOWS.NET/storage

Jun 26 08:26:58 unRaid kernel: sd 0:0:12:0: [sdm] tag#1062 Sense Key : 0x1 [current]

Jun 26 08:26:58 unRaid kernel: sd 0:0:12:0: [sdm] tag#1062 ASC=0x1c ASCQ=0x0

Jun 26 08:26:58 unRaid kernel: sd 0:0:13:0: [sdn] tag#1749 Sense Key : 0x1 [current]

Jun 26 08:26:58 unRaid kernel: sd 0:0:13:0: [sdn] tag#1749 ASC=0x1c ASCQ=0x0

Jun 26 08:27:01 unRaid kernel: CIFS: VFS: cifs_mount failed w/return code = -512

Jun 26 08:27:01 unRaid unassigned.devices: Warning: shell_exec(/sbin/mount -t 'cifs' -o rw,hard,relatime,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,retrans=3,actimeo=10,rsize=1048576,wsize=1048576,closetimeo=30,credentials='/tmp/unassigned.devices/credentials_XXXXXXXXX.FILE.CORE.WINDOWS.NET_storage' '//xxxxxxxxx.FILE.CORE.WINDOWS.NET/storage' '/mnt/remotes/xxxxxxxxxx.FILE.CORE.WINDOWS.NET_storage' 2>&1) took longer than 15.0s!

Jun 26 08:27:01 unRaid unassigned.devices: Mount SMB share '//xxxxxxx.FILE.CORE.WINDOWS.NET/storage' using SMB 3.1.1 protocol.

Jun 26 08:27:01 unRaid unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,hard,relatime,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,retrans=3,actimeo=10,rsize=1048576,wsize=1048576,closetimeo=30,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_xxxxxxxx.FILE.CORE.WINDOWS.NET_storage' '//xxxxxxxx.FILE.CORE.WINDOWS.NET/storage' '/mnt/remotes/XXXXXXXXX.FILE.CORE.WINDOWS.NET_storage'

Jun 26 08:27:01 unRaid kernel: CIFS: enabling forceuid mount option implicitly because uid= option is specified

Jun 26 08:27:01 unRaid kernel: CIFS: enabling forcegid mount option implicitly because gid= option is specified

Jun 26 08:27:01 unRaid kernel: CIFS: Attempting to mount //xxxxxxxx.FILE.CORE.WINDOWS.NET/storage

That 15 second hang followed by a cifs_mount failed error could mean your ISP is blocking outbound traffic on Port 445.

Azure Files relies on standard SMB, which communicates over port 445. Because of historical malware vulnerabilities some ISPs completely block outbound port 445 traffic to the WAN, so that's worth testing to make sure it's open.

What does this return?

(timeout 5 bash -c 'cat < /dev/null > /dev/tcp/xxxxxxxxx.file.core.windows.net/445') && echo "PORT OPEN" || echo "PORT BLOCKED"