PDA

View Full Version : Strange etc/sysconfig/kernel issue after updating



W_ Prindl
15-Feb-2012, 17:24
Just did a full upgrade up to current date of a SLES10SP4 (and OES2SP3)
32-bit virtual machine. After reboot, the machine did not come up.
Lateron I discovered that initrd did not contain any filesystem drivers
and this was because the etc/sysconfig/kernel file did not contain any
INITRD_MODULES variables. (In fact the first lines of the file
including the line with the INITRD_MODULES variable definition were
missing.) I am quite sure, that nobody including me did manually touch
that file - only installation routines have worked with that file.

As it seems to be quite common that upgrades break the boot sequence -
why is the boot sequence so prone to errors in Linux? You hardly ever
see those types of problems with Windows, Mac Os*, or Vmware ESX, ESXi.

And this one was quite annoying as I had to download the SLES10 SP4
media, and wait for the download to succeed to get access to the system
and repair the initrd content.
--
W. Prindl

Automatic reply
23-Feb-2012, 14:30
W_,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your issue been resolved? If not, you might try one of the following options:

- Visit http://www.suse.com/support and search the knowledgebase and/or check all
the other support options available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.suse.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.suse.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your SUSE Forums Team
http://forums.suse.com

heinkonijn
26-Feb-2012, 23:53
This is a know issue, I think it's a bug in VMware tools.

For more info read:
http://www.novell.com/support/viewContent.do?externalId=7005233&sliceId=1
http://screamingadmin.wordpress.com/2010/03/18/problem-with-sles-10-sp3-and-vmware-tools/


Just did a full upgrade up to current date of a SLES10SP4 (and OES2SP3)
32-bit virtual machine. After reboot, the machine did not come up.
Lateron I discovered that initrd did not contain any filesystem drivers
and this was because the etc/sysconfig/kernel file did not contain any
INITRD_MODULES variables. (In fact the first lines of the file
including the line with the INITRD_MODULES variable definition were
missing.) I am quite sure, that nobody including me did manually touch
that file - only installation routines have worked with that file.

As it seems to be quite common that upgrades break the boot sequence -
why is the boot sequence so prone to errors in Linux? You hardly ever
see those types of problems with Windows, Mac Os*, or Vmware ESX, ESXi.

And this one was quite annoying as I had to download the SLES10 SP4
media, and wait for the download to succeed to get access to the system
and repair the initrd content.
--
W. Prindl

W_ Prindl
27-Feb-2012, 00:24
Thanks for the info, now I have one file more to check after each
install before the reboot.
--
W. Prindl


heinkonijn wrote:

>
>This is a know issue, I think it's a bug in VMware tools.
>
>For more info read:
>http://www.novell.com/support/viewContent.do?externalId=7005233&sliceId=1
>http://screamingadmin.wordpress.com/2010/03/18/problem-with-sles-10-sp3-and-vmware-tools/
>
>W_ Prindl;2399 Wrote:
>> Just did a full upgrade up to current date of a SLES10SP4 (and
>>OES2SP3) 32-bit virtual machine. After reboot, the machine did not
>>come up. Lateron I discovered that initrd did not contain any
>>filesystem drivers
>> and this was because the etc/sysconfig/kernel file did not contain
>>any INITRD_MODULES variables. (In fact the first lines of the file
>> including the line with the INITRD_MODULES variable definition were
>> missing.) I am quite sure, that nobody including me did manually
>>touch that file - only installation routines have worked with that
>>file.
>> As it seems to be quite common that upgrades break the boot
>>sequence - why is the boot sequence so prone to errors in Linux?
>>You hardly ever see those types of problems with Windows, Mac Os*,
>>or Vmware ESX, ESXi.
>>
>> And this one was quite annoying as I had to download the SLES10 SP4
>> media, and wait for the download to succeed to get access to the
>> system
>> and repair the initrd content.
>> --
>> W. Prindl