dlandon

I just found this in your latest syslog. Dec 26 12:51:50 TNAS kernel: r8169 0000:08:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] Dec 26 12:51:50 TNAS kernel: r8169 0000:09:00.0 eth1: jumbo features [frames: 9194 bytes, tx checksumming: ko] There are several issues here. First the Realtek NICs are notorious for having issues with Linux because the drivers are not well maintained, and second Jumbo Frames are not recommended because it requires a lot of network configuration to get it right and honestly it is not worth the issues caused by misconfiguring Jumnbo Frames. What is confusing is that eth0 is showing in ifconfig with an mtu=1500: eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether 38:d5:47:78:ac:53 txqueuelen 1000 (Ethernet) RX packets 9658345 bytes 13781359482 (12.8 GiB) RX errors 0 dropped 347 overruns 0 frame 0 TX packets 1068484 bytes 413838386 (394.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xfe400000-fe41ffff Please check your configuration and verify that Jumbo Frames are not being used. This can cause a lot of problems with NFS and SMB shares.

Do the following: Upgrade to 7.0.0-rc2. This is the best version to use with NFS issues addressed. Set the shareNOFILE="655360". A much larger number. Do not use the sript mentioned above. Be sure to stop/start or reboot the server to get the setting to take effect.

It looks like one or more of your disks have a problem: Dec 25 18:15:02 Saturn kernel: sd 1:0:1:0: Power-on or device reset occurred Dec 25 18:15:05 Saturn emhttpd: device /dev/sdw problem getting id Dec 25 18:16:14 Saturn kernel: sd 10:0:7:0: device_block, handle(0x0010) Dec 25 18:16:16 Saturn kernel: sd 10:0:7:0: device_unblock and setting to running, handle(0x0010) Dec 25 18:16:16 Saturn kernel: sd 10:0:7:0: [sdw] Synchronizing SCSI cache Dec 25 18:16:16 Saturn kernel: sd 10:0:7:0: [sdw] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Dec 25 18:16:16 Saturn kernel: mpt3sas_cm1: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221103000000) Dec 25 18:16:16 Saturn kernel: mpt3sas_cm1: removing handle(0x0010), sas_addr(0x4433221103000000) Dec 25 18:16:16 Saturn kernel: mpt3sas_cm1: enclosure logical id(0x56c92bf0004cc904), slot(1) Dec 25 18:16:16 Saturn kernel: mpt3sas_cm1: enclosure level(0x0000), connector name( )

Finish your array rebuild and then come back here for more debugging.

Unraid 6.12.9 and beyond all have NFS issues. We believe we have addressed the last of the NFS issues with 7.0.0-rc2. All Unraid versions from 6.12.9 to 6.12.14 will have one issue or another with NFS. Either stay on 6.12.8, or upgrade to 7.0.0-rc2

No.

Share it in Windows and then mount it as a remote mount in UD. You will then have access to the disk in Unraid.

It looks like the disk is formatted with a file system without a partition. UD will only mount a disk that has a file system on a partition. Can you move the drive to a system that can mount it? If you can, you can then mount it as a remote mount in UD and deal with it that way.

Try this: Click on 'Default' on the device settings page. Replace the default script section when the disk mounts with the desired script, or reference the desired script in the section that executes when the device is mounted. Or, place your desired script at '/boot/config/plugins/unassigned.devices/' and choose it from the dropdown. '/boot/' is the Linux reference, '/flash/' is the SMB reference. Click 'Save'. The only thing you can change in the 'Device Script:' field is the file name. You can't change the path. I would just use the default file name. You can run a script at another location by referencing it in the UD script, but UD wants all device scripts at '/boot/config/plugins/unassigned.devices/'. Any other path will be rejected.

Unraid will attempt to spin down a disk if it has a partition. If there is no partition, it will not attempt to spin down the disk. Once a disk is precelared, the preclear signature and a blank partition are created on the disk. Unraid will attempt to spin down the disk during post read. As you noted, the disk will spin back up. The reason this happens is Unraid is detecting file reads and writes to determine if a disk should be spun down and because there is no file system, there will not be any file reads and writes. The spin downs can be ignored. I did release a new version of UD Preclear today to address some nginx issues I saw in your log.

I'm really confused here. You said: and the same day you said: How can that be? And stop using the script. Make this change as suggested: We need to have answers that we can implement in Unraid. The script is not the answer to address this issue.

Post Unraid diagnostics and UD disgnostics,. Get UD diagnostics by entering 'ud_diagnostics" on a command line, then post the /flash/logs/ud_diagnostics.zip file here. Also, go to the UD Settings and click on the "Remote Servers" tab and enter the server name or IP address and then the 'Test' button and post the output here.

This will be added to the next release of the AD Extras plugin. Please follow this post for updates:

I am working on an upgrade to this plugin: Additional settings for Samba related to AD permissions. Backup and restoration of the database so permissions will remain persistent on a reboot. Set initial share and disk permissons specifically for AD. Only 'tdb' will be available as a backend database. The idea here is to get AD working properly and then incorporate these changes into Unraid. Keep in mind this is beta/test software so be prepared to deal with issues and provide feedback so we can get any kinks worked out. The one thing that can't be done right now is keeping the vfs object acl_xattr on shares when a share change is made. You can fix that by clicking on the 'Clear Cache' or 'Default' buttons or make a change on the page and click 'Apply' on the AD Extras page. That will re-apply the 'vfs object = acl_xattr' back to all the shares. When the changes are made in Unraid, this will no longer be an issue. I do not have a Windows Server and can only do limited testing. I rely on AI to give me direction. I will need feedback from the community to verify the changes.

The UI is at IP:9000. 9000 is a common docker container port so check for conflicts.

Post diagnostics.

What browser do you use?

I see an issue and will update UD Preclear after my testing. For now it is fairly harmless.

What version of Unraid are you using? This has been fixed since Unraid 6.12.5. If you are using a later version of Unraid, please post the full diagnostics.

Where are you trying to use special characters?

Does the log show the: [Dec19 21:13] receive_cb_reply: Got unrecognized reply: calldir 0x1 xpt_bc_xprt 00000000c25205b7 xid 783fc85a messages. This is on 7.0.0 rc2?

If you click on the "Clear Cache" it will clear the cache and restart Samba for you. Let me see what I can do.

I thought you were running 7.0.0-rc2? Please run rc2 with the addition to the share.cfg file. You can edit this file, update to rc2, then reboot and it will take effect.

Post diagnostics when the array won't stop.

You need to post on the LMS Forum as this is a coere LMS issue.