-Zeus-
November 24th, 2009, 06:24 AM
Hi,
I recently upgraded to 9.10, and have reason to believe it was an uncomplete upgrade. Upon boot, I first for an error with sreadahead, which I fixed by changing /etc/conf/sreadahead.conf to Start on filesystem.
Now, I get an error:
mountall start/spawned, process 2704
mountall:/proc: unable to mount: Device or resource busy
mountall:/proc/self/mountinfo: No such file or directory
mountall: root filesystem isn't mounted
init: mountall main process (2704) terminated with status 1
General error mounting filesystems.
A maintenance shell will now be started.
CONTROL-D will terminate this and re-try
root@laptop:~#
However, both / and /home are mounted, as is /proc. I ran a fsck.ext3 -f on / and /home, both of which came out fine. I also tried dpkg --configure -a, which did nothing.
starting X dies saying that it could not touch /tmp/.X0-lock. perhaps that is the issue?
Thanks
I recently upgraded to 9.10, and have reason to believe it was an uncomplete upgrade. Upon boot, I first for an error with sreadahead, which I fixed by changing /etc/conf/sreadahead.conf to Start on filesystem.
Now, I get an error:
mountall start/spawned, process 2704
mountall:/proc: unable to mount: Device or resource busy
mountall:/proc/self/mountinfo: No such file or directory
mountall: root filesystem isn't mounted
init: mountall main process (2704) terminated with status 1
General error mounting filesystems.
A maintenance shell will now be started.
CONTROL-D will terminate this and re-try
root@laptop:~#
However, both / and /home are mounted, as is /proc. I ran a fsck.ext3 -f on / and /home, both of which came out fine. I also tried dpkg --configure -a, which did nothing.
starting X dies saying that it could not touch /tmp/.X0-lock. perhaps that is the issue?
Thanks