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


Recommended Posts

I'm not able to format a USB drive to exfat.

It's a new drive. It had vfat on it. I was able to mount it with Unassigned Devices and see that it had some Manufacturer software on it. Next I clicked the red X for "Clear Disk" and that partition was deleted.

Next I tried to format it to exfat. I end up with an empty partition.

 

Quote

Jul 26 19:38:45 Antec kernel: sd 8:0:0:0: [sdn] 488374272 512-byte logical blocks: (250 GB/233 GiB)
Jul 26 19:38:45 Antec kernel: sd 8:0:0:0: [sdn] Write Protect is off
Jul 26 19:38:45 Antec kernel: sd 8:0:0:0: [sdn] Mode Sense: 43 00 00 00
Jul 26 19:38:45 Antec kernel: sd 8:0:0:0: [sdn] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jul 26 19:38:45 Antec kernel: sdn: sdn1
Jul 26 19:38:45 Antec kernel: sd 8:0:0:0: [sdn] Attached SCSI removable disk
Jul 26 19:39:19 Antec unassigned.devices: Removing all partitions from disk '/dev/sdn'.
Jul 26 19:39:53 Antec unassigned.devices: Format device '/dev/sdn'.
Jul 26 19:39:53 Antec unassigned.devices: Device '/dev/sdn' block size: 488374272.
Jul 26 19:39:53 Antec unassigned.devices: Clearing partition table of disk '/dev/sdn'.
Jul 26 19:39:53 Antec unassigned.devices: Reloading disk '/dev/sdn' partition table.
Jul 26 19:39:53 Antec unassigned.devices: Reload partition table result: /dev/sdn:  re-reading partition table
Jul 26 19:39:53 Antec unassigned.devices: Creating a 'gpt' partition table on disk '/dev/sdn'.
Jul 26 19:39:54 Antec unassigned.devices: Formatting disk '/dev/sdn' with 'exfat' filesystem.
Jul 26 19:39:54 Antec mkfs.exfat: failed to open '/dev/sdn1' in read-write mode: No such file or directory
Jul 26 19:39:54 Antec kernel: sdn: sdn1
Jul 26 19:39:57 Antec unassigned.devices: Reloading disk '/dev/sdn' partition table.
 

 

Quote

root@Antec:~# fdisk -l /dev/sdn
Disk /dev/sdn: 232.88 GiB, 250047627264 bytes, 488374272 sectors
Disk model:  SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Device     Start       End   Sectors   Size Type
/dev/sdn1   2048 488372223 488370176 232.9G Microsoft basic data

 

image.thumb.png.9b79445aebd19b137312d797dacf308d.png

\

 

Edit: I was able to format to exFat in Windows. After I did that, I could mount it with Unassigned Devices.  I tried again red X for "Clear Disk" and that partition was deleted. Next I tried to format it to exfat again and now it worked.

 

Second Edit:

Unassigned Devices does NOT LIKE the default Disk Label "USB_SanDisk_3.2Gen1" and this causes the problem somehow.

If I change the Disk Label by changing the Mount Point to "USB250GB" now everything works and it can format to exfat.

image.png.dd6cb8380c2e5f209b262877f949f067.png

 

 

 

 

Edited by frank-unr
Link to comment

I have three drives that are not part of my array and am expecting that all three would show up under "Unassigned Devices", but only one of the drives is showing up as "dev 1".  Can someone point in the right direction as to what I must be missing?  How do I get the other two drives to show up under "Unassigned Devices"?

 

Thanks in advance.

Link to comment
5 hours ago, ecuster said:

I have three drives that are not part of my array and am expecting that all three would show up under "Unassigned Devices", but only one of the drives is showing up as "dev 1".  Can someone point in the right direction as to what I must be missing?  How do I get the other two drives to show up under "Unassigned Devices"?

 

Thanks in advance.

Post your diagnostics.

Link to comment

Hello guys. I have two drives that I use to back up my array. They worked normally. Now they appear as mounted but does not show the folders within it. Even if I disconnect and connect, they go back to the same state. The folders don't even appear in Krusader. I only see the drives.  

image.thumb.png.c3d521b10c930e9c04b2b7d622277aae.png

 

image.thumb.png.27092356d57e8cacc354f3f9b27555d2.png

image.thumb.png.5c450c73d837a1d02c74dd0acad0df76.png

Here is the script used in user scripts and rsync. All the folders still exists in the drive.

 

