Search results

does somebody know if this is still an issue with DRBD ? https://github.com/LINBIT/drbd/issues/125

hi, for a long time, i'm a little bit annoyed that there is quite a reasonable number (2724) of open , unresolved tickets in proxmox bugzilla at https://bugzilla.proxmox.com i don't want to blame proxmox team here, but my question is , how we can put some systematic work into this to better...

yes it did

damn, i must have overseen that. thanks for the pointer

we upgraded from 8 to 9 a while ago, this time i did just apt update/upgrade and got this message. don't know if this is new or did exist since the upgrade from 8 to 9 reboot does not fix it - still get this message on entering psql tool root@pmg:~# su - postgres postgres@pmg:~$ psql WARNING...

Hello, on latest updates i get WARNING: database "postgres" has a collation version mismatch DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41. HINT: Rebuild all objects in this database that use the default collation and run...

> proxmox rescue boot no such device pool @corianito , do you mean rescue boot menu entry from pve9 installation iso?

@whc2001 Try NVRAM Reset with onboard switch, this helped for me with R620 Server

>running Proxmox 9.0.1 so, why are you running proxmox 9.0.1 instead of 9.0.11 ?

apparently, the linux community and maintainers don't care for this issue. this indeed underpins that proxmox considers mdraid "unsupported" and i would also like to say: stay away from linux mdraid! not only because it's broken for O_DIRECT or difficult to handle in error situations -...

please install all updates first before reporting issues, as things may have already been fixed.

that's a good idea, shouldn't we file a RFE in bugzilla for that?

@Stoiko Ivanov , as i also have struggled hours with this, too - could we perhaps make lsblk perhaps make more "robust" against failure like the above, if the param which defines the access order for lsblk is changed and blkid is being used first ? --properties-by blkid,udev,file from the...

mh. came across this one. but for me , it doesn't even work after using "reset" in efi bios https://bugzilla.proxmox.com/show_bug.cgi?id=2599 i'm out of ideas. setting in grub cmdline to kern.vt.fb.default_mode=1024x786 or efi_max_resolution="1024x768" doesn't have any effect, too. i...

@t.lamprecht @giner , i have created a reproducer for the issue to make this happen without O_DIRECT write by user - but just by accessing memory and make system swap/thrash i have done so because there wer some complaints that "you aren't allow to submit direct_io this way" , for example on...

Hello, i use proxmox from macbook retina, which has very high display resolution. i setup uefi vm to check some details of XCP-ng hypervisor, but though i set display resolution to 1024x768 in uefi bios settings of VM (Device Manager -> OVMF Platform Configuration), the linux of XCP-ng boots...

that error must be also cause by different reason, as i see this from time to time on non-clustered host, too.

ok. i should stop wasting my time by digging into issues with totally outdated proxmox versions.... https://lore.proxmox.com/all/20210706095026.3785241-1-s.ivanov@proxmox.com/

maybe yes | pvesh create ..... is worth a try? not sure, if pve9 made a progress with this issue, as i don't know how to reproduce this one. anyhow, i searched a bit and that "PMBR signature detected" message seems to originate from "lvcreate", which should be used under the hood. lvcreate...

it seems there is no mention about the pve clustering - just setting up the drbd mirroring. so i have difficulties in understanding how this can work, as we need three nodes minimum with proxmox pve.