В Sat, 10 Jan 2015 23:35:53 +0100 (CET)
Istvan Gabor
Hello:
This is on openSUSE 12.2. Before the problem I installed NVIDIA drivers during which I could see long message in YaST window (unusual). I don't know if this has to do anything with my problem.
When I try to boot the system, GRUB starts to load it, but it the boot stops with the following. (I abbreviate the device name.):
------------------------------------------
Boot logging started on /dev/tty1(/dev/console) at Sat [snip] Waiting for device /dev/disk/by-id/ata-Maxtor_...-part2 to appear: ok fsck from util-linux 2.21.2 [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/sda2 /dev/sda2: clean, .../... files, .../... blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/disk/by-id/ata-Maxtor_...-part2 mount -o rw,acl,user_xattr -t ext3 /dev/disk/by-id/ata-Maxtor_...-part2 /root [ 3.597595] EXT3-fs (sda2): error: no journal found. mounting ext3 over ext2? mount: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail os so could not mount root filesystem -- exiting to /bin/sh sh: cannot set terminal process group (-1): Inappropriate ioctl for device sh: no job control in this shell $_
--------------------------------------------------------------------
I could boot another system where I could mount the named /dev/disk/by-id/ata-Maxtor_...-part2 (/dev/sda2) device without problem. I also could run fsck on it, which did not show any error.
I wonder if this could have removed journal.
I've never seen such thing before and now I am stucked, don't know to do, how to fix this. Google did not brought up anything useful (at least for me).
If you are absolutely sure it was ext3 system you could use "tune2fs -j" to add journal back. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org