dlandon

Also give me the output of this command: cat /var/state/unassigned.devices/share_names.json

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.

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.

Post your diagnostics zip file.

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.

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

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.

I forgot to mention that there was a change in the iommu configuration in 6.10 that solved some issues with certain HP servers that might have affected the graphics card pass through for you.

You're posting the same issue in multiple places. Please post your issue in one place only. It makes it hard to get to the bottom of the problem if it is posted in multiple places. Stay with the post and respond to requests for more information until resolved. I understand that your issue is solved in Unraid 6.9, but shows up in 6.10. The major change from 6.9 to 6.10 is the Linux Kernel. This is probably where the problem lies. I'm not sure if it is an Unraid problem. I can appreciate your frustration with this issue., biut you also need to understand that Unraid can be installed on just about any hardware and it is an impossible task to test all combinations of hardware. This issue did not come up with any public or internal beta and RC testing. My suggestion for the moment is to stay on 6.9 until this can be researched and a resoluton found. We will do what we can to find the source of the 43 error. It may take a little time because we will probbly have to reproduce the error before we can track down the source of the problem and provide a fix. I'm going to report this issue to the LT team so other developers are made aware of the issue.

Post the diagnostics zip file, and a screen shot of the UD Device.

Clicking the device designation brings up the SMART page. Then make a change to any parameter on the SMART page You can change and then change it back. The Apply button will be active, then click it. This will set the monitoring to the serial number. You don't change the devX here.

Yes.

If you're going to put it into the array, don't clear the disk. Unraid will format it. Preclearing creates a partition, but does not create a file system. That's why it is not mountable.

Click on the red X next to the disk serial to clear the disk and then format the disk.

Does the tabbed mode show disk info?

Click on the 'Dev 2' or whatever the designation is:: This is where to make a change:

Do any of the other tabs show anything? Like Dashboard?

Click on the device designation in UD for the device in question and make a change to the SMART settings and then click 'Apply'. This will set up disk monitoring by serial number and not devX. I don't know how hwmon works so I don't know if it will work, but I suspect it will.

UD copies the script file to /tmp/, sets the execute permission, and executes it from there.

Post diagnostics and give a screen shot of the disk setting page where you are setting up the script.

This is telling you there are issues. Read the second paragraph.

You set user access in UD Settings. Set user access by user.

It looks like you haven't enbled SMB security in UD Settings.

Are you talking about on Unraid shares? I don't think there is a global setting that applies to all on Unraid. Can you not set the rule to apply to all ip addresses by setting the "*" instead of individual ip addresses?

Check your NFS rules on the client. They affect permissions. This is what UD uses when mounting remote NFS shares: *(sec=sys,rw,insecure,anongid=100,anonuid=99,no_root_squash)