Search results

After I had removed faulty "devices" (sdxx), I flushed maps with multipath -f 360xxxxxxxx... that is, using these long strings (you have 368ccf...). Maybe you get the error because you use PVE-VM-02 instead? P.S. I can add that I had various experience in such situations. Sometimes I had to...

Facts about the backups are kept at the PBS. The PVE can only get the facts if the PBS agrees to give them to the PVE. I.e., the PVE needs the appropriate permissions at the PBS.

I would remove the datastore and create it from scratch.

Welcome, @internetnick Boot Proxmox in rescue mode and fsck the filesystem on your drive.

Welcome, @John EH Exactly because of the device physically missing but included in /etc/fstab. You can say "Thank you!" to systemd overlord :-(. One may secure oneself against this danger by using nofail option in fstab, though I wouldn't vouch for it because I've lost track of systemd...

If I understand your issue right, you want to verify things at PBS side. So permissions at PBS matter.

Hi, @pulipulichen In a similar situation I have cleared faulty devices with, e.g.: echo 1 > /sys/block/sdq/device/delete

Hi, @Skye0 You may want to have a look at https://pbs.proxmox.com/docs/user-management.html#api-tokens and https://pbs.proxmox.com/docs/user-management.html#access-control

Hi, @TobiTobs A quick G. search gives: https://www.postfix.org/TLS_README.html "You can ENFORCE the use of TLS, so that the Postfix SMTP server announces STARTTLS and accepts no mail without TLS encryption, by setting "smtpd_tls_security_level = encrypt". According to RFC 2487 this MUST NOT...

Quite possible. There may be more info above the visible area. Sometimes you can scroll some more visible pages up by means of Shift+PgUp on the keyboard connected to the server (unless also the display is completely locked). There do exist ways of finding the reason of a panic - with these...

Hi, @kransom If you have or can have a monitor (I mean a physical display) connected to the server, there may be some errors displayed on it when for any reason the system isn't already able to log anything to the files.

One more time ;-( apt-get dist-upgrade or apt full-upgrade I shouldn't post having high temperature ;-(

You mistyped this. apt update ; apt-dist-upgrade Edit: sorry! This time I mistyped! apt dist-upgrade

apt-get update apt-get install debsums P.S. Strange you have quotation mark even it the shell prompt. Maybe some locales or emulation problem. Try first export LC_ALL=C (note it isn't permanent).

When you click on the ">" arrow visible at the very right side of your screenshot, isn't there more information than already visible "unexpected status"?

Hi, @mhentrich I remember a similar issue reported in the Forum. Unfortunately I don't remember the outcome and have no time to search for that thread in the moment, but knowing you're not the first reporting it, maybe you'll be able to find it :) P.S. I think I've found it...

@Charrat , I seem to remember that in similar cases, harmful repositories occurred to be added by these khe-khe-...helper scripts. So just in case, check what is below /etc/apt/

Yes, seems it is created. So either it didn't exist just before this backup or it existed but the current backup mode (stop mode) invalidated it. I don't know. I would check what events will take place during the next stop-mode backup. Will the bitmap be used or "created new" again?...

Dirty bitmap is used in snapshot mode (I don't know for suspend mode).

This is a banal question, but: have you tried other keyboards?