Ubuntu is failing to boot after an XP virtual machine crashed my system.

hollowheaded · 02-01-2018, 01:01 AM

Hello all, I'm in dire need of some help at the moment. Please forgive me, I'll get all the terminology wrong I'm sure.

About a half an hour ago I tried running a Windows XP VM and my laptop (System76 Galago Pro) completely froze up immediately. After restarting the system, GRUB loads up just some logs and a shell. From what I can tell, all of my files are still intact but I've lost the ability to load Ubuntu (16.04 with GNOME) and go about my usual business.

I was getting an error similar to this and I followed those steps to no avail. I don't know how to adequately read log files in order to know what's going on, but I'm also seeing "fsck failed with error code 8."

It appears I'm stuck in my first virtual console. Usually my working environment is the second one, and pressing alt-ctrl-f2 just shows a blinking cursor. Anyone know what kind of information I should be looking for in the logs?

Thanks in advance for any help.

jsbjsb001 · 02-01-2018, 01:11 AM

From what you've said, it sounds like your system is starting but is going into "console mode" - dropping to a virtual console. (on the host system - Ubuntu)

While based on this "fsck failed with error code 8.", your drive's UUID may have changed, we really should get some more information from you.

Can you post the output of the following commands:
(please use CODE tags.)

Code:

cat /var/log/fsck/checkfs

And then;

Code:

sudo blkid

hollowheaded · 02-01-2018, 01:38 AM

Thank you for the quick response!

The fsck directory is curiously empty, but the output of blkid is as follows:

Code:

/dev/nvme0n1p1: LABEL="EFI" UUID="2384-A296" TYPE="vfat" PARTLABEL="primary" PARTUUID="91e95d22-456e-4d93-8127-0941f062a173"
/dev/nvme0n1p2: LABEL="Ubuntu" UUID="b1d2a86b-6e8c-4431-8073-96d11072560c" TYPE="ext4" PARTLABEL="primary" PARTUUID="75183de0-1fec-4a7d-90de-69c8ddc5c9c9"
/dev/nvme0n1p3: UUID="5182851d-b936-43fe-9f72-25eb2ced75a0" TYPE="swap" PARTLABEL="primary" PARTUUID="69c2d759-e8ae-4f70-a189-0de7e3521fde"
/dev/sda1: LABEL="ExtraDrive1" UUID="36859e53-4b8b-40f7-a906-9724c209b3c0" TYPE="ext4" PARTLABEL="primary" PARTUUID="7f296c6e-30c8-4496-a246-f3a64154b19a"
/dev/nvme0n1: PTUUID="72c728f9-83e8-40cc-969e-6af9f272717c" PTTYPE="gpt"

jsbjsb001 · 02-01-2018, 02:08 AM

Quote:

Originally Posted by hollowheaded

Thank you for the quick response!

The fsck directory is curiously empty, but the output of blkid is as follows:

Code:

/dev/nvme0n1p1: LABEL="EFI" UUID="2384-A296" TYPE="vfat" PARTLABEL="primary" PARTUUID="91e95d22-456e-4d93-8127-0941f062a173"
/dev/nvme0n1p2: LABEL="Ubuntu" UUID="b1d2a86b-6e8c-4431-8073-96d11072560c" TYPE="ext4" PARTLABEL="primary" PARTUUID="75183de0-1fec-4a7d-90de-69c8ddc5c9c9"
/dev/nvme0n1p3: UUID="5182851d-b936-43fe-9f72-25eb2ced75a0" TYPE="swap" PARTLABEL="primary" PARTUUID="69c2d759-e8ae-4f70-a189-0de7e3521fde"
/dev/sda1: LABEL="ExtraDrive1" UUID="36859e53-4b8b-40f7-a906-9724c209b3c0" TYPE="ext4" PARTLABEL="primary" PARTUUID="7f296c6e-30c8-4496-a246-f3a64154b19a"
/dev/nvme0n1: PTUUID="72c728f9-83e8-40cc-969e-6af9f272717c" PTTYPE="gpt"

Can you post the output of the following commands as well:

Code:

sudo lsblk -f

Code:

sudo cat /etc/fstab

hollowheaded · 02-01-2018, 02:26 AM

I'll do my best to preserve formatting

Code:

root@c9:~#lsblk -f
NAME         FSTYPE  LABEL         UUID                                  MOUNTPOINT
sda
|_sda1       ext4    ExtraDrive1   36859e53-4b8b-40f7-a906-9724c209b3c0  

nvme0n1
|_nvme0n1p3  swap                  5182851d-b936-43fe-9f72-25eb2ced75a0  [SWAP]
|_nvme0n1p1  vfat    EFI           2384-A296                             /boot/efi
|_nvme0n1p2  ext4    Ubuntu        b1d2a86b-6e8c-4431-8073-96d11072560c  /

root@c9:~#cat /etc/fstab
# /etc/fstab: static file system information
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system>  <mount point>  <type>  <options>  <dump>  <pass>

