[SOLVED] HP DL380 G5 with hardware Raid 1

sardinha · 04-15-2014, 07:47 AM

Usualy I prefer to use software raid, but now i'm testing install Slackware64 14.1 in a HP Server with two SAS disks configured in hardware raid 1 with Smart Array P400 controller.
It's booting with huge kernel. I'm trying with Generic Kernel without success with "kernel panic - not syncing: VPS: Unable to mount root fs on unknown-block".

/usr/share/mkinitrd/mkinitrd_command_generator.sh -l /boot/vmlinuz-generic-3.10.17

Code:

# Linux bootable partition config begins
# initrd created with 'mkinitrd -c -k 3.10.17 -f ext4 -r /dev/cciss/c0d0p3 -m cciss:usbhid:hid_generic:uhci-hcd:mbcache:jbd2:ext4 -u -o /boot/initrd.gz'
image = /boot/vmlinuz-generic-3.10.17
  initrd = /boot/initrd.gz
  root = /dev/cciss/c0d0p3
  label = 3.10.17
  read-only
# Linux bootable partition config ends

my /etc/lilo.conf

Code:

lba32
append="acpi=off ipv6.disable=1 vt.default_utf8=1"
boot = /dev/cciss/c0d0
bitmap = /boot/slack.bmp
bmp-colors = 255,0,255,0,255,0
bmp-table = 60,6,1,16
bmp-timer = 65,27,0,255
prompt
timeout = 50
change-rules
reset
vga = normal
root = /dev/cciss/c0d0p3
read-only

image = /boot/vmlinuz
  label = Huge

image = /boot/vmlinuz-generic-3.10.17
  label = Generic

my setup of initrd:

Code:

mkinitrd -c -k 3.10.17 -f ext4 -r /dev/cciss/c0d0p3 -m cciss:usbhid:hid_generic:uhci-hcd:mbcache:jbd2:ext4 -u -o /boot/initrd.gz

lilo -v

Code:

LILO version 24.0 (released 07-Juni-2013)
  * Copyright (C) 1992-1998 Werner Almesberger  (until v20)
  * Copyright (C) 1999-2007 John Coffman  (until v22)
  * Copyright (C) 2009-2013 Joachim Wiedorn  (since v23)
This program comes with ABSOLUTELY NO WARRANTY. This is free software
distributed under the BSD License (3-clause). Details can be found in
the file COPYING, which is distributed with this software.
Compiled at 17:40:54 on Oct 27 2013

Reading boot sector from /dev/cciss/c0d0
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/slack.bmp
Calling map_insert_file

Boot image: /boot/vmlinuz -> vmlinuz-huge-3.10.17
Added Huge  *

Boot image: /boot/vmlinuz-generic-3.10.17
Added Generic

Writing boot sector.
/boot/boot.6800 exists - no boot sector backup copy made.

What's I'm missing?
I can make use of Huge kernel but I thank you for any help to find a way to use Generic Kernel.

Additional help request with this server: And I have other tweak to take with cpu... "Fail to access perfctr msr (MSR c1 is 34f01bc4)

TracyTiger · 04-16-2014, 01:53 AM

Your lilo.conf file doesn't show a "initrd = /boot/initrd.gz". It needs to be there.

The lilo.conf line "root = " can cause trouble when using an initrd. You've already specified the root partition when you created the initrd. (https://www.linuxquestions.org/quest...6/#post4801795)

I use ...

image =
initrd =
label =
read-only

for each image in the lilo.conf file. I've never tried making the "root =" and "read-only" lines global as you have.

sardinha · 04-17-2014, 10:19 AM

Thank you, Tracy Tiger.
The "initrd = /boot/initrd.gz" make the difference! I removed "root = /dev/cciss/c0d0p3" as you mention too. Now it's booting with generic Kernel!

my /etc/mkinitrd.conf

Code:

SOURCE_TREE="/boot/initrd-tree"
CLEAR_TREE="1"
OUTPUT_IMAGE="/boot/initrd.gz"
KERNEL_VERSION="$(uname -r)"
MODULE_LIST="usbhid:hid_generic:uhci-hcd:cciss:ext4"
ROOTDEV="/dev/cciss/c0d0p3"
ROOTFS="ext4"
RAID="1"
LVM="0"
UDEV="1"
MODCONF="0"
WAIT="1"

Code:

/boot# mkinitrd -F

my last lines in /etc/lilo.conf

Code:

# Linux bootable partition config begins

image = /boot/vmlinuz-generic-3.10.17
  initrd = /boot/initrd.gz
  label = Generic
  read-only

image = /boot/vmlinuz
  initrd = /boot/initrd.gz
  label = Huge
  read-only

# Linux bootable partition config ends

Code:

/boot# lilo

I marked Solved, the main problem it was resolved!

The only warning log entry shown in dmesg is:

Code:

[    0.115016] Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Broken PMU hardware detected, using software events only.
[    0.115023] Failed to access perfctr msr (MSR c1 is ffa43a5a0b)

Any advice?

TracyTiger · 04-17-2014, 10:57 AM

I don't have any knowledge about your dmesg entry. Perhaps someone else at LQ may know.

Often one will get dmesg entries showing an issue of some type, but the computer will perform well in spite of the issue.

You may want to search online for some of the keywords in the dmesg log entry to help you figure out what the log message means.

sardinha · 04-17-2014, 11:42 AM

It seem that only sees one core of Xeon processor. It's a very different issue and not related with the other already solved, I will start another topic.