Homelab Proxmox VE crashes

[Gamix]

Hello, I've recently made a Proxmox VE homelab on a PC. Recently he started crashing a lot (happenned 4 times now) even where there a 0 VM / Containers on. I've put a screenshot below to show the message. I cannot SSH or Https into the server when it happens.

Modified configuration :

CPU: Intel Core i7-4770K
RAM: Micron 8 x 4 DDR3 - 1600MHz
Storage: 1 SSD 2To SATA

Original PC :
Dell OptiPlex XE2 SFF

 

[fireon]

The Ext4 file system is defective. For security reasons, the file system is then remounted in ‘read-only mode’. Perhaps a defective hard drive (dm-1)? Please check the smart values of your drives.

1. Check your filesystem - this only works if the filesystem is unmounted. With this Tutorial you can do this during an reboot.

fsck.ext4 <device>

2. Check the smart values of your drives

Show your existing drives:

ls -l /dev/disk/by-id/

Check smart values:

smartctl -a /dev/disk/by-id/<your drive>

 

[Gamix]

I've managed to do some tune2fs test but didn't get any result.



At first I couldn't do a SMART Test because it always was crashing so I used a CrystalDiskInfo test via USB (I later did a smartctl test which came back blank too).



I'm at a loss here, did I failed the installation of my VE? I used the last version (Proxmox VE 8.2) and my SSD looks healthy.

 

[pikey]

Use a Live CD and

fsck.ext4 /dev/sda
fsck.ext4 /dev/sdb

Your root Partition (/) is mounted and you should avoid use fsck with a root partition that's mounted

 

[Gamix]

I used a Ubuntu LiveCD and did the following (as root) :

fsck.ext4 /dev/sda3
e2fsck 1.47.0 (5-Feb-2023)
/dev/sda3 is in use.
e2fsck: Cannot continue, aborting.

fsck.ext4 /dev/sda
e2fsck 1.47.0 (5-Feb-2023)
/dev/sda is in use.
e2fsck: Cannot continue, aborting.


umount /dev/sda
umount: /dev/sda: not mounted

I tried listing it to be sure:

fdisk -l
Disk /dev/sda: 1.86 TiB, 2048408248320 bytes, 4000797360 sectors Disk model: SSD 2TB
Units: sectors of 1* 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8BE224E3-D3F8-4F82-9E34-7A8B29532C69

lsblk



How can it be in use if it's not mounted?

 

[Azunai333]

How can it be in use if it's not mounted?

/dev/sda is the whole disk.
/dev/sda3 is a LVM partition. Ubuntu activates (mounts) LVM partitions on boot. This is good, as you don't need to to this yourself now.

Try fsck.ext4 /dev/mapper/pve-root or fsck.ext4 /dev/pve/root.

 

[Gamix]

I got the following results :

fsck.ext4 /dev/mapper/pve-root
e2fsck 1.47.0 (5-Feb-2023)
/dev/mapper/pve-root: clean, 53631/6291456 files, 9924461/25165824 blocks

fsck.ext4 /dev/pve/root
e2fsck 1.47.0 (5-Feb-2023)
/dev/pve/root: clean, 53631/6291456 files, 9924461/25165824 blocks

 

[pikey]

Try it again with fsck.ext4 -f

Also

lvdisplay -m

and

pvck -v /dev/sda3

 

[Gamix]

For the fsck:

fsck.ext4 -f /dev/pve/root
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/pve/root: 53646/6291456 files (0.2% non-contiguous), 9926581/25165824 blocks

fsck.ext4 -f /dev/mapper/pve-root
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/pve-root: 53646/6291456 files (0.2% non-contiguous), 9926581/25165824 blocks

The pvck gave me this:

pvck -v /dev/sda3
    Found label on /dev/sda3, sector 1, type=LVM2 001
    Found text metadata area: offset=4096, size=1044480

lvdisplay gave me the pve partition and some VM I have on it. The data partition is in read only though.