Hi, my PVE don't boot : freeze or kernel panic and shutdown.
I put my damaged PVE (pve) in an rescue PVE (pvessd) to repair it
But I have this message on boot:
Found volume group ' 'pvessd" using metadata type lvm2 <<< my rescue PVE
5 logical volume(s) in volume group "pvessd" now active
/dev/mapper/pve-root: recovering journal <<< my bad PVE
fsck .ext4: Input/output error uhile trying to re-open /dev/mapper/pve-root
/dev/mapper/pve-root: WARNING: Filesystem still has errors
fsck exited with status code 12
The root filesystem on /dev/mapper/pve-root requires a manual fsck
BusyBox vl.35.0 (Debian 1:1.35.O—4+b3) built-in shell (ash)
Enter 'help' for a list of built—in commands.
(initranfs) help
Built—in commands:
alias bg break cd chdir command continue echo eual exec
exit export false fg getopts hash help history jobs kill let
local printf pud read readonly return set shift source test tines
trap true tYF ulinit umask unalias unset uait
(initramfs) fsck /dev/mapper/pve-root
fsck fron util—linux 2.38.1
fsck: error 2 (No such file or directory) uhile executing fsck.ext2 for /dev/mapper/pve-root
(initramfs) fsck.ext4 /dev/mapper/pve—root
e2fsck 1.47.O (5-Feb-Z023)
fsck.ext4: Input/output error while trying to open /dev/mapper/pve—root
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you night try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768
( initramfs )
what should I do?
THANKS
I put my damaged PVE (pve) in an rescue PVE (pvessd) to repair it
But I have this message on boot:
Found volume group ' 'pvessd" using metadata type lvm2 <<< my rescue PVE
5 logical volume(s) in volume group "pvessd" now active
/dev/mapper/pve-root: recovering journal <<< my bad PVE
fsck .ext4: Input/output error uhile trying to re-open /dev/mapper/pve-root
/dev/mapper/pve-root: WARNING: Filesystem still has errors
fsck exited with status code 12
The root filesystem on /dev/mapper/pve-root requires a manual fsck
BusyBox vl.35.0 (Debian 1:1.35.O—4+b3) built-in shell (ash)
Enter 'help' for a list of built—in commands.
(initranfs) help
Built—in commands:
alias bg break cd chdir command continue echo eual exec
exit export false fg getopts hash help history jobs kill let
local printf pud read readonly return set shift source test tines
trap true tYF ulinit umask unalias unset uait
(initramfs) fsck /dev/mapper/pve-root
fsck fron util—linux 2.38.1
fsck: error 2 (No such file or directory) uhile executing fsck.ext2 for /dev/mapper/pve-root
(initramfs) fsck.ext4 /dev/mapper/pve—root
e2fsck 1.47.O (5-Feb-Z023)
fsck.ext4: Input/output error while trying to open /dev/mapper/pve—root
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you night try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768
( initramfs )
what should I do?
THANKS
Last edited: