Search results

We could find out how to trigger it: /sbin/fstrim --listed-in /etc/fstab:/proc/self/mountinfo --verbose --quiet-unsupported after that command the filesystem goes read-only. This command is also executed once at week: /usr/lib/systemd/system/fstrim.timer

Problematic node cat /var/log/syslog

I'm sure its happening on weekens because we have this setup now for about 4 weeks and this error only occurs over weekend. I'm everday testing / looking after the proxmox node with touch a rm -f a and the touch: cannot touch 'a': Read-only file system happens 3x now at Monday. My setup: 6x...

Happen now again. What I could find out, that is is always happening at weekend.

We have running some proxmox node with 7.4-17 and added a new server Lenovo System x3650 M5. These server has no load and crashes after some day (currently strangely at weekend) with a Read-Only filesystem. The node itself is running but no new commands can't be executed or files / data saved...

Bestätigung. ```apt install binutils``` half bei mir auch.

Yeaha it is now working! I changed the "Base Domain Name" directly to the OU where the users are located.

Hello, trying to use LDAPS with bind_dn. The error message from Proxmox server is pvedaemon[11487]: authentication failure; rhost=10.101.66.25 user=r.sikorski@example.de msg=no entries returned /etc/pve/domains.cfg ldap: example.org base_dn dc=example,dc=org server1...

Thanks @Stoiko. With gdisk I could resize the disk and then complete with pvresize.

Hello, I created with lvm a volume group over fibre channel and added it over the webinterface into Proxmox Storage. It is working fine. Only problem is i don't get the storage extended. I extended the volume on the storage from 1tb to 4tb. # lvextend -l +100%FREE...