Search results

Is it a real hardware RAID or pretend RAID where you need a driver to make it work? The latter used to be popular for Windows machines but often don't work on Linux. Perhaps if you posted the model of the controller someone can help.

Do you trim inside the VM?

Based on the log you should look at the permissions on /var/log/pveproxy/access.log. It could be not writable or non-existent. Since SSH and ping work it isn't a network problem, but maybe pveproxy is timing out while attempting to open the log file. ETA: It could also be that your root disk is...

Maybe setting the start order of the TrueNAS to be earlier than the CT's that need it. You can also add a delay before the startup moves on to the next VM/CT. ETA: I use autofs for this as well, although I have no bind mounts. I just make sure that the NFS VM is started before any of the ones...

Yeah, I would like to see the outputs @Pifouney asked for. Because it really looks like you have done more than you let on. You've got a couple of disks mounted but no storage defined for them, plus the disk you do have a storage defined for seems to either not exist or be mounted somewhere...

There isn't anything to solve. Bridges broadcast some traffic to all ports.

I should add that I am of the opinion that LVM is the right thing for most home users if they have SSD storage. ZFS is very demanding of SSD's because of a thing called "write amplification", which is a consequence of it being copy-on-write. You will see people in this forum advocating for...

The default install will create an LVM pool if there is only one drive, or a ZFS pool if there is more than one. It will allocate some amount of that space to the root filesystem, how much depends on the size of the drive and you can change it. The rest of it will be used as block storage for...

Maybe use the code tags next time. That's pretty hard to read! It looks like your network is up so that's not the problem. The error in your first post refers to /media/general. That UUID in fstab doesn't look right, are you sure it is correct? It is way longer than normal. Mabye two got...

Please read about storage types in the manual, which is linked at the top of the PVE web GUI. https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_storage_types

Did you check if the name of your NIC changed? Sometimes adding PCI devices causes that. Use "ip a" to check.

Your assumption is incorrect. The vCPU setting has to do with CPU hotplug. It is the number of cores the machine will start with, then you can hot-plug up to the number in the upper section of that dialog. From the Proxmox Manual (linked at the top of the web GUI in PVE): vCPU hot-plug Modern...

Note that this question or a variant of it is asked every few days. Searching the forum should yield lots of results.

RAM must be pre-allocated when using PCI pass-through. This is because the device might do DMA to any address behind the back of the CPU. Are you really sure you removed the device rather than just not using it?

You have to add /mnt/pve/BACKUP as a directory storage.

Why do you keep saying that? I thought I was pretty clear that I am asking for the output of lsblk ON THE PVE HOST. I am trying to figure out how your disks are configured since you don't seem to know.

Yes, /etc/fstab is correct. Sorry about that.

Please log in to your server command line (console or ssh) and post the output of "lsblk" and "cat /etc/fdisk". Then we can help figure out what goes where. If you can't do that it is very hard to help you.

Well, that is a little new info. Proxmox can't find your first disk and the VM won't start. It really sounds like the disks were mounted by name (e.g. /dev/sda) rather than by id and adding new disks changed the enumeration. That or the administrator got confused and mounted things in the wrong...

apt install apcupsd apcupsd-doc Then read the docs in /usr/share/doc/apcupsd.