Nevermind my mention of formatting the flash drive, I was thinking of the steps to upgrade a motherboard bios or the like. Just dd the image onto the flash...
https://superuser.com/questions/351814/how-to-copy-an-iso-image-onto-usb-with-dd
Here's my $.02.
Install 'ncdu' or run the following to see if there is anything obvious taking up space that you can delete... This may buy you some time.
# du / | sort -nr | head -99 | numfmt --from-unit=1024 --to=iec
Then get the 'hrmpf' rescue boot iso...
Well I'm a bit embarrassed and I thank you for the help. The problem was that I had a recursive rpool snapshot on a non-root dataset mounted at '/'... As soon as I unmounted it, changed canmount to noauto, and changed the mountpoint to the path where the remote snapshot lives, for good measure...
Hello, I don't believe I have any additional software that could have made changes. No unusual settings changes either.
root@host:~# unshare -mnU
unshare: unshare failed: Operation not permitted
root@host:~# systemctl cat pve-container@.service
# /lib/systemd/system/pve-container@.service
#...
One of the lxc developers shared this:
root@host:~# cat ./gftrace.sh
#!/usr/bin/bash
if [ "$#" -lt 1 ]; then
echo "usage: $0 <kernel_function> [<kernel_function> ...]"
echo "kernel_function - functions to trace (separated by spaces), all should be in #available_filter_functions list"...
I can't format the following text with color as in the terminal output due to the <code> tags but the three lines below with '>>>' indicate this is a problem, how can I best resolve it? Thanks.
root@host:~# lxc-checkconfig
LXC version 5.0.0
Kernel configuration not found at /proc/config.gz...
Here is the journalctl output.
Dec 01 02:42:06 host pvedaemon[10590]: starting CT 123: UPID:host:0000295E:0000B4B5:638884FE:vzstart:123:root@pam:
Dec 01 02:42:06 host pvedaemon[4212]: <root@pam> starting task UPID:host:0000295E:0000B4B5:638884FE:vzstart:123:root@pam:
Dec 01 02:42:06 host...
Hello, yes, it's running on bare-metal AORUS Master X570 for 18 months with many update/upgrades between then and now.
root@host:~# uname -a
Linux host 5.15.74-1-pve #1 SMP PVE 5.15.74-1 (Mon, 14 Nov 2022 20:17:15 +0100) x86_64 GNU/Linux
root@host:~# neofetch
.://:`...
Also, I have found a recent thread here where installing package 'binutils' enabled LXCs to start again. I already have this package installed.
Lastly, some other similar threads ask for the LXC config so here's that:
root@host:~# pct config 123
arch: amd64
cores: 4
features: nesting=1...
OK, update. I have run 'apt-get full-upgrade' without issue and rebooted.
Problem is unchanged.
Existing LXCs fail to start with errors as shown previously.
I attempted to create multiple new LXCs and they also failed with errors as shown previously. This time I also tried creating them with...
Oh I have not upgraded yet, and the problem remains. I was just considering that path.
I will make some time soon to do so though, unless there's another option.
I was holding off upgrading for now as I don't want to make matters worse.
Thank you.
So I guess I'm the only one experiencing this. I see 'pve-container' is one of the packages to be upgraded with 'apt update && apt full-upgrade', wondering if I just give that a go and hope it solves the problem.
The following NEW packages will be installed:
proxmox-mail-forward...
Hello, here you go, thanks.
root@host:~# pct start 123 --debug
lxc_spawn: 1734 Operation not permitted - Failed to clone a new set of namespaces
__lxc_start: 2074 Failed to spawn container "123"
../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type g nsid 0 hostid 100000 range 65536...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.