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

[Bob@unraid]

Hello everyone,
I mounted a smb root share from another unraid server to act as my backup target. The two system are "connected" with a Zerotier network through docker on each machine. I worked flawless and the the backup programm failed because my remote target share suddenly wasn´t available anymore.
The two systems can ping each other with the zerotier address, I can add the folder with unassigned devices plugin but cannot mount it. The remote folder in crussador is showing the folders but they are empty and I cannot copy or see anything. 
Is there anything I can try to fix this issue or can anyone help me out?
Thanks a lot

 

[dlandon]

14 minutes ago, Bob@unraid said:

Hello everyone,
I mounted a smb root share from another unraid server to act as my backup target. The two system are "connected" with a Zerotier network through docker on each machine. I worked flawless and the the backup programm failed because my remote target share suddenly wasn´t available anymore.
The two systems can ping each other with the zerotier address, I can add the folder with unassigned devices plugin but cannot mount it. The remote folder in crussador is showing the folders but they are empty and I cannot copy or see anything. 
Is there anything I can try to fix this issue or can anyone help me out?
Thanks a lot

 

Post diagnostics.

[Bob@unraid]

Thanks for the fast replay. Here are the files from both systems

unraid-diagnostics-20230727-0004.zip

tower-diagnostics-20230727-0015.zip

Edited July 26, 2023 by Bob@unraid

[Gray J]

Has anyone else having trouble with exfat drives, macOS, and smb share?

 

I have a usb 3.0 drive hooked up to Unraid via unassigned drives, I have it shared as a private smb share, but only around half of all the top dir folders are showing up in MacoOS.

 

is there any way to fix this?

[dlandon]

3 hours ago, Bob@unraid said:

Thanks for the fast replay. Here are the files from both systems

Can you see the files with the built in file browser?

[dlandon]

1 hour ago, Gray J said:

Has anyone else having trouble with exfat drives, macOS, and smb share?

 

I have a usb 3.0 drive hooked up to Unraid via unassigned drives, I have it shared as a private smb share, but only around half of all the top dir folders are showing up in MacoOS.

 

is there any way to fix this?

Do you have 'Enhanced macOS interoperability:' set to 'Yes'?

 

Post diagnostics.

[dlandon]

On 7/24/2023 at 4:38 PM, tazire said:

Looking for a bit of help removing an NFS share using command line. The server that was running a remote share shut down due to a power outage.. The share is still mounted in UD. When I clicked the unmount button in UD it locked up the GUI completely. I can SSH into the server... so i'm just looking for the commands to force unmount the share or force remove it ideally. I dont want to just try reboot on the off chance this hangs the server completely. I'd like to avoid a hard reset if possible. 

 

EDIT

Found my answer.

umount -l /pathofmount/

Sorted the issue and GUI was immediately accessible again. 

Can you post diagnostics so I can see why UD got hung?

[Masterwishx]

Using @SpaceInvaderOne ZFS Snapshot script with sanoid plugin and have sometimes warnings for unnasigned.devices:

 

 

[dlandon]

3 minutes ago, Masterwishx said:

Using @SpaceInvaderOne ZFS Snapshot script with sanoid plugin and have sometimes warnings for unnasigned.devices:

The reason this showed up is that you had a PC with the UD GUI open and apparently your server was working very hard.  The command that timed out is UD trying to read the mounts file to determine mounted status of the UD devices.  Reading that file should not take longer than 1 second.  I will increase the time out a bit to try to keep this from happening, but it is harmless other than to show UD could potentially be hanging.  UD will catch up on the mounted status at the next background scan.

 

Maybe ask the plugin author if they can adjust the priority.

[Masterwishx]

34 minutes ago, dlandon said:

The reason this showed up is that you had a PC with the UD GUI open and apparently your server was working very hard.  The command that timed out is UD trying to read the mounts file to determine mounted status of the UD devices.  Reading that file should not take longer than 1 second.  I will increase the time out a bit to try to keep this from happening, but it is harmless other than to show UD could potentially be hanging.  UD will catch up on the mounted status at the next background scan.

 

Maybe ask the plugin author if they can adjust the priority.

Thanks i got it , i will send it to sanoid plugin author 

[darckhart]

Is there a way (in some setting maybe) to make sure this plugin obeys the same update check procedure as other Unraid Plugins? ie, when I want to check updates for all my plugins, I go to the very top menubar and click Plugins, then the Check for Updates button at the top right. But UD appears to decide to check for updates itself outside of this. And then it adds this notification banner on the main Dashboard. I only want this unraid box to go out to the internet when I explicitly tell it to. Am I missing a configuration somewhere? Thanks!

[dlandon]

2 hours ago, darckhart said:

Am I missing a configuration somewhere?

No, this is the way the plugin system update works.  It's not a UD specific thing.

 

