Whenever I try to install Asterisk@Home, I get this error at about 43% There was an error installing rpmdb-redhat-3.4-0.20050105. This can indicate media failure, lack of disk space, and/or hardware problems. This is a fatal error and your install will be aborted. Please verify your media and try your install again. I've gotten this on 3 different cd's I've burned. To make sure it wasn't a hardware problem of some sort, I installed Debain last night. Went without a hitch, but *@Home doesn't like it... Any ideas as to why?
--- Scheda <scheda@gmail.com> wrote:> Whenever I try to install Asterisk@Home, I get this > error at about 43% > > There was an error installing > rpmdb-redhat-3.4-0.20050105. This > can indicate media failure, lack of disk space, > and/or hardware > problems. This is a fatal error and your install > will be aborted. > Please verify your media and try your install again. > > I've gotten this on 3 different cd's I've burned. To > make sure it > wasn't a hardware problem of some sort, I installed > Debain last night. > Went without a hitch, but *@Home doesn't like it... > Any ideas as to > why?Scheda, You _did_ verify that you have sufficient disk space, right? I recently installed Linux on an old 6 GB hard drive and forgot to tell it to take the whole drive, so it only took what was left over after a Win2000 installation (not much was left, obviously), and I got the same error before the OS finished installing. Doesn't hurt to double check using df. Other than that, I don't know ... looks like it's not the media, unless those CDs won't let you install on a different Linux box either. Hardware problems can be a pain to isolate ... good luck! Cheers, Maya __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/
Scheda wrote:>Whenever I try to install Asterisk@Home, I get this error at about 43% > > There was an error installing rpmdb-redhat-3.4-0.20050105. This >can indicate media failure, lack of disk space, and/or hardware >problems. This is a fatal error and your install will be aborted. >Please verify your media and try your install again. > >I've gotten this on 3 different cd's I've burned. To make sure it >wasn't a hardware problem of some sort, I installed Debain last night. >Went without a hitch, but *@Home doesn't like it... Any ideas as to >why? > >I have had similar problems with various installations, all traceable to a CD drive that the install didn't like. RH8, RH9, Fedora and the Asterisk@home All the CD's were fine, and changing out the drive resulted in repeatable installs. All the drives were usable with a different OS ( not Linux ) Seems that some versions of the install are impatient about the CD drive. But then I was using used surplus drives. On a somewhat related note, CentOS, once installed from the CD, when restarted, runs Kudzu on boot, and SOME network cards that installed fine are "killed" by Kudzu , and no longer work. The 3Com card is one, and this problem has existed since FC1, Mandrake10, and probably others. Wouldn't you think that would have been corrected by now? John Novack> >
> Whenever I try to install Asterisk@Home, I get this error at about 43% > > There was an error installing rpmdb-redhat-3.4-0.20050105. This > can indicate media failure, lack of disk space, and/or hardware > problems. This is a fatal error and your install will be aborted. > Please verify your media and try your install again. > > I've gotten this on 3 different cd's I've burned. To make sure it > wasn't a hardware problem of some sort, I installed Debain last night. > Went without a hitch, but *@Home doesn't like it... Any ideas as to > why? > _______________________________________________I've had problems installing Asterisk @ Home on my IBM Netfinity system (dual P-233MHz, SCSI, blah, blah). It just won't install. I thought I had bad CD's but tried them on another system and they worked fine. I don't remember the error, but it wouldn't even start the install. If you have another PC, I'd try installing it on that. I think it'd be much easier and quicker than trying to figure out a hardware problem (and save some hair, if you have any left)