vicidial.org

Hi there, log time lurker, first time poster.

I've been stressing over being unable to install the newest (3.1.8, downloaded yesterday) ISO image and just now came across an interesting issue. The server would freeze immediately after grub went to the kernel, inidcating the drive could not be found, and asking if I'd like to fall back to my main drive (/dev/sda2). Much searching later allowed me to identify this as a kernel issue, where the megaraid_sas drivers were missing.

There are two kernels installed on the iso: 2.6.34-12 and 2.6.34.7.0.7. By default the system attempts to load -12, which is missing the megaraid_sas drivers (and other stuff like USB drivers). The .7 kernel has everything and boots normally.

To fix my no-boot i simply added a line to grub for the .7 kernel, and voila!

But, which kernel is the intended one for Vicidial? Should i attempt to fix the -12 kernel, or am i safe to stick with .7?

Thanks,

-Matt

Is this during the .iso install or after install after removing the .iso and attempting to boot from the freshly installed OpenSuSE OS?

Hi mmeier,williamconley

Actually when i installed the vicibox 3.1.8 version i also had the same problem. It just happens that vicibox 3.1.6 works on my server but i really wanna try vicibox 3.1.8.

As per williamconley's question, it happens after the os install and booting on the hard drive.

@mmeier
What line exactly did you add? Is it ok if i ask that specific line and how to do it? Thank you in advance ...

he likely modified the menu.lst file in the grub folder. but for your first boot you can modify it directly on the grub itself (there are directions visible if you press a button during the countdown to allow interaction with grub).

hit e

then go to the line you want to edit and hit e again.

make your change and hit b to boot

NO changes there will survive a reboot, however, so you'll need to modify the menu.lst file for a permanent fix

you could have just used zypper refresh and zypper up to get to the 3.1.8 from 3.1.6 read through a few of these posts on this board (the vicibox server install board)

@William,

Yes. I did simply edit the /boot/grub/menu.lst and added this to the end:

Code: Select all

title openSUSE 11.3 (2.6.34.7)
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.34.7-0.7-default root=/dev/sda2 resume=/dev/sda2 splash=silent quiet showopts vga=0x31a
    initrd /boot/boot/initrd-2.6.34.7-0.7-default


After testing that it worked I also set the default X value to represent that option (1st = 0, 2nd = 1, etc.) so it would boot fine.

This was the initial hard disk boot after the os-install. I tried several 64 bit versions found on the web, but they all seemed to have a problem with the kernel. I didn't know it was the kernel first, so I went through the process of re-partitioning my raid array, swapping drives, etc..

I discovered this when a google search for the no-boot issue described using mkinitrd to rebuild my initrd files. During the build for the other kernel it told me a number of necessary drivers weren't found, so I manually checked the folders and was missing the LSI MegaRaid drivers and USBHID. Explained both the no-boot and inability to press "Y" at boot time to get the minimal shell.

Btw, this won't affect everyone. Generic RAID drivers and PS2 stuff is in there, it's only us LSI boards (Dell 1950) with USB keyboards who were hooped.

Still though, is there a reason to use the -12 kernel? Just want to make sure there's nothing custom built-in to that one.

@Randy,

If you want to try this I'd first make sure you're modifying the correct menu.lst. You'll want to mount the drive (mount /dev/sdaX /mnt) and edit those accordingly.

Hope this helps,

-Matt

Also, in the code provided make sure you're using the drive appropriate for your build. You can usually scrape this from the old -12 kernel options.

This also solved my problem as well. Dell PowerEdge 2950 and 1950, using Vicibox 3.1.8 64bit.

Thank you!!