[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: EMERGENCY 'umount /'



Hello,

per_adua32:
> So I decided to try the rescue disk. 
> 
> After booting with linux-init=/bin/sh I was dropped into bash. I then
> tried to unmount the root filesystem so that I could mount it again as
> read/write.

I think you don't want to do that - the root filesystem you are in at that
point is *not* your normal filesystem, but the rescue root filesystem.

What you probably want to do is mount your normal root filesystem under
/mnt and fix it there.

So:
  mount -t ext2 /dev/hda1 /mnt
  cd /mnt/etc/kbd
  mv default.map bkp.default.map
    OR
  mv default.map.gz bkp.default.map.gz

That should get rid of the bad keyboard mapping; I assume without one it'll
be some sort of sane default, but if not, you'll also have to do:

  cp /mnt/usr/share/keytables/us.map.gz /mnt/etc/kbd/default.map.gz

> However, when I entered the command
> 
> umount /
> 
> I got some message like can't open mtab: file doesn't exist or something
> like this.

Umounting the root filesystem is really bad... most anything you do needs
to access the disk, and if the root filesystem isn't mounted, it can't get
to it.

I'm surprised it let you do it at all.


Jiri
-- 
<jiri@baum.com.au>
We'll know the future has arrived when every mailer transparently
quotes lines that begin with "From ", but no-one remembers why.


Reply to: