Search results

pct start 108 run_buffer: 314 Script exited with status 32 lxc_init: 798 Failed to run lxc.hook.pre-start for container "108" __lxc_start: 1945 Failed to initialize container "108" startup for container '108' failed

108 stopped <name>

I do.

Can anyone please assist? Thanks!

Here is what syslog shows: Oct 30 10:59:54 server pvedaemon[11378]: startup for container '108' failed Oct 30 10:59:54 server pvedaemon[5517]: unable to get PID for CT 108 (not running?)

() run_buffer: 314 Script exited with status 32 lxc_init: 798 Failed to run lxc.hook.pre-start for container "108" __lxc_start: 1945 Failed to initialize container "108" TASK ERROR: startup for container '108' failed

A lvconvert --repair pve/data then a reboot fixed this.

The fstab file has the line needed to mount the qnap device. I do a "mount -a", and it fixes this. Doesn't the fstab get read and executed? I would think this share would come up as the system comes up.

Can anyone please help me with this?

I may have lost power unexpectedly, and the server was shut down. I see this message: "Check of pool pve/data failed (status:1). Manual repair required! bad checksum in metadata index block. "

It looks like it failed to mount due to a bad option... looking into the fstab file.

I noticed that I can no longer connect to my qnap device in PBS. I receive this error message in PBS: "unable to open chunk store 'qnap' at "/mnt/qnap/.chunks" - No such file or directory (os error 2)". Would this be a qnap-relevant error message, or pbs issue? The only thing that has changed...

I was reading the documentation about the Verify All button. I noticed this recommendation: What are other recommendations that I should be aware of with PBS?

Error: EPERM: Operation not permitted

I am using a qnap device. I set the backup user on the qnap to 'rw', but I get the same error message.

I am now running 1.1-5. I tried adding that option, but upon reboot, it failed to mount the remote qnap drive. Here is what my fstab file looks like: 192.168.0.3:/pve-backup /mnt/qnap nfs rw,hard,intr,rsize=8192,wsize=8192,timeo=14 0 0 I am able to mount with that line.

I have a remote file share mounted locally. This is the error when I attempt to add the new datastore in the gui: "EPERM: Operation not permitted". Here are the folder permissions: "drwxrwxrwx 6 root root 4096 Apr 11 18:21 qnap". I am running Backup Server 1.0-1.

I am trying to access my GUI via https://<ip>:8007. Here is what my netstat looks like: How do I configure it to listen on port tcp 8007?

proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve) pve-manager: 6.3-3 (running version: 6.3-3/eee5f901) pve-kernel-5.4: 6.3-3 pve-kernel-helper: 6.3-3 pve-kernel-5.3: 6.1-6 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-5.4.78-1-pve: 5.4.78-1 pve-kernel-5.3.18-3-pve: 5.3.18-3...

I ran a backup job to my pbs datastore, and received the following: ... INFO: issuing guest-agent 'fs-freeze' command INFO: issuing guest-agent 'fs-thaw' command ERROR: VM 102 qmp command 'backup' failed - backup register image failed: command error: No such file or directory (os error 2) INFO...