On 05/05/2015 10:21 PM, Frans de Boer wrote:
On 05/05/2015 08:00 AM, Per Jessen wrote:
Frans de Boer wrote:
OK, I compiled a new kernel for the 13.2 release and was installing it. I have to manually copy bzImage and System.map because I do not use the make install which requires the perl-Bootloader to be available.
Before I just did mkinitrd -B and the initrd file was made. Now that is part of dracut and I can't create a new initrd file. The message log states that many modules are not supported - like "Module "raid1.ko" is not supported......". This is true because I did not compiled this as a module, but as a build-in.
You say "I can't create a new initrd", but below:
My system is not booting because it is waiting for my drives to appear. The exact same config is used under 12.3 and of course working. Now with dracut I run into problems.
you're booting your system so I guess you do have an initrd?
It sounds like you need to look at the config of the initrd & the kernel - when raid support is built in, your array should become available without extra effort. After reviewing the config, the next step is probably to attach a serial console and capture the console output so you can see what's going on.
Sorry, I had to say "it seems I can't create a working initrd". I used the exact same config as under 12.3, and still the machine hangs by counting "[x of 3] start jobs....". I now use the "make install" command for the kernel as it seems to work, It does not complain about the absence of perl-BootLoader anymore.
I use a construct of a mastergrub partition with chainings to the relevant openSuSE distributions/partitions. Anyhow, whatever I do, nothing seems to work for creating an initrd gets me booted. Back in the days when mkinitrd was not hijacked by dracut, things did work always.
Has there to be anything special within the compiled kernel? If no answer, I will install perl-bootloader in the hope that this will solve the problem - hoping that starting the mastergrub code does not get nuked.
I will also remove the initrd as provided by the distribution and recreate it again. Let's see if the same problem occurs.
Frans. And No, I recreated the initrd for the stock kernel and everything worked...:\ So, maybe not the initrd creation is at fault, maybe something in the kernel itself? If so, what has changed between 12.3 and 13.2 that the kernels compiled do not proceed with the boot process but seem to wait for disks. my guess is the dracut modules?
Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org