13.2 boot failed at Reached target system initialization

A newly updated 13.2 runs well with win 8.1 on my laptop. I was trying to boot it at safe mode but it just halt after “Reached target system initialization”. Anyone can tell me what does it mean? Thanks!

What is “safe mode”? How to you boot into it?

Sorry it should be recovery mode, one of the options in advanced option in boot menu.

Anyone can help please?

Do you have NVIDIA and did you install the NVIDIA driver?

Yes I do have a GeForce graphic card with the NVIDIA driver but it runs well. I don’t think I updated the NVIDIA driver in the recent zypper update.

That is the point it won’t be updated with the rest is is proprietary so has to be reinstalled.

You mean the reinstallation of NVIDIA driver? But basically I can’t go to anywhere. Any tips?

Can you boot to a terminal?

At boot press e find line starting linux press end key to go to end of that line enter space and a 3 press F10 to continue boot login as root type yast go to software management and in stall NVIDIA driver. Not knowing the card I can’t comment on what flavor to use. Note you may need to connect hard wired to net if normally wifi.

Thanks! I’ve followed these steps but it still doesn’t work… after F10, it reboots and halts after the 3 blinking green dots, pretty much the same as before.

I just would like something clarified here, first.

This seems to say that you can boot into 13.2 without any problem if you use normal boot…

but, that you cannot boot into openSUSE if you try the Recovery option?

Is this correct?

Or, are you not able to boot into openSUSE at all, now?

Sorry for the confusion. I couldn’t boot into the normal mode and I’ve tried with the recovery mode but couldn’t boot into it either. Basically I’m not able to boot into openSUSE at all.

How did you do the update? What method did you use?

And, from what version to version 13.2?

Did it “run well” after the update?

If so, for how long? Once, a few times, or a day or more?

What was the last thing you remember doing before it quit booting into openSUSE?

I updated the 13.1 to 13.2 by DVD.

It runs well every day for about two weeks. It has been left on or hibernate all the time unless I need to switch to Windows. There’s no extensive use recently and I do the zypper update frequently.

I can’t remember what I did exactly when I switched to Windows, but nothing suspicious. It has been failed to boot to openSUSE after Windows.

Do you have a formatted, ready-to-go USB stick handy? If so:

If you also have the 13.2 install DVD (If not, get it downloaded and burned.), boot with that and choose, 3rd item down, “Rescue System”. Click on that and wait for it to load.

It will stop with the line

Rescue login:

Type (without the quotes) “root” then press Enter.

You will now see the prompt, probably in a red font:

Rescue:~#

Do

fdisk -l

to get a listing of drives.

Note that is a lower case L, not a numeral “1”.

You should be able to tell which in the list is your USB key (sda, sdb, sdc, or …?).

In the next set of commands, replace the X with the correct letter that matches your USB key.

Do

mount /dev/sd**X**1 /mnt

Then, do

fdisk -l > /mnt/disklayout.txt

Follow that with:

df -h > /mnt/diskfull.txt

The first of the above fdisk commands will give you a readout of the disk layout. From that, you should be able to determine which are your Linux partitions.

Run

fsck -f /dev/sd**Xn**

replacing the X with the letter for that partition and the n with the number for the partition.

Do this for each of your Linux partitions.

After that, do

shutdown now

Try booting your system again. If it works, great. If not, come back here and post the contents of those two files, disklayout.txt and diskfull.txt, that were created on the USB key by the above commands.

To paste the contents, first go to the menu at the top of the Message Editor, second row of icons, near the right, press the # symbol. Your cursor should now be blinking between two CODE tags. Paste the contents of one of the files there.

Do this again, but paste the contents of the other file between the second set of CODE tags.

Gerry thank you very much for your detailed rescue guide. I’ve got no DVD right now but will follow your guide at a later time.

You can do it also from a USB stick. You don’t hae to have a DVD

I’ve done the “repair” step by step but it still stops at “Reached target System Initialization” as before. The output files are as shown below:

disklayout.txt


Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3BAC8C79-DE3F-4304-82B8-DA4BC3C1979D
Device          Start        End    Sectors   Size Type
/dev/sda1        2048    1574911    1572864   768M Windows recovery environment
/dev/sda2     1574912    3147775    1572864   768M unknown
/dev/sda3     3147776    3680255     532480   260M EFI System
/dev/sda4     3680256    3942399     262144   128M Microsoft reserved
/dev/sda5     3942400  488364031  484421632   231G Microsoft basic data
/dev/sda6   488364032  489080831     716800   350M Windows recovery environment
/dev/sda7   489080832  489490431     409600   200M EFI System
/dev/sda8   489490432  489900031     409600   200M EFI System
/dev/sda9   489900032  494110719    4210688     2G Linux swap
/dev/sda10  494110720  536057855   41947136    20G Microsoft basic data
/dev/sda11  536057856 1911576575 1375518720 655.9G Microsoft basic data
/dev/sda12 1911576576 1953523711   41947136    20G Windows recovery environment
Disk /dev/loop0: 35 MiB, 36634624 bytes, 71552 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/loop1: 9 MiB, 9437184 bytes, 18432 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/loop2: 47.9 MiB, 50200576 bytes, 98048 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/loop3: 13.7 MiB, 14352384 bytes, 28032 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/loop4: 4.1 MiB, 4325376 bytes, 8448 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.6 GiB, 8178892800 bytes, 15974400 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: 0x49464555
Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1        2048 15974399 15972352  7.6G  b W95 FAT32

diskfull.txt

Filesystem      Size  Used Avail Use% Mounted on
/dev/loop0       35M   35M     0 100% /parts/mp_0000
/dev/loop1      9.0M  9.0M     0 100% /parts/mp_0001
devtmpfs        3.9G     0  3.9G   0% /dev
/dev/loop2       48M   48M     0 100% /mounts/mp_0000
/dev/loop3       14M   14M     0 100% /mounts/mp_0001
/dev/loop4      4.2M  4.2M     0 100% /mounts/mp_0002
tmpfs           3.9G     0  3.9G   0% /dev/shm
tmpfs           3.9G  8.9M  3.9G   1% /run
tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/sdb1       7.7G   16K  7.7G   1% /mnt

You appear to have 3 EFI boot partitions. that is not at all normal. Though EFI supports multiple boot partitions you normally use only one. It is not at all clear where Linux is installed. You did not select to use NTFS file system did you??

Yes it looks interesting (annoying as well). The pre-installed win8 is on NTFS for sure but I don’t think I used that for the Linux system.