The root filesystem on /dev/mapper/pve-root requires a manual fsck - is my PVE server dead?

dschneid

New Member
Aug 1, 2022
3
0
1
After a reboot of my proxmox server, it stops on the cmd shell for initramfs.
It shows me that my root file systems needs a manual run of fsck.

capture.JPG

when executing:

Code:
fsck /dev/mapper/pve-root

is see many many errors prompting again on the screen but after a reboot (ctrl+alt+del) it does not solve the issue:

capture.JPG
capture.JPG


Is my server dead or is there a chance to fix it?

BR
Dieter
 
Maybe your boot disk is dying? I would also run a smartctl -t long /dev/YourBootdisk to check the state of that disk.
 
I tried it but unfortunately it ends up with the same picture as without rescue boot that I get a lot of erros and (initramfs) tells me that my root file system needs a manual fsck
 
the symptoms look very much like a dying disk. I'd recommend booting with a live cd of your choice (e.g. GRML, or even Ubuntu or Debian Live) and making a full rescue copy of the physical disk (plain dd or ddrescue). then you can attempt to repair the filesystem on-disk, and if that fails, attempt to recover any relevant data from the backup copy.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!