Boot won't work after update (12.1)

English Install/Boot/Login
1

I have been using 12.1 for quite a while with no problems. A couple days ago I tried to add the ability to mount my android cell phone by adding MTP support. The upgrade, through YAST, indicated a couple hundred files need to be changed or upgraded. During the process the system seemed to hang when it was updating what seemed to be the kernal or something similar - I think it was something to do with changing to systemd. In any case there was a power spike after it had been “hanging” for about 30 min. When the machine tried to reboot I get the following:

“doing fast boot
boot/o2-start.sh: line 34: mount: command not found
boot/o2-start.sh: line 35: mount: command not found
boot/o2-start.sh: line 36: mount: command not found
boot/o2-start.sh: line 40: mount: command not found
mknod: ‘/dev/console’: File exists
boot/o2-start.sh: line 52: mount: command not found
boot/o2-start.sh: line 54: mount: command not found
boot/o2-start.sh: line 56: mount: command not found
cat: /proc/cmdline: No such file or directoru
boot/o3-storage.sh: line 88: /dev/fd/62: No such file or directory
boot/o3-storage.sh: line 89: /dev/fd/62: No such file or directory
boot/o3-storage.sh: line 88: /dev/fd/62: No such file or directory
boot/o3-storage.sh: line 89: /dev/fd/62: No such file or directory
creating devices nodes with udev
boot/04-udev.sh: line 30: /sbin/udevadm: Not a directory
boot/04-udev.sh: line 30: /sbin/udevadm: Not a directory
boot/06-blogd.sh: line 23: mount: command not found
blogd: No standard input: No such file or directory
boot/04-udev.sh: line 17: /sbin/udevadm: Not a directory
Trying manual resume from /dev/disk/by-id/ata-SAMSUNG_HD_-part2
boot/04-udev.sh: line 17: /sbin/udevadm: Not a directory
Trying manual resume from /dev/disk/by-id/ata-SAMSUNG_HD_-part2
boot/04-udev.sh: line 17: /sbin/udevadm: Not a directory
Waiting for device /dev/disk/by-id/ata-SAMSUNG_HD_-part3 to appear:…
Want me to fall back to /dev/disk/by-id/ata-SAMSUNG_HD_-part3? (Y/n)”

If I type “Y”, it just keeps doing the “Waiting for device…” over and over. If I type “no” I get what seems to be a console prompt, but no commands (like “ls”) work. I used a live 12.1 cd to boot and checked the various disks. Doesn’t seem to be any problems as they can all be read and fsck reports no errors. The main HD (/dev/disk/by-id/ata-SAMSUNG_HD_*********) has four partitions. Partition 2 is the swap space and partition 3 is “/” (partition 1 is “/boot” and 4 is “/home”). I know Grub works since I can boot into Windows. The above error occurs no matter if I choose my regular desktop of the failsafe mode. There might be more error mesages, but I don’t know of a way to capture or display them.

So, can the system be rescued or do I have to reinstall? If I have to reinstall, would it be better to stay at 12.1 or bite the bullet and move to 13.2?

2

On 2015-03-27, rfmhunt <rfmhunt@no-mx.forums.opensuse.org> wrote:
> So, can the system be rescued or do I have to reinstall? If I have to
> reinstall, would it be better to stay at 12.1 or bite the bullet and
> move to 13.2?

I say whatever you decide, 12.1 is way past EOL and you need to reinstall. I see two viable options for you:

  1. Install openSUSE 13.2: you’ll have the latest packages and I know they work fine with MTP.
  2. Install openSUSE 13.1: I found this also worked with MTP, but the advantage of 13.1 is that it has been marked for
    long-term support (i.e. Evergreen) and will therefore be EOL after 13.2’s retirement. Seeing as you’re coming from 12.1,
    I suspect this option might be better for you since it would appear you’re not a regular reinstaller!
3

Well, my philosophy is if something works just fine there is no need to change for change’s sake. Since I can do all I want (other than MTP mounting) with 12.1 it makes no sense to try something different and risk introducing problems. I don’t worry about the security aspect since my only internet connection is the limited times I tether my cell phone. Mostly I use the machine for video/mulimedia work on personal files…import stuff from camera or video recorder and mess around wiht it.

If no one else has helpful advice I might just do the upgrade since it looks like I will have to (re)install something anyway.