Search results

Do you by any chance run docker inside that LXC? I think the only people with access problems are doing this. Because for me there never have been any issues no matter which applications inside the LXC needs access to the share. I am however not using docker, instead I directly install those...

I don't understand, why would it? Please share your thoughts! It only grants access to the files having the correct permissions and are mounted to the LXC.

I think that many people, including me, are using ext4 (Directory) as type for their VM/LXC storage. Why? Because ZFS on consumer grade SSDs tends to cause problems due to the lack of available cache. Your solution makes use of a feature called "subvolumes" that not all filesystems support...

Okay, I understand. Very clever indeed. However this will only work if your LXCs are stored on a ZFS/BTRFS volume. Therefore I still prefer my solution since it works with any type of storage.

Can you elaborate a bit more on this and give a minimal working example for a CIFS share (step by step)? I understood some aspects of it but not all.

Yes sure, just google for "fstab smb/cifs credentials file".

NVME cache is pretty useless for Plex since it doesn't involve reading of various small files. My solutions has not much to do with you current issue. You will first have to sort out how you want to combine/structure your drives. After that you can think about bind mounting the storages to the...

No issues here. Well, what do you think this means?

Never happened to me. Must be an issue with your LXC. Maybe something is still accessing the mount and delays the unmount.

Is this within the LXC or on the PVE host? I don't have any delays rebooting / starting my Jellyfin LXC.

Well, very closely compare your "mp0: ..." line with the one I provided in the tutorial, you should be able to spot the issue on your own. If you would have just used my commands then the error wouldn't have happened.

Working fine here ever since. Double check that the share is actually working on the pve host. If yes, then share the lxc.conf file. Also there is no need to create the "/mnt/nas" folder in the lxc manually as this is handled my the mount points.

What I think is that... (no hate below) is the reason you had to ask for help in the first place! If you would have read the Proxmox docs (https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_virtual_machines_settings) about the startup order and delays you could have figured this out on...

Ehm.... Either you have a typo in your post or your 2nd LXC, that is trying to access the share hosted on your first LXC, is in fact NOT being started after your first LXC. LXC_1 is set to boot_order=1, which is what you want it to be. BUT your LXC_2 is, based on your comment, also set to...

You are right. I did some reading and the "noauto" option does indeed have no effect when x-systemd.automount is set. Please also note that "noauto" being set in the fstab entry will have no negative effect on the mountpoint as it is simply ignored by systemd. They also don't have to be...

1. sudo shouldn't be necessary to create the folder. 2. Check if you are able to create a folder in the mounted share on the PVE host! If that also doesn't work than your SMB/CIFS share is misconfigured. 3. If it works on the PVE host then check if you used the right command that grants the...

Sorry, but totally out of scope of this tutorial. I run plex directly in an LXC. Well, you can also use a credentials file located in the root users home directory. This would be a little bit safer. There are other tutorials on how to do this.

It is still working fine on PVE 7.x and should always continue to work. My "command" is intended to be used by the fstab file! It will obviously not work when manually running it because it uses options that are only available in the fstab file. Also the mount type "cifs" is located correctly...

I don't use hotplug memory on any of my VMs. But thank you still for the link.

Ahh, well SeaBIOS is also fine for me! Only OVMF (UEFI) VMs are affected!