Search results

I have recently replaced (technically not replaced, just left all the drives in the machine) my rpool drives with new, larger nvme drives. The system was using: Dell Poweredge T410 with PCIe nvme+sata adapter in a zfs mirror for boot. both drives were set up with three partitions, the second as...

guessing that real admins use laptops. I just want an easy way to check on stuff on the road.

I think I've resolved this. I had an unused onboard lan that was bridged to the VM and getting IPV6 address. I disabled it and things started working properly.

I am stumped and I have come here for help! I have two proxmox installs that are pretty similar. pve1: pve-manager/8.0.4/d258a813cfa6b390 (running kernel: 6.2.16-19-pve) pve1 is also running LMDE6 as a workstation and a bunch of lxc and vm stuff. pve2: pve-manager/8.0.4/d258a813cfa6b390...

Thank you again for an awesome tutorial and the effort to test that this works. I did my PVE 7 to 8 upgrade and LMDE 5 to 6 upgrade concurrently and other than a few gpg complaints, it went very well. I did have to update the /usr/lib/os-release file again to fix the UI's repositories glitch...

@trentnbauer wrote you a little instruction set above. hope it helps!

It's been a while since I set this up, but I will do my best to give the best information I can remember: The basic instructions are here: https://support.google.com/cloud/answer/6158849?hl=en for reference. For proxmox users: https://pve.proxmox.com/wiki/User_Management Do not enter the quotes...

Long time no update but after still having this issue, I decided to investigate a bit further. It looks like the file with the os-release info was causing Proxmox to error out. Specifically the line VERSION_CODENAME=elsie root@pve:~ # cat /usr/lib/os-release PRETTY_NAME="LMDE 5 (elsie)"...

Done. There was a similar one for mobile web but none for the app that I saw.

I'm using google as my oauth2/openid login provider and have it working nicely to log in to my local proxmox install via a web browser. I realized the other day that the mobile interface and the Proxmox mobile app do not allow for the use of Oauth logins. If I select that realm, it still...

@aureladmin I've been getting an occasional error pop up in the PVE web interface when using this setup: "unknown Debian code name 'elsie' (500)" Does proxmox not like having the linuxmint 'elsie' sources in its repository list? I can't even load the pve web interface "Repositories" for my...

Did my upgrade and the above Cinnamon LMDE is still intact.

Maybe not the answer to my question, but: I just spun up a proxmox 7 VM and, after adding the non-sub source, installed cinnamon-desktop-environment and it works pretty well. It's not "mint", but it appears to be functional. My real question is: will everything break when I upgrade from 6.4...

@aureladmin Long shot, but have you tried running the cinnamon desktop on proxmox 7 bullseye? I see articles about the cinnamon debian guy moving on, but people picking up where he left off. thanks!

That is what I figured. I would be less cavalier about the "format" command.

Yes. Yes I can. And did. And it didn't explode. result: root@pve:~ # uname -r 5.4.101-1-pve root@pve:~ # zpool version zfs-2.0.3-pve2 zfs-kmod-2.0.3-pve2 Thanks for pointing me in the right direction.

I forget what process I used. I believe it started with a fresh install and migration of data from the old pair (raid z mirror). Can I run the pve-efiboot-tool init command on a running system without breaking it? it should have the EFI VFAT partitions in place.

Additional info: /etc/kernel/pve-efiboot-uuids was showing outdated information (I replaced both drives). So I removed the original file. Can I just copy the new vfat UUID for the new drives into a new file? e.g. lsblk -f | grep vfat ?

I'm not sure which is the problem and which is the symptom or if they're independent... I was checking status of my pools and saw the message about running zpool upgrade. I'm fine with that, this is not production and there's no concern about running with older versions of zfs. However upgrade...

@inxsible were you ever able to get caddy v2 working on the proxmox host? I tried today with a dns challenge and I was able to get a cert for my unrouted internal domain via dns challenge (e.g. pve.dom.com reverse_proxy localhost:8006). but it throws a very long error and the web interface...