Recent content by ErkDog

I just had this problem on: pve-manager/8.4.1/2a5fa54a8503f96d (running kernel: 6.8.12-9-pve) I fixed it by updatedb locate libcurl.so.4 sure enough it was there in the /usr/lib/vmware folder I went in there rm libcurl.so.4 ln -s /usr/lib/x86_64-linux-gnu/libcurl.so.4 libcurl.so.4 ldconfig...

Awesome that fixed the GUI Itself. I wonder if its' going to fix the spam I'm getting in journalctl and to console about trying to mount /mainceph cephfs mount?

I searched, a lot for how to fix this. Had Ceph setup and working. Had two storages: mainceph an FS and RDBBlock an RDBBlock pool. Ceph died in a fire and I had to rebuild everything. But they are still hanging around: https://ss.ecansol.com/uploads/2024/04/26/chrome_2024-04-26_21-02-22.png...

It's a new VM I'm trying to setup. I'll redo the install using LVM and see if that fixes, will let everyone know.

the first command is a wall of text that continues with more of: root@pveclua:~# rados ls -p RDBRedMail|more rbd_data.b904aebd3b3049.000000000003ae00 rbd_data.b904aebd3b3049.0000000000000123 rbd_data.b904aebd3b3049.0000000000135e00 rbd_data.b904aebd3b3049.00000000000e5c00...

OHHHH I think this might be a generic Linux issue. For root file systems over a certain size, you have to use LVM instead of standard partition stuff yeah?

@Phillip Hufnagl root@pveclua:~# cat /etc/pve/storage.cfg dir: local path /var/lib/vz content vztmpl,iso,backup zfspool: local-zfs pool rpool/data content images,rootdir sparse 1 cephfs: mainceph path /mnt/pve/mainceph content...

any ideas @Phillip Hufnagl

Absolutely: root@pveclua:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 16.4T...

https://ss.ecansol.com/uploads/2023/11/09/chrome_2023-11-09_10-11-31.png https://ss.ecansol.com/uploads/2023/11/09/chrome_2023-11-09_10-12-27.png root@pveclua:~# pveversion pve-manager/8.0.4/d258a813cfa6b390 (running kernel: 6.2.16-15-pve) Any ideas how to fix this? Thanks, Matt

you should 1: shutdown the vm gracefully 2: detach the storage volume 3: boot the VM and make sure everything works and no data is missing 4: then destroy the volume.

I found and deleted the unused disk in the 102.conf and it went away. Is there anything else I need to do?

Getting this error: https://ss.ecansol.com/uploads/2023/08/07/chrome_1691423600.png When I try to remove this unused disk: https://ss.ecansol.com/uploads/2023/08/07/chrome_1691423614.png I initiated a disk removal operation, which churned like for days, and it nerfed the related RDP Pool in...

I'm thinking the fact that I have the rdb application enabled on some of these pools somehow may also be part of the problem but I don't know how to remove it: pool 9 'default.rgw.log' replicated size 3 min_size 2 crush_rule 0 object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on...

I followed the guide here with appropriate changes for my environment: https://base64.co.za/enable-amazon-s3-interface-for-ceph-inside-proxmox/ For example I don't have node1 2 3 I have pveclua b c d 4 Nodes. So I replaced all instances of node# with pveclua b c d etc. However, when I went...