image.thumb.png.7eb58597071c81f193fa4bc360ed5f33.png

Thanks.

 

 

Edited by danilodino
Link to comment
37 minutes ago, danilodino said:

Hello guys. I have two drives that I use to back up my array. They worked normally. Now they appear as mounted but does not show the folders within it. Even if I disconnect and connect, they go back to the same state. The folders don't even appear in Krusader. I only see the drives.  

image.thumb.png.c3d521b10c930e9c04b2b7d622277aae.png

 

image.thumb.png.27092356d57e8cacc354f3f9b27555d2.png

image.thumb.png.5c450c73d837a1d02c74dd0acad0df76.png

Here is the script used in user scripts and rsync. All the folders still exists in the drive.

 

image.thumb.png.7eb58597071c81f193fa4bc360ed5f33.png

Thanks.

 

 

Post diagnostics.

Link to comment
7 minutes ago, danilodino said:

 

You have multiple issues.  The log is loaded with SMB messages caused by AD.  This is making it hard to find UD messages.

Aug  4 20:51:06 TW-NAS winbindd[13584]:   idmap_hash_initialize: The idmap_hash module is deprecated and should not be used. Please migrate to a different plugin. This module will be removed in a future version of Samba

 

This is what I found related to your UD disks:

Aug  5 14:24:02 TW-NAS unassigned.devices: Partition 'sdg1' does not have a file system and cannot be mounted.
Aug  5 14:24:02 TW-NAS unassigned.devices: Adding partition 'sdg2'...
Aug  5 14:24:02 TW-NAS unassigned.devices: Mounting partition 'sdg2' at mountpoint '/mnt/disks/backup_nas'...
Aug  5 14:24:02 TW-NAS unassigned.devices: Partition 'sdg2' is already mounted.
Aug  5 14:24:02 TW-NAS unassigned.devices: Partition 'backup_nas' cannot be mounted.
Aug  5 14:25:37 TW-NAS webGUI: Successful login user root from 192.168.0.61
Aug  5 14:25:44 TW-NAS ntfs-3g[10650]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Aug  5 14:25:44 TW-NAS ntfs-3g[10650]: Failed to read index block: Input/output error
Aug  5 14:25:55 TW-NAS unassigned.devices: Cannot unmount 'sdg2'. UD did not mount the device or it was not properly unmounted.
Aug  5 14:25:55 TW-NAS unassigned.devices: Partition 'backup_nas' cannot be unmounted.
Aug  5 14:26:02 TW-NAS unassigned.devices: Unmounting partition 'sdg2' at mountpoint '/mnt/disks/backup_nas'...
Aug  5 14:26:02 TW-NAS unassigned.devices: Cannot unmount 'sdg2'. UD did not mount the device or it was not properly unmounted.
Aug  5 14:26:02 TW-NAS unassigned.devices: Partition 'backup_nas' cannot be unmounted.
Aug  5 14:26:04 TW-NAS unassigned.devices: Unmounting partition 'sdg2' at mountpoint '/mnt/disks/backup_nas'...
Aug  5 14:26:04 TW-NAS unassigned.devices: Cannot unmount 'sdg2'. UD did not mount the device or it was not properly unmounted.
Aug  5 14:26:04 TW-NAS unassigned.devices: Partition 'backup_nas' cannot be unmounted.
Aug  5 14:26:05 TW-NAS unassigned.devices: Unmounting partition 'sdg2' at mountpoint '/mnt/disks/backup_nas'...
Aug  5 14:26:05 TW-NAS unassigned.devices: Cannot unmount 'sdg2'. UD did not mount the device or it was not properly unmounted.
Aug  5 14:26:05 TW-NAS unassigned.devices: Partition 'backup_nas' cannot be unmounted.

Because the disks are marked "Array", and the log messages about how the disk cannot be unounted, it looks like the disks were removed without being unmounted.

 

Your best way out of this predicament is to reboot.

Link to comment

Could you change this "Error:" to "Info:" or "Warning:"?

 

Quote

Event: Unraid Status

Subject: syslog error

Description: Aug 6 08:41:43 thoth unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/DESKTOP-I0HHMD9_Users' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! Aug 6 08:41:46 thoth unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/DESKTOP-I0HHMD9_Users' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!

Importance: alert

 

As you can see I monitor all errors and this is not really an error.

Link to comment
2 minutes ago, dlandon said:

Works for me on Brave.

 

Screenshot 2022-08-07 151935.png

 

Try clearing your browser cache.

 

