Infrastructure/fedora-infrastructure

bvmhost-p09-03 not starting complaining disks don't exists #12271

New issue

Closed

opened 2024-11-04 11:23:49 +00:00 by zlopez · 3 comments

zlopez commented

2024-11-04 11:23:49 +00:00

Contributor

Describe what you would like us to do:

Today the bvmhost-p09-03 stopped responding and after restart it ended up in state when it couldn't find attached disks:

[  255.918671] dracut-initqueue[1616]: Warning: Could not boot.
         Starting dracut-emergency.service - Dracut Emergency Shell...
Warning: /dev/disk/by-id/md-uuid-496fb4e8:d91bbaf4:3551e83a:a7c6e9ac does not exist
Warning: /dev/disk/by-id/md-uuid-bc65d529:55a1eab2:b79d716e:e29d799a does not exist
Warning: /dev/mapper/vg_guests-LogVol00 does not exist
Warning: /dev/vg_guests/LogVol00 does not exist
Warning: /dev/vg_guests/LogVol01 does not exist
Warning: crypto LUKS UUID 457151a4-f404-4232-a873-cea57ec14ca5 not found

Something is definitely strange with this one. I tried to restart it once more, in case it was just some one shot issue, but I got the same issue on second try.

When do you need this to be done by? (YYYY/MM/DD)

# Describe what you would like us to do: ---- Today the bvmhost-p09-03 stopped responding and after restart it ended up in state when it couldn't find attached disks: ``` [ 255.918671] dracut-initqueue[1616]: Warning: Could not boot. Starting dracut-emergency.service - Dracut Emergency Shell... Warning: /dev/disk/by-id/md-uuid-496fb4e8:d91bbaf4:3551e83a:a7c6e9ac does not exist Warning: /dev/disk/by-id/md-uuid-bc65d529:55a1eab2:b79d716e:e29d799a does not exist Warning: /dev/mapper/vg_guests-LogVol00 does not exist Warning: /dev/vg_guests/LogVol00 does not exist Warning: /dev/vg_guests/LogVol01 does not exist Warning: crypto LUKS UUID 457151a4-f404-4232-a873-cea57ec14ca5 not found ``` Something is definitely strange with this one. I tried to restart it once more, in case it was just some one shot issue, but I got the same issue on second try. # When do you need this to be done by? (YYYY/MM/DD) ----

kevin commented

2024-11-05 00:38:15 +00:00

Metadata Update from @kevin:

Issue assigned to kevin

**Metadata Update from @kevin**: - Issue assigned to kevin

kevin commented

2024-11-05 00:38:22 +00:00

So, I figured things out.

Somehow the latest kernel was not fully installed, it only had kernel-core and kernel-modules (not kernel-modules-core, which it needed to see disks).

I booted it in the bootloader and rebuilt the raid fully there, then rebooted into the previous kernel and it's back up now.

Lets hope it stays up...

So, I figured things out. Somehow the latest kernel was not fully installed, it only had kernel-core and kernel-modules (not kernel-modules-core, which it needed to see disks). I booted it in the bootloader and rebuilt the raid fully there, then rebooted into the previous kernel and it's back up now. Lets hope it stays up...

kevin commented

2024-11-05 00:38:22 +00:00

Metadata Update from @kevin:

Issue close_status updated to: Fixed with Explanation
Issue status updated to: Closed (was: Open)

**Metadata Update from @kevin**: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)

Sign in to join this conversation.

No labels

Fixed with Explanation

Initiative Worthy

Insufficient data

Closed As/Will Not

mini-initiative

Needs investigation

packager_workflow_blocker

🔥 URGENT 🔥

Waiting on Assignee

Waiting on External

Waiting on Reporter

release-monitoring

request-for-resources

websites-general

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/fedora-infrastructure#12271

No description provided.