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

Arubial · June 16, 2022

Since upgrading to 6.10.3, I am unable to see my SMB shares with UD. I have rebooted the server and rebooted my Windows clients, but the share doesn't show up when I browse to my Unraid server. I can see the share if I SSH into the Unraid server, and the Docker containers can all see the share, but I can't access it via SMB. Diagnostics attached (the share is called "SSD")

jarvis-diagnostics-20220616-0934.zip

monroe · June 16, 2022

Mine is doing the same as your's , checked every share setting etc... rebootetd a few times ,,, but no luck

dlandon · June 16, 2022

5 hours ago, Arubial said:

Since upgrading to 6.10.3, I am unable to see my SMB shares with UD.

You have SMB enabled, which is necessary. The other pieces are the UD Settings for SMB:

Make sure you don't have 'SMB Security?' set to hidden. If you do, you can't browse.

The last thing is to enable 'Share' for the device:

Because of the way Unraid handles shares, it can take up tp several minutes for the share to actually show up in the Network Neighborhood.

Arubial · June 16, 2022

10 minutes ago, dlandon said:

You have SMB enabled, which is necessary. The other pieces are the UD Settings for SMB:

Make sure you don't have 'SMB Security?' set to hidden. If you do, you can't browse.

The last thing is to enable 'Share' for the device:

I checked my settings, and they haven't changed. SMB is enabled, and I have it set to public like I always have. I don't really need security on this particular share. I also made sure the share option is enabled in the UD settings. What's going on?

dlandon · June 16, 2022

16 minutes ago, Arubial said:

SMB is enabled, and I have it set to public like I always have.

What do you mean Public? You mean setting 'SMB Security?' to 'No'?

monroe · June 16, 2022

Prior I do not rememeber having to set the SMB Security to "Yes" and then specifing read/write for the users, but it has been a while ago that I setup the SMB sharing so it could have just got reset with the update to unraid OS 6.10.3. Thanks for quick responses

dlandon · June 16, 2022

15 hours ago, monroe said:

Prior I do not rememeber having to set the SMB Security to "Yes" and then specifing read/write for the users, but it has been a while ago that I setup the SMB sharing so it could have just got reset with the update to unraid OS 6.10.3. Thanks for quick responses

It was a recent change in UD, not in Unraid. The issue is a recent change I made that disabled SMB when the security setting was 'No'. Previously, the 'No' setting was SMB Public sharing. This was not appropriate to set Public sharing with security set to 'No'. What I will do is add a 'Public' setting. So you can set the security to 'No', 'Public', 'Yes', and 'Yes (hidden)'.

This change will be in the next UD release.

monroe · June 17, 2022

Thank's for the reply, your proposed solution sounds really good.

zwar77 · June 17, 2022

Hello,

I am hoping someone can help me out. I just am getting started with Unraid and want to move over my data from my Windows NTFS drives to Unraid. I downloaded unassigned devices so I could mount the NTFS drives and begin copying over their files to my unraid array. However I am having an issue where 6 of my NTFS drives (all above 12TB) are not mountable and appear to not mount at all. In unassigned devices the mount button is completely grey. When I go to syslog I am getting errors about the disk not being able to mount due to

Mount of 'sdf3' failed: 'mount: /mnt/disks/21274H802348-part3: unknown filesystem type 'LVM2_member'. '

I did read through the first two posts to check if my issue was answered and found a a tidbit on the second post of this thread talking about the mount being grayed out, but that does not appear to be applicable as it deals with an not symbol / array issue and my button does not look like that. I also found a post on reddit where a user had this issue also, however they had put on pass through accidentally. I did test out enabling and then disabling pass through on one drive to see if that had any effect and it did not. I am attaching my diagnostic file if someone is able to assist.

If I am not able to mount the drives in unassigned devices, does anyone have any advice on how I can get the data off to Unraid?

Thank you for your time!

unraid-diagnostics-20220617-0456.zip

JorgeB · June 17, 2022

15 minutes ago, zwar77 said:

If I am not able to mount the drives in unassigned devices, does anyone have any advice on how I can get the data off to Unraid?

Please post the output of:

blkid

Arubial · June 17, 2022

14 hours ago, dlandon said:

It was a recent change in UD, not in Unraid. The issue is a recent change I made that disabled SMB when the security setting was 'No'. Previously, the 'No' setting was SMB Public sharing. This was not appropriate to set Public sharing with security set to 'No'. What I will do is add a 'Public' setting. So you can set the security to 'No', 'Public', 'Yes', and 'Yes (hidden)'.

This change will be in the next UD reslease.