Cleared the cache/cookies for both of my unRAID servers but it's still empty. I suspect it's related to an issue with my ISP - Shaw in Canada has had a major outage since 11am MT Friday. It's causing all sorts of slowdowns for the network, and for some reason is even impacting my local network performance. If I disconnect the WAN cable from my modem and reboot my systems, my internal LAN is as fast as expected, but not when my LAN is connected to the internet. Thanks for posting that screenshot - that'll suffice until my ISP things get sorted.

 

Link to comment

I am a noob, 3 days on unRAID. I found out that I can use my eSATA dock with unRAID and transfer directly to the array. My old mobo (ASUS Sabertooth Z77) has an eSATA port. I have 18 old data HDDs 150GB to 500GB that I am filtering through for good media, transfer speed is much better than USB2 (the only alt on the dock). I watched a Spaceinvader video on Krusader and Unassigned disk and they are working great.

Link to comment

I've applied the UD update this morning after getting notified of it, don't know if it's related... then connected my external backup drive, the automatic backup script ran normally, so far so good.

 

But later I've connected a completely different drive that doesn't have automount set nor any scripts assigned and obviously different identifiers and partition names and strangely I heard the notification sounds the backup scripts makes. UD somehow automounted it, decided the EFI partition of that drive (which is a full OS install) should be assigned the mountpoint of my backup drive even though that's not what the UI shows, and started running the script. Now that EFI partition is filled to the brim with backups that were never supposed to be there. The partition in question is that with the SSD_256 label and got mounted into UNRAID_SAVE that's supposed to be the correct drive's mountpoint.

 

Clipboard01.thumb.png.78bb0aa7449734fa73970b224845bc19.png

 

Diags attached...

unraid-diagnostics-20220808-1043.zip

Link to comment
4 hours ago, Kilrah said:

The partition in question is that with the SSD_256 label and got mounted into UNRAID_SAVE that's supposed to be the correct drive's mountpoint.

The partition with label 'SSD_256' never got mounted.  No where in the logs does it show anything that got mounted to /mnt/disks/UNRAID_SAVE.

 

As far as the automount, I don't know what is going on with that.

 

My suggestions:

  • Click the double arrows in the upper right corner of the UD webpage.  The configuration files in ram may have an issue.  This will refresh those.
  • Check your UD mount points and scripts.  Your script should not write to a non existant mount point /mnt/disks/UNRAID_SAVE.
Link to comment
41 minutes ago, dlandon said:

The partition with label 'SSD_256' never got mounted.  No where in the logs does it show anything that got mounted to /mnt/disks/UNRAID_SAVE.

 

It did!

In the syslog between 10:02 and 10:21 you see an xfs drive mounted as UNRAID_BACKUP and a backup script running, that is the real backup drive. Starting at 10:40:16 another drive is detected, and at 10:40:19

Aug  8 10:40:19 Unraid unassigned.devices: Mount drive command: /sbin/mount -t 'vfat' -o rw,noatime,nodiratime,nodev,nosuid,iocharset=utf8,umask=000 '/dev/sdh1' '/mnt/disks/UNRAID_BACKUP'
[...]
Aug  8 10:40:19 Unraid unassigned.devices: Successfully mounted 'sdh1' on '/mnt/disks/UNRAID_BACKUP'.

 

This is the EFI partition of the unrelated drive, you can see the type is vfat because of that. It just went by "sdh1" which is the same in both cases, ignoring that it's not the same drive.

 

The script then runs and unmounts. It only unmounted that partition, left the other '/mnt/disks/155327401441-part2' mounted.

 

I then remounted the EFI partition and it was full, with a backup folder on it. Deleted it and all good, but still...

 

41 minutes ago, dlandon said:

Click the double arrows in the upper right corner of the UD webpage.  The configuration files in ram may have an issue.  This will refresh those.

Will try that.

 

For the record, here's unassigned.devices.cfg

 

[Config]
common_cmd=""
destructive_mode="disabled"
automount_usb="no"
discard="yes"
symlinks="no"
smb_version="no"
debug_level="0"
key=""
iv=""
smb_security="public"
smb_share="read-write"
smb_timemachine="no-access"
case_names="auto"
mac_os="no"
force_user="yes"
[SanDisk_SD7SN6S-256G-1006_155327401441]
unassigned_dev="dev3"
mountpoint.1="/mnt/disks/SSD_256"
[WD_Elements_SE_25FF_57584131444137305043384C-0:0]
unassigned_dev="dev2"
mountpoint.1="/mnt/disks/UNRAID_BACKUP"
user_command.1=""
command_bg.1="true"
command.1="/boot/config/plugins/unassigned.devices/UNRAID_BACKUP.sh"
automount="yes"
[WD_Elements_SE_25FF_575836314431384B43584652-0:0]
unassigned_dev="dev1"

 

