Command line (not bash prompt) at beginning in Emergency Mode:

# start job is running for /dev/mapper/almalinux_heb-home # error this never starts up. From journalctl -xb:
sda: p2 size 486297600 extends beyond EOD, enabling native capacity
kernel: sdb: p2 size 186297600 extends beyond COD, enabling native capacity
kernel: sda: sdal sda2
kernel sdb: sdbl sdb2
kernel: sda: p2 size 486297600 extends beyond EOD, truncated
kernel: sdb: p2 size 186297600 extends beyond EOD, truncated
sdc: sdcl sdc?
kernel: sdc: p2 size 486297600 extends beyond EOD, enabling native capacity
kernel: sdc: sdcl sdc2
kernel: dc: p2 size 486297600 extends beyond EOD, truncated
dev-mapper-almalinux_server_nx2dhome device: Job dew-mapper-almalinux_server_n2dhome.device/start timed out
..mdl11: Timed out. waiting for device dev/mapper/almalinux_server_n-home.


Anybody know how I can fix this issue? Started after I took out a volume and rebooted.

/dev/mapper? Have you LVM? Put the volume back in, and write 20 lines:

Please do not bold all your text. Bold is for emphasis of certain parts and on a forum large quantities bolded implies yelling.

These lines tell the story, especially the Fix the changes you made and reboot.

It was never out. It's the nvme drive:

nvme0n1 259:0 0 232.9G 0 disk
├─nvme0n1p1 259:1 0 1G 0 part
└─nvme0n1p2 259:2 0 231.9G 0 part
├─almalinux_server_n-root 253:0 0 70G 0 lvm /
├─almalinux_server_n-swap 253:1 0 7.7G 0 lvm [SWAP]
└─almalinux_server_n-home 253:2 0 154.2G 0 lvm /home

That's why I'm confused as it's never left.

All drives are back in and it still does it. That's why I posted. See my last response.

If this is one drive them please explain what you meant when you said
I interpreted that statement to mean you removed one drive from the machine and the errors indicate that the device size is less than is expected. The errors also seem to be related to LVM since it is directly identifying a device in /dev/mapper/

Did you remove a physical device?, did you remove a partition?, did you use some tool other than lvm management commands to change an LVM device size?

What exactly did you do just before the boot that showed these errors?

One tool that may be able to assist would be to boot from a live install media to analyze the remaining hardware device in the system. There are tools there in most distros that may be able to assist with recovery.

BTW, you stated this is the nvme drive, but the logs you posted show sda, sdb, and sdc and the errors seem to indicate that the partition size(s) extends beyond the end of the device.

Volumes and partitions were all screwed up, so I'm starting from scratch. All good.