dual booting an HP laptop,4gb ram,intel i3 6006.Windows 10 and ubuntu dual boot, each time i install ubuntu “something else” option in installation

I am installing ubuntu on HP laptop with windows 10 preinstalled . Each time i install ubuntu on a partition the grub is not installing i386 file in /boot/grub folder which causes error as grub searches for that file and run into grub rescue at each boot , hence i cannot boot into ubuntu nor windows , i manually added the file by live usb but failed to make grub config for such changes . My partition show (hd,msdos6) as root . grub is installed on root partition. Grub never installs the i386 file and this file can be found in /usr/lib/grub .

Computer does not support booting to a NVMe SSD

I have a Dell Optiplex 3040 with a HDD running Ubuntu 19.4. I installed a NVMe SSD and Ubuntu sees it and I can use it. I would like to use the SSD as my main drive, but the computer does not support booting to a NVMe SSD. On a Raspberry Pi there is a process to boot from one drive but run the OS from another drive.


I tried that with Ubuntu, but it is still running from the HDD. How do I get Ubuntu to boot from the HDD and run from the NVMe SSD?

Thanks in advance, Kevin

Booting Kernel Failed: Invalid Argument (Non-VM)

Backstory: I have been trying to install Ubuntu the last few days, but I have been facing problems. First, I had to change the File System of my Ubuntu USB and then after that I am facing this problem.

What happened?: I launched the Ubuntu Installer with my USB and then say an accessibility icon and a keyboard when booting. Right after, I saw a black screen saying “Booting Kernel Failed: Invalid Argument”. I can confirm that my install of the iso is not corrupted with qBitTorrent confirming it. Also my USB is not the problem. I used Rufus’ dd mode to install Ubuntu on the drive to keep it in FAT. Also, I tried using my USB on a Chromebook but just stated a “Graphics Initialization Problem” message. I also tried writing help and enter but it did not boot.

“You are in emergency mode” error on booting Ubuntu 18.04

I use ubuntu 18.04 , on boot I get the following error:



I try journalctl To see the log

journalctl -xb 

I saw that there were two red lines in the logs :

log response:

log response

and With my searches, I realized I had to use fsck

fsck -f /dev/sda5 

and I get this response :

fsck -f /dev/sda5 results:

fsck -f /dev/sda5 results

and I added -n to fsck command

fsck -nf /dev/sd5  

and I get the following results :

fsck -nf results:

fsck -nf results

Storage HD can’t be mounted at booting

Ubuntu 16.04 desktop


I have 2 WD HDs solely for storage.



About 1 day before both of them could be mounted automatically at booting and their icons appeared on the left vertical menu. I just found that only WD HD2-2TH could be mounted at booting and WD HD1-4TB unable to be mounted for unknown reason.

⟫ sudo fdisk -l

Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 75CD82BD-3AF3-44B0-A04D-B4C97B6A381C

Device Start End Sectors Size Type /dev/sdc1 34
1987 1954 977K Linux filesystem /dev/sdc2 1988 7814037118 7814035131 3.7T Linux LVM

Partition 1 does not start on physical sector boundary. (in red color) Partition 2 does not start on physical sector boundary. (in red color)

Please advise how to fix the problem. Thanks in advance.

16.04 not booting. Mounted it on 18.04, data seems fine. Repaired Grub

Been raked over the coals with this one.

16.04 crashed while running. Could not even get grub to come up. It is not a dual boot system. Only 16.04. Just screen flashing. No command line access with no ability to read log files. No ability to go back to run level 3 (systemctl in ubuntu). Nothing.

At first, I reinstalled grub from an 18.04 trial install. After that I Was able to select “ubuntu recovery” on boot but with no effect. Same flashing of the screen with no command line access.

I’m sure that it is not a physical problem with the disk. A few weeks ago this same thing happened on another drive. I cloned the drive with DDrescue to another drive. Data was ok. The problem followed the new drive, implying that the problem was in the operating system. Somehow, not sure how, I was able to boot the new drive.

Now I am “in” the new drive and the same thing happened.

Loaded 18.04 on top of 16.04 and I can mount 16.04 and see programs, data.

Is there a way back from this? I don’t want to have to download 300G on another drive at this point (downloading that much data is expensive).

Thank You Tom