Edited by Kilrah
Link to comment

Changing the mount points on UD volumes is a convenient way to change volume labels.  As a result, the mount points are stored in unassigned.devices.cfg.  However, subsequent changes to the drive, not done in UD, can leave the plugin very confused.    

 

1982489556_UDScreenshot.thumb.png.6692bc25f42de0fe6220d295db31aabe.png

 

The Sandisk Cruser Fit is currently /dev/sdo with 4 partitions, and the Samsung Flash Drive is /dev/sdp with 1 partition.

 

From:
ls -l /dev/disk/by-id

lrwxrwxrwx 1 root root  9 Aug  8 09:09 usb-Samsung_Flash_Drive_0374421030005963-0:0 -> ../../sdp
lrwxrwxrwx 1 root root 10 Aug  8 09:09 usb-Samsung_Flash_Drive_0374421030005963-0:0-part1 -> ../../sdp1

lrwxrwxrwx 1 root root  9 Aug  8 06:48 usb-SanDisk_Cruzer_Fit_4C530007541116121314-0:0 -> ../../sdo
lrwxrwxrwx 1 root root 10 Aug  8 06:48 usb-SanDisk_Cruzer_Fit_4C530007541116121314-0:0-part1 -> ../../sdo1
lrwxrwxrwx 1 root root 10 Aug  8 06:48 usb-SanDisk_Cruzer_Fit_4C530007541116121314-0:0-part2 -> ../../sdo2
lrwxrwxrwx 1 root root 10 Aug  8 06:48 usb-SanDisk_Cruzer_Fit_4C530007541116121314-0:0-part3 -> ../../sdo3
lrwxrwxrwx 1 root root 10 Aug  8 06:48 usb-SanDisk_Cruzer_Fit_4C530007541116121314-0:0-part4 -> ../../sdo4

From:
ls -l /dev/disk/by-label

lrwxrwxrwx 1 root root 10 Aug  8 09:09 SAMSUNG -> ../../sdp1

lrwxrwxrwx 1 root root 10 Aug  8 06:48 UNBOOT -> ../../sdo1
lrwxrwxrwx 1 root root 10 Aug  8 06:48 UN610 -> ../../sdo3
lrwxrwxrwx 1 root root 10 Aug  8 06:48 UN611 -> ../../sdo4
lrwxrwxrwx 1 root root 10 Aug  8 06:48 UN692 -> ../../sdo2

 

Unraid 6.9.2, UD 2022.08.07.

unassigned.devices.cfg

Edited by aim60
Link to comment
3 hours ago, Kilrah said:

It did!

In the syslog between 10:02 and 10:21 you see an xfs drive mounted as UNRAID_BACKUP and a backup script running, that is the real backup drive. Starting at 10:40:16 another drive is detected, and at 10:40:19

That's UNRAID_BACKUP, not UNRAID_SAVE.  UNRAID_SAVE is not a mount point defined in your UD config file, and the mount in the log snippet you posted is /mnt/disks/UNRAID_BACKUP.

 

UD doesn't mount a disk using another disks mount point, unless something is broken in your system.

 

The only thing I can come up with is:

  • The previous disk was not properly unmounted, or
  • Your flash and/or ramfs has a problem.

Your best course of action here is a reboot.  If that doesn't sort it out, post your new diagnostics.

 

 

Link to comment
3 hours ago, aim60 said:

Changing the mount points on UD volumes is a convenient way to change volume labels.  It also results in the mount points being stored in unassigned.devices.cfg.  This can cause UD to get very confused.

When changing the mount point, the disk label is also changed using a Linux utility for the file system being used.  The label change on the Samsung flash either failed to change, or the drive doesn't support changing the label.

 

The label is not really important if you change the mount point.  It is not used by UD except to set a mount point if it is not user defined.  If the mount point is set manually, the label change is really only a convenience to the user.

 

This situation doesn't really confuse UD.  If you expect the mount point to be "SAMSUNG" (the disk label), then it might be confusing to you.

 

Post your diagnostics so I can see the result of the labelchange command.

 

 

Link to comment

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

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.