phone switch for our new offices. I downloaded the "AsteriskNOW-1.5.0-
i386-1of1.iso" image and burned a CD. The installation was very
straight forward but now when I try to boot the server, I get the
following error:
Cannot open root device "VolGroup00/LogVol00" or unknown block(0,0)
Please append a correct "root=" boot option
I’m guessing that it has something to do with the hardware and how the
boot blocks are identified. I am installing this on a dedicated HP
Proliant DL360 G4 server. It has 4GB memory and mirrored 146.8GB
drives. (they're being mirrored off the internal HP Smart Array 6i
64MB RAID Controller) It is a full partition that was formatted by the
installation process with nothing else on it. It’s strange that it
boots part of the way, but then fails at this instruction. That’s why
I’m guessing that the path the installer created by default isn’t how
the volumes are registered on this server. (but that’s a UNIX noob’s
assessment.)
If any UNIX gurus can look at it tonight at the meeting, that would be
appreciated. I'm guessing it's a 30 second correction of some file
path, but I am clueless when it comes to UNIX operating systems.
I believe that's an LVM related error, likely because of how the disks
are partitioned. The master boot record doesn't appear to understand
how the disks are laid out.
Yea, what he said! It's been too long since I've had to deal with
hardware and now with cloud computing maturing, I hope I rarely have
to deal with it moving forward.
I also left the AsteriskNOW installation CD on the server if we need
to reformat/install things. I will be getting to the meeting late
tonight, but if anyone wants to look at it before I get there, don't
wait for me.
I watched Ed do a reinstall of AsteriskNOW and observed this:
- It's basically CentOS.
- It sets up two partitions, one for /boot and one for LVM by default
(we didn't see a way to turn it off).
- GRUB sees the kernel on /boot just fine.
- There is no initrd in /boot, no initrd mentioned in the GRUB entry,
and no other kernel commandline options of interest. Every CentOS
install I've ever dealt with, it created an initrd because that was
necessary to bootstrap into an LVM root filesystem. Maybe I'm missing
something really important, but I don't see how it's even possible for
a stock install made in this manner to boot.
So we tried an install of Ubuntu Server and this appears to be working
just fine. But if anyone more knowledgeable has suggestions for
AsteriskNOW (seeing that his server is for Asterisk), these are the
symptoms. The only thing I can think of trying - and this slipped my
mind last night - is booting the install CD after an installation,
using its tools to chroot into the installed root FS and then generate
an initrd.
It's been too long since I've had to deal with