Thanks, I'm good to go now

zwar77 · June 17, 2022

7 hours ago, JorgeB said:
Please post the output of:
blkid

Here is the output!

Quote

root@Unraid:~# blkid
/dev/sdb1: LABEL="backup" BLOCK_SIZE="512" UUID="025632645632589D" TYPE="ntfs" PARTLABEL="easystore" PARTUUID="82864739-67c3-411d-91d2-9923ba1d3f24"
/dev/sdc1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272B-4CE1" BLOCK_SIZE="512" TYPE="vfat"
/dev/sda1: LABEL="Archive1 - Backup" BLOCK_SIZE="512" UUID="3614906514902A3F" TYPE="ntfs" PARTUUID="6ed2dd88-01"
/dev/loop1: TYPE="squashfs"
/dev/mapper/pve-root: UUID="32785e2a-2652-4e1b-9edb-4107a1cb2650" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdf3: UUID="bVEEYf-MmrG-iADj-BQbh-umZG-c6Fg-efGWI1" TYPE="LVM2_member" PARTUUID="2aba9529-fac5-4f14-a9ef-d39228d98a64"
/dev/sdf2: UUID="4F5D-61D5" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="99b4d5ca-4b31-4e7b-995b-ebb1e7c527a1"
/dev/loop0: TYPE="squashfs"
/dev/mapper/pve-swap: UUID="f26b9952-afd2-4959-a69c-e84adb19553d" TYPE="swap"
/dev/sdj1: UUID="ab2df9f5-95e5-4971-8ae6-ead5bcfb5938" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="ed6dc693-b376-4214-9b27-2764b121a295"
/dev/sdf1: PARTUUID="fa614fe7-267a-4d8d-b901-affca6f71e58"
/dev/sdk3: PARTLABEL="LDM data partition" PARTUUID="9b1c1bb1-4f4b-11eb-9f2b-1078d2cc7d10"
/dev/sdk1: PARTLABEL="LDM metadata partition" PARTUUID="9b1c1bad-4f4b-11eb-9f2b-1078d2cc7d10"
/dev/sdk2: PARTLABEL="Microsoft reserved partition" PARTUUID="9b1c1bae-4f4b-11eb-9f2b-1078d2cc7d10"
/dev/sdi3: PARTLABEL="LDM data partition" PARTUUID="9b1c1baa-4f4b-11eb-9f2b-1078d2cc7d10"
/dev/sdi1: PARTLABEL="LDM metadata partition" PARTUUID="9b1c1ba6-4f4b-11eb-9f2b-1078d2cc7d10"
/dev/sdi2: PARTLABEL="Microsoft reserved partition" PARTUUID="9b1c1ba7-4f4b-11eb-9f2b-1078d2cc7d10"
/dev/loop2: UUID="d9ff8a7a-3e65-44e8-a059-53de61902f0c" UUID_SUB="b809f3ce-e295-4670-9a68-8fea819ddac5" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sdg3: PARTLABEL="LDM data partition" PARTUUID="a6a0e03f-adee-11ea-85a2-1078d2cc7d10"
/dev/sdg1: PARTLABEL="LDM metadata partition" PARTUUID="a6a0e03b-adee-11ea-85a2-1078d2cc7d10"
/dev/sdg2: PARTLABEL="Microsoft reserved partition" PARTUUID="a6a0e03c-adee-11ea-85a2-1078d2cc7d10"
/dev/sde2: PARTLABEL="Microsoft reserved partition" PARTUUID="a6a0e043-adee-11ea-85a2-1078d2cc7d10"
/dev/sde3: PARTLABEL="LDM data partition" PARTUUID="a6a0e046-adee-11ea-85a2-1078d2cc7d10"
/dev/sde1: PARTLABEL="LDM metadata partition" PARTUUID="a6a0e042-adee-11ea-85a2-1078d2cc7d10"
/dev/sdl3: PARTLABEL="LDM data partition" PARTUUID="9c66e569-41fb-11ec-ada2-005056c00008"
/dev/sdl1: PARTLABEL="LDM metadata partition" PARTUUID="9c66e565-41fb-11ec-ada2-005056c00008"
/dev/sdl2: PARTLABEL="Microsoft reserved partition" PARTUUID="9c66e566-41fb-11ec-ada2-005056c00008"
/dev/md1: UUID="ab2df9f5-95e5-4971-8ae6-ead5bcfb5938" BLOCK_SIZE="512" TYPE="xfs"
/dev/loop3: UUID="1d81be51-41b4-4d91-862b-b504b20570ce" UUID_SUB="3d4659df-0ce6-4fb4-a41c-64a039b1904c" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sdh3: PARTLABEL="LDM data partition" PARTUUID="9c66e562-41fb-11ec-ada2-005056c00008"
/dev/sdh1: PARTLABEL="LDM metadata partition" PARTUUID="9c66e55f-41fb-11ec-ada2-005056c00008"
/dev/sdh2: PARTLABEL="Microsoft reserved partition" PARTUUID="a060f8e6-2edb-4e61-a57e-18cbf10dda22"

