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


dlandon

Recommended Posts

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
2 hours ago, dlandon said:

That's UNRAID_BACKUP, not UNRAID_SAVE. 

Sorry, simply mixed up the names, unraid_save is the name of the backup folder on the drive, everytime I mentioned that I meant UNRAID_BACKUP.

Edited by Kilrah
Link to comment

Hi, I have 3 external hdds mounted using unassigned devices.  Unraid UI shows these as mounted, shared, not passed through.  I can see the contents of the shares if I browse via the Unraid UI.  However I am unable to see these shares at all while browsing the shares from client devices (macos/windows11).  Native unraid shares are listed as normal, the UD shares are not visible.  This was working in the past and appears to have stopped working recently although unfortunately I haven't been paying adequate attention and I don't know the specific point when things stopped working. 😞 

Diagnostics attached.  Thank you in advance for any pointers you can provide?

nas-diagnostics-20220808-2345.zip

Link to comment
7 minutes ago, leaskc said:

Hi, I have 3 external hdds mounted using unassigned devices.  Unraid UI shows these as mounted, shared, not passed through.  I can see the contents of the shares if I browse via the Unraid UI.  However I am unable to see these shares at all while browsing the shares from client devices (macos/windows11).  Native unraid shares are listed as normal, the UD shares are not visible.  This was working in the past and appears to have stopped working recently although unfortunately I haven't been paying adequate attention and I don't know the specific point when things stopped working. 😞 

Diagnostics attached.  Thank you in advance for any pointers you can provide?

nas-diagnostics-20220808-2345.zip 120.6 kB · 1 download

There has been a recent change in the SMB sharing setting in UD.  Go to the UD settings page and review the setting:

Screenshot 2022-08-08 180117.png

 

The change was that the "No" setting no longer shares UD devices Public.  The "Public" setting is used to share devices Public.

  • Like 1
Link to comment
16 minutes ago, dlandon said:

There has been a recent change in the SMB sharing setting in UD. 

 

Thank you @dlandon - I saw "enable security = No" and incorrectly assumed that would be the correct setting for my use case.  Appreciate the super-prompt response, thank you

Link to comment
22 hours ago, dlandon said:

This situation doesn't really confuse UD

 

The partition structure of both flash drives were changed while in a workstation.  After bringing them back to the server, the GUI information was inconsistent with the current state of the drives.  Rebooting the server resolved the issue.

 

Thanks.

Link to comment
58 minutes ago, aim60 said:

 

The partition structure of both flash drives were changed while in a workstation.  After bringing them back to the server, the GUI information was inconsistent with the current state of the drives.  Rebooting the server resolved the issue.

 

Thanks.

What was inconsistent?  The disk label?

Link to comment

I am slowly moving some of my external drives (1 at a time) to a Netshelf. This was my 3rd drive that I just added and started running Preclear.

It showed me the MB/s and timer, but then it all went away. No error or anything. To make things interesting it does look like the HD is flashing non-stop but none of the counters are moving whatsoever.

 

Should I just wait to see if anything changes and reboot if nothing?

preclear01.png

preclear01.txt

Link to comment
1 hour ago, dlandon said:

What was inconsistent?  The disk label?

 

Go back to my original post. 

Carefully compare the (incorrect) screenshot with the (correct) ls -l outputs. 

   The Sandisk Cruzer Fit shows 1 partition on /dev/sdp.

      It has 4 partitions and is on /dev/sdo

 

    The Samsung flash shows 4 partitions on /dev/sdo

      It has 1 partition and is on /dev/sdp

 

I have to admit, what I did is far from typical.  The Samsung drive originally had 4 partitions, with 4 unique labels.  The Cruzer had 1 partition.  I moved both drives to a workstation.  I repartitioned the Sansung drive with 1 partition, and the Cruzer with 4 partitions -  with the same 4 labels that existed on the other drive.  

 

 

 

Link to comment
1 hour ago, dimitriz said:

I am slowly moving some of my external drives (1 at a time) to a Netshelf. This was my 3rd drive that I just added and started running Preclear.

It showed me the MB/s and timer, but then it all went away. No error or anything. To make things interesting it does look like the HD is flashing non-stop but none of the counters are moving whatsoever.

 

Should I just wait to see if anything changes and reboot if nothing?

preclear01.png

preclear01.txt 3.02 kB · 2 downloads

Look at the preclear web page.  That should show status 

  • Thanks 1
Link to comment
2 minutes ago, aim60 said:

 

Go back to my original post. 

