[CentOS] Server fails to boot

Sun Jul 14 08:53:26 UTC 2019
Rob Kampen <rkampen at kampensonline.com>

On 14/07/19 10:15 AM, Gordon Messmer wrote:
> On 7/8/19 4:28 AM, Rob Kampen wrote:
>> Warning: /dev/disk/by-id/md-uuid-xxxxxxxx:xxxxxxxx:xxxxxxxx:xxxxxxxx 
>> does not exist 
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1451660
>
> It sounds like your kernels aren't assembling the RAID device on boot, 
> which *might* be related to the above bug if one of the devices is 
> broken.  It's hard to tell from your description.  You mentioned that 
> the rescue kernel boots, but I wonder if the array is degraded at that 
> point.
>
I agree, it sounds like the initramfs kernel is not assembling the raid1 
devices (/,/boot,swap) or certainly not setting the links /dev/md/root 
/dev/md/boot and /dev/md/swap which then cause dracut to fail.

I have no idea why the rescue kernel boots just fine, although it does 
not establish the above links either, rather it sets up the links 
/dev/md/<hostname>:{boot,root,swap} pointing to the assembled /dev/md125 
etc.

My particular problem is: how do I get it to boot the later kernels? 
What should be my repair process?

I have tried a boot with the rhgb and quiet removed and got no 
additional information.

BTW once booted cat /proc/mdstat gives:

Personalities : [raid1]
md57 : active raid1 sdb7[1] sda7[0]
       554533696 blocks super 1.2 [2/2] [UU]

md99 : active raid1 sdd[1] sdc[0]
       976631360 blocks super 1.2 [2/2] [UU]

md121 : active raid1 sdb2[1] sda2[0]
       153500992 blocks [2/2] [UU]

md120 : active raid1 sda3[0] sdb3[1]
       263907712 blocks [2/2] [UU]

md125 : active raid1 sde1[0] sdf1[1]
       478813184 blocks super 1.2 [2/2] [UU]
       bitmap: 3/4 pages [12KB], 65536KB chunk

md126 : active raid1 sde2[0] sdf2[1]
       1046528 blocks super 1.2 [2/2] [UU]
       bitmap: 0/1 pages [0KB], 65536KB chunk

md127 : active (auto-read-only) raid1 sde3[0] sdf3[1]
       8382464 blocks super 1.2 [2/2] [UU]

unused devices: <none>

no degraded raid devices .....


> Otherwise, you might remove "rhgb" and "quiet" from the kernel boot 
> parameters and see if there's any useful information printed to the 
> console while booting a recent kernel.
>
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos