gwalker2104
February 9th, 2009, 06:40 AM
Hi I am hoping someone will give me a hand. I Installed 64-bit Ubuntu Server v8.10 on a computer that has an Adaptec HOSTRaid array configured RAID1. The Ubuntu installer correctly detected the array and appeared to install everything there.
When Ubuntu boots up, I get the error ALERT! /dev/mapper/ddf1_UGA1 does not exist. Dropping to a shell!
Well, UGA is the name of the array I built in the BIOS of this computer.
I did some searching around on this forum and discovered that if I type dmraid -ay at the (initramfs) prompt and then press CTRL-D, then Ubuntu finishes booting normally.
Now this server is intended to be installed in a remote data center so it is totally unacceptable to have to type this command in every time the server is rebooted. I either need to figure out how to automatically execute the command dmraid -ay at bootup or determine the root cause of this error so that it will not happen.
Someone else suggested putting a timeout in the kernal command in the menu.lst file. I tried that, but the only thing that happens is a longer delay before I get the error.
I tried a few other kernal parameters pointed out on these forums, but none of them worked.
While I have been searching these forums, I have been downloading the huge Fedora installed. I guess I will try that next unless someone has another quick suggestion to try with Ubuntu.:(
When Ubuntu boots up, I get the error ALERT! /dev/mapper/ddf1_UGA1 does not exist. Dropping to a shell!
Well, UGA is the name of the array I built in the BIOS of this computer.
I did some searching around on this forum and discovered that if I type dmraid -ay at the (initramfs) prompt and then press CTRL-D, then Ubuntu finishes booting normally.
Now this server is intended to be installed in a remote data center so it is totally unacceptable to have to type this command in every time the server is rebooted. I either need to figure out how to automatically execute the command dmraid -ay at bootup or determine the root cause of this error so that it will not happen.
Someone else suggested putting a timeout in the kernal command in the menu.lst file. I tried that, but the only thing that happens is a longer delay before I get the error.
I tried a few other kernal parameters pointed out on these forums, but none of them worked.
While I have been searching these forums, I have been downloading the huge Fedora installed. I guess I will try that next unless someone has another quick suggestion to try with Ubuntu.:(