Hello,
It just recently happened that I got a nasty problem after trying some 3d games. Trouble is somewhere in inittab file and sdb3, and not graphic crash or such - I am sure because I have descently installed ATI drivers and was running 3D effects with no problem. First game I tried to emulate was through wine but then all froze and after restart it reported something about initab, fstab,sbd or similar. But I solved it somehow with fcsk, it then seemed alright after check/repair. Then I tried another game, client for 3d game actually, written for linux(.sh file install) and noticed after that no application can be started, firefox, opera, terminal, nothing. Next reboot brought me the latest problem. This is what it says:
doing fast boot
Creating device nodes with udev
Trying manual resume from /dev/disk/by-id/ata-Hitachi_HDS721616PLAT80_PV690... **(etc)**... -part6
resume device /dev/disk/by-id/ata-Hitatchi...**(ED - SAME LINE AS ABOVE)**.. not found (ignoring)
resume device **(SAME LINE)** not found ignoring
Waiting for device **SAME LINE AS ABOVE** -part 3 to appear: ok
fsck from util-linux-ng 2.16
[/sbin/fsck.ext4 (1) --/] fsck.ext4 -a /dev/sdb3
(by less than a day, probably due to buggy init scripts). FIXED.
/dev/sdb3: Superblock last write time is in the future.
(by less than a day, probably due to buggy init scripts). FIXED.
/dev/sdb3 contains a file system with errors, check forced.
/dev/sdb3: Missing '..' in directory inode 16419.
/dev/sdb3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck failed. Mounting root device read only.
Mounting root /dev/disk/by-id/ata-Hitachi....**(AGAIN, SAME AS MENTIONED)** -part3
mount -o ro,acl,user_xattr -t ext4 /dev/disk/by-id/ata-Hitachi_HDS7216...**ETC** -part3 /root
INIT: version 2.86 booting
INIT: No inittab file found
Enter runlevel: "
Any number I enter, it will respond:
INIT: Entering runlevel: 3
INIT: no more processes left in this runlevel
After entering I can’t do anything further.
I tried to use DVD Repair option and any error concerning SDB was impossible to fix, I could only go with “Skip”. I’ve chosen to repair sdb3, by necessary delete of some other 3 partitions, not sure which but its not important now. Finished the procedure, restarted and nothing… Its still the same errors.
Suse 11.3 is coming out soon, but it would be good if I menage to start this system again and keep the data (if most of if remained anyway), so can someone please help here?