Search results

@Dunuin I'm getting pretty tired, could you help him with the data rescue? I have some ideas via a prior ZFS file rescue I did in the past in a prior post in this thread.

The above is because you mentioned file corruption, and we probably need to make the target non-sparse, and then convert the ZFS volume out into a qcow2 formatted file. That'll allow you to copy it to an ext4 or other filesystem on your USB rescue HDD.

I have some notes from my evil rescue: Rescueing: qemu-img create -f qcow2 /mnt/USBBACKUP/images/100/vm-100-disk-0.qcow2 6000G /usr/bin/qemu-img convert --salvage -p -n -T none -f raw -O qcow2 /dev/zvol/rpool/data/vm-100-disk-0 zeroinit:/mnt/USBBACKUP/images/100/vm-100-disk-0.qcow2 Worth...

You can literally copy those files to another location, if you have sftp access to the proxmox server you can download them to your desktop using a tool such as Filezilla. (I actually use Filezilla extensively to grab copies of local backups. No reason why you can do the same with the target...

Let's say 100 was on ZFS-BULK: I could change the entry to ZFS-Bulk, but that's assuming PVE can see it as an entry.

That's the thing, I'm not sure it does. In my experience, most systems will prohibit root login over ssh, and it has to be set explicitly. Note: I've been installing systems with non-root accounts and then setting them up with sudo and ssh keys for login. As a result, I personally don't see...

Each of those conf files contains all the VM details, including the file structure; it's an example. You can adjust those as needed on your new install.

Fortunately, those are not too big. You could copy them to the new installation data directories; or mount and reuse. If you have and use the config.db from the old installation [make sure you keep a copy of this] it should be possible to edit the locations of the files for each VM on the new...

I should add, not anything bad, really, but keep in mind bad vs good does depend on what you are running in the VMs. Lots of writing could be a problem.

Yes, the config.db should have the settings for those VMs. So, you need to mount the old proxmox installation and acquire the config.db from /var/lib/config.db It's sort of being covered in this thread over here: https://forum.proxmox.com/threads/how-to-mount-a-zfs-drive-from-promox.37104/ Oh...

Okay, make sure you copy that file. The intention would be to install it on a new proxmox installation so that when it boots, it mounts /etc/pve. Then, you'll have all the access to the configuration files you need. [So, make a backup of the file. Copy it into the same position on a new...

It lives here: /var/lib/pve-cluster/config.db It is a loopback filesystem, a database. /etc/pve is mounted to it.

In your CT we can edit the sshd configuration, we are going to edit that configuration so it has settings the same as a configuration that permits root. In the CT: nano /etc/ssh/sshd_config Change each of the following lines: PermitRootLogin ChallengeResponseAuthentication UsePAM To...

With error 68, that will be because the rescue disk has support for an older version of ZFS, without support for the newer ZFS version. I suspect, though, you're running the most recent version of the proxmox iso? Now, I've suffered this pain before myself, the method I went on to use was to...

Ubuntu = Not work. Debian 11 = work.

Progress :) Okay, now we know it is something explicitly stopping root logins and not another ssh fault. In the CT: cat /etc/ssh/sshd_config Now make sure the following are set (we'll brute-force it, and set it the same as the Proxmox host): PermitRootLogin yes ChallengeResponseAuthentication...

Old picture, take new screenshot with output of useradd command. [or adduser , which is an easier command, but not always available.]

In the instructions, the command is: env | grep LANG

With the container, I would be interested in seeing what language it is set to. The instructions, provided earlier, give the commands to do this, and also give the directions and commands to set the language.

Okay, here's the instructions for Debian: https://wiki.debian.org/ChangeLanguage I'd be most interested in what the container is set to at the moment.