PDA

View Full Version : Unable to boot after updating to SLES11SP2



gladys90
10-Jun-2013, 13:52
Hi all,

My system restarts after completing the basic installation (update from 11SP1 to 11SP2), however it failed to boot up to complete the automatic configuration. The grub menu display fine and when trying to boot into 11SP2, it displays the system specification(i.e. filesystem type, partition type, etc) and hang after displaying: initrd /boot/initrd-3.0.12-0.27-default
[Linux-initrd@0x378f3000, 0x6fc94b bytes].

I have tried repairing the system and updating my system again but I am still unable to boot up. I'm really not sure where the problem is and how to resolve. I do not wish to do a fresh installation as it would wipe out all previous stored data.

KBOYLE
10-Jun-2013, 19:37
gladys90 wrote:

> My system restarts after completing the basic installation (update
> from 11SP1 to 11SP2), however it failed to boot up to complete the
> automatic configuration.

Does this help?
https://www.novell.com/support/kb/doc.php?id=7011861


--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

gladys90
11-Jun-2013, 14:14
Hi Kevin,

I do not have any error message when it try to boot. The last printout is initrd /boot/initrd-3.0.12-0.27-default
[Linux-initrd@0x378f3000, 0x6fc94b bytes], followed by a blinking cursor which does not respond to any key input.

KBOYLE
12-Jun-2013, 00:18
Hi Kevin,

I do not have any error message when it try to boot.

That doesn't mean much...

An error message can point you in the right direction. The lack of an error message does not necessarily mean that there is no error. :-(

TID 7011861 describes an issue and the workaround. If initrd is not the issue, rebuilding it will not hurt.

You can check /var/log/messages for a clue but since this error happens so early in the boot process you may not find anything.

You can type "dmesg" at a console prompt and see if it provides any additional information.

gladys90
12-Jun-2013, 06:21
Hi,

There is no response when i type "dmesg", I have tried to boot into the BIS (boot installed system using the installation DVD) which give me this error: No Linux root partition found.
I have also tried to do a fresh new installation, but the same situation happens again; system hangs after boot. Only the grub details screen is displayed; last output is s initrd /boot/initrd-3.0.12-0.27-default
[Linux-initrd@0x378f3000, 0x6fc94b bytes]

I am new to Linux, may I know what should I do next to get the system up. Thank you.

gladys90
12-Jun-2013, 15:29
Hi,

I managed to boot into the installed system via the installation dvd after a few repairs. However, still cannot boot via the hard disk; still faced system freeze after showing the grub details. I have tried to perform the grub-install /dev/sda and I faced "no corresponding BIOS drive". May I know how to solve this? Thanks

gladys90
12-Jun-2013, 16:00
Sorry for the multiple posts.

Additional info: If I open the boot loader from yast2, I get this error message: because of the partitioning the bootloader cannot be installed properly

KBOYLE
12-Jun-2013, 19:44
gladys90 wrote:

>
> Sorry for the multiple posts.
>
> Additional info: If I open the boot loader from yast2, I get this
> error message: because of the partitioning the bootloader cannot be
> installed properly

It looks like you are able to boot the system. Did you try to rebuild
your initrd (mkinitrd)? If you haven't, please try to do so.

I will try to help you but when you have serious problems with your
server you may need to open a Service Request with Suse/Novell. You do
have maintenance, do you not?
http://support.novell.com/contact/getsupport.html?maintab=1

Please run this command:


fdisk -l (That's a lower case "L")


Please post the output between "code" tags to make it easy to read.
From the web interface, click on "Go Advanced" you will then see
additional formatting options. The "#" will create code tags for you.

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

gladys90
13-Jun-2013, 04:39
Hi,

I have tried to rebuild the initrd and reboot, but it is not working; boot to grub detailed screen and freeze.

I am not sure if we have the maintenance, still waiting for my head administrator to get back to me.

This is the output of fdisk -l


Disk /dev/sda: 146.7 GB, 146685296640 bytes
255 heads, 63 sectors/track, 17833 cylinders, total 286494720 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000833bb

Device Boot Start End Blocks Id System
/dev/sda1 63 33559784 16779861 82 Linux swap / Solaris
/dev/sda2 * 33559785 180361754 73400985 83 Linux
/dev/sda3 180361755 286487144 53062695 83 Linux

KBOYLE
13-Jun-2013, 06:55
gladys90 wrote:

> I have tried to rebuild the initrd and reboot, but it is not working;
> boot to grub detailed screen and freeze.

I'm not sure what to make of your drive partitioning. :-(

You have three primary partitions that allocate all of the 146 GB.

The first partition (/dev/sda1) is your swap partition. Normally this 1
or 2 GB but, if I calculated it correctly, yours is ~17 GB. I have no
idea why it should be so large.

The second partition (/dev/sda2) looks like it is your / (root)
partition. It is ~73 GB.

Because your swap partition is so large, your / partition starts at
(again, if I calculated correctly) cylinder 2089. There are so many
limitations (hardware and software) that affect a system's ability to
boot I can't remember them all. To avoid many of these issues I usually
create a small (~200 MB) /boot partition as the first partition on the
disk.

You said you upgraded from SLES11-SP1 to SLES11-SP2. That would suggest
this partitioning scheme worked with SLES11-SP1 so perhaps it is not
the problem.

I suggest you search the knowledgebase:
https://www.suse.com/support/kb/

Here are some of the documents I found that may (or may not) apply to
your issue. Have a look at them and see if they help.

https://www.suse.com/support/kb/doc.php?id=3864925
https://www.suse.com/support/kb/doc.php?id=7008279
https://www.suse.com/support/kb/doc.php?id=7001376
https://www.suse.com/support/kb/doc.php?id=7010670
https://www.suse.com/support/kb/doc.php?id=7009728

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...