I have changed the display of the update banner.  It now shows in the UD webpage and not on the top like it did before.  It shoud not be quite as in your face as it was before.

[B Train]

Hello unRaid community.

I am trying to format an HDD under an Unassigned Devices' category.

Following the original post I have:

• Installed Community Applications
• Tried to enable destructive mode (cannot find it)
• Tried to format the HDD but no option is available.

I have read that I have to "Enable destructive mode in unassigned devices config then delete all of the partitions."

 

Using the web user interface, I go to 'Main' then scroll down to 'Unnasigned Devices' and then I see me unformated drive.

I am not getting any options to enable destructive mode or format my drive.

 

Any help would be much appreciated.

 

I am attaching a screenshot just in case.

 

Thank you for your help.

 

On 1/21/2016 at 7:55 AM, dlandon said:

need to install (UD+) ...to enable 'Destructive Mode' for formatting of some UD supported disk formats.

...

UD and UD+ are available in Community Applications (CA).

• UD has a destructive mode that allows deleting disk partitions and formatting disks.  If Destructive Mode is not turned on in the UD Settings, you WILL NOT be able to format a disk.  Go the the Settings page and scroll to the bottom to see the UD settings.  To format a disk:
  • Destructive Mode must be enabled.  You will need to install the 'Unassigned Devices Plus' plugin to enable Destructive Mode.  UD Plus will install the 'parted' package needed for formatting and deleting partitions.
  • Disk must have all partitions removed.  Unmount the disk, click on the '+' icon next to the serial number, and click on all red-X to delete partitions.  You can also click on the red-X next to the disk serial number to delete all partitions.
  • A precelared disk will have a partition without a file system and will show a grayed 'Mount' button.  You can assign this disk directly to the array and Unraid will see the disk as 'pre-cleared' and will not clear it again.  If you want to format the disk for use in UD, you need to first click on the red-X on the preclear status line to remove the preclear stats and then remove all partitions by clicking on the red-X icon next to the serial number and then you'll be able to format the disk.

[Amr0d]

Hello everyone, after a reboot of our unraid servers a friend of mine and myself can't mount our smb shares because of an error that occurs in the logs.

 

Quote

Jul 29 22:33:22 Tower kernel: CIFS: VFS: Error connecting to socket. Aborting operation.
Jul 29 22:33:22 Tower kernel: CIFS: VFS: cifs_mount failed w/return code = -111
Jul 29 22:33:22 Tower unassigned.devices: SMB 1.0 mount failed: 'mount error(111): could not connect to [remote wireguard IP]Unable to find suitable address. '.
Jul 29 22:33:22 Tower unassigned.devices: Share '[remote share]' failed to mount.

 

We both had this problem with 6.11.5 and now we have it with 6.12.3

 

What can we do to repair this?

tower-diagnostics-20230729-2240.zip

[wgstarks]

36 minutes ago, B Train said:

Hello unRaid community.

I am trying to format an HDD under an Unassigned Devices' category.

Did you also install UD+? IIRC you must install both.

[B Train]

14 minutes ago, wgstarks said:

Did you also install UD+? IIRC you must install both.

 

Thank you very much for replying, I was just on my way to provide an update as I have solved the issue:

I was unaware that 'UD' (Unassigned Devices) is two things:

1. Unassigned devices under the 'Main' menu
2. an installable app!

So, dear future reader, here is my solution to ' how to format drives '

You need four (4) apps:

1. Community Applications
2. Unassigned devices app
3. Unassigned devices addon
4. Unassigned devices pre-clear

To install apps go to Apps and search away.

To see if apps are installed check on the left pane and click on 'Installed Apps'.

See attached screenshot.

 

Thank you for your support, wgstarks

 

[wgstarks]

1 minute ago, B Train said:

Unassigned devices pre-clear

This isn’t really needed to format a drive. Only to pre-clear it.

[B Train]

4 minutes ago, wgstarks said:

This isn’t really needed to format a drive. Only to pre-clear it.

Sorry wgstarks, I am not sure what pre-clearing is and how does it differ from formatting a drive.

Can you please direct me to a location where I can learn this?

 

Thanks!

[dlandon]

Settings->Unassigned Devices.

[wgstarks]

1 hour ago, B Train said:

Sorry wgstarks, I am not sure what pre-clearing is and how does it differ from formatting a drive.

Can you please direct me to a location where I can learn this?

 

Thanks!

For drives to be added to the unRAID array they must first be cleared by writing zeros to every sector of a drive. In the past the array had to be off-line during this process. Thus users would pre-clear the drive before adding it to the array in order to avoid an extended off-line period for their server.

 

It is no longer necessary to take the array off-line. The clearing process is now done in the background, so pre-clearing is not really necessary now but many users like to pre-clear a new drive in order to stress test it. A pre-clear will write and read to every sector of a new drive as many times as you like (I usually run 3 cycles). This will put a fair amount of stress on a drive and probably reveal any faults. Of course the drawback to this is that with large drives each cycle can take a week or more so it’ll be a while before you get to use the drive.

