Score:0

"Gave up waiting for root file system; Alert! UUID= ... does not exist! Dropping to a shell." Previous Thread Solutions have not Worked

cn flag

I am running on VMware Workstation with Ubuntu 18.04.5. Whenever I try to boot my own Linux 5.4.0 Kernel, which so far is just fork of the original repo, I get this Error Message.

Here are some images that may be relevant:

/etc/fstab,

/etc/default/grub,

blkid,

ls /boot/

Additionally, I have tried various fixes:

  1. I set rootdelay=600; I have also tried using rootwait to no avail.
  2. I have run update-initramfs -u -k 5.4.0+
  3. I have run mkconfig-grub; update-grub; update-grub2
  4. I have completely reinstalled my VM ova.
  5. I have made sure that I am not using RAID; I am using AHCI.
  6. Additionally when setting up the .config file I used the default recommended settings for 5.4.0.

Any help/guidance would be greatly appreciated. Thank you!

heynnema avatar
ru flag
Why are you trying to mount a floppy disk in /etc/fstab? What is all of that extra stuff in /etc/default/grub?
heynnema avatar
ru flag
At the initramfs prompt, type `fsck -f /dev/sda1`.
quezo avatar
cn flag
Hello @heynnema, a lot of the extra stuff is related to the class I am taking for OS, I have in the past successfully used this ova with all of the extras. I ran `fsck -f /dev/sda` and got: "fsck from util-linux 2.31.1 fsck: error 2 (No such file or directory) while executing fsck.ext2 for /dev/sda1"
heynnema avatar
ru flag
You didn't do the `fsck` command correctly.
quezo avatar
cn flag
Ah, that's a typo. I did type `fsck -f /dev/sda1` I received the output "fsck from util-linux 2.31.1 fsck: error 2 (No such file or directory) while executing fsck.ext2 for /dev/sda1"
heynnema avatar
ru flag
How is your disk physically connected? How do you run VMWare if you can't boot to your own disk?
quezo avatar
cn flag
Currently, VMware is using 50Gb off of one of my HDDs. I run VMware on a Windows 10 Computer and the screenshots of /etc/fstab /etc/default/grub are from a working kernel. If there is anymore specific information you need, I'd be more than happy to add in screenshots; I'm just not entirely sure what exactly would be relevant.
heynnema avatar
ru flag
Did this ever work for you? Did you create this with *"fork of the original repo"*? I'm not exactly familiar with VMWare...
quezo avatar
cn flag
The kernel that is booting correctly came with the ova file for the virtual machine I am running. It is running the same version of Linux. In the past, I have used the repo that I forked from to create a working/bootable version of Linux that would run on this virtual machine.
heynnema avatar
ru flag
I guess that I'm now over my head. Sorry.
Terrance avatar
id flag
Previous thread solutions are based on using the kernels that are released from Canonical. Have you tried the official kernel that came with 18.04 to eliminate your kernel as being the problem?
quezo avatar
cn flag
It is likely that there is something wrong with my kernel that is stopping it from booting; however, the only thing that I have done with it is run (w/ sudo): `make oldconfig; make -j8; make modules_install; make install`. The version that is booting is the official kernel that came with 18.04, or at least I think it should be based on what I've read on ubuntu's website. Typing `cat /proc/version_signature` I get: `Ubuntu 5.4.0-80.90~18.04.1-generic 5.4.124`
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.