I recently upgraded from OpenSuse 13.1 to OpenSuse 13.2 by downloading the iso image on a usb flash drive (no cd / dvd on my laptop). Things seemed to work for a few days, but yesterday, I shut down the computer and when I restart it, it doesn’t make it to the user login screen. What I see is the following:
[FAILED] Failed to start Load Kernel Modules.
See “systemctl status systemd-modules-load.service” for details.
Starting Apply Kernel Variables…
OK ] Started Create static device nodes in /dev.
OK ] Started Apply Kernel Variables
OK ] Started Setup Virtual Console
OK ] Started dracut cmdline hook.
Starting udev Kernel Device Manager…
OK ] Started udev Kernel Device Manager.
Starting dracut pre-trigger hook…
OK ] Started dracut pre-trigger hook.
Started udev Coldplug all Devices…
OK ] Started udev Coldplug all Devices.
Starting dracut initqueue hook…
Starting Show Plymouth Boot Screen…
OK ] Reached target System Initialization
I am a linux newbie, so I may need some additional explanation regarding some of the terms. I tried rebooting the system in Safe Mode, but I get the same error. I don’t know if this is important or not, but this screen was previously appearing on my machine when I would wake it up from hibernation, but after a few seconds, it would take me to the login screen. For some reason, after shutting down and restarting, it stopped doing that.
A few things;
Do you have an nVidia or ATI display adapter that you installed proprietary drivers for?
Does it take you to the text mode, as in you can login as root or your normal user? -> If so, login as root and run; zypper ref ; zypper up -y -l and let it install any updates. Then reboot.
On 2015-06-22 16:06, kyle lange81 wrote:
>
> Hello,
>
> I recently upgraded from OpenSuse 13.1 to OpenSuse 13.2 by downloading
> the iso image on a usb flash drive (no cd / dvd on my laptop).
Was that an Upgrade, or did you install fresh?
Ie, on boot of the DVD you can choose install, or upgrade. Which one did
you use?
Besides that, I would try disabling plymouth on boot. There is an option
for that, but I don’t remember the right spelling at the moment…
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
> robin_listas,
>
> This was an upgrade from Opensuse 13.1. If you could send me some
> instructions on how to disable plymouth, that would be great.
You have to add “plymouth.enable=0” on the kernel line, directly on the
grub screen. I can’t describe detailed instructions from memory, and
anyway I have to run. There is a dentist waiting for me…
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I tried adding this line to kernel and the installation went further before some other problems occurred. Now my output is:
[FAILED] Failed to start Load Kernel Modules.
See “systemctl status systemd-modules-load.service” for details.
Starting Apply Kernel Variables…
OK ] Started Create static device nodes in /dev.
OK ] Started Apply Kernel Variables
OK ] Started Setup Virtual Console
OK ] Started dracut cmdline hook.
Starting udev Kernel Device Manager…
OK ] Started udev Kernel Device Manager.
Starting dracut pre-trigger hook…
OK ] Started dracut pre-trigger hook.
Started udev Coldplug all Devices…
OK ] Started udev Coldplug all Devices.
Starting dracut initqueue hook…
OK ] Reached target Paths.
OK ] Reached target System Initialization
OK ] Reached target Basic System
OK ] Found device TOSHIBA_MQ01ABF0.
Starting File System Check on /dev/disk/by-uuid/ad99e800-bdb7-42b0-b100-b998471767b…
OK ] Started dracut initqueue hook.
Starting dracut pre-mount hook…
OK ] Reached target Remote File Systems (Pre).
OK ] Reached target Remote File Systems.
OK ] Started dracut pre-mount hook.
FAILED ] Failed to start File System Check on /dev/disk/by-uuid/ad99e800-bdb7-42b0-b100-b998471767b.
See “systemctl status ‘systemd-fsck@dev-disk-by\x2duuuid-ad99e800\x2dbdb7\x2d42b0\x2db100\x2db99847176c7b.service’” for details.
[DEPEND] Dependency failed for /sysroot.
[DEPEND] Dependency failed for Initrd Root File System
[DEPEND] Dependency failed for Reload Configuration from the Real Root.
Generating “/run/initramfs/rdsosreport.txt”
Entering emergency mode. Exit the shell to continue.
Type “journalctl” to view system logs.
You might want to save “/run/initramfs/rdsosreport.txt” to a USB stick or /boot after mounting them and attach it to a bug report
So I got a live USB stick and was able to do an fdisk -l output. I think that this means that /dev/sda1 is the linux partition. When I first got my laptop, it had windows installed, but when I installed linux, I didn’t see the option where I could remove the Windows partition.
When I run fsck on /dev/sda1, it finds a corrupt bit and asks if I want to fix it. I say yes, but then it doesn’t fix anything; it leaves the filesystem unchanged. Any thoughts on what I should do next? This is all very new to me.
Device Start End Sectors Size Type
/dev/sda1 2048 1026047 1024000 500M EFI System
/dev/sda2 1026048 1107967 81920 40M unknown
/dev/sda3 1107968 1370111 262144 128M Microsoft reserved
/dev/sda4 1370112 2906111 1536000 750M Windows recovery environment
/dev/sda5 2906112 363902725 360996614 172.1G Microsoft basic data
/dev/sda6 961269760 976771119 15501360 7.4G Windows recovery environment
/dev/sda7 363902976 368097279 4194304 2G Microsoft basic data
/dev/sda8 368097280 410042367 41945088 20G Microsoft basic data
/dev/sda9 410042368 961269759 551227392 262.9G Microsoft basic data
Partition table entries are not in disk order.
Disk /dev/loop0: 783.6 MiB, 821624832 bytes, 1604736 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sdb: 7.2 GiB, 7776239616 bytes, 15187968 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe28d2fda
Device Boot Start End Sectors Size Id Type
/dev/sdb1 4224 12415 8192 4M ef EFI (FAT-12/16/32)
/dev/sdb2 * 12416 1861631 1849216 903M 83 Linux
/dev/sdb3 1861632 15187967 13326336 6.4G 83 Linux
linux:/home/linux # fsck /dev/sda1
fsck from util-linux 2.25.1
fsck.fat 3.0.26 (2014-03-07)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Remove dirty bit
No action
? 1
Leaving filesystem unchanged.
/dev/sda1: 342 files, 13962/126976 clusters
linux:/home/linux # fsck /dev/sda1
fsck from util-linux 2.25.1
fsck.fat 3.0.26 (2014-03-07)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
On 2015-06-23 02:06, kyle lange81 wrote:
>
> So I got a live USB stick and was able to do an fdisk -l output. I think
> that this means that /dev/sda1 is the linux partition. When I first got
> my laptop, it had windows installed, but when I installed linux, I
> didn’t see the option where I could remove the Windows partition.
>
> When I run fsck on /dev/sda1, it finds a corrupt bit and asks if I want
> to fix it. I say yes, but then it doesn’t fix anything; it leaves the
> filesystem unchanged. Any thoughts on what I should do next? This is all
> very new to me.
fsck -a /dev/sda1
and “man fsck.fat” to read why
sda1 is not a windows partition, it is your EFI boot partition.
Your entire sda disk seems dedicated to Windows. Your other disk, sdb,
seems to be the Linux disk. Or it is the live system you used for repair :-?
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2015-06-23 04:36, kyle lange81 wrote:
>
> I tried the following:
>
> linux:/home/linux # fsck -aV /dev/sdb1
> fsck from util-linux 2.25.1
> [/sbin/fsck.vfat (1) – /dev/sdb1] fsck.vfat -a /dev/sdb1
> fsck.fat 3.0.26 (2014-03-07)
> /dev/sdb1: 6 files, 1080/2036 clusters
> linux:/home/linux #
>
>
> This did not fix the problem. When I reboot, it still hangs at “Reached
> target System Initialization”.
Well, you have to disable plymouth to see what is hidden under it…
Look, if it says:
FAILED ] Failed to start File System Check on
/dev/disk/by-uuid/ad99e800-bdb7-42b0-b100-b998471767b.
You should then find what partition is that one, and check it manually:
ls -l /dev/disk/by-uuid/ad99e800-bdb7-42b0-b100-b998471767b*
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
robin_listas, Thank you for your suggestion. I didn’t realize that the by-uuid tag represented one of the partition entries. In this case, it was sda8, which was one of the Windows partitions. I am not sure how that got broken with the linux install, but after running fsck manually on /dev/sda8, I can restart my computer and I don’t have any problems. Thanks for your patience and help, as well as gogathorp.
