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...) 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...