Carefully compare the (incorrect) screenshot with the (correct) ls -l outputs. 

   The Sandisk Cruzer Fit shows 1 partition on /dev/sdp.

      It has 4 partitions and is on /dev/sdo

 

    The Samsung flash shows 4 partitions on /dev/sdo

      It has 1 partition and is on /dev/sdp

 

I have to admit, what I did is far from typical.  The Samsung drive originally had 4 partitions, with 4 unique labels.  The Cruzer had 1 partition.  I moved both drives to a workstation.  I repartitioned the Sansung drive with 1 partition, and the Cruzer with 4 partitions -  with the same 4 labels that existed on the other drive.  

 

 

 

I suspect it is because ud is caching udev info and doesn't expect any partition changes outside of ud.  If you change things outside ud, I think ud will still use the previous udev info and not the updated info.  I'll have a look.

  • Like 1
Link to comment
On 8/9/2022 at 3:33 PM, dlandon said:

Look at the preclear web page.  That should show status 

I have a potential fix for your situation.  I'll do some more testing before I consider it ready for prime time.

 

I have to say, I am amazed this hasn't come up until now.  Normally I come across these kinds of issues when I'm testing UD.  This is kind of a corner case, but pretty messy when it happens.

Link to comment

I have just noted that's not possible to use and password for encryption with a   '+' . 

The character should be contained in the printable ascii chararacters but when I try to mount :

 

Aug 12 02:25:43 Tower unassigned.devices: Using disk password to open the 'crypto_LUKS' device.
Aug 12 02:25:45 Tower unassigned.devices: luksOpen result: No key available with this passphrase. 
Aug 12 02:25:45 Tower unassigned.devices: Partition '9VPDDZC0' cannot be mounted.

 

Is it normal? 

Link to comment
10 hours ago, Hitokiri said:

I have just noted that's not possible to use and password for encryption with a   '+' . 

The character should be contained in the printable ascii chararacters but when I try to mount :

 

Aug 12 02:25:43 Tower unassigned.devices: Using disk password to open the 'crypto_LUKS' device.
Aug 12 02:25:45 Tower unassigned.devices: luksOpen result: No key available with this passphrase. 
Aug 12 02:25:45 Tower unassigned.devices: Partition '9VPDDZC0' cannot be mounted.

 

Is it normal? 

Yes.  There are some characters used in the password that cause an issue with php.  The '+' character is one of them.

Link to comment
6 hours ago, fr05ty said:

hello all hopefully someone much smarter than me can tell me why I'm getting this error in my syslogs and if there is a way to fix it

 

unassigned.devices: Warning: shell_exec(/usr/bin/cat /proc/mounts | awk '{print $1 ',' $2}') took longer than 1s!

 

been having a few random lockup lately trying to narrow down causes 

 

iceberg-diagnostics-20220816-1456.zip 245.41 kB · 1 download

The UD error is happening because your system is too busy, or hanging up somewhere.

 

There are some file missing errors in the log:

Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739665 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /us HTTP/1.1", host: "localhost"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739666 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /us HTTP/1.1", host: "127.0.0.1"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739667 open() "/usr/local/emhttp/status/format/json" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status/format/json HTTP/1.1", host: "127.0.0.1"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739668 open() "/usr/local/emhttp/basic_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /basic_status HTTP/1.1", host: "127.0.0.1"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739669 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /stub_status HTTP/1.1", host: "localhost"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739670 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /stub_status HTTP/1.1", host: "127.0.0.1"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739671 open() "/usr/local/emhttp/nginx_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /nginx_status HTTP/1.1", host: "127.0.0.1"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739672 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status HTTP/1.1", host: "127.0.0.1"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739673 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status?full&json HTTP/1.1", host: "localhost"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739674 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status?full&json HTTP/1.1", host: "127.0.0.1"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739675 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: ::1, server: , request: "GET /status?full&json HTTP/1.1", host: "[::1]"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739676 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "localhost"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739677 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "127.0.0.1"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739679 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "localhost"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739680 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "127.0.0.1"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739681 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?format=plain HTTP/1.1", host: "localhost"
Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739682 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?format=plain HTTP/1.1", host: "127.0.0.1"
Aug 15 17:16:26 iceberg kernel: wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
Aug 15 17:16:26 iceberg kernel: wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <email@removed.com>. All Rights Reserved.
Aug 15 17:16:33 iceberg nginx: 2022/08/15 17:16:33 [error] 9676#9676: *3739814 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status HTTP/1.1", host: "localhost"
Aug 15 17:16:33 iceberg nginx: 2022/08/15 17:16:33 [error] 9676#9676: *3739815 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status HTTP/1.1", host: "127.0.0.1"
Aug 15 17:16:33 iceberg nginx: 2022/08/15 17:16:33 [error] 9676#9676: *3739816 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: ::1, server: , request: "GET /status HTTP/1.1", host: "[::1]"

