dlandon

No.

How are you using the drive as a VM? If you're not using the extra partitions, delete them.

Why is this so much of a concern? Just ignore the partitions you aren't interested in.

Read this: Remove the partition with no or unsupported file system ('unassigned1') and then format the disk.

The Zoneminder docker is unable to update the OS. It might be a temporary issue with the update servers.

Auto mount applies to the disk and not individual partitions.

The best way to handle this is to create a User Script that will run this at Unraid startup.

Remove the spaces. "appdata,system,AppDataBackup,Downloads"

The time zone is set from your Unraid server when the docker is started. What time do you see that is off?

Movies-A has an unclean file system and is being mounted read only because of that. Jun 1 15:49:46 AnimNAS ntfs-3g[28329]: Mounted /dev/sdm2 (Read-Only, label "Movies-A", NTFS 3.1) Jun 1 15:49:46 AnimNAS ntfs-3g[28329]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,umask=000 Jun 1 15:49:46 AnimNAS ntfs-3g[28329]: Mount options: rw,nodiratime,nodev,nosuid,allow_other,nonempty,noatime,ro,default_permissions,fsname=/dev/sdm2,blkdev,blksize=4096 Jun 1 15:49:46 AnimNAS ntfs-3g[28329]: Global ownership and permissions enforced, configuration type 1 Jun 1 15:49:46 AnimNAS unassigned.devices: Mount error: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Falling back to read-only mount because the NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting.) You need to fix that before the file system will be mounted r/w.

Hibernated means that it was hibernated from a Windows computer and the file system is in a hibernated state. It doesn't mean the disk is hibernated in Unraid. UD logs to the system log. You probably can't unmount the drive because it is busy. You may have created some additional issues by messing around with the NTFS driver package. Don't do anything with the NTFS driver package. It is built into Unraid and UD mounts NTFS disks r/w except as I said in certain cases where it is not safe to mount it r/w. Your syslog will show the status of mounting the disk file system and why it is mounted read only. Start by posting your diagnostics so we can help you. Tools->DIagnostics. Don't do any other messing around until we can see where you are.

UD already does this. Take a look at the log. A disk with the NTFS file system will be mounted read only under certain conditions - like the disk is hibernated.

The size information showing as 0B is because it is taking too long and UD eventually gives up trying to determine the size so the UI is not totally frozen. It sounds like a network issue. It would help if you could post diagnostics for us to look at.

You could mount it manually.

UD doesn't mount a ufs file system.

I don't know enough about the crusader docker to be able to help. Hopefully someone else can chime in here and offer some assistance.

How are you trying to view the remote share?

The issue was related to how blank credentials were formed for the mount line. Originally the blank user and password were quoted with a '. That created errors when mounting. That bug was fixed, but there is nothing to fix this time because that bug was fixed and is not your issue this time. This was your error last time. It's not the same issue.

If memory issues still linger, go to a command line and type 'df' to see the file system usage. Post the results. That's the next thing to do if the memory issue is not solved. Disable all Dockers and re-enable them one at a time. A mis-configured Docker can consume a lot of memory in the ram file system.

I don't see the problem with the code and I can't reproduce the problem.

That was a fix for your issue last time, but your problem is different this time.

I don't have much experience with using a disk directly, but I suspect the format is not a vdisk file, but a NTFS file system and that's why it won't work with UD. As long as the VM works, you should be good to go. Now monitor and see if you have memory issues again. Only make one change at a time to see if you can find out what is causing the problem if it still exists.

Please follow my suggestions until you get stability. Cut down the memory on both your VMs to 4 to 6 GB. You can increase it later once you achieve stability. I think you are over committing memory. Assign only 4 VCPUs to the VM. You are way over committing CPUs and a Windows VM doesn't need that much. If you do really need more CPUs, you can add them later. Tips and Tweaks disk cache should be like this: It would be better to mount the disk in UD and then assign the vdisk to that.

You have some strange vdisk and CDROM mappings. Why is your primary vdisk mapping in the configuration twice? Why are you mapping the vdisk directly to a disk? Set it to cache disk or other disk in the array or Unassigned Disk device. Once the Windows 10 VM is installed, remove the CDROM mappings. The drivers are not needed any longer. This is more of what I would expect as a Windows VM mapping. Other suggestions: Make VM xml changes. You have some strange settings. Cut down the CPU usage to: 4/10 and 5/11 for Windows 10 and 2/8 and 3/9 for Ubuntu. Neither one should require that many CPUs. Change later if desired once system is stable. Cut down memory to 4 to 6 GB for Windows. Cut down Ubuntu memory to 4 to 6 GB. Adjust later once system is stable. I think you are over committing memory. Install the Tips and Tweaks plugin and adjust the disk caching as suggested.