# /dev/nvme0n1p2
UUID=b1d2a86b-6e8c-4431-8073-96d11072560c  /  ext4  discard,noatime,errors=remount-ro  0  1

# /dev/nvme0n1p1
UUID=2384-A296  /boot/efi  vfat  umask=0077  0  1

#/dev/nvme0n1p3
UUID=5182851d-b936-43fe-9f72-25eb2ced75a0  none  swap  sw  0  0

# Storage
/dev/sda1  /media/chase/ExtraDrive1  ext4  rw,nosuid,nodev,noatime,data=ordered  0  0

jsbjsb001 · 02-01-2018, 02:58 AM

Well, it doesn't look like your drive's UUID is incorrect.

I'd suggest starting your system from a live CD/USB like systemrescuecd and running the command below to check the file system. I'd check the root partition (/dev/nvme0n1p2)

Code:

fsck /dev/nvme0n1XX

Change "nvme0n1XX" to the device node assigned to your Ubuntu "root" partition.

hollowheaded · 02-01-2018, 03:11 AM

I tried to start gnome by running 'lightdm' and I got the following:

Code:

** (lightdm:2281): WARNING **: Failed to get system bus: Could not connect: No such file or directory

followed by a few more lines then:

Code:

Failed to get a D-Bus connection

I'm trying to Google around for this but I'm coming up short.

jsbjsb001 · 02-01-2018, 03:14 AM

Quote:

Originally Posted by hollowheaded

I tried to start gnome by running 'lightdm' and I got the following:

Code:

** (lightdm:2281): WARNING **: Failed to get system bus: Could not connect: No such file or directory

followed by a few more lines then:

Code:

Failed to get a D-Bus connection

I'm trying to Google around for this but I'm coming up short.

While you should check your file system, can you try running the command below and if it doesn't load the graphical environment, post the messages you get:

Code:

startx

hollowheaded · 02-01-2018, 03:38 AM

startx also complains about no connection to D-bus.

What about the possibility of just restoring the 'Ubuntu' partition, nvme0n1p2? I just so happened to make a backup of it earlier today. Or is the problem beyond just that partition?

hollowheaded · 02-01-2018, 03:46 AM

Well, just tried to restore via Clonezilla, but it said nvme0n1p2 did not contain a partition table... Back to square one.

hydrurga · 02-01-2018, 03:50 AM

This doesn't solve your problem, but don't run that Windows XP VM again until you check its settings, more specifically how much memory it was allocated compared to how much memory you have on your system. Did you try running it while another VM was running perhaps? In any case, if there is not enough RAM to go around then the "lock-up" problem you describe may occur.

Which leads me on to the next question. How did you restart your machine when it locked up? If you cut the power and restarted then it is this which could have well caused the problem you are currently experiencing.

If I encountered a situation like yours then I probably would try to recover from my most recent system image so, yes, restoring that Ubuntu partition might do the trick, although you may also have to have a look at the grub/boot side of things afterwards.

hydrurga · 02-01-2018, 03:54 AM

Quote:

Originally Posted by hollowheaded

Well, just tried to restore via Clonezilla, but it said nvme0n1p2 did not contain a partition table... Back to square one.

nvme0n1p2 is an ordinary partition, it shouldn't contain a partition table (unless this is some form of partitioning that I'm not aware of). Are you sure that you're attempting the restore correctly? Is this something that you've successfully done before?

hollowheaded · 02-01-2018, 04:34 AM

Yes, you're correct. Sorry, I should have gone to bed a long time ago...

I've never done a restore through Clonezilla before, but I regularly backup my filesystem partition to another partition on an external drive. I assumed I could essentially do the same process in reverse, where the source partition is the one on the external drive and the target is the corrupted one. But when I went to attempt that, I was getting an error relating to a partition table.

I'm now going to attempt a fresh install of Ubuntu then restore it, but I have a feeling I might run into a similar problem. Running

Code:

fsck -nf /dev/nvme0n1p2

gives the following:

Code:

Warning! /dev/nvme0n1p2 is mounted.
Journal superblock has an unknown incompatible feature flag set.
Abort? no

Journal superblock is corrupt.
Fix? no

fsck.ext4: The ext2 superblock is corrupt while checking ext3 journal for Ubuntu

Ubuntu: ************ WARNING: Filesystem still has errors **********

hydrurga · 02-01-2018, 04:51 AM

If you have successfully backed up the Ubuntu partition then you should be able to restore that partition. I would concentrate on achieving that if I were you (post here exactly what you are doing in Clonezilla and what error messages you receive).

I don't understand why you would want to do a fresh install and then try to restore the previous partition, thus overwriting your brand new installation.

From what you are describing, your file system has taken a bit of a beating. That's why, in circumstances like this, I would normally restore to my last system image.

However, first you may want to try properly fscking the file system (ensure it is not mounted), accepting any recommended modifications, just to see what gives. Use fsck without any parameters to do so.