major issue. no boot

**kirkface8** · November 5th, 2010

as i boot the plymouth starts.
which is just the text based one saying ubuntu with the "."(fullstops) changing color.
pushing f1 displays

Code:

init: plymouth main process (339) terminated with status 1

**kirkface8** · November 5th, 2010

booting standard it has the text plymouth. ubuntu with the fullstops changing color below.pushing f1 displays the plymouth process has been terminated.

recovery mode runs commands then halts at.

Code:

init: mountall main process (422) terminated with status 1
init: failed to spawn mountain post-stop process: unable to exectue: Permission denied

i cant right it all down but its then followed by the same structure. etc 'init: failed - Permission denied' by the processes
spawn plymouth
spawn mountall
spawn mountall-shell
spawn udev

all of these are unable to execute

**chaanakya_chiraag** · November 5th, 2010

That is a big problem...I think that means the permissions are wrong on the boot scripts or something...not sure though...

**kirkface8** · November 5th, 2010

ahh dammnit. this is really bugging me

**kirkface8** · November 5th, 2010

im wondering if this could be something to do with the time. the problem seemed to arouse from 12am on the dot. and was working perfect all day

EDIT: http://ubuntuforums.org/showthread.php?t=1335937 is that similar to my issue?

**chaanakya_chiraag** · November 6th, 2010

I don't think it is unless you edited /etc/conf/sreadahead.conf. I think the best thing to do is to boot up a live cd, back up all your stuff, and reinstall.

**kirkface8** · November 7th, 2010

Originally Posted by chaanakya_chiraag

I don't think it is unless you edited /etc/conf/sreadahead.conf. I think the best thing to do is to boot up a live cd, back up all your stuff, and reinstall.

yeah i didnt edit it.
ive got a backup buts its not heeps recent but if i cant find a solution i shall use the backup

**chaanakya_chiraag** · November 7th, 2010

Basically, if even the recovery mode isn't working...you have a MAJOR problem, and even if you DO manage to get things working again (a.k.a actually make it boot up), things will probably be completely screwy anyway. Therefore, I would definitely just do a backup and reinstall.