Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have 2 drives in my machine with Windows being on SDA and I installed Ubuntu 18.04 on SDB. When I boot up it gets past the Grub screen but then tells me it gave up waiting for the suspend/resume device followed by this message
Code:
Gave up waiting for root device. Common problems:
-Boot args (cat /proc/cmdline)
-Check rootdelay= (did the system wait long enough?)
-Check root= (did the system wait for the right device?)
-Missing modules (cat /proc/modules; ls /dev)
It also tells me the UUID of my SDB device is missing. I am booting off of a USB stick and am able to look at the different parameters of SDB. When I cat /proc/cmdline I get this:
I had to use the cables from my cdrom drive to use for the second harddrive so I'm wondering if it needs to see my cdrom for some reason and that could be the issue?
Which version of windows are you using and is it an EFI install or Legacy/MBR install? How did you install Ubuntu, EFI/Legacy? Are you able to boot windows?
So did you check to see what the UUID of the Ubuntu partition is and check the grub.cfg file to see what was there? Is it sdb or a partition, sdb1, ssdb2,?
That's from the live cd or flash drive, not the hard drive install.
You should not expect beta software such as Ubuntu 18.04 to work flawlessly. Since you volunteered to test their pre-release OS, be sure to report the problem to Canonical/Ubuntu.
Windows 10, legacy. Ubuntu is legacy as well. Yup, Windows boots fine. You're right, cmdline in SDB doesn't exist. The menu entry in grub.cfg is
Code:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-a3d4d11d-34ec-476d-8950-f76530aa3ced' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd1,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2 a3d4d11d-34ec-476d-8950-f76530aa3ced
else
search --no-floppy --fs-uuid --set=root a3d4d11d-34ec-476d-8950-f76530aa3ced
fi
linux /boot/vmlinuz-4.15.0-15-generic root=UUID=a3d4d11d-34ec-476d-8950-f76530aa3ced ro quiet splash $vt_handoff
initrd /boot/initrd.img-4.15.0-15-generic
}
That is the correct UUID for my drive.
I'm turning off the Linux UUID in /etc/default/grub next and see what that does.
***Update**
So I've tried 3 different distros and a couple different harddrives with the same issue. Bios maybe? I'm looking at the hardware next. Different SATA ports and what not.
Last edited by snowman81; 04-18-2018 at 11:54 AM.
Reason: Update
If you are booting from the sdb drive, you should check to see if Grub sees that drive as sdb or sda. Boot Ubuntu and when you see the Grub menu, hit the c key on your keyboard and you should see a Grub prompt (grub>), just type: ls
Check the ouput to see which drive is seen as sda or sdb. You can also look for the boot partition from the grub prompt:
Code:
ls (hd1,msdos2)/
If that's your Ubuntu partition, you should see the directories in the / of the filesystem. If that isn't it, try whichever other partitions you saw with the ls output.
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,521
Rep:
I don't think Win10 will boot in legacy mode. When the grub menu appears, you can move to the Linux entry, hit 'e', and edit the kernel line to read root=/dev/sdbN instead of root=UUID, where /dev/sdbN is your root partition. Then, after your into the system, fix grub so it uses the correct UUID.
Yes, it will. If a drive is GPT, then windows will only install UEFI but if it is a Legacy/MBR partitioned drive, there should be no problem installing/booting it.
so as an update, re-doing grub didn't work. I changed harddrives, flashed the bios to the latest update, changed sata cables, replaced the entire machine with the same harddrive, changed out that harddrive, tried Ubuntu 16, 17, and 18 all with 3 different flash drives, tried Fedora, same error. I eventually tried Linux Mint and got it to install and then boot back up from the harddrive. If this works I'm staying with Mint for awhile.
**Update**
So this appears to be a kernel issue. Everything was fine for Linux Mint until I updated the headers/kernel. Then it wouldn't boot again.
Last edited by snowman81; 04-19-2018 at 02:21 PM.
Reason: Update
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,521
Rep:
If you suspend Windows, and then try to boot into Linux, you can have problems. Try booting into Windows and doing a full shutdown. Then try Linux again. Did you try to reinstall the boot loader with the Linux install disk?
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch, AntiX, ArtiX
Posts: 1,356
Rep:
Quote:
Originally Posted by AwesomeMachine
If you suspend Windows, and then try to boot into Linux, you can have problems. Try booting into Windows and doing a full shutdown. Then try Linux again. Did you try to reinstall the boot loader with the Linux install disk?
This is a good point. However, rather counter-intuitively, Windows 10 will typically NOT shutdown completely using the "Shut Down" menu item. It will go into a hybrid state more resembling hibernation. To completely shutdown Windows 10, the "Restart" option is the surest way. Thereafter, if one actually wanted to turn off the computer, hold down the power button to power down.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.