2 nodes won't boot

daramullally

Member
Mar 27, 2022
6
2
8
After an issue with my nodes I rebooted both servers. Since then I cannot boot them. I get the following messages:

/dev/mapper/pve-root: recovering journal
/dev/mapper/pve-root: clean, xxxxx/xxxxx files, xxxxx/xxxxx blocks

Is there any way to overcome this?
 
I would boot in rescue mode from the PVE installer USB stick and look what might be wrong. Have a look at the syslog, check that the LVM/ZFS/CEPH is healthy and so on.
 
I have booted one of the systems with the rescue boot option. I am not an expert with this at all.

Any ideas?

Below is the outout from fdisk -l

root@pve2:/# fdisk -l
Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: VB0250EAVER
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: 6656B236-03D7-4683-8D31-FB897AB682B4

Device Start End Sectors Size Type
/dev/sda1 34 2047 2014 1007K BIOS boot
/dev/sda2 2048 1050623 1048576 512M EFI System
/dev/sda3 1050624 488397134 487346511 232.4G Linux LVM


Disk /dev/sdb: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EZRX-00D
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 5D74D641-C3AD-7B4C-9922-6BED96CEA154

Device Start End Sectors Size Type
/dev/sdb1 2048 5860533134 5860531087 2.7T Linux filesystem


Disk /dev/mapper/pve-swap: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/DataDrive-vm--107--disk--0: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 9C1761A0-9B13-4019-9001-8FF005B281D8

Device Start End Sectors Size Type
/dev/mapper/DataDrive-vm--107--disk--0-part1 34 2047 2014 1007K BIOS boot
/dev/mapper/DataDrive-vm--107--disk--0-part2 2048 1050623 1048576 512M EFI System
/dev/mapper/DataDrive-vm--107--disk--0-part3 1050624 67108830 66058207 31.5G Linux LVM

Partition 1 does not start on physical sector boundary.


Disk /dev/mapper/DataDrive-vm--106--disk--0: 60 GiB, 64424509440 bytes, 125829120 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xb81f94f5

Device Boot Start End Sectors Size Id Type
/dev/mapper/DataDrive-vm--106--disk--0-part1 * 2048 117440511 117438464 56G 83 Linux
/dev/mapper/DataDrive-vm--106--disk--0-part2 117442558 125827071 8384514 4G 5 Extended
/dev/mapper/DataDrive-vm--106--disk--0-part5 117442560 125827071 8384512 4G 82 Linux swap / Solaris

Partition 2 does not start on physical sector boundary.


Disk /dev/mapper/DataDrive-vm--106--disk--1: 2.15 TiB, 2362232012800 bytes, 4613734400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4C4C01B4-3E19-48F9-99D4-F67F25F7C51D

Device Start End Sectors Size Type
/dev/mapper/DataDrive-vm--106--disk--1-part1 2048 4613734366 4613732319 2.1T Linux filesystem


Disk /dev/mapper/DataDrive-vm--112--disk--0: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 09E6A23E-F715-438E-8F6B-6ED611D5455B

Device Start End Sectors Size Type
/dev/mapper/DataDrive-vm--112--disk--0-part1 34 2047 2014 1007K BIOS boot
/dev/mapper/DataDrive-vm--112--disk--0-part2 2048 1050623 1048576 512M EFI System
/dev/mapper/DataDrive-vm--112--disk--0-part3 1050624 67108830 66058207 31.5G Linux LVM

Partition 1 does not start on physical sector boundary.


Disk /dev/mapper/DataDrive-vm--112--disk--1: 470 GiB, 504658657280 bytes, 985661440 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 5EABDE15-9C99-514B-B050-52F2CC4A8340

Device Start End Sectors Size Type
/dev/mapper/DataDrive-vm--112--disk--1-part1 2048 985643007 985640960 470G Solaris /usr & Apple ZFS
/dev/mapper/DataDrive-vm--112--disk--1-part9 985643008 985659391 16384 8M Solaris reserved 1


Disk /dev/mapper/pve-root: 224.38 GiB, 240929210368 bytes, 470564864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
GPT PMBR size mismatch (2019431 != 16056318) will be corrected by write.


Disk /dev/sdc: 7.66 GiB, 8220835328 bytes, 16056319 sectors
Disk model: Storage Device
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: C81BBAAC-BB6C-4938-9EED-462D5AA2C82E

Device Start End Sectors Size Type
/dev/sdc1 64 495 432 216K Microsoft basic data
/dev/sdc2 496 6255 5760 2.8M EFI System
/dev/sdc3 6256 2018783 2012528 982.7M Apple HFS/HFS+
/dev/sdc4 2018784 2019383 600 300K Microsoft basic data
root@pve2:/#
 

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!