No more KDE in openSUSE 13.2 after installation of tumbleweed

English Install/Boot/Login
1

Hi all!

I made a fresh install of tumbleweed on a triple boot machine (13.2, now tumblewee, win xp).

Trying to boot 13.2, partly it is a bit difficult to enter the password for the encrypted /home, but even if I manage to do that I end up in maintenance mode.

Running fsck from there on the partition with /home on it, and smartctl, everything looks fine, and I can access the encrypted /home of 13.2 if I boot into tumbleweed.

Disk label: “msdos” (no EFI).

Can it be that grub2 of tumbleweed causes the problem?
Because grub2 of tumbleweed - to my understanding - is loaded after the installation of tumbleweed, for which the boot flag obviously is set (I could check that), no matter which oS is then bootet.

Any ideas?

2

Show fdisk -l

3

This is the output of parted -l:

Model: ATA ST2000NM0033-9ZM (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system     Flags
 1      32,3kB  33,6GB  33,6GB  primary   ntfs            type=07
 2      33,6GB  67,1GB  33,6GB  primary   ext4            type=83
 3      67,1GB  101GB   33,6GB  primary   ext4            boot, type=83
 4      101GB   2000GB  1900GB  extended                  type=05
 5      101GB   107GB   6442MB  logical   linux-swap(v1)  type=82
 6      107GB   245GB   137GB   logical                   type=83
 7      245GB   382GB   137GB   logical                   type=83
 8      382GB   2000GB  1618GB  logical   ntfs            type=07

root of oS 13.2 is on /dev/sda2,
root of tumbleweed is on /dev/sda3 (with the boot flag).

Encrypted /homes of sO 13.2 and tumbleweed are on /dev/sda6 and /dev/sda7, respectively.

I have an idea: perhaps moving the boot flag from /dev/sda3 to /dev/sda2 may solve the problem.

4

Nope, moved boot flag using gparted, but it didn’t work.

Last message from journalctl -xb in emergency/maintenance mode is:

May 21 17:46:54 myHost systemd[1]: Received SIGTERMIN+21 from PID 209 (plymouthd).

I’ll try

systemctl default

from there now.

5

Ah, this is interesting, but I have to type it by hand:

 589.721...] EXT4-fs (sda7): VFS: Can't find ext4 filesystem

Will post the results of mount.

6

Not yet.

Saying

shutdown -h now

I get the prompt to enter the password for the encrypted /home directly afterwards, a highlightened message.

7

Hmpf.

Have to sort out how to move boot flag again using the command line.

Will take a bit.

8

OK, I’m back.

Didn’t want to type the output of mount.
Here it is:

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=1955364k,nr_inodes=488841,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
/dev/sda2 on / type ext4 (rw,relatime,data=ordered)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda1 on /windows/C type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/sda8 on /windows/D type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/sda3 on /sys421 type ext4 (rw,relatime,data=ordered)
/dev/mapper/cr_home on /home type ext4 (rw,relatime,data=ordered)

And now?

Should I re-install grub2 for oS 13.2 using the command line?

Can anybody please help me with the necessary commands for that?

9

Don’t think grub is the problem seems to be a missing or corrupt partition. Did you move or resize anything? it my have changed the UUID which also would stop a mount

BTW Is that the 13.2 mount or the TW mount???

10

No no, I didn’t resize or repartition anything.

I just installed tumbleweed.

Which runs fine, besides.

And as I told, I can access the encrypted /home of 13.2 after booting tumbleweed.

11

It’s a bit weird, just checked it all again.

But thinking about it again, it doesn’t seem logical that this is caused by the installation of tumbleweed, because if I move the boot flag then grub2 of oS 13.2 is loaded at boot.

Perhaps it rather was a recent update of oS 13.2.
It is not that long ago that I had a similar problem getting the encrypted volume mounted on the same PC after an update of systemd, see
https://forums.opensuse.org/showthread.php/512301-13-2-got-bust-by-updates-how-to-re-install-with-encrypted-home-partition

12

Hi again, the system still is bust.

I plugged an Ethernet cable.

Then I booted it.

It boots into maintenance mode, as before.

Then I entered ‘yast’ on the command line.

But when I run ‘online updates’ it fails to connect to the internet.

How could I get this system to recognize the cable connection to the router/the internet, which otherwise just works fine?
I’ve Leap installed on another partition of this PC, which is multi boot, and there everything with the network runs fine!

Thanks in advance!

Mike