[klaushipp]

Hi everybody, I love unRaid and I love this plugin. I saw that there is a DeviceScript and UserScript (from the UserScript Plugin). I think, that the DeviceScript is triggered if for a example a device has been mounted. But how can I trigger a UserScript from there. I dont understand how they interact.
Do you have a post here somewhere which explains the usage here?
Thank you in advance!

[dlandon]

12 minutes ago, klaushipp said:

Hi everybody, I love unRaid and I love this plugin. I saw that there is a DeviceScript and UserScript (from the UserScript Plugin). I think, that the DeviceScript is triggered if for a example a device has been mounted. But how can I trigger a UserScript from there. I dont understand how they interact.
Do you have a post here somewhere which explains the usage here?
Thank you in advance!

User scripts can be used to initiate some action on a UD disk.  For example, I have a mounted UD disk for backups and once a day I have a User script initiate a backup.  The User Script setting is used by UD to detect when a User Script is running and show 'Running' on the mount button.  When on the Device Settings page, click on the Help icon in the upper right part of the page and help script will show that gives more information on each field of the page.

 

UD does not initiate a User Script.

[dopeytree]

Had some problems with a sandisk extreme SSD usb3.

Drive is exfat and used with a mac.

Was using a usbc extension so that may cause an issue!?

 

In the end I copied over network instead

 

