dlandon

Post diagnostics.

With 6.9.1 I am struggling with the font size in a terminal window being very small. How can I adjust the terminal to a larger font size? I'm using Brave browser and if I zoom in on the terminal, it zooms all my browser pages.

Fixed in the next release of UD.

Go to a command line and post the contents of this file '/var/state/unassigned.devices/unassigned.devices.ini'

Passed Through means that the Docker is taking control of the disk directly and UD should not mount it. That's why the 'Mount' button was grayed out. If the Docker mounts the disk and UD mounts it also, you will get a corrupted file system, The way you were referencing the disk in your Docker assumed that UD mounted it. When the disk is Passed Through to the Docker, you deal with it differently in the Docker. Anyway, glad you got it sorted out.

No. Unraid doesn't have built in partition management tools like windows. You'll need to copy the data from the two partitions, remove all partitions, format the drive, then copy all back.

Nvme drives can spike to a high temperature under a heavy load and Unraid doesn't update the displayed temperature very often. In between the display refreshes, the temperature is probably spiking and you aren't seeing it, but it is going over the threshold. I have mine set to 65C.

Yea, I got busted by the permissions cop too.

Post diagnostics.

How about you update UD. The version you have installed is almost a year old. Before asking for help with a plugin, be sure you have the latest version installed.

I don't believe that your Host Path is correct. Shouldn't it be /mnt/disks/UNASSIGNED to access the UD disk?

The disk is not mounted. Because the mount points are in ram and incorrect mappings can cause ram to fill, there is a protection on the mount point /mnt/disks and it is limited to 1MB. You are not really seeing the UD disk you think you are, You need to find out why the disks aren't mounted and get them mounted.

Zoneminder with ES is painful no matter the implementation. ES uses AI and GPU hardware to accelerate the AI. This is not easy stuff, and ES has way too many options. It's not any more difficult in a docker, in fact it is probably easier for the user because everything is pre-packaged. It's only a matter of the user configuring their particular setup.

VFAT is not a good choice. I would reformat the disk.

That disk has errors: Mar 10 09:07:57 unRAID unassigned.devices: Mount drive command: /sbin/mount -t vfat -o rw,auto,async,noatime,nodiratime,nodev,nosuid,iocharset=utf8,umask=000 '/dev/sdc1' '/mnt/disks/ST1000DM003-1CH162_S1DETV80-part1' Mar 10 09:07:57 unRAID kernel: FAT-fs (sdc1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Mar 10 09:07:57 unRAID unassigned.devices: Successfully mounted '/dev/sdc1' on '/mnt/disks/ST1000DM003-1CH162_S1DETV80-part1'. Mar 10 09:07:57 unRAID unassigned.devices: Adding disk '/dev/sdc2'... Mar 10 09:07:57 unRAID unassigned.devices: Mount drive command: /sbin/mount -t ext4 -o rw,auto,noatime,nodiratime,async,nodev,nosuid '/dev/sdc2' '/mnt/disks/ST1000DM003-1CH162_S1DETV80-part2' Mar 10 09:07:58 unRAID kernel: EXT4-fs (sdc2): warning: mounting fs with errors, running e2fsck is recommended Click on the check mark when the disk is unmounted and UD will check the disk and fix the error. Why are you using a VFAT file system for a VM? It would be better to use BTRFS, or XFS.

It's very difficult to help you with this limited information. Please post diagnostics.

Turn off the docker and see if it will spin down.

Are you using cache dirs? If so, remove it and see if it fixes your issues.

I think the configuration file may be corrupted. Can you remove this drive and then remove the disk from the Historical settings? That should clear the settings and start over. No.

Read the message at the top about using cache dirs.

If this is the disk, it is not marked as auto mount: Mar 7 12:09:31 Kuroko unassigned.devices: Mounting 'Auto Mount' Devices... Mar 7 12:09:31 Kuroko unassigned.devices: Disk with serial 'WDC_WD30EFRX-68EUZN0_WD-WMC4N2434274', mountpoint 'temp' is not set to auto mount.

Post diagnostics.

The spin down delay for UD devices is the global disk spin down delay. Maybe you aren't giving it enough time.

That is no longer necessary.

Does it stay spun down?