Recent content by Becod

No, I said before: That's why I came to the forum to ask questions. What I can think of now is: Move a part of the file and delete another part of the file. The space occupied by RAW files can be reduced (LXC hard disk uses RAW file format).

Thank you for your timely reply! But this is not the solution I want. My request is to move the LXC files to the PVE host. Instead of copying one copy in the PVE host. I asked questions in the forum because I couldn't reduce the size of the LXC's hard drive while moving files. It will always...

Here's the thing: I have nearly 20TB of files on my LXC drive, For some reason, I have to migrate these files to the PVE host, The problem now is that I don't have so much space to stage these files for me to migrate, So I would like to ask how to migrate these files from LXC to the PVE host...

Wish you success, the relevant RPMs can be found on the apt sources.

Thank you, but I don't know how to do it. The way I came up with was to migrate LVM-thin to a new host.

Thanks, I found the missing file. Some files in the /lib/x86_64-linux-gnu folder are missing, I copied them from the new PVE. I think it's a problem caused by incompatible versions, but I forgot which version the broken PVE is using.

The system is broken by me. Now it can't be boot. I tried a lot of ways and they can't be repaired. I need to back up the configuration file mounted in /etc/pve. Now I don't know how to mount it. Can someone help me, please? I would be grateful!

Proxmox 6.1 Because of my misoperation (reducing the root space), the root is broken and cannot be boot normally (A lot of documents have disappeared). I tried many ways to fix it. Now I just want to export the data of my LXC / VM so that I can use it on the new PVE. Most of the data is in...

It's not empty. It has more than 4K files root@pve:~# ls -l /var/lib/dpkg/info| grep "^-" | wc -l 4424

I used the following script to fix it, but the problem still remains #!/usr/bin/env python # -*- coding: utf-8 -*- __author__ = 'Fitzeng' import re def main(): fix = open('fix.sh', 'w+') for line in open("txt"): pkg = re.match(re.compile('''dpkg: warning: files list file for...

I changed it, but the problem remains Yes, I've used dpkg to install many packages. These phenomena appear when I update QEMU (Customized), but I don't care about it. Instead, I use dpkg to manually update the software package.

It's here root@pve:~# apt update Hit:1 https://mirrors.tuna.tsinghua.edu.cn/debian buster InRelease Hit:2 https://mirrors.tuna.tsinghua.edu.cn/debian buster-updates InRelease Hit:3 https://mirrors.ustc.edu.cn/proxmox/debian/ceph-nautilus buster InRelease Hit:4...

When I use apt, it will prompt the following information for example apt install lrzsz root@pve:~# apt-get install lrzsz Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: minicom The following NEW packages will be installed...

I fix /var/lib/dpkg/info, I can install&upgrade #!/bin/bash set -e # Clean out /var/cache/apt/archives apt-get clean # Fill it with all the .debs we need apt-get --reinstall -dy install $(dpkg --get-selections | grep '[[:space:]]install' | cut -f1) DIR=$(mktemp -d -t info-XXXXXX) for deb in...

Proxmox VE version: 6.1-3 I used dpkg install pve-qemu-kvm_4.2.0-2_amd64.deb, and solved some dependency problems that apt could not solve (maybe it was broken at that time). History apt install -y & apt upgrade -y Reading package lists... Done Building dependency tree Reading state...