sniff - It doesn't know me anymore..

[Kyrre Ness Sjobak]

fre, 15.10.2004 kl. 17.40 skrev Bob Gustafson:
> On Thu, 14 Oct 2004 20:49:29 +0200, Kyrre Ness Sjobak wrote:
> >Urk...
> >
> >What you should have done was REMOUNTED / ro... unmounting root is an
> >incredible stupid thing to do (and i have no clue why your box did not
> >panic INSTANTLY...)
> 
> Thanks very much for your reply. Suffice to say that I take my role as
> tester seriously. I do tend to explore the fringes of Murphy's law though.
> 
> I have my system up and running now. doing a 'mv / /old' preserved my old
> system and I installed FC2-3 from CDs (this process is not quite ready for
> prime time - will add some notes later).
> 
> A 'yum update' which loaded in 642 updates last night worked pretty nicely.
> It is loading a fresh batch of updates this morning as I write.
> 
> I do have some configuration updates to make. Doing a 'mv /old/home/user1
> /home/user1' took care of my user configurations, but the /etc files may
> not behave well if I did the same thing there..  Murphy has its limits.
> 
> ----
> 
> I guess the best way to have cleaned up my root filesystem would would have
> been to boot up from my other disk (RH9) and do e2fsck on it when it was
> not part of a running system. The majority of newbies to Linux may not have
> these extra resources though.
> 
> ---- Thanks very much for your suggestions (below). They seem quite
> reasonable. Perhaps you can add these to the 'what to do if things go very
> wrong' part of the On line Linux documentation.
> 
> BobG
> 

I have never had to do it myself. Since you now have the hands-on
experience, cant you do it? And what documentation are you talking
about?

> 
> >
> >Well, you could always try the "single" boot argument - it should give
> >you a root shell without you having to enter the root password.
> >
> >tor, 14.10.2004 kl. 06.18 skrev Bob Gustafson:
> >> I did some things and then rebooted
> >>
> >> It went through the module/application stage of the reboot very quickly
> >> (too quickly) and I now have
> >>
> >>   Fedore Core release Rawhide (Rawhide)
> >>   Kernel 2.6.8-1.610smp on an i686
> >>
> >>   (none) login:
> >>
> >> I typed in all of the usual suspects (root, user1, ..), but none are known.
> >> Even when I type in 'none', it doesn't know him either.
> >>
> >> What did I do?
> >>
> >> I was a bit annoyed that it was wanting me to do an 'e2fsck'. A couple of
> >> days ago, I was able to 'umount /boot' and do '/sbin/e2fsck -p /dev/sda1'
> >> and similar on all of the partitions except '/'. Doing 'umount /' was not
> >> successful (busy, busy) and I could not do e2fsck without umounting that
> >> partition.
> >>
> >> However, there was a lazy umount option 'umount -l /'
> >>
> >> This completed fine - no busy busy complaints.
> >>
> >> But, when I went to do '/sbin/e2fsck -p /dev/sda2' on the '/' partition -
> >> it still said it was mounted and that terrible things would happen if I
> >> continued.
> >>
> >> Can you imagine that? I already had 'umount'ed it, lazy whatever. So I went
> >> ahead and did the e2fsck.
> >>
> >> And, terrible things did happen.
> >>
> >> -----
> >>
> >> I really did need to download the latest FC2 test release iso disks - and
> >> do the i2o driver installs...
> >
> >--
> >fedora-devel-list mailing list
> >fedora-devel-list at redhat.com
> >http://www.redhat.com/mailman/listinfo/fedora-devel-list