initrd: RAID is not started, partitions are not mounted
by Tarantula from LinuxQuestions.org on (#5DGPJ)
I have a setup consisting of on Intel Value SSD (basically a 2GB thumb drive plugged into the MB) a regular SATA SSD and an MD RAID.
The SATA SSD hosts /usr the MD raid hosts /var.
The rest is on the Intel Value SSD.
I use elilo and initrd to boot the system.
When booting something happens, the MD array is not started, no partitions are mounted.
Because /var is not mounted, I only have dmesg, but it says nothing about what is going on.
If after boot I manually start the array, I can than mount all partitions can run rc.M and the system works.
This used to work with the old 5.4.30 kernel.
Or better said with the 5.4.30 era current.
Cause the problems started when I updated to the latest current (without updating the kernel).
Got to admit I have not rebuilt the initrd image, cause I did not update the kernel.
Than I re-install the whole thing with the latest current and the accompanying kernel, but still not go.
Does anyone have any idea how could I make the boot process go step by step, maybe I can get a glimpse of why the array is not started and why no partitions (not even the basic SATA SSD) are mounted?
Or what might have changed in the latest current that the initrd images, old or newly generated no longer seem to function?
Does it have maybe anything to do with /usr being on a non-booted separate partition?
If yes does that mean that the era of /usr on separate partitions is gone?
The SATA SSD hosts /usr the MD raid hosts /var.
The rest is on the Intel Value SSD.
I use elilo and initrd to boot the system.
When booting something happens, the MD array is not started, no partitions are mounted.
Because /var is not mounted, I only have dmesg, but it says nothing about what is going on.
If after boot I manually start the array, I can than mount all partitions can run rc.M and the system works.
This used to work with the old 5.4.30 kernel.
Or better said with the 5.4.30 era current.
Cause the problems started when I updated to the latest current (without updating the kernel).
Got to admit I have not rebuilt the initrd image, cause I did not update the kernel.
Than I re-install the whole thing with the latest current and the accompanying kernel, but still not go.
Does anyone have any idea how could I make the boot process go step by step, maybe I can get a glimpse of why the array is not started and why no partitions (not even the basic SATA SSD) are mounted?
Or what might have changed in the latest current that the initrd images, old or newly generated no longer seem to function?
Does it have maybe anything to do with /usr being on a non-booted separate partition?
If yes does that mean that the era of /usr on separate partitions is gone?