12.1 upgraded system: Emergency Mode Only

[Liquid_Squelch]

I upgraded my openSUSE box last night from 11.4 to 12.1 using Zypper.
In the past, I never had a problem doing the upgrade this way, but come to think of it, it was 11.x -> 11.x upgrades only.



Now that I've upgraded, I can't boot openSUSE. I've tried the recovery console with the same results.



I can log in with root's password, but it seems like there are no services running. My ifconfig only shows local loop port. The computer has a single internal hdd. It also has a Western Digital My Book External drive on USB that is never turned off or disconnected. I also have a 6 serial card installed that runs m9865 drivers. I did see a lot of upgrade failures with that driver, wondering if that might have something to do with it.

Can my pc be saved? If not, can I at least have an easy way of backing up my Home directory?


Here is a visual copy and paste as to what I am seeing on my screen when I attempt to boot:
(Can't believe I had to type all this in.. Sorry for any type-os')

[     1.366490] /home/abuild/rpmbuild/BUILD/kernel-default-3.1.0/linux-3.1./driver
)
doing fast boot
FATAL: Module pilx not found.
FATAL: Module ide_pcl_generic not found.
Creating device nodes with udev
udevd(164): failed to execute '/etc/sysconfig/network/scripts/ifup-sysctl' '/etc
/systconfig/network/scripts/ifup-sysctl lo -o hotplug;: No such file or directory

Trying u resume from /dev/dis/by-id/ata-SAMSUNG_SP0802N_S00JJ20X738657-part1
Invoking userspace rese from /dev/disk/dev/dis/by-id/ata-SAMSUNG_SP0802N_S00JJ20X738657-part1



resume: libcrypt version: 1.5.0
Trying manual resume from  /dev/dis/by-id/ata-SAMSUNG_SP0802N_S00JJ20X738657-part1
invoking in kernel resume from /dev/dis/by-id/ata-SAMSUNG_SP0802N_S00JJ20X738657-part1
Waiting for device /dev/dis/by-id/ata-SAMSUNG_SP0802N_S00JJ20X738657-part2 to appear:  ok
fsck from util-linux 2.20.1
[/sbin/fsck.ext4 (1) -- /] fsck.ext4 a -C0 /dev/sda1
/dev/sda2: recovering journal
/dev/sda2: clean, 252478/13132820 files, 1863428/524800 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/dis/by-id/ata-SAMSUNG_SP0802N_S00JJ20X738657-part2
mount -o rw,acl,user_xattr -t ext4 /dev/dis/by-id/ata-SAMSUNG_SP0802N_S00JJ20X738657-part2 /root
[   3.988930] usbid 3-2.3:1.1: couldn't find an input interrupt endpoint
[   7.032495] system[1]: [/etc/init.d/cups:19] Failed to add LSB Provides name cupsd.service, ignoring: File exists
[  11.404287] sd 2:0:0:0 [sdb] No Caching mode page present
[  11.404534] sd 2:0:0:0 [sdb] Assuming drive cache: write through
[  11.411022] sd 2:0:0:0 [sdb] No Caching mode page present
[  11.411272] sd 2:0:0:0 [sdb] Assuming drive cache: write through
system-fsck[581]: /dev/sda3: clean 2675/3448843 files, 2835094/13775737 blocks
[  19.276173] sd 2:0:0:0 [sdb] No Caching mode page present
[  19.276419] sd 2:0:0:0 [sdb] Assuming drive cache: write through
Welcome to emergency mode.  Use "systemctl default" or ^D to activate default mode.
Give root password for login:

FWIW, /var/log/boot.log is empty

[robin_listas]

On 2011-12-08 14:36, Liquid Squelch wrote:

> Now that I've upgraded, I can't boot openSUSE. I've tried the recovery
> console with the same results.
>
>
> I can log in with root's password, but it seems like there are no
> services running.

Now, this makes no sense. If you get to log in by root's password, then you
are booting.


> Here is a visual copy and paste as to what I am seeing on my screen
> when I attempt to boot:
> (Can't believe I had to type all this in.. Sorry for any type-os')

You could use a camera.

>
> Code:
> --------------------
> Welcome to emergency mode. Use "systemctl default" or ^D to activate default mode.
> Give root password for login:
>
> --------------------

You are booted to emergency mode, in which you are expected to repair
whatever is broken before you are allowed to a full normal boot. Typically
it is because fsck failed, or a partition listed in fstab could not be mounted.

I would instead simply try to boot in traditional systemV mode (F5 at grub).

> FWIW, /var/log/boot.log is empty

Two reasons: root is probably mounted in read mode, so nothing is written,
and systemd doesn't support that file. It goes instead to /var/log/messages.

--
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 "Celadon" at Telcontar)

[Liquid_Squelch]

I was able to boot into GUI.

From the emergency console, I ran vi and edited the fstab file. I commented out the listing for the external USB drive. Did a save and shutdown -r now.

The computer came right up with the new 12.1.

[robin_listas]

On 2011-12-09 17:26, Liquid Squelch wrote:
>
> I was able to boot into GUI.
>
> From the emergency console, I ran vi and edited the fstab file. I
> commented out the listing for the external USB drive. Did a save and
> shutdown -r now.

That's a typical.
You can re-add it to fstab if you use the "nofail" option.


> The computer came right up with the new 12.1.

Good! :-)

--
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 "Celadon" at Telcontar)

[davidlwilcox]

I've just had the same thing happen to me. Edited fstab to remove the USB disc and the system came up with no problem. I then added the USB disc but using the old fashion syntax, i.e. /dev/sdc1 and that came up OK.