your root partition is on a disk that is experiencing problems- either hardware, cabling, or software.
smartctl --test=long /dev/[path to your root device)
dmesg | grep [your root device]
You can't make miracles, 16384 is not enough for many scripts
Let's be clear, if YOU don't make things easy for me, I will not bother sharing my solutions
What do you want, 1x 16kb one liner or 8 of them ?
I'm not asking people to go elsewhere...
A Debian 13 installation use a non compatible Network Setup. You must install the needed Packages and setup the correct IPv4, vmbrX and/ or bondY.
# https://pve.proxmox.com/wiki/Network_Configuration
Just recently I setup a PBS server on a Debian 13 VM. Ext4 install. Created a datastore /backups as a directory.
It's on some sort of RAID at Interserver that is SATA HDD ZFS pool backed. ~200 iops on a backup ontegrity test but also 2 vcpus...
Please boot with the older kernel, log in, and run:
journalctl --list-boots
Please share the output. We can then identify the failed boot and determine the command needed to retrieve its kernel log.
Uups der Tippfehler ist meinen dicken dicken Fingern zuzuschreiben. Eine interfaces.new gibt es nicht. Nur vor der vmbr0 steht auto. Die Konfigurationen hab ich schon mit anderen Hosts verlichen.
Die von @Bu66as gewünschten Screenshots werde...
I am going to attempt to run TrueNAS on my proxmox server (I don't have proxmox set up at the moment but i've used it before so i know the basics.)
On this TrueNAS server I would like to access it from two different locations:
Over tailscale...
This is what I get:
journalctl --list-boots
IDX BOOT ID FIRST ENTRY LAST ENTRY
-24 cc65a312b5b7441bbbca1eb3cd6f75ac Sat 2026-08-08 12:23:15 IDT Sat 2026-08-08 12:45:53 IDT
-23...
Please boot with the older kernel, log in, and run:
journalctl --list-boots
Please share the output. We can then identify the failed boot and determine the command needed to retrieve its kernel log.
This is all the output I get after the selecting the new kernel, and again, after that is a blank screen (the zfs-error is fine, I have TrueNAS VM):
Found volume group "pve" using metadata type lvm2
13 logical volume(s) in volume group "pve"...
I don't see it in the ILO logs, will try to reboot again to capture those logs before.
Anyway, after those errors I get a blank console and no option to login and it doesn't respond to any input
Yes, and honestly, even if someone just wants to share it directly here, I'd say the "workaround" of attaching it as a file is perfectly acceptable. And for regular forum posts that are expected to be read by humans, I'd say the current limit is...
Im not sure your Username does you any favor with this request...
Additionally, there is a whole slew of pve Scripts in a separate repository. You could submit it there and let it be reviewed.
Well..., now the seconds before this one would be interesting. Everything here is too late.
Is it possible to catch them the same way? There must be a reason for "remount read-only" - possibly/hopefully logged in the seconds before.
ILO has a...
There is no answer to this one - there are a trillion ways to setup a server incorrectly. Think about "let it run directly from a chap USB stick"-class of "wrong" doings...
I would call a Debian installation on a (hard- or software-) Raid6 with...