I upgraded my 64bit Opensuse 13.1 machine using zypper up and it no longer boots. I have tried the advanced option from grub and it fails to boot after printing:
Reached target sound card
[TIME] Timed out waiting for device …Part4_Dev
Dependency failed for /home
e[32m OK e[0m] Found device HDS721025CLA382.e[32m OK e[0m] Found device HDS721025CLA382.
e[32m OK e[0m] Found device HDS721025CLA382.
e[32m OK e[0m] Started dracut initqueue hook.
Mounting /sysroot...
e[32m OK e[0m] Reached target Remote File Systems (Pre).
e[32m OK e[0m] Mounted /sysroot.
e[32m OK e[0m] Reached target Initrd Root File System.
Starting Reload Configuration from the Real Root...
e[32m OK e[0m] Started Reload Configuration from the Real Root.
e[32m OK e[0m] Reached target Initrd File Systems.
e[32m OK e[0m] Started Show Plymouth Boot Screen.
e[32m OK e[0m] Reached target Paths.
e[32m OK e[0m] Reached target Basic System.
e[32m OK e[0m] Reached target Initrd Default Target.
Welcome to e[0;32mopenSUSE 13.2 Milestone 0 (Harlequin) (x86_64)e[0m!
[e[32m OK e[0m] Stopped Switch Root.
e[32m OK e[0m] Stopped target Switch Root.
e[32m OK e[0m] Stopped target Initrd File Systems.
e[32m OK e[0m] Stopped target Initrd Root File System.
Starting Replay Read-Ahead Data...
Starting Collect Read-Ahead Data...
e[32m OK e[0m] Created slice User and Session Slice.
e[32m OK e[0m] Created slice system-getty.slice.
e[32m OK e[0m] Listening on Syslog Socket.
Starting Create dynamic rule for /dev/root link...
e[32m OK e[0m] Reached target Slices.
e[32m OK e[0m] Listening on Delayed Shutdown Socket.
e[32m OK e[0m] Listening on /dev/initctl Compatibility Named Pipe.
Starting LSB: Set default boot entry if called...
e[32m OK e[0m] Set up automount Arbitrary Executable File Formats File System Automount Point.
Mounting POSIX Message Queue File System...
Mounting Huge Pages File System...
e[32m OK e[0m] Reached target Encrypted Volumes.
e[32m OK e[0m] Listening on udev Kernel Socket.
e[32m OK e[0m] Listening on udev Control Socket.
Starting udev Coldplug all Devices...
Starting Create list of required static device nodes for the current kernel...
Expecting device dev-disk-by\x2did-ata\x2dHDS721025CLA382_39M4511_42C0463IBM_JPA270H82P24EL\x2dpart2.device...
Expecting device dev-disk-by\x2did-ata\x2dHDS721025CLA382_39M4511_42C0463IBM_JPA270H82P24EL\x2dpart1.device...
Expecting device dev-disk-by\x2did-ata\x2dHDS721025CLA382_39M4511_42C0463IBM_JPA270H82P24EL\x2dpart4.device...
e[32m OK e[0m] Stopped Trigger Flushing of Journal to Persistent Storage.
Stopping Journal Service...
e[32m OK e[0m] Stopped Journal Service.
Starting Journal Service...
e[32m OK e[0m] Started Journal Service.
e[32m OK e[0m] Started Collect Read-Ahead Data.
e[32m OK e[0m] Started udev Coldplug all Devices.
e[32m OK e[0m] Started Replay Read-Ahead Data.
Starting Load Kernel Modules...
Starting File System Check on Root Device...
e[32m OK e[0m] Mounted POSIX Message Queue File System.
e[32m OK e[0m] Mounted Huge Pages File System.
e[32m OK e[0m] Started Create list of required static device nodes for the current kernel.
Starting Create static device nodes in /dev...
e[32m OK e[0m] Started Load Kernel Modules.
Starting Apply Kernel Variables...
e[32m OK e[0m] Started Apply Kernel Variables.
systemd-fsck[403]: /dev/sda3: clean, 493237/4448736 files, 8423081/17760256 blocks
e[32m OK e[0m] Started File System Check on Root Device.
Starting Remount Root and Kernel File Systems...
e[32m OK e[0m] Started Create dynamic rule for /dev/root link.
e[32m OK e[0m] Started LSB: Set default boot entry if called.
e[32m OK e[0m] Started Create static device nodes in /dev.
e[32m OK e[0m] Started Remount Root and Kernel File Systems.
Starting Load/Save Random Seed...
Starting udev Kernel Device Manager...
e[32m OK e[0m] Reached target Local File Systems (Pre).
Mounting Runtime Directory...
Mounting /sys/kernel/debug...
Mounting Lock Directory...
e[32m OK e[0m] Started udev Kernel Device Manager.
e[32m OK e[0m] Mounted Runtime Directory.
e[32m OK e[0m] Started Load/Save Random Seed.
e[32m OK e[0m] Mounted /sys/kernel/debug.
e[32m OK e[0m] Mounted Lock Directory.
e[32m OK e[0m] Reached target Sound Card.
e[1;31m TIME e[0m] Timed out waiting for device dev-disk-by\x2did-ata\x2dHDS721025CLA382_39M4511_42C0463IBM_JPA270H82P24EL\x2dpart4.device.
e[1;33mDEPENDe[0m] Dependency failed for /home.
e[1;33mDEPENDe[0m] Dependency failed for Local File Systems.
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" to try again
to boot into default mode.
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" to try again
to boot into default mode.
Any ideas anyone?
How do I back out of this update? I didn’t realise the update would result in 13.2 being installed. My bad but I need this machine running again…
On 2014-05-22 18:16, hcvv wrote:
>
> hcvv;2644771 Wrote:
>> Will be moved and is CLOSED for the moment.
>
> The thread is now merged with another obe about the same subject.
Please, which is the other one? I tried to locate it and could not find
it (I looked for the from field). If I answer unknowingly on it, via
nntp, I’ll make another mess…
The first two messages were from one original thread. The third and fourth are from another thread. Most of the remainder were probably posted to the merged thread. The title (or “Subject:” line) of the 3rd and 4th messages gives the title of the other thread, which was “Can’t boot 13.2”.
On 05/22/2014 09:46 AM, nrickert pecked at the keyboard and wrote:
> benbowc;2644745 Wrote:
>> How do I back out of this update? I didn’t realise the update would
>> result in 13.2 being installed. My bad but I need this machine running
>> again…
>>
>> Craig
> It is probably easier to just install 13.1. Or update to 13.1 with the
> DVD.
>
>
Or change all of your repos to only use 13.1 and issue zypper dup and
let it do it’s thing.
Sorry for the mess of messages…I’ll try to be tidier
I tried doing a reinstall and it failed with problems in creating initrd… I’m going to nuke it and start over. Would like to know however if others are able to get 13.2 installed and running.
On 2014-05-22 23:16, nrickert wrote:
>
> robin_listas;2644835 Wrote:
>> Please, which is the other one? I tried to locate it and could not find
>> it (I looked for the from field).
>
> Looking at it on the web forum:
>
> The first two messages were from one original thread. The third and
> fourth are from another thread. Most of the remainder were probably
> posted to the merged thread. The title (or “Subject:” line) of the 3rd
> and 4th messages gives the title of the other thread, which was “Can’t
> boot 13.2”.
Ok, found it.
Uh Oh… I found a thread named “Can’t boot 13.2”, which got a new post
about an hour ago, with a different subject (same thread), named
“Upgrade to 13.2 Milestone 0 causes boot failure”.
I’m confused, both threads seem active. One is number 498216, and this
one is 498216 - same one!
I’m afraid there is some kind of mess on the nntp side which I don’t
understand. There are two distinct nntp threads, pointing to the same
one on web side, and posts appears some in one, some in the other.
I’d better refrain from further posting in any of the two.
Sorry? zypper up is for normal updating of installed packages and that was what I was doing. After doing that update my system would not start and showed 13.2 milestone 0. That is not normal behaviour and that is why I got caught out.
It took me some time to understand this myself, but yes; When you do a normal update, as in upgrading each package in the repositories to newer versions, you do the usual “zypper up”. When there is a major update however, which also requires adding / removing new packages in order to adapt your distribution, you must use “zypper dup”. I assume that changing the repositories and only doing a simple update might have caused incomplete package changes, which could be responsible for this problem.
Either way, being stuck with a system that doesn’t boot is what I consider the worst thing to have happening to your machine, so I’m sorry to hear that. The only advice I can personally for the moment is to upgrade back to the latest stable release of 13.1 (downgrade actually, but “upgrade” is the term the installer uses regardless). After that, maybe there’s more someone here can suggest in order to find out what caused the problem, so upgrading again won’t break your machine a second time.
On 2014-05-23 07:46, benbowc wrote:
>
> gogalthorp;2644912 Wrote:
>> From origianl post zypper up was used you can not upgrade with zypper up
>> you use zypper dup. This is probably what caused the problem
>
> Sorry? zypper up is for normal updating of installed packages and that
> was what I was doing. After doing that update my system would not start
> and showed 13.2 milestone 0. That is not normal behaviour and that is
> why I got caught out.
But 13.2 is not the normal distribution, it is the Beta. And the beta
has to be always updated/upgraded with “zypper dup”, nothing else. The
same goes for Tumbleweed.
If it was not your intention to use the Beta release… well,
repositories are not added automatically, you add them yourself. You can
investigate in your logs to find out when the factory repos were added.
If it wasn’t clear from the above posts,
I’d recommend
Network Method (Modify only your files, but automatically with latest current)
Boot to Recovery Mode.
Assuming you can successfully boot (since you couldn’t boot into normal mode) and if you have network access, verify only 13.1 repos are enabled and all 13.2, Factory and extra repos are disabled or removed.
With your system pointing only to the 13.1 base repos, run
zypper dup
DVD Method (Modify files to the original 13.1 Release which is almost guaranteed to work always, but files will be old. System then needs to be updated)
The alternative is if you have the 13.1 DVD, then you can boot to the DVD and run a repair followed by
zypper up
Note this command is <not> “zypper dup” which is a distro upgrade while “zypper up” merely updates your packages for that distro version without upgrading.
