My linux system froze when trying to run the 2.0b4 Netscape. I had to
power cycle to get out of that. Now the boot fails as follows:
Dec 23 17:20:20 init: version 2.4 booting
init: cannot execute "/etc/rc.d/rc.S"
Dec 23 17:20:20 init: cannot execute "/etc/rc.d/rc.S"
init: Entering runlevel: 5
init: cannot execute "/etc/rc.d/rc.M"
Dec 23 17:20:20 init: cannot execute "/etc/rc.d/rc.M"
_setuent: can't open utmp file: no such file or directory
I get a login - it's in multi-user mode, not single user. I can log in as
root. Only the root file system is mounted, and it's read-only. I cannot
mount any other file systems (/tmp, /usr, /var, /var/spool, /home),
because the mount command wants to write a lock file to the read-only root
file system. I understand that just about all my symptoms stem from the
fact that the rc.d files were not processed.
I have tried the following:
1. I can read all files in rc.d, they look ok.
2. I can mount all file systems after booting from the emergency boot
3. I have repaired all file systems. Only a couple had errors, and they
were bitmap errors, seemed pretty normal for a power cycle.
4. I cannot remount the root filesystem as read write. I tried "mount -o
rw -o remount /dev/hda4 /" and only got the usual complaint about not
being able to write the lock file.
5. /tmp is normal, mounted or not; 777 is what I remember.
6. /var/spool is 85% full, all the others are much less.
7. Booting linux from LILO with "single" added has the only affect of
asking for a run level, but still gives the same "cannot execute rc.[SM]"
8. Find of all files newer than the 2.0b4 netscape tar file found only
/etc/passwd (I added a different root entry from the emergency disk boot),
/dev/tty, /dev/ttyp[1-4], and root's .bash_history.
This is Linux 1.2.13, ELF, X 3.1.2. 16MB RAM, Pentium overdrive on a
486 motherboard. The upgrade process from the original slackware 2.1 has
been somewhat twisted, but all has functioned that way for several months
before this crash.
I am really lost here. If you think you know what is going on, PLEASE
call collect 1-510-679-9806. I don't even care if you use 1-800-COLLECT!
If you want to respond by email with suggestions, I'd rather waste a
dollar or two on a collect call, but try me work email if you have to:
several times a day. Posting is similar: post if you must, but if you
have anything useful, I WOULD RATHER YOU CALL COLLECT. I have to post
this from MS-DOG WINDOZE.
I do have backups, maybe a month old, and will spend Wednesday seeing if I
can find some useful differences, maybe restoring. But I have no real
I am even willing to pay consulting fees, based on you fixing my problem.
And to show how desperate I am, if you call (COLLECT :-) and I think you
have a real good chance at fixing this, I would be willing to drive the
damn box over to you, and still pay some kind of reasonable fee. I live
halfway between SF and Sacramento.
I had big plans for my computer this holiday, and they have sure