Help please: I'm running SuSE 9.0 on an athlon with the most recent SuSE stock kernel. Since attempting to archive my home directory a couple of days ago I have been having progressively more serious problems, culminating this morning when I couldn't log in, even in failsafe mode. As the system boots I get a series of "failed" messages that seem to focus on being unable to touch files or change permissions on them. The final message before the boot prompt is: Failed services in runlevel 5: random SuSEfirewall2_init hotplug resmgr SuSEfirewall2_setup SuSEfirewall2_final ptal acipd postfix kbd cron xdm Skipped services in runlevel 5; smbfs When I attempt to log in either as a user or root I get the following message: FATAL: cannot change permissions of TTY: Read-only file system I have booted into the rescue system and run reiserfsck on all the partitions: /, /boot, /opt, & /home. No errors are logged. I can mount each of the partitions under the rescue system and have created text files on each of the partitions so I don't think the problem is a corrupted file system. Any suggestions as to where to go from here will be appreciated. Thanks, George -- Some mornings it just doesn't seem worth it to gnaw through the leather straps. Emo Philips
The Monday 2004-01-19 at 11:05 -0700, George H Griffin wrote:
Failed services in runlevel 5: random SuSEfirewall2_init hotplug resmgr SuSEfirewall2_setup SuSEfirewall2_final ptal acipd postfix kbd cron xdm Skipped services in runlevel 5; smbfs
I don't think you can log in if resmgr failed. Or kbd. Or... Start the rescue cd, and fsck your disks, for starters.
I have booted into the rescue system and run reiserfsck on all the partitions: /, /boot, /opt, & /home. No errors are logged. I can mount each of the partitions under the rescue system and have created text files on each of the partitions so I don't think the problem is a corrupted file system.
Mmm. Need more info. What exactly is the first error? Are any script in /etc/init.d unreadable? Any partition is full? -- Cheers, Carlos Robinson
Carlos E. R. wrote: snip
I have booted into the rescue system and run reiserfsck on all the partitions: /, /boot, /opt, & /home. No errors are logged. I can mount each of the partitions under the rescue system and have created text files on each of the partitions so I don't think the problem is a corrupted file system.
Mmm. Need more info. What exactly is the first error? Are any script in /etc/init.d unreadable? Any partition is full?
In doing additional research on the problem I learned that /etc/fstab was trashed. I repaired that file and found that the root partition was indeed full. The culprit was a 5.7 gig archive in /tmp. I deleted that and the major problems have been fixed. Thanks for the interest, I never would have thought of a full partition since root is 8.3 gig and normally less than half full. George -- George H. Griffin Powered by SuSE Linux 9.0, kernel 2.4.21 "Some mornings it just doesn't seem worth it to gnaw through the leather straps" Emo Philips
The Tuesday 2004-01-20 at 10:35 -0700, George H. Griffin wrote:
Mmm. Need more info. What exactly is the first error? Are any script in /etc/init.d unreadable? Any partition is full?
In doing additional research on the problem I learned that /etc/fstab was trashed. I repaired that file and found that the root partition was indeed full. The culprit was a 5.7 gig archive in /tmp. I deleted that and the major problems have been fixed.
Uau! 5.7 Gigabytes... You'd better find out who/what created it.
Thanks for the interest, I never would have thought of a full partition since root is 8.3 gig and normally less than half full.
Welcome. Weird things happens in that case. An educated guess / shot in the dark :-) -- Cheers, Carlos Robinson
participants (3)
-
Carlos E. R.
-
George H Griffin
-
George H. Griffin