Search results

I found the solution in the outdated article from proxmox wiki I changed the following parameters: node.startup: manual => automatic node.session.timeo.replacement_timeout: 120 => 15 in the /etc/iscsi/iscsid.conf and /etc/iscsi/nodes/<TARGET>/<PORTAL>/default The problem is gone. The latest...

my storage.cfg: ~# cat /etc/pve/storage.cfg dir: local path /var/lib/vz content vztmpl shared 0 lvmthin: local-lvm thinpool data vgname pve content rootdir iscsi: iscsi_block portal 10.10.1.10 target...

The delay in the VM autostart settings does not help when it is the first VM to autostart.

Hello, I found out that after proxmox starts VMs which have their disks on iscsi storage and are expected to autostart fail to do this because their storage is not ready yet. By the time I login to the web gui I can start the VMs by hand with no problem: ........... Aug 12 07:00:11 hv02...

I see. Thank you very much again for your comprehensive explanations!

Yes, after leaving out the -Zn option the problem seems to disappear. I remember that I added this option because there was an advice somewhere that this can speed up the provisioning of the big pool which now seems a bit odd to me when I again read the man page about this option. As the man...

So, after repeating all the steps in Step 2 and restoring a VM from backup to the new lvm-thin storage (where the vm is corrupted again) I see the following: ~# lvdisplay '/dev/vg_local/lv_thin_local' --- Logical volume --- LV Name lv_thin_local VG Name...

Thank you for the hint! I will repeat step 2 and check metadata usage.

Thank you. But I still do not understand why limiting hdsize is a bad option while it exactly does what I need?

This is sort of test lab so during proxmox installation I chose hdsize 15GB to try to limit the storage size proxmox takes by itself. IIRC, during the install proxmox said that it would not create data partition because of too small hdsize. According to wiki: hdsize Defines the total hard disk...

Hello, I have a strange situation with my single node installation. I have a free space on the proxmox install disk /dev/nvme0n1: lsblk ... nvme0n1 259:0 0 476.9G 0 disk |-nvme0n1p1 259:1 0 1007K 0 part |-nvme0n1p2...

Hello. After backup some Linux KVM VMs regularily seem to have done hard reset and cannot boot anymore. I fix these VMs by booting from live CD and using gpart -W /dev/sda /dev/sda and grub install Is there a way to fix that? PVE Manager version 5.3.7

Make sure the time on all cluster nodes is synchronized. Use an external time server to keep the time in sync.

Re: CMAN no restarting correctly The problem solved. The NFS share was unavailable. Therefore cman halted on "unmounting configfs..."

Recently I had a power failure in the server room, after that all the servers started successfully and worked for two days without errors. But a day ago all the nodes in my cluster became red. I used my old simple script to restart all the needed services like this: #!/bin/bash service...

I'll try it but the main quistion remains: HOW to correctly enable udp-option in the file storage.cfg and how to remount the storage without rebooting the proxmox host?

Don't additional options to storage.cfg work anymore? I really need this because NFS storage on OpenBSD is very slow on reading with tcp.

I didn't know this. I added this option long time ago (in versio 2.0) and it worked well. My NFS storage was made on OpenBSD OS and it worked well only when the udp option was on. Recently I had to remove this storage completely for reconfiguration but I can't remember what precisely I added to...

How can I make my NFS storage (used for backup) mount with udp option? What should I add to storage.cfg and how can I remount the storage with this option on the fly?

How can I make my proxmox ve host detect new hot-added hard disks without reboot?