I'm not sure where these are coming from.  There may be a plugin causing this.

 

Your diagnostics zip is missing a lot of folders in the /flash/config/ folder.  For example, plugins/ is missing.  It looks like there may be an issue on your flash.

 

I woud do the following:

  • Shut down your system and check the flash drive on a PC.
  • Remove NerdPack.  There may be a package causing some issues.  See if the UD timeout messages continue.
  • Start your system in safe mode and run it that way to see if the random shut downs continue.
Link to comment

thanks for having a look, that error block was right after I installed netdata and it started up, I have export on the flash drive and just browsed to \flash in windows and it shows the plugin folder, to check the usb is there any particular program to use, I have a win and a linux pc if you have a fav program

 

I don't think the system would be to busy its a 3900x and most of the time sits at around 5-10% usage and looking at glances iowait is around 1-5%

 

folders.thumb.PNG.26049c7eecd0eab44f38064a025c4985.PNG

 

glances.thumb.PNG.25ddbb984e9516d7c440f999131dd141.PNG

 

 

Link to comment
3 hours ago, fr05ty said:

to check the usb is there any particular program to use, I have a win and a linux pc if you have a fav program

Insert the flash drive, right click Properties, Tools, Check to check the drive.

 

3 hours ago, fr05ty said:

I don't think the system would be to busy its a 3900x and most of the time sits at around 5-10% usage and looking at glances iowait is around 1-5%

The timeout warning is from a 'cat' command that shows the contents of a file.  That file is in the ramfs and should be extremely fast.  Something slowed it down.

Link to comment

I have an unassigned disk going bad that needs to be replaced. I'm a little unsure what the process is. 

Do I just unmount it, pop in the new disk? I see the below info for disk1 which is the drive that needs to be replaced. I want to make sure the new disk keeps the same share name.

Any guidance would be appreciated.

image.png.e7c0a8a556259edd30e84381360f841f.png

Link to comment
2 hours ago, DigitalDivide said:

I have an unassigned disk going bad that needs to be replaced. I'm a little unsure what the process is. 

Do I just unmount it, pop in the new disk? I see the below info for disk1 which is the drive that needs to be replaced. I want to make sure the new disk keeps the same share name.

Any guidance would be appreciated.

image.png.e7c0a8a556259edd30e84381360f841f.png

You would need to set the share name explicitly having changed the drive.

Link to comment

I replaced an unnassigned disk that was going bad by buying a new drive which I used to replace an existing data drive in the array and then used that disk to replace the bad unassigned disk. However, it won't mount. Is it because I need to format it ...which I'd like to do but not sure how once it's all plugged in or is it because it recognizes it as a drive that was in the array? I'm not sure what to do at this point to mount it.

 

I see this in the disk log for the drive

Aug 20 06:02:12 Tower kernel: XFS (sdc1): Filesystem has duplicate UUID 7e86783e-dde7-4256-879e-46d4aa1884ae - can't mount
Aug 20 06:02:12 Tower unassigned.devices: Mount of 'sdc1' failed: 'mount: /mnt/disks/UNASSNDisk: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error. '
Aug 20 06:02:55 Tower emhttpd: spinning down /dev/sdc

Edited by DigitalDivide
Link to comment
11 minutes ago, DigitalDivide said:

I replaced an unnassigned disk that was going bad by buying a new drive which I used to replace an existing data drive in the array and then used that disk to replace the bad unassigned disk. However, it won't mount. Is it because I need to format it ...which I'd like to do but not sure how once it's all plugged in or is it because it recognizes it as a drive that was in the array? I'm not sure what to do at this point to mount it.

 

I see this in the disk log for the drive

Aug 20 06:02:12 Tower kernel: XFS (sdc1): Filesystem has duplicate UUID 7e86783e-dde7-4256-879e-46d4aa1884ae - can't mount
Aug 20 06:02:12 Tower unassigned.devices: Mount of 'sdc1' failed: 'mount: /mnt/disks/UNASSNDisk: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error. '
Aug 20 06:02:55 Tower emhttpd: spinning down /dev/sdc

Go to ud settings and change that drive uuid.  The duplicate is because it was previously in the array.

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.