dlandon

Linux is not detecting any Unassigned Devices. Is the disk showing in your BIOS?

Update to the latest version of the recycle bin.

Try changing the filme share.

Edit the the duplicated share "ron" /flash/config.shares/ folder and change the duplicate to the next in the sequence for fsids. i.e. change ron to fsid 104. I don't know how you got duplicates. Can you take your flash drive to a PC and check the file system in case you have a flash issue? Edit: You'll have to reboot or stop and restart the array.

You can't control the fsid. Unraid takes care of it for you. Have you tried a reboot? Post the /etc/exports file content after a reboot. You may have run into a bug. I'll do some testing and see if there is a problem.

Put this in your /flash/config/go file or create a User Script to run when the array is first started: ulimit -Sn 40960 You can't edit the /etc/security/limits/conf file because it is not persistent on reboots. This command will apply the soft limit at the start of the array. The soft limit should apply to any non root users. Is there a way to apply the ulimit in the backup system script? That would apply the ulimit when it runs.

Yes for version 6.11. Updating the plugin should remove those entries though.

Post your diagnostics zip file.

The issue with all the log messages, is we made changes for 6.11 so we could remove the recycle bin entries in the smb-extra.conf file. The problem is the logging mechanism is different on 6.10 and below. The latest recycle bin version did not keep the settings for 6.10. They are now restored. Update to the latest version and this should be fixed.

Post diagnostics file.

and the messages stopped?

Did you run this command? /etc/rc.d/rc.rsyslogd restart

Reinstall the recycle bin plugin and show the output of: cat /etc/rsyslog.d/03-recycle-bin.conf Run this command to see if the log entries stop: /etc/rc.d/rc.rsyslogd restart

Check this guide on ulimit: https://phoenixnap.com/kb/ulimit-linux-command I think you may want: ulimit -Sn 40960 To set the soft limit. When you're at a root prompt, I believe the soft limit is the hard limit.

Looks like it might be the USB controller: Oct 24 14:32:20 Server kernel: usb 2-4: new SuperSpeed USB device number 4 using xhci_hcd Oct 24 14:32:20 Server kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.CR01._PLD], AE_NOT_FOUND (20220331/psargs-330) Oct 24 14:32:20 Server kernel: ACPI Error: Aborting method \_SB.UBTC.RUCC due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Oct 24 14:32:20 Server kernel: ACPI Error: Aborting method \_SB.PCI0.XHC.RHUB.SS04._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Oct 24 14:32:20 Server kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.CR01._PLD], AE_NOT_FOUND (20220331/psargs-330) Oct 24 14:32:20 Server kernel: ACPI Error: Aborting method \_SB.UBTC.RUCC due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Oct 24 14:32:20 Server kernel: ACPI Error: Aborting method \_SB.PCI0.XHC.RHUB.SS04._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Oct 24 14:32:20 Server kernel: usb-storage 2-4:1.0: USB Mass Storage device detected Oct 24 14:32:20 Server kernel: usb-storage 2-4:1.0: Quirks match for vid 174c pid 55aa: 400000 Oct 24 14:32:20 Server kernel: scsi host6: usb-storage 2-4:1.0 Oct 24 14:32:22 Server kernel: scsi 6:0:0:0: Direct-Access Space ke USB 3.0 Device 0 PQ: 0 ANSI: 6 Oct 24 14:32:22 Server kernel: sd 6:0:0:0: Attached scsi generic sg1 type 0 Oct 24 14:32:22 Server kernel: sd 6:0:0:0: [sdg] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) Oct 24 14:32:22 Server kernel: sd 6:0:0:0: [sdg] 4096-byte physical blocks Oct 24 14:32:22 Server kernel: sd 6:0:0:0: [sdg] Write Protect is off Oct 24 14:32:22 Server kernel: sd 6:0:0:0: [sdg] Mode Sense: 43 00 00 00 Oct 24 14:32:22 Server kernel: sd 6:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 24 14:32:22 Server kernel: sdg: sdg1 Oct 24 14:32:22 Server kernel: sd 6:0:0:0: [sdg] Attached SCSI disk Oct 24 14:32:23 Server unassigned.devices: Adding partition 'sdg1'... Oct 24 14:32:23 Server unassigned.devices: Mounting partition 'sdg1' at mountpoint '/mnt/disks/Camera'... Oct 24 14:32:23 Server unassigned.devices: Partition 'sdg1' is already mounted. Oct 24 14:32:23 Server unassigned.devices: Partition 'Z52BTLRX' cannot be mounted. Oct 24 14:32:24 Server emhttpd: read SMART /dev/sdg

Probably. UD thinks the disk was not unmounted correctly and then showed back up. Can you connect the disk using sata instead of USB? I'll take a look at your diagnostics.

The "Reboot" notation is when a disk is improperly unmounted. You are getting errors in your log related to the disk share: Oct 24 12:59:59 Server smbd[10708]: make_connection_snum: '/mnt/disks/Camera' does not exist or permission denied when connecting to [Camera] Error was Input/output error Oct 24 12:59:59 Server smbd[10708]: [2022/10/24 12:59:59.185551, 0] ../../source3/smbd/smb2_service.c:830(make_connection_snum) Oct 24 12:59:59 Server smbd[10708]: make_connection_snum: '/mnt/disks/Camera' does not exist or permission denied when connecting to [Camera] Error was Input/output error Oct 24 12:59:59 Server smbd[10708]: [2022/10/24 12:59:59.186321, 0] ../../source3/smbd/smb2_service.c:830(make_connection_snum) Try another USB port, or change the cable. Next time please attach the complete diagnostics file. A syslog only doesn't always provide enough information.

Post diagnostics.

Post diagnostics.

Post a diagnostics zip file.

Update the UD plugin to remove the "#unassigned_devices" entry in the smb-extra.conf file. Also update the Recycle Bin plugin to remove that entry from smb-extra.conf. As explained above, don't do any fruit settings in the smb-extra.conf file. Use the smb-fruit.conf file. Several users have reported the following in the smb-extra.conf file will stop these mesages: logging = 0

Comment out the lines in the smb-extra.conf and see if that helps. There have been some reports that the "veto files = /.*/.DS_Store/" is not working. Show the result of the command "ls -la /mnt".

Post the diagnostics file.

That's the hope.

Any script you want to use has to be in the /flash/config/plugins/unassigned.devices/ folder. Put your script there and then select the script from the drop down. This is done for security. You can't run a script from just anywhere. Click on the 'Help' to show the help text for the "User Script:" field. The "User Script:" is not an executed device script. Again, look at the Help text. What logs?