On 01/10/2015 05:35 PM, Istvan Gabor wrote:
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'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).
Any help is appreciated.
I've hit this many times, but my root is on LVM and its usually a problem with the kernel wanting lvmetad when its not there to make the LVM mapper appear. What I have to do is go into maintenance mode and set up all preliminary requirements for a CROOT, then do the CROOT and a mkinitrd with the 'proper' system, having edited the appropriate config. In my case that is /etc/lvm/lvm.conf, but that's not what applies in yours. What I would do is this. Go into rescue mode and determine the real type of file system of your Maxtor ... Part2 that seems to be root, using blkid. Make sure that is root. Mount it as /mnt and take a look. While you are there make sure that the entry in /mnt/etc/fstab is correct, according to the blkid. You seems to have some confusion over wether it is journaled or not. Is that in the fstab entry? Perhaps unmount it and run fsck with different parameters to do a whatever to the journal. Do you recall if you created it journaled? Oh, and check the /boot entry, the grub or grub2 menu line to see what it is trying to do, just to be sure. I'm not a grub expert but I've learnt what does work :-) And I stick to it :-) Ultimately you are probably going to have to run a 'mkinitrd' in the chrooted system. How this might interplay with the remake of Nvidia driver, I'm not sure. You are going to have to research that separately. But working within the chrooted system you can fix just about everything .... Eventually. The page I used, though it had to be modified slightly for suse, is part of this https://wiki.archlinux.org/index.php/boot_debugging#Mounting_and_chrooting_a... There is this, but I don't think it is quite relevant to fixing things, only finding out more about what's wrong http://freedesktop.org/wiki/Software/systemd/Debugging/#Debug_Logging_to_a_S... -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org