coLinux won't boot Asterisk@home

TheBigB · 02-01-2006, 04:19 PM

I'm sorry if the title's non-descriptive as I couldn't think of any better way to put it. Anyway, I installed Asterisk@Home (a specialized copy of CentOS designed to use as an Asterisk PBX) onto an extra hard drive in order to bring it into coLinux (as I have many windows-only things I need to do but I'm a n00b to Asterisk so I need AMP) I've been using Linux for years but i never got really advanced at it. Basically I did a ton of searching around to get it to work and I got as far as getting to the fsck but then it says:

Code:

                Welcome to  CentOS release 4.2 (Final)
                Press 'I' to enter interactive startup.
Starting udev:                                             [FAILED]
Initializing hardware...  storage network audio done       [  OK  ]
raidautorun: failed to open /dev/md0: 6
Configuring kernel parameters:                             [  OK  ]
hwclock is unable to get I/O port access:  the iopl(3) call failed.
Setting clock  (localtime): Wed Feb  1 00:09:12 EST 2006   [  OK  ]
Loading default keymap (us):                               [  OK  ]
Setting hostname asterisk1.local:                          [  OK  ]
Checking root filesystem
/dev/hda2 is mounted.  e2fsck: Cannot continue, aborting.


                                                           [FAILED]

*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):

I don't know how to get it to unmount it, check it, and mount it again, which it seems to not be doing. I realize there are a lot of errors here

TheBigB · 02-01-2006, 06:32 PM

Well I found out that if I get the timing right I can skip the fsck with ctrl+c but i'd prefer it check successfully so I can run it as a service. if anyone has any ideas i'd really appreciate it.

TheBigB · 02-01-2006, 06:54 PM

Alright, another update. I can skip the checks with t he fastboot kernel argument. I still want it to check it but I guess this is fine for now. I can probably check it like once a week or something manually.

TheBigB · 02-02-2006, 10:23 PM

Well I fixed it. I installed via VMWare and did some mods and it works fine

jmann · 02-16-2006, 02:32 PM

So, did you get it working in colinux when you were done, or did you just run it in vmware?

TheBigB · 02-18-2006, 04:50 PM

I installed it on a second hdd rather than an image using VMWare and then I used the mods stated in the coLinux wiki for converting Fedora to coLinux (I honestly am not positive it was for fedora that I used as I don't have the best memory :-P ) but I managed to get it to work on coLinux.

kits123 · 08-21-2007, 03:51 AM

Quote:

Originally Posted by TheBigB

Alright, another update. I can skip the checks with t he fastboot kernel argument. I still want it to check it but I guess this is fine for now. I can probably check it like once a week or something manually.

hi,
i had mailed yu regarding the same prob..
i referred to the fedora to colinux and changed the bootparams in colinux.xml to the following:

<bootparams>root=/dev/cobd0 fastboot</bootparams>

its working fine for now..
thanks a lot for yur updates.