trurl · June 17, 2022

7 hours ago, zwar77 said:

how I can get the data off to Unraid?

Put them back in the computer they were in and copy over network

JorgeB · June 17, 2022

22 minutes ago, zwar77 said:

/dev/sdk3: PARTLABEL="LDM data partition" PARTUUID="9b1c1bb1-4f4b-11eb-9f2b-1078d2cc7d10"
/dev/sdk1: PARTLABEL="LDM metadata partition" PARTUUID="9b1c1bad-4f4b-11eb-9f2b-1078d2cc7d10"
/dev/sdk2: PARTLABEL="Microsoft reserved partition"

Disks are not showing as NTFS, that's why UD doesn't recognize them, but don't ask me what kind of partitions are those, were the disks basic or dynamic?

zwar77 · June 17, 2022

1 hour ago, JorgeB said:

Disks are not showing as NTFS, that's why UD doesn't recognize them, but don't ask me what kind of partitions are those, were the disks basic or dynamic?

They are dynamic disks from Windows. The disks were used to mirror/backup the drives within Windows disk manager. I searched google but found nothing for how to mount these / convert them from LDM to NTFS though. Now I am in a pickle

Is there any way to transfer the data locally? I have Windows on that machine, but have no way to boot unraid and windows at the same time to transfer the files over the network. All my drives are in that machine locally. Any help is appreciated.

trurl · June 17, 2022

2 minutes ago, zwar77 said:

All my drives are in that machine locally

Do you not have backups? Or any capacity to make backups? Parity is not a substitute, and neither is mirrors.

zwar77 · June 17, 2022

I do luckily have backups. I am going to format my current (LDM) disks and then transfer over the backup data, then hopefully unassigned devices will read the files (since the disk should now be all NTFS data and not LDM). This way my backup data will remain read only/untouched and I can work with the fresh NTFS drive data. I have my fingers crossed and it seems logically correct. To move the data back will take some time, but I will post back here when done (or edit this post), so anyone having the issue in the future knows a potential fix.

Thank you for your assistance everyone!

gleech · June 18, 2022

I need help. I updated Unraid to 6.10.3 from 6.9.2. I have 7 disks in UD and I set it to auto-mount. Right after the update, only one disk was mounted, I tried to click the MOUNT button, it just spins and goes back to MOUNT. I tried to reboot and disable auto-mount, and still the same. Any idea how to resolve my issues. Thank you.

skylake · June 18, 2022

I updated my Unraid OS to 6.10.3 from 6.9.2 but I am unable to mount a smb share. It was mounting the share just fine on 6.9.2 but not on the new OS 6.10.3. I double checked the settings and everything is the same. Is there anything I can check on my end to help solve this issue? Thank you.

826231899_2022-06-17210938.png.daef8dc7dde4f3766e64bc063370353d.png

tower-diagnostics-20220617-2107.zip

dlandon · June 18, 2022

7 hours ago, gleech said:

I need help. I updated Unraid to 6.10.3 from 6.9.2. I have 7 disks in UD and I set it to auto-mount. Right after the update, only one disk was mounted, I tried to click the MOUNT button, it just spins and goes back to MOUNT. I tried to reboot and disable auto-mount, and still the same. Any idea how to resolve my issues. Thank you.

Post your diagnostics zip file.

dlandon · June 18, 2022

7 hours ago, skylake said:

I updated my Unraid OS to 6.10.3 from 6.9.2 but I am unable to mount a smb share. It was mounting the share just fine on 6.9.2 but not on the new OS 6.10.3. I double checked the settings and everything is the same. Is there anything I can check on my end to help solve this issue? Thank you.

tower-diagnostics-20220617-2107.zip 120.42 kB · 0 downloads

The remote mount is failing when trying to use SMB 2.0:

Jun 17 21:04:01 Tower unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=2.0,credentials='/tmp/unassigned.devices/credentials_memorycard' '//EPSON3640/memorycard' '/mnt/remotes/EPSON3640_memorycard'
Jun 17 21:04:01 Tower kernel: CIFS: Attempting to mount \\EPSON3640\memorycard
Jun 17 21:04:01 Tower kernel: CIFS: Status code returned 0xc000000d STATUS_INVALID_PARAMETER

