Search results

Hey! If i'm not mistaking - not really. These are different storage types. The lvm one is LVM-Thin. This allows ot store the raw data for VMs and over-provision storage for VMs. Local is Directory. It's great for storing images and backups, but not VMs. My advice would be to opt for ZFS. When...

My pleasure! If my understanding is correct, that flag is used during boot. As soon as the device is mounted, there is no point in having nofail, since no actual fail occurred :)

Try including UUID="479c7c08-c841-45b7-8679-cbf67258be45" /media/Backup ext4 nosuid,nodev,nofail 0 0 into fstab and reboot with the USB removed. See if it blocks the boot.

Can you please specify what drivers you use for the VM controller, disk? Is your physical server using any cache-capable RAID controller? What file system are you using?

Can you explain how the "no boot" looks like? Is it stuck before the kernel is loaded?

Try these flags: nosuid,nodev,nofail E.g. UUID="479c7c08-c841-45b7-8679-cbf67258be45" /media/Backup ext4 nosuid,nodev,nofail 0 0 Btw, have you created the Backup folder?

It may sound stupid, but are the shutdown commands executed with root privileges? Can it be the case that the system simply rejects it since the apcupsd does not have the right privileges?

Interesting! It's very good to know. We've used this setup since we haven't managed to migrate all the machines to controllers allowing the pass-through (we still have a mix of H310 and H710 for DELLs) and in order to have the compatibility for all the hardware we've opted for RAID0 per drive...

This is weird. Have you tried doing the command line shutdown manually? It may be the case that some VMs don't have the QEMU agent running. It also happened that the shutdown of VM was stuck due to Windows update.

Ok, leaving this for posterity. No, the issue was not related to an error with BIOS, hardware, firmware, etc. Turns out - the external HDD connected via USB to the server was causing the issue. It still leaves a couple of questions unresolved: why was it booting normally in the past? why even...

Can you clarify please: - does it reach the ProxMox Installer GUI or it fails before? - if it does reach the installer, what file system do you try to make? - does it fail during installation routine, or after the first reboot?

Hey! Instead of trying to achieve drives pass-through, you can create a RAID0 virtual disk for each separate drive. This is how i have it atm.

I am using a Smart UPS and their PowerChute instead of apcupsd. I cannot tell much about apcupsd, but it seems that the UPS sends the correct messages, while apcupsd does not process them. I.e. the UPS tells that the UPS is lacking power, but when the shutdown sequence is initiated, no actual...

Thank you @udo To be honest, i'm not sure where to start digging. I have 4 Dell R620s. All have identical setup. All have identical hardware (give-or-take). The drives are from the same batch. The RAID controllers are of the same type. BIOS settings are identical and so are the iDRAC settings...

Hey! Since i figured this out, decided to share for posterity: echo 'deb http://linux.dell.com/repo/community/openmanage/iSM/340/stretch stretch main' | tee -a /etc/apt/sources.list.d/linux.dell.com.sources.list && \ apt install dirmngr && \ gpg --keyserver pool.sks-keyservers.net --recv-key...

Hey guys! Inquiring about the Grub boot ZFS problem issue: https://pve.proxmox.com/wiki/ZFS:_Tips_and_Tricks#Grub_boot_ZFS_problem I have a couple of Dell R620 and some boot normally and some don't. The setup is identical. Has anybody managed to get to the root of this issue? Details: The...

@silbro I use it for VMs. Work like a charm. Haven't tried Ceph yet, though. But i'm sure they can manage.

If i'm not mistaking, you're talking about Sandisk IoMemory. They should be crazy fast. I use the previous generation of Fusion-Io and i get 1-1.5GBps RW and around 200k IOPS. So it should be very good.

Here's my sample of NGINX conf. Maybe it can help you: server { listen 443; server_name <proxmox_domain> root "/var/www/html/htdocs/"; #or another folder ssl_certificate <proxmox_fullchain>...

Valid point, but it makes sense only if you are the cluster manager. If you have a multi-user setup and the user has access to manage the VM, this will bring more confusion. You end up with different alert messages based on the user role and this complicates the overall Proxmox UI logic. I guess...