trurl

Click on the icon for a particular VM and you will get a menu of actions you can do with that VM.

I have copied the report to this thread.

Please just plain text file

The only difference is the number of disks.

In what way was it failing? Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

https://wiki.unraid.net/Upgrading_to_UnRAID_v6

not The user share security settings only affect network access to the files.

Then it didn't work. You should have asked about it then. There are 2 ways to shrink the array after making sure the disk is empty. The simplest is to New Config without the disk and rebuild parity. The other way is to clear the disk while it is in the array, then New Config without the disk and trust parity (since the clear disk has no effect on parity). Either way New Config without the disk is necessary. You seem to have missed that somehow. As far as Unraid is concerned, the disk is still part of the array whether or not it has any data, or whether or not it is missing or unassigned. In fact, Unraid has been emulating the missing disk all this time and you have been unprotected.

Stop the array. Click on drive to get to its page. Choose a different filesystem for the disk. Start the array. It will tell you there are disk(s) to format. If it is showing the correct disk(s) to format and no others, check the box and click format. Repeat if you want to change it back to the original filesystem

"mount" refers to a filesystem, and as you noted earlier so no filesystem to mount.

https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta22-available-r955/?do=findComment&comment=9350

You can set a user share to only include certain disks and so they can only become as large as the included disks capacity.

Could you be more specific?

What do you get from the command line with this? ifconfig

Do you have backups? The CA Backup plugin makes backups of your appdata for just these situations. Your docker mappings and other settings from the Add/Edit Container page are in templates on flash and the Previous Apps feature on the Apps page will install your dockers exactly as they were. But without the appdata you would be starting over with plex, etc.

Check filesystem on disk1: Jun 19 02:50:27 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 6692 does not match to the expected one 1 Jun 19 02:50:27 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 1738342401. Fsck? Jun 19 02:50:27 Tower kernel: REISERFS (device md1): Remounting filesystem read-only https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Be sure to capture the output so you can post it.

Basically, when you specify the Use cache setting for any user share, you get to choose which cache pool that user share uses when it uses cache. It still works the same as cache, just different caches. So you can have separate caches for separate purposes.

Probably because your BIOS is trying to boot from those other ports. Make sure only the flash drive is allowed as a boot device in the BIOS. Here is another link I found about that, but I'm not sure if that is the final word on whether your NIC is supported. https://forums.unraid.net/topic/73697-cache-drive-not-working/?do=findComment&comment=678161 There is this in your syslog which suggests it may be communicating with the router: Jun 21 13:40:33 Tower avahi-daemon[4808]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Jun 21 13:40:33 Tower avahi-daemon[4808]: New relevant interface virbr0.IPv4 for mDNS. Jun 21 13:40:33 Tower avahi-daemon[4808]: Registering new address record for 192.168.122.1 on virbr0.IPv4.

Setup the WireGuard VPN built-in to Unraid: That will get you the unraid gui and really everything else on any device you setup as a WireGuard peer. If you still have some reason to want reverse proxy see this:

Looking at your syslog I'm not very hopeful of preserving anything. Even if you could copy any of it there might not be any way to use it without the rest of the things you couldn't copy. It might be simpler to just reformat cache and start over with your dockers.

Instead of syslog, we always prefer diagnostics, which contains syslog and many other things that give a more complete understanding of your configuration and situation. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

For example, I am running 16 dockers, and they only use 39% of my 20G docker image. Docker image basically should only contain the executable code of your dockers, and everything else should be in appdata or in other user shares.

Start your own thread and explain your problem.

Why do you have 100G docker image anyway? Very rarely would anyone need more than 20G. Any time a user has more than 20G docker image I suspect they have one or more of their applications misconfigured. An application will write into the docker image if it writes to a path that isn't mapped to the host. Common mistakes are application paths that don't match the mapped container path in upper/lower case, or application paths that are relative (what are they relative to?)