dlandon

wsdd is reatarted when samba is restarted by the recycle bin. It is not the recycle bin creating those log entries.

The recycle bin restarts samba. Those are from wsdd restarting.

Thanks. Still trying to find all those.

Look at the help on the UD page. It will explain how to mount and unmount disks.

I agree. Using /mnt/ and having VMs or Docker Containers misconfigured can cause some serious issues. UD sets write limits of 1MB on the /mnt/disks/, /mnt/remotes/, and /mnt/rootshare/ to keep misconfigured VMs and Docker Containers from filling the tmpfs and crashing Unraid. Install UD and ignore it. You don't have to use any of it's features. The only thing is the ZFS mounts have to happen after UD has installed.

It's very hard to review your log when it is clogged with these messages: Mar 18 12:56:15 Bigboii kernel: mce: [Hardware Error]: Machine check events logged Mar 18 12:56:15 Bigboii kernel: [Hardware Error]: Corrected error, no action required. Mar 18 12:56:15 Bigboii kernel: [Hardware Error]: CPU:0 (17:31:0) MC18_STATUS[Over|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0xdc2040000000011b Mar 18 12:56:15 Bigboii kernel: [Hardware Error]: Error Addr: 0x0000000057ffdd40 Mar 18 12:56:15 Bigboii kernel: [Hardware Error]: IPID: 0x0000009600150f00, Syndrome: 0x149901000a800500 Mar 18 12:56:15 Bigboii kernel: [Hardware Error]: Unified Memory Controller Ext. Error Code: 0, DRAM ECC error. Mar 18 12:56:15 Bigboii kernel: EDAC MC0: 1 CE on mc#0csrow#0channel#1 (csrow:0 channel:1 page:0x1afff7 offset:0x540 grain:64 syndrome:0x100) Mar 18 12:56:15 Bigboii kernel: [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD Mar 18 13:01:43 Bigboii kernel: mce: [Hardware Error]: Machine check events logged Mar 18 13:01:43 Bigboii kernel: [Hardware Error]: Corrected error, no action required. Mar 18 13:01:43 Bigboii kernel: [Hardware Error]: CPU:0 (17:31:0) MC18_STATUS[Over|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0xdc2040000000011b Mar 18 13:01:43 Bigboii kernel: [Hardware Error]: Error Addr: 0x0000000057ddb800 Mar 18 13:01:43 Bigboii kernel: [Hardware Error]: IPID: 0x0000009600150f00, Syndrome: 0x149901000a800500 Mar 18 13:01:43 Bigboii kernel: [Hardware Error]: Unified Memory Controller Ext. Error Code: 0, DRAM ECC error. Mar 18 13:01:43 Bigboii kernel: EDAC MC0: 1 CE on mc#0csrow#0channel#1 (csrow:0 channel:1 page:0x1af76e offset:0x100 grain:64 syndrome:0x100) Mar 18 13:01:43 Bigboii kernel: [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD

Post your diagnostics.

What's dirty about it? You can ignore the warning about rebooting, but the reason for that notice is to apply the write protection on the /mnt/disks/ that keeps misconfigured VMs and Docker Containers from writing into /mnt/disks/ from crashing Unraid.

Are you browsing with a Windows or Mac computer?

What are your UD security settings?

What version of Unraid?

No. It is available for 6.9.2.

Yes, that would help, but my understanding is they are auto mounted and I don't know how or when. This discussion should probably move the the ZFS support forum.

Please don't recommend using the cli. It is too prone to mistakes and is not a good idea. Install UD+ and then you will be given the opportunity to clear the disks. A red X will appear next to the serial number you can use to clear the disk. Note: Enable destructive mode in UD settings.

It's the boot up sequence that is the issue. The UD plugin has to be installed before the zpool is mounted.

Mount the ZFS disk after UD has installed.

Delete the plugin file at /flash/config/plugins/unassigned.devices.plg. It will not install the next boot.

It sounds as if there is a Java script error in UD. Remove UD and boot normally and see if everything is OK. Install UD and if the problem persists, hold ctrl, shift, and J at the same time. Let me know if you see any Java errors.

Does the "Unassigned Devices" tab show?

UD creates three folders at /mnt/ for its mounts. They are /mnt/disks/, /mnt/remotes/, and /mnt/rootshare/. When UD is installed, it adds a protection mount to each of those folders that prevents adding files and folders to those folders. This is to prevent the /tmp file system from filling up from misconfigured dockers and VMs and crashing Unraid. If one of those folders has mounts when this protection is added (this can happen when UD is upgraded), you will be asked with the banner you are seeing to reboot so UD can apply the protection mounts. It appears that something other than UD is adding a mount point to one of those folders. Check your ZFS configuration.

Stop your preclear, update UD Preclear, then resume the preclear. The log messages should stop.

Right now the script saves a resume status file on the flash drive every two minutes. This is too much writing to the flash drive. I'm rewriting the preclear script so the resume status is only saved when the script is paused or stopped. This will prevent the log messages while the preclear script is running. They may still show up if the flash drive has an issue when the resume status file is written.

Looks to be an issue with your flash drive.

Thank you. Unraid is in fact adding the parity disk to the unassigned disks, I'll report this and see if we can get a resolution.