Jul 30 15:03:36 Moulin-rouge usb_manager: Info: rc.usb_manager Autoconnect No Mapping found SanDisk_Extreme_55AE_323134363846343031373739 /dev/bus/usb/002/005 002 005 port 2-1
Jul 30 15:03:38 Moulin-rouge unassigned.devices: Error: Device '/dev/sdl1' mount point 'Drone_Drive' - name is reserved, used in the array or a pool, or by an unassigned device.
Jul 30 15:03:38 Moulin-rouge unassigned.devices: Disk with serial 'SanDisk_Extreme_55AE_323134363846343031373739-0:0', mountpoint 'Drone_Drive' cannot be mounted.
Jul 30 15:03:55 Moulin-rouge smbd[9315]: [2023/07/30 15:03:55.574493,  0] ../../source3/lib/adouble.c:2363(ad_read_rsrc_adouble)
Jul 30 15:03:55 Moulin-rouge smbd[9315]:   ad_read_rsrc_adouble: invalid AppleDouble resource 1 TB - Drone Drive SSD - (2023)/Inspire3 tests.fcpbundle
Jul 30 15:03:55 Moulin-rouge smbd[9315]: [2023/07/30 15:03:55.577146,  0] ../../source3/lib/adouble.c:2363(ad_read_rsrc_adouble)
Jul 30 15:03:55 Moulin-rouge smbd[9315]:   ad_read_rsrc_adouble: invalid AppleDouble resource 1 TB - Drone Drive SSD - (2023)/Inspire3 tests.fcpbundle
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0xe0008
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to open directory '/$RECYCLE.BIN'
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0x7
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to open directory '/.Spotlight-V100'
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0x3265d
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to open directory '/.Trashes'
Jul 30 15:04:08 Moulin-rouge kernel: buffer_io_error: 4 callbacks suppressed
Jul 30 15:04:08 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 234883840, async page read
Jul 30 15:04:08 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 2560, async page read
Jul 30 15:04:08 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 52846592, async page read
Jul 30 15:04:08 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 6656, async page read
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0x17
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to open directory '/.fseventsd'
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0x3ba69
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to open directory '/Final Cut Original Media'
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0x482b
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to open directory '/Inspire3 tests.fcpbundle'
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0x4d
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to open directory '/Photos - Sony rx100'
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0x92e8
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to open directory '/Snow'
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0xe0002
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to open directory '/System Volume Information'
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0x2c424
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to open directory '/ Sabrent backup'
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0x1b483
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to open directory '/ Doc Martin Drone 300522 '
Jul 30 15:04:08 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 62548992, async page read
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0x7a07
Jul 30 15:04:08 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 4730368, async page read
Jul 30 15:04:08 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 20480, async page read
Jul 30 15:04:08 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 9628416, async page read
Jul 30 15:04:08 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 234882304, async page read
Jul 30 15:04:08 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 46409472, async page read
Jul 30 15:04:08 Moulin-rouge mount.exfat: failed to read cluster 0x7a07
Jul 30 15:05:07 Moulin-rouge kernel: buffer_io_error: 3 callbacks suppressed
Jul 30 15:05:07 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 62548992, async page read
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to read cluster 0x3ba69
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to open directory '/Final Cut Original Media'
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to read cluster 0x482b
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to open directory '/Inspire3 tests.fcpbundle'
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to read cluster 0x4d
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to open directory '/Photos - Sony rx100'
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to read cluster 0x92e8
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to open directory '/Snow'
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to read cluster 0x2c424
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to open directory '/ Sabrent backup'
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to read cluster 0x1b483
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to open directory '/ Doc Martin Drone 300522 '
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to read cluster 0x7a07
Jul 30 15:05:07 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 4730368, async page read
Jul 30 15:05:07 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 20480, async page read
Jul 30 15:05:07 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 9628416, async page read
Jul 30 15:05:07 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 46409472, async page read
Jul 30 15:05:07 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 28608000, async page read
Jul 30 15:05:07 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 7997952, async page read
Jul 30 15:05:07 Moulin-rouge mount.exfat: failed to read cluster 0x7a07
Jul 30 15:05:07 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 7997952, async page read
Jul 30 15:05:23 Moulin-rouge emhttpd: read SMART /dev/sdl
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x7
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/.Spotlight-V100'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x7
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/.Spotlight-V100'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x17
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/.fseventsd'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x17
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/.fseventsd'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x4d
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Photos - Sony rx100'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x4d
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Photos - Sony rx100'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0xe0002
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/System Volume Information'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0xe0002
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/System Volume Information'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x2c424
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/ Sabrent backup'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x2c424
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/ Sabrent backup'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0xe0008
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/$RECYCLE.BIN'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0xe0008
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/$RECYCLE.BIN'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x92e8
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Snow'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x92e8
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Snow'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x482b
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Inspire3 tests.fcpbundle'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x482b
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Inspire3 tests.fcpbundle'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x3ba69
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Final Cut Original Media'
Jul 30 15:07:01 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 2560, async page read
Jul 30 15:07:01 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 2560, async page read
Jul 30 15:07:01 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 6656, async page read
Jul 30 15:07:01 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 6656, async page read
Jul 30 15:07:01 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 20480, async page read
Jul 30 15:07:01 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 20480, async page read
Jul 30 15:07:01 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 234882304, async page read
Jul 30 15:07:01 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 234882304, async page read
Jul 30 15:07:01 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 46409472, async page read
Jul 30 15:07:01 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 46409472, async page read
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x3ba69
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Final Cut Original Media'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x3265d
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/.Trashes'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x3265d
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/.Trashes'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x1b483
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/ Doc Martin Drone 300522 '
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x1b483
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/ Doc Martin Drone 300522 '
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x7
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/.Spotlight-V100'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x7
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/.Spotlight-V100'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x17
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/.fseventsd'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x17
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/.fseventsd'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x4d
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Photos - Sony rx100'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x4d
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Photos - Sony rx100'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0xe0002
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/System Volume Information'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0xe0002
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/System Volume Information'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x2c424
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/ Sabrent backup'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x2c424
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/ Sabrent backup'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0xe0008
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/$RECYCLE.BIN'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0xe0008
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/$RECYCLE.BIN'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x92e8
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Snow'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x92e8
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Snow'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x482b
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Inspire3 tests.fcpbundle'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x482b
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to open directory '/Inspire3 tests.fcpbundle'
Jul 30 15:07:01 Moulin-rouge mount.exfat: failed to read cluster 0x7a07
Jul 30 15:07:07 Moulin-rouge mount.exfat: failed to read cluster 0x7a07
Jul 30 15:07:07 Moulin-rouge kernel: buffer_io_error: 29 callbacks suppressed
Jul 30 15:07:07 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 7997952, async page read
Jul 30 15:07:07 Moulin-rouge kernel: Buffer I/O error on dev sdk1, logical block 7997952, async page read

 

Edited July 30, 2023 by dopeytree

[dlandon]

On 7/22/2023 at 4:42 PM, akguy said:

Any ideas if there is a way I can get that NVME1n1p3 device off of this list?

In the next release of UD the partition marked with 'Format' will show as 'Pool' on the mount button and all UD operations will be blocked.  It will also not show up as a preclear candidate to prevent an accidental preclear.  It's marked as 'Pool' because LVM is a pool and the disk is a pool member.

 

I'd like to put that partition under the main disk, but the way the disk is formatted, udev thinks it is a stand alone disk.  Because your situation is a corner case, this is the best I can do for now.  Unraid and UD don't handle this situation because disks in Unraid are always formatted wth a partition.  LVM appears to create a 'disk' within a partition on the disk.

[akguy]

1 hour ago, dlandon said:

Because your situation is a corner case, this is the best I can do for now.  Unraid and UD don't handle this situation because disks in Unraid are always formatted wth a partition.  LVM appears to create a 'disk' within a partition on the disk.

 

Thank you; you have gone above and beyond and I really appreciate the care and attentiveness you have put into maintaining this plugin.  I am pretty sure that my blood pressure will run lower once the "Format" button is gone.