dlandon

So the unassigned devices are staying straightened out now. The issue is that the parity disk spins up when an unassigned disk is installed?

I see two unassigned disks. sdb and sdi. I know UD has them right because I can see UD trying to auto mount both of them, but they are not set for auto mount. What does the dashboard show? What does UD show on the UD page?

Thank you. I'm out of ideas.

Can you post your diagnostics? We've added some additional information to the diagnostics that might help me track this down.

Post your diagnostics.

Thanks for the info in a PM. Now let's do a few more things. Go to your Settings->Management Access and show me how you have "Local TLD:" set. Also execute this command at the cli: arp -a DISKSTATION I think I might see something I can do.

I use the 'arp' command and it is known to have some issues - like hangs. Unfortunately, I think this is out of my control.

UD does that by pinging servers to see if the server supports the SMB port. Thanks to Windows and Linux samba changes for security, it has become more difficult to do named lookups unless you enable NetBIOS, which is now considered too insecure to use. Do you have NetBIOS enabled? Another thing I want you to look at is the 'Local TLD:' setting in the Settings->Management Access. Let me know what you have set.

I'd like to do a bit more research. Having UD cause oom issues is not a good thing. Even if the remote share won't work, UD should be robust enough to handle it. Post the output of this command: cat /etc/hosts This will expose some IP addresses. You can PM that to me and not post it on the forum.

I can't answer that. It's a Linux thing. I don't know enough about VMWare disks. The expert at disks is @JorgeB. Maybe he has a suggestion. I could add the mounting of VMWare disks in UD, but I would need a VMWare disk (I don't have one) and a week or so to implement.

There aren't any writes to the /mnt/remotes/ folder because the remote share has not even been mounted. What I suspect is going on is the ping status check to update the remote server online status. If you remember @Squid that's the routine you and I had to troubleshoot when your Windows computer would not mount a remote share. I'm not an expert at all the networking stuff, but I think that routine is stuck in a loop and kills avahi. Remove the share and add it using the IP address instead of the name 'DISKSTATION' and see if the same thing happens.

Windows deals with the VMWare tag on the disk and will mount them as NTFS disks. Linux doesn't recognize them as NTFS because of the VMWare tag. It takes a special Linux package to mount the VMFS disks. This has not been implemented into UD at this time.

What is the remote share you are trying to use? Show a screen shot of the UD page.

Linux sees those disks as VMWare disks. UD does not currently mount those kinds of disks. My suggestion is to put them back into the old server and do a UD remote share mount and transfer the data that way.

It appears that avahi-daemon did the oom: Mar 12 23:05:34 UNRAID-BLUE rc.docker: Nginx-Proxy-Manager-Official: started succesfully! Mar 12 23:06:59 UNRAID-BLUE kernel: avahi-daemon invoked oom-killer: gfp_mask=0x100dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO), order=0, oom_score_adj=0 Mar 12 23:06:59 UNRAID-BLUE kernel: CPU: 15 PID: 6129 Comm: avahi-daemon Tainted: P O 5.10.28-Unraid #1 Mar 12 23:06:59 UNRAID-BLUE kernel: Hardware name: Gigabyte Technology Co., Ltd. Z390 UD/Z390 UD, BIOS F10 11/05/2021 Mar 12 23:06:59 UNRAID-BLUE kernel: Call Trace: Mar 12 23:06:59 UNRAID-BLUE kernel: dump_stack+0x6b/0x83 Mar 12 23:06:59 UNRAID-BLUE kernel: dump_header+0x45/0x1e8 Mar 12 23:06:59 UNRAID-BLUE kernel: oom_kill_process+0x7b/0xf6 Mar 12 23:06:59 UNRAID-BLUE kernel: out_of_memory+0x3dd/0x410 Mar 12 23:06:59 UNRAID-BLUE kernel: __alloc_pages_slowpath.constprop.0+0x665/0x74c Mar 12 23:06:59 UNRAID-BLUE kernel: __alloc_pages_nodemask+0x1a1/0x1fc Mar 12 23:06:59 UNRAID-BLUE kernel: alloc_pages_vma+0x114/0x130 Mar 12 23:06:59 UNRAID-BLUE kernel: handle_mm_fault+0x9b6/0xec3 Mar 12 23:06:59 UNRAID-BLUE kernel: exc_page_fault+0x259/0x373 Mar 12 23:06:59 UNRAID-BLUE kernel: ? asm_exc_page_fault+0x8/0x30 Mar 12 23:06:59 UNRAID-BLUE kernel: asm_exc_page_fault+0x1e/0x30 Mar 12 23:06:59 UNRAID-BLUE kernel: RIP: 0033:0x1550e0e6798c UD Remote shares did not mount until some time after this: Mar 12 23:07:03 UNRAID-BLUE unassigned.devices: Mounting Remote Share '//DISKSTATION/movies'... Mar 12 23:07:03 UNRAID-BLUE unassigned.devices: Mount SMB share '//DISKSTATION/movies' using SMB default protocol. Mar 12 23:07:03 UNRAID-BLUE 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,credentials='/tmp/unassigned.devices/credentials_movies' '//DISKSTATION/movies' '/mnt/remotes/movies-ds' Mar 12 23:07:03 UNRAID-BLUE kernel: Key type cifs.idmap registered Mar 12 23:07:03 UNRAID-BLUE kernel: CIFS: Attempting to mount //DISKSTATION/movies Mar 12 23:07:03 UNRAID-BLUE kernel: CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount. Mar 12 23:07:09 UNRAID-BLUE kernel: CIFS: VFS: Error connecting to socket. Aborting operation. Mar 12 23:07:09 UNRAID-BLUE kernel: CIFS: VFS: cifs_mount failed w/return code = -113 and it failed with error connecting to socket. Not sure what this means: Mar 12 23:05:34 UNRAID-BLUE kernel: kmem.limit_in_bytes is deprecated and will be removed. Please report your usecase to [email protected] if you depend on this functionality. I would suggest removing all plugins and start with CA and bare UD. Then add others until you find the offending plugin. I have suspicions about the following: disklocation-master.plg gpustat.plg NerdPack.plg nvidia-driver.plg I'm not blaming any plugins, just eliminate them to start off.

You probably have network issues and UD commands are timing out because of it. Please post diagnostics.

Remove those plugins and install the UD Preclear that replaces the older preclear.

Click on the red X to delete the precler log. The 'Preclear' on the mount button will go away.

None of the settings should have been touched. Flash issue?

Look at Mac OS Interoperability in UD and the Settings->SMB.

I'm not seeing it. What is happening/not happening. I don't understand the screen shot.

You need to set the 'SMB Security' settings in UD Settings.

Let me know how it goes and we'll pick back up if you still have the issues.

Have you updated to RC3? If not then please do that and let's work on this again.

UD sets up several mount folders when it is installed. /mnt/disks/ for disk drives, /mnt/remotes/ for remote shares, and /mnt/rootshare/ for root shares, even if these features are not actively being used. These folders can contain many mount points. For example the /mnt/rootshare/ folder can contain a mount point for /mnt/user/, and /mnt/disks/ at the same time. Those folders are not mount points. What is your concern with this arrangement?