[opensuse] boot stops with "could not mount root filesystem -- exiting to /bin/sh"
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. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 2015-01-11 00:04, Anton Aylward wrote:
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?
Further to that, the error is saying it thinks the filesystem is ext2 (no journal) but fstab specifies ext3 (no journal). By the way, 12.2 is too old. I would not try to tinker with Nvidia driver installation on it, now (years after its time). -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
"Carlos E. R." írta:
By the way, 12.2 is too old. I would not try to tinker with Nvidia driver installation on it, now (years after its time).
Well, I do know that. Now I explain why I'm still using it. 1. I installed this system one and a half years ago. I find the ~18 month life cycle too short. I don't have time and don't want to install my system so frequently. I prefer to keep the configured and installed system longer. Furthermore I don't like to install the most recent versions because they cause too much trouble for me. 2. The other reason I keep oS 12.2 is that this is the last version where I could make hal work. hal is necessary for KDE3 automounting and I prefer KDE3 to any other desktops . Though recently I've been experimenting and learning KDE4 (as you can see my several posts regarding KDE questions) I still find it much clumsier than KDE3. I don't see any advantage of KDE4 to KDE3 but for my use case there are several disadvantages. (Not only that KDE4 lacks features that KDE3 offers but the way of configuring the desktop is overcomplicated.) But please don't turn this into a discussion on KDE3/KDE4. I don't mean these notes against KDE4 (I'm over that by now) I just wanted to explain why I'm still using an outdated system with an "outdated" desktop manager. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-12 00:04, Istvan Gabor wrote:
"Carlos E. R." írta:
By the way, 12.2 is too old. I would not try to tinker with Nvidia driver installation on it, now (years after its time).
Well, I do know that. Now I explain why I'm still using it.
1. I installed this system one and a half years ago. I find the ~18 month life cycle too short. I don't have time and don't want to install my system so frequently. I prefer to keep the configured and installed system longer. Furthermore I don't like to install the most recent versions because they cause too much trouble for me.
11.4 Evergreen still gets some maintenance :-) That's way longer than 18 months. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Anton Aylward írta:
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.
OK, that helped. blkid reported that the filesystem was ext2. I have converted it to ext3 using tune2fs (as Andrei suggested). After that oS 12.2 booted normally. What I don't understand why the original ext3 root filesystem became ext2. I am sure it was ext3, because fstab was not modified. Anyway, it's not that important to know. Thanks all for your help. Istvan. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/11/2015 05:35 PM, Istvan Gabor wrote:
What I don't understand why the original ext3 root filesystem became ext2. I am sure it was ext3, because fstab was not modified. Anyway, it's not that important to know.
My guess is that for some reason it could not find the journal at boot so assumed (and hence converted it to) a ext2. (anton waves hands, shrugs shoulders, gives a silly grin...) -- /"\ \ / 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
В 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
On Sun, 11 Jan 2015 09:17:49 +0300 Andrei Borzenkov wrote:
If you are absolutely sure it was ext3 system you could use "tune2fs -j" to add journal back.
That's brilliant :-) I'd also suggest using clonezilla or dd or something comparable to grab a backup image of the partition in question, just in case. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrei Borzenkov -
Anton Aylward -
Carl Hartung -
Carlos E. R. -
Istvan Gabor