Not asking for help. (only wanted to let others know what I saw)
Did an upgrade (from a working 12.3) using the 13.2 DVD. All the normal packages/files were updated o.k. – but there was NO initrd-3.14.0-rc5-1 file generated in /boot – therefore trying a boot-up of 13.2 stopped with a kernel panic. [Tried the update again - SUSE install still did not generate the initrd file.] I wish the init process would show an error message when something as vital as the initrd file fails to be generated.
13.2 does not exist. I’m assuming that you mean 13.2-Milestone 0.
You can file a bug report on this. I’ve asked moderators to move the thread to the beta forum.
On 04/25/2014 06:06 PM, mikus wrote:
>
> Not asking for help. (only wanted to let others know what I saw)
>
> Did an upgrade (from a working 12.3) using the 13.2 DVD. All the normal
> packages/files were updated o.k. – but there was NO initrd-3.14.0-rc5-1
> file generated in /boot – therefore trying a boot-up of 13.2 stopped
> with a kernel panic. [Tried the update again - SUSE install still did
> not generate the initrd file.] I wish the init process would show an
> error message when something as vital as the initrd file fails to be
> generated.
I know you are not looking for help; however, as 13.2 is in M0, you should
report this in the prerelease-beta forum, or on the openSUSE Factory mailing
list at opensuse-factory@opensuse.org.
In my case, I follow that mailing list and install the various Mx releases on
VMs. Only when it starts to be reasonably stable, then I install it along side
my operating version. For most releases, M4 or M5 is the first release that gets
into a real machine.
Thread closed temorarily and will move to beta forum (nntp users please note).
Thread moved and open for user consumption.
On 2014-04-26 02:26, malcolmlewis wrote:
>
> mikus;2639237 Wrote:
>> Not asking for help. (only wanted to let others know what I saw)
>>
>> Did an upgrade (from a working 12.3) using the 13.2 DVD. All the normal
>> packages/files were updated o.k. – but there was NO initrd-3.14.0-rc5-1
>> file generated in /boot – therefore trying a boot-up of 13.2 stopped
>> with a kernel panic. [Tried the update again - SUSE install still did
>> not generate the initrd file.] I wish the init process would show an
>> error message when something as vital as the initrd file fails to be
>> generated.
>
> Thread moved and open for user consumption.
AFAIK, it is a known issue. 13.2 is going to use Dracut, and there are
problems.
Vital? Yes. So? It is a Beta…
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I did install OpenSUSE 13.2 yesterday, and got bitten by the same problem (the upgrade doesn’t replace “mkinirt” with “dracut” and thus doens’t generate the necessary initrd files)
In 13.2, “mkinitrd” is a script that runs “dracut”.
On 2015-01-13 17:06, dr-yak wrote:
>
> robin_listas;2639256 Wrote:
>> AFAIK, it is a known issue. 13.2 is going to use Dracut, and there are
>> problems.
>>
>> Vital? Yes. So? It is a Beta…
>
> I did install OpenSUSE 13.2 yesterday, and got bitten by the same
> problem (the upgrade doesn’t replace “mkinirt” with “dracut” and thus
> doens’t generate the necessary initrd files)
Well, now 13,2 is no longer a beta, so you are posting on the wrong
forum 
But you could expand that information. Fresh install, upgrade, what kind
of upgrade… symptoms…
But better in the install-boot-login forum, not the beta forum.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)