When this fails, UD will attempt to use SMB v1.0 to mount the remote share, which is what you have shown in the log snippet. I'm not sure what the STATUS_INVALID_PARAMETER is referring to, but it may be your credentials on the remote server. I would change the credentials on the remote server and then re-do the UD remote share to match. Try to not use any special characters.

gleech · June 18, 2022

11 hours ago, gleech said:

I need help. I updated Unraid to 6.10.3 from 6.9.2. I have 7 disks in UD and I set it to auto-mount. Right after the update, only one disk was mounted, I tried to click the MOUNT button, it just spins and goes back to MOUNT. I tried to reboot and disable auto-mount, and still the same. Any idea how to resolve my issues. Thank you.

3 hours ago, dlandon said:

Post your diagnostics zip file.

Thank you. Here is my diagnostics zip file.

tower-diagnostics-20220618-0818.zip

dlandon · June 18, 2022

1 hour ago, gleech said:

Thank you. Here is my diagnostics zip file.

tower-diagnostics-20220618-0818.zip 156.74 kB · 1 download

UD is detecting duplicate mount point/share names:

Jun 17 18:50:02 Tower unassigned.devices: Error: Device '/dev/sdg1' mount point 'nftc' - name is reserved, used in the array or by an unassigned device.
Jun 17 18:50:02 Tower unassigned.devices: Disk with serial 'WDC_WD120EMFZ-11A6JA0_Z2K5V93T', mountpoint 'nftc' cannot be mounted.
Jun 17 18:50:02 Tower unassigned.devices: Error: Device '/dev/sdh1' mount point 'nftf' - name is reserved, used in the array or by an unassigned device.
Jun 17 18:50:02 Tower unassigned.devices: Disk with serial 'WDC_WD140EDFZ-11A0VA0_9KHGR42M', mountpoint 'nftf' cannot be mounted.
Jun 17 18:50:02 Tower unassigned.devices: Error: Device '/dev/sdi1' mount point 'nfte' - name is reserved, used in the array or by an unassigned device.
Jun 17 18:50:02 Tower unassigned.devices: Disk with serial 'WDC_WD140EDFZ-11A0VA0_9LGG46BG', mountpoint 'nfte' cannot be mounted.
Jun 17 18:50:02 Tower unassigned.devices: Error: Device '/dev/sdj1' mount point 'nftd' - name is reserved, used in the array or by an unassigned device.
Jun 17 18:50:02 Tower unassigned.devices: Disk with serial 'WDC_WD120EMFZ-11A6JA0_QGGL6E3T', mountpoint 'nftd' cannot be mounted.
Jun 17 18:50:02 Tower unassigned.devices: Error: Device '/dev/sdk1' mount point 'nftg' - name is reserved, used in the array or by an unassigned device.
Jun 17 18:50:02 Tower unassigned.devices: Disk with serial 'WDC_WD80EZAZ-11TDBA0_1SGV50EZ', mountpoint 'nftg' cannot be mounted.

This looks suspicious to me because the names are all 'nftX'. I think UD might think any name with 'nft' is considered a duplicate. Post the output of:

cat /var/state/unassigned.devices/disk_names.json

I'll do a little troubleshooting.

dlandon · June 18, 2022

1 hour ago, gleech said:

Thank you. Here is my diagnostics zip file.

tower-diagnostics-20220618-0818.zip 156.74 kB · 2 downloads

Also give me the output of this command:

cat /var/state/unassigned.devices/share_names.json

gleech · June 18, 2022

57 minutes ago, dlandon said:
cat /var/state/unassigned.devices/disk_names.json

root@Tower:~# cat /var/state/unassigned.devices/disk_names.json
{
    "sdj": "dev1",
    "sdk": "dev2",
    "sdh": "dev3",
    "sdg": "dev4",
    "sdb": "dev5",
    "sdf": "dev6",
    "sdi": "dev7"
}root@Tower:~#

51 minutes ago, dlandon said:
cat /var/state/unassigned.devices/share_names.json

root@Tower:~# cat /var/state/unassigned.devices/share_names.json
{
    "sdj1": "nftd",
    "sdk1": "nftg",
    "sdh1": "nftf",
    "sdg1": "nftc",
    "sdb1": "nftb",
    "sdf1": "cctv",
    "sdi1": "nfte"
}root@Tower:~#

Thank you for the help @dlandon.

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

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

dlandon

dlandon

dlandon

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation