FC3 won't boot after installation on HP DL380 G4

[X-Jax]

Hello,


after a succesfull installation of FC3 on a HP DL380 G4 SCSI hardware raid, the system won't boot!

It tries to start from fd, cd, then disk and then it simply stops and does nothing!?!

starting the system by using the rescue cd works fine. I can access /mnt/sysimage, I can check everything , but.... the sysmtem won't boot from hd

Any Idea :confused:

[james_in_denver]

It sounds like your bootloader didn't get upgraded, or is not pointing to the right partition.

can you post your:
Hard disk partition information

/etc/fstab file

and either
/etc/lilo.conf (if you are using lilo)
OR
/boot/grub/grub.conf (if you are using grub)

and a dir listing of your /boot directory????

[X-Jax]

hello

here what you requested

/etc/fstab

/dev/vg01/lv00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/vg01/lv03 /usr/local ext3 defaults 1 2
/dev/vg01/lv02 /var ext3 defaults 1 2
/dev/vg01/lv01 swap swap defaults 0 0

/boot/grub/grub.conf

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/vg01/lv00
# initrd /initrd-version.img
#boot=/dev/cciss/c0d0
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core 3 (2.6.9-1.667smp)
root (hd0,0)
kernel /vmlinuz-2.6.9-1.667smp ro root=/dev/vg01/lv00 rhgb quiet
initrd /initrd-2.6.9-1.667smp.img
title Fedora Core 3-up (2.6.9-1.667)
root (hd0,0)
kernel /vmlinuz-2.6.9-1.667 ro root=/dev/vg01/lv00 rhgb quiet
initrd /initrd-2.6.9-1.667.img

and the /boot content

-rw-r--r-- 1 root root 50929 Nov 2 2004 config-2.6.9-1.667
-rw-r--r-- 1 root root 50395 Nov 2 2004 config-2.6.9-1.667smp
drwxr-xr-x 2 root root 1024 Aug 25 23:14 grub
-rw-r--r-- 1 root root 1053170 Aug 25 23:05 initrd-2.6.9-1.667.img
-rw-r--r-- 1 root root 1039614 Aug 25 23:05 initrd-2.6.9-1.667smp.img
drwx------ 2 root root 12288 Aug 26 01:02 lost+found
-rw-r--r-- 1 root root 714266 Nov 2 2004 System.map-2.6.9-1.667
-rw-r--r-- 1 root root 742506 Nov 2 2004 System.map-2.6.9-1.667smp
-rw-r--r-- 1 root root 1405861 Nov 2 2004 vmlinuz-2.6.9-1.667
-rw-r--r-- 1 root root 1370272 Nov 2 2004 vmlinuz-2.6.9-1.667smp


I did a second installation on a another DL380 and there I use only primary and extended partitions like

Part. 1 /boot primary
Part. 2 / primary
Part. 3 swap primary
Part. 4 extended
Part. 5 /var logical
Part. 6 /usr/local logical

the installation was again succesfully, but after rebooting the server it says

Loading Bootstrap ...
No Operatin System

Any Idea?

I'm now going to test it with FC2

[X-Jax]

hello again,

The FC2 installation, without LVM (not tried yet), is working fine!

Now I upgraded the FC2 to FC3 and this is booting and running also fine.
I choose the option "Skip bootloader updating"

What's wrong in FC3?

[X-Jax]

Now I upgraded the FC2 to FC3 and this is booting and running also fine.

Sorry, it's NOT working that fine :mad:

As I did a minimal installation of FC2 and I tried now to add or remove some Applications, the system pops-up with error that packages are missing.

I will try to install FC3 again by using the DVD, how knows :rolleyes:

By the way, is anyone intressted in what I'm doing here, otherwise I simply stop wasting forum space :D

[linuzlalala]

Yes,
very
interrested.
I've had the same misfortune on first boot of FC3 on a freshly reformatted drive.
Please keep updating this post.
Thx

[bricox]

I'm also having the same problem. Everything seems to install fine, but the system won't boot. The screen says it's booting from c:, but then goes blank.

[vi11an]

Same here..

Two SCSI disks in raid 0 on an adaptec controller.. Installation was fine, on reboot.. No OS found.. :(

[Mephisto]

Same here (HP Proliant DL380 server).

Booted from the FC3 rescue CD, then:
# chroot /mnt/sysimage
# grub-install /dev/cciss/c0d0
# reboot

and the thing started playing.

Ciao, Meph

PS: Still have problems with the graphics card but at least the GRUB loader will now be started.

[Void Main]

Interesting. I had FC2 installed on a DL380 (G3) and it was running fine. I upgraded it to FC3 on Monday and it's still running and booting fine. I wonder if something serious has changed between the G3 and G4? Have you tried playing around with some of the BIOS options? I can you you partition and boot info later today if you want.

[Void Main]

I just found a thread on Red Hat regarding this same issue:
https://www.redhat.com/archives/fedora-devel-list/2004-December/msg00413.html
According to this:
https://www.redhat.com/archives/fedora-devel-list/2004-December/msg00434.html

it was as simple as setting the system type to "Linux" in the BIOS (which is something I have always done on HP servers prior to installing which is why I might not have run into the problem before).

[Mephisto]

In my case the system type was set to "Linux" and it didn't work anyway. I installed a second server on the afternoon and the same problem took place again: FC3 setup didn't install GRUB correctly, I had to boot from the rescue CD and install it manually.

I've checked the contents of the master boot record before installing grub. The sector did not contain the GRUB sector code.

Ciao, Meph

[Void Main]

At least you found a workaround. To be honest now that I think about it again I might have had the same issue and booted into rescue and installed manually. I do recall having this happen to me before but don't remember it being the 580. I install on so many systems combined with my bad memory my life is a fog.

[joeSnuffy]

I had the no-boot-after-install, RHEL4 U6 for 64-bit, all of which is irrelevant as the problem was with 4x dummy LUNs being assigned to the HBA by the EMC, when I was trying to boot from local RAID adapter. GRUB isn't smart enough to know that the dummy LUNs, which were recognized as sd[a-d] by the installer kernel would not be found at POST, making the RAID card the first (hd0). Anaconda had configured it as hd4, presumably due to its assumption that hd[0-3] would be found at POST time (even though it encountered I/O errors trying to format sd[a-d]). Pulling the fibre cables and changing grub.conf to use hd0 did the trick.

[JN4OldSchool]

I had the no-boot-after-install, RHEL4 U6 for 64-bit, all of which is irrelevant as the problem was with 4x dummy LUNs being assigned to the HBA by the EMC, when I was trying to boot from local RAID adapter. GRUB isn't smart enough to know that the dummy LUNs, which were recognized as sd[a-d] by the installer kernel would not be found at POST, making the RAID card the first (hd0). Anaconda had configured it as hd4, presumably due to its assumption that hd[0-3] would be found at POST time (even though it encountered I/O errors trying to format sd[a-d]). Pulling the fibre cables and changing grub.conf to use hd0 did the trick.

Those of us that have been hanging on the edge of our seats since January 2005 thank you for sharing. I suppose the secret is to set up your dummy LUNs after you have installed the distro. That way the EMTs can find the bloody CEO after he ODs as a response to the RAID. Now, if I could just fix my bobbly-dongle I would be in good shape.