"cannot remove /var/run/console.lock"

[Norberto Quintanar]

The first thing to try is to boot to single user mode. This MIGHT not
work for you, because your system might be configured to still ask
for a root password to get to single user mode. If that's the case,
we'll use another trick that replaces init with /bin/bash. 

First, try single user, just type "linux single" and that should do
it.  You should get a fairly normal looking boot sequence except that
it terminates a little early at a bash prompt. 

If you do get the prompt, the / filesystem may not be mounted rw
(although "mount" may say it is). Do 

mount -o remount,rw /

If that doesn't work (it might not), just type "mount" to find out
where "/" is mounted. Let's say it is on /dev/sda2. You'd then type: 

mount -o remount,rw /dev/sda2

If you can do this, just type "passwd" once you are in and change it
to whatever you like. Or just edit /etc/shadow to remove the password
field: move to just beyond the first ":" and remove everything up to
the next ":". With vi, that would be "/:" to move to the first ":",
space bar once, then "d/:" and ENTER. You'll get a warning about
changing a read-only file; that's normal. Before you do this,
/etc/shadow might look like: 

root:$1$8NFmV6tr$rT.INHxDBWn1VvU5gjGzi/:12209:0:99999:7:-1:-1:1074970543
bin:*:12187:0:99999:7:::
daemon:*:12187:0:99999:7:::
adm:*:12187:0:99999:7:::

and after, the first few lines should be: 

root::12209:0:99999:7:-1:-1:1074970543
bin:*:12187:0:99999:7:::
daemon:*:12187:0:99999:7:::
adm:*:12187:0:99999:7:::

You'll need to force the write: with vi, ":wq!". (If that still
doesn't work, you needed to do the -o remount,rw, see above). 

Another trick is to use the kernela argument "init=/bin/bash"  This
will dump you to a bash prompt much earlier than single user mode,
and a lot less has been initialized, mounted, etc. You'll definitely
need the "-o remount,rw" here. Also note that other filesystems
aren't mounted at all, so you may need to mount them manually if you
need them. Look in /etc/fstab for the device names. 


--- raiyza <info@rayza.biz> wrote:

> on 7/8/04 12:42 PM, Andrew at virgule88@videotron.ca wrote:
> 
> Thanks Andrew,
> will try to be more specific with the detail.
> What I did was load the base install from the installation cd over
> my
> existing linux operating system.
> This had no effect in that I am still unable to login.
> 
> > check in /root/install.log or maybe even in
> /root/install.log.syslog.
> > These two are created by Anaconda during the installation
> process. All
> > the others 'real' logs are in /var/log/XFree86.*.log, dmesg,
> boot.log,
> > messages are the most important.
> 
> When try to open:
> /root/install.log, /root/install.log.syslog and
> /var/log/XFree86.*.log
> get a message saying no such file or directory.
> The other logs seemed to contain nothing sinister.
>  
> > What have you tried exactly? How have you tried to open glade?
> 
> All I did was glade <return> from the command line when I go to
> linux 1 at
> boot.
>  
> > hmm... You typed in your username <return> then your password
> <return>
> > and nothing is happening?
> 
> Correct, it just takes me back to an empty login box.
> -- 
> Regards, ray.
> 
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
>
http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> HINT: to Google archives, try  '<keywords>
> site:terrasoftsolutions.com'
> 



	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail