Search results

Reading this thread, but not being experienced in clusters, I'm really worried about a couple of points: a) fencing should be different, i.e. Proxmox node finds itself isolated, understands that has to "suicide" then stops/kills all KVM processes (or LXC or whatever), logs the fact, syncs the...

I do remember that for a long time, "maintenance mode" was in the roadmap list, now is no more there... bad sign! https://pve.proxmox.com/wiki/Roadmap#Roadmap

Sigh, I did not noticed the "menu" / "submenu" structure, my fault! For the record, with my setup, the right line was: GRUB_DEFAULT="gnulinux-advanced-cc2c0db059b7f802>gnulinux-5.4.128-1-pve-advanced-cc2c0db059b7f802" Now worked as expected, thanks! BTW, since proxmox-boot-tool are able to...

No luck, I've tested and failed with grep menuentry /boot/grub/grub.cfg | grep 5.4.128 menuentry 'Proxmox VE GNU/Linux, with Linux 5.4.128-1-pve' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5 .4.128-1-pve-advanced-cc2c0db059b7f802' { so I...

Grub blue menu, as you can read in my post I do have a "legacy boot" setup (no UEFI) (also proxmox-boot-tool status output confirms this). That's why I ask if the proxmox-boot-tool commands to set the boot kernel to use is only for UEFI, if not and I'm doing something wrong, or also there is a...

Is it me that I'm doing something wrong, or because my test machine (a VM with Proxmox zfs installed but BIOS mode) needs different commands, and if so, which are? I.e. in this example I've tried to boot with 5.4.128-1-pve but after reboot the same 5.11.22-5-pve was used # proxmox-boot-tool...

IS NOT SOLVED, is a bug / problem of 5.13 kernel, soon or later 5.11 will be removed from Proxmox and these problems need to be analyzed and solved in the new kernel. Your "solution" is just a temporary workaround of a partial upgrade (running older kernel)

There is a very similar problem about the installer and the zpool created, so I've added my user case there https://bugzilla.proxmox.com/show_bug.cgi?id=3703

If I create a datastore from a new disk of type "Directory" then is mounted as relatime /dev/sdg1 on /mnt/datastore/bktestext4 type ext4 (rw,relatime) while if I create of type "ZFS" the resulting dataset has "atime on" and "relatime off" zfs get all bkpool02 | grep 'time'...

Read from the "Model" column of your screenshot regarding disks. Without VMs running, just as "poor man's benchmark", try a pveperf command from shell, against the "VM" pool. My Kingston DC500M (960GB) has a fsync performance index of 8710 (ZFS single disk). Hope you have zfs pool configured as...

Use Kingston DC500M (so not 450R, never "R" series, and 500 is better than 450 series) that is mixed use optimized and has powerloss protection. You as asking for "how to make 450R work better", but I think your starting point is hopeless in any case, and if you can effort "Dell server with...

Proxmox does not use libvirt, so I think will not work (not tried either)

Probably he does not have Proxmox reboot every day, but instead someone using the VM and shutting sometime it (the VM ony) down by accident at the end of the working day, then complaining that "does not work" the day after.

Ok, I usually edit user crontab, so I become root and issue crontab -e I've the feeling that /etc/crontab could be overwritten if you update the crontab package, not an expert of crontab but maybe you'd better have a look at possible consequences

Just curiosity, what file is that (or how did you open it with nano)? First time I see a crontab with "user-name" column

I have a Asus MB too (ASUS Prime X570-Pro) and a U.2 Kingston DC1000M NVMe ssd. To be more "compatible" I bought the "Asus Hyper Kit" (M.2 to SFF-8643 converter for U.2 cable). It worked fine until I updated the DC1000M firmware, after that the HyperKit did not see the SSD anymore. I then...

Just asking for a clarification: a) why do you say that qdevice is not supported? It's officially documented b) what do you mean with "ZFS replication would not run when I failed two nodes and was left with one node and the qdevice"? Of course if you have only one storage node, the replication...

At least you misunderstood the UPSNAME parameter! # UPSNAME xxx # Use this to give your UPS a name in log files and such. This # is particulary useful if you have multiple UPSes. This does not # set the EEPROM. It should be 8 characters or less. homeups <------------- WRONG!!! the correct...

Hope you are aware that the "R" models are for "read oriented" workload, so you should always choose the "M" variant, that is much more durable and has better performances (at slightly higher costs).

Try Kingston DC1000M ('M' and NOT 'R'!!!) that is U.2 format (you need to buy a M.2 adapter or a pcie adapter), 960GB is around 300$, Power Loss protection and 3500 TBW (1DWPD / 5 years), I've the 1.92TB model, there is also a 3.84 one.