vicidial.org

Hi,

I'm installing Vicibox 3.1.7 on a Dell R410, with a RAID controller.

Everything goes well until the end of os-install script. After it boots up, I get this:

Code: Select all

doing fast boot
FATAL: Module processor not found.
FATAL: Module thermal not found.
FATAL: Module fan not found.
Creating device nodes with udev
Waiting for device /dev/disk/by-id/scsi-......
Id not find /dev/disk/by-id/scsi-....
Want me to fall back to /dev/sda2? (Y/n)


I get no keyboard action at this time, so can't type Y ou N

I hope someone had this problem ou somenthing like this to give me an idea on what to do.

1) look at the previous notes regarding vicibox redux and some startup issues after os-install (especially on raid).

2) consider trying goautodial, even if just to see if it works.

I have installed vicibox 3.0.8 on R410 with PERC H200 controller ( raid1 )

** Only the 64 bit version worked

Ok thanks for the tips. I had previosly looked at some reports here of some related situation, but my thougth was to find something more specific, because all the solutions sounded like work-arounds: install other OS CD and install vicidial stuff, or remove the RAID Card and use the onboard controller. Not that they are not an option, but if we can find a way to fix them, that would be better.

Well, I followed kumba's advice on removing Grub, listed on the link that william posted above, and during the os-install I got some wierd messages, that I didn't notice before, but at the end of the script, when writing grub, I got an error.

As I'm no Linux Guru, my guess the 2 messages bellow are related, I didn't know there was a limit of 128 GB on the boot partition.

My partitions are divided like this:

sda1 = swap 4Gb
sda2 = / ext3 1.81 TB


This message shows up on the summary screen, before you confirm the install.

Code: Select all

Booting
The bootloader is installed on a partition that does not lie entirely below 128 GB. The system might not boot.       



This one shows up after the installation script starts to write boot information.

Code: Select all

GNU GRUB  version 0.97  (640K lower / 3072K upper memory)
[ Minimal BASH-like line editing is supported.  For the first word, TAB
lists possible command completions.  Anywhere else TAB lists the possible
completions of a device/filename. ]

grub> setup --stage2=/boot/grub/stage2 --force-lba (hd0,0) (hd0,0)
Checking if "/boot/grub/stage1" exists... no
Checking if "/grub/stage1" exists... no

Error 15: File not found
grub> quit


My next options here are, create a smaller partition for / and boot information. (which I'm doing right now)
And if this don't work, use an older version 3.0.8 64bits as iulianm recommended.

Plan B is to tell the client to buy other cheaper server that would work too and use this Dell server to something else, like print server... lol... But if I can make this work, it would be great to not go down that road.

Any advices from the linux gurus out there ?

thanks

Ok . But did you tried with 3.1.7 64 bit?

I have tried with 3.0.8 32 bit and was not working ... only 64 bit was working for me. That was the latests in that moment .

what raidcontroller are you using?

Hi again,

It seems that this problem I'm having is much deeper than simply Vicibox ISO compilation.

I googled "grub r410" and got a lot of forums with people relating the same problem in a variety of linux distros.

This one solved the issue on Ubuntu, and I'm gonna try the same.
http://stoilis.wordpress.com/2009/11/20 ... dell-r410/

As it needs physical access to the server, it will take a little while for me.

@iulianm: yes, 64bit since the beginning. if the above fails I'll try 3.0.8 64bit

@Michael_N: I actually don't know, I don't have phisical access to it. But I asked my client for the details on the server, no answer yet. I'm guessing it is a PERC H700.

thanks

Wow. 35-seconds. That is amazing.