boot – Kernel 4.15.0-118 causing kernel panic on Kubuntu 18.04?

It looks like the 4.15.0-118 is causing a kernel panic during boot on my machine (Alienware 15 R3 from Dell).

Booting with the previous kernel works.

Last line in the output I get when attempting to boot with the new kernel is:
---( end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Maybe it has something to do with my partition encryption with LUKS (I have a Windows partition, and a LUKS partition)?

I tried following and went to Launchpad, but couldn’t figure out how to file a bug there…

Does anybody else have the problem?
I tried solving it temporarily by changing the GRUB to boot the older kernel by default (without me going through advance boot options when I turn on the machine). But it doesn’t seem to work for me.

Kernel panic error message when trying to boot Ubuntu from USB drive

I’ve been trying to install Ubuntu on my computer for the first time, which runs Windows 10. I have Ubuntu installed on a memory-stick. However, when I try to boot it from the USB drive when I turn on my computer, I just get this kernel panic error message (image attached below). I’ve done a lot of research but can’t get a clear answer and I’m very confused on how to fix this. Not to mention, when I tried to boot Linux Mint 20 to see if it would work (which was installed in a different memory-stick), I got the same error message as shown in the attached image. I would really appreciate it if someone can help me and explain in simple words what the problem could be and also, how it can be fixed.

Thank you in advance
Here’s the link to the kernel panic error message

redhat – Boot menu is stopping after selecting media in inst.dd command

I’m trying to install CentOS7 into HP Microserver G8. I need to disable AHCI and changing array driver as following site describe.

I did following command from boot prompt.

linux modprobe.blacklist=ahci inst.dd

And selected the number for the driver media of kmod-hpvsa-1.2.16-102.rhel7u3.x86_64.rpm

Then pressed ‘c’ to continue after i confirmed the toggle was selected as ‘x’ forkmod-hpvsa-1.2.16-102.rhel7u3.x86_64.rpm.

However, nothing is happen even showing error message.

It seems stopping or waiting something.

Does anyone tell how to continue the boot menu or how to check the system.

I’ve posted same issue in stack-overflow and super-user.

server – Need TTY Console mode to be able to enter LUKS password at boot (Ubuntu 18.04)

I have a (supposed to be) headless server running Ubuntu 18.04 where the boot volume is LUKS encrypted. I am unable to redirect the initial boot process to the serial console (running Putty from a Windows 10 PC) so that I can enter the password. At this point the only option I have to leave the enclosure open with a video card and usb keyboard installed so I can enter the password–not a workable option.

The serial console port (from the W10 PC) sees the initial GRUB menu up to the “Press ESC for options”, but nothing until I enter the password. After I enter the password, the remainder of the boot process output appears on the serial console port and I can login. Initially I couldn’t even get the output after the password and the console login to work. To get that far I did the following:

  1. Edit /etc/default/grub file so that GRUB_CMDLINE_LINUX reads “console=tty1 console=ttyS5,115200”
  2. Update GRUB with sudo update-grub
  3. sudo systemctl start getty@ttyS5
  4. sudo systemctl enable getty@ttyS5

I need to get the entire boot sequence, including prompt for LUKS password redirected to the serial console port. I’ve tried so many different procedures I can’t possibly put them all down, including a half dozen from this site. Someone please help, I need to be able to seal up the enclosure, with the video card and USB keyboard removed and all interaction with the boot process managed from the serial console port.

Many thanksto the Ubuntu Community in advance

grub2 – Unable to boot due to drm_kms_helper errors

I’m trying to boot an old computer with Ububntu (I think it’s version 19.04 but i’m not 100% sure).
The problem is I’m getting drm_kms_helper errors, same as described in the follwing solved questions:
Boot very slow because of drm_kms_helper errors, Ubuntu server 18.04 slow boot due to drm_kms_helper

The thing that is different in my case that it’s unable to boot, it might be due to the age of the computer or it’s just taking A LOT of time (I waited 4 hours).

My question is is there any way to run those command which should help solving the problem before booting the system?
Is there any other way to fix it?

Thanks in advance!

boot – Centos Crashed After Removing Some Packages

I was cleaning up packages I don’t use, and I found that I have the emacs package installed but I don’t use emacs. So I ran this command to make sure I don’t have any emacs:

sudo yum remove *emacs*

It ran for a while, but then right after it finished my computer crashed and it showed this screen with a bunch of log output. I restarted my computer, and when centos booted up, it just took me to a shell screen. I tried reinstalling the packages with

sudo yum install *emacs*

but after I restart my computer it shows the same screen again. How do I get centos back to normal? I was using the GNOME desktop environment.

java – Questioning on Spring Boot collection validation request

Hello I have following model in my spring boot app:

public class CreateInvoice extends BaseModel {
    private String invoice_number;
    private Integer company_id;
    private Integer branch_id;
    private Integer customer_id;
    private Integer primary_currency_id;
    private Integer secondary_currency_id;
    private Float exchange_rate;
    private String invoice_type;
    private Float discount_percent;
    private Float discount_value;
    private Integer status;
    private List<CreateInvoiceItem> items;
    private CreateReceipt receipt;

I would like to ask how can I validate private List<CreateInvoiceItem> items; to prevent empty size?

boot – Is it possible to create a bootable installation partition for a PowerPC mac using an Intel-based Mac?

I had a hard drive failure on my old PowerPC G4 Mac. I need that old Mac to be able to run OS X and OS 9, because I can’t retrieve and convert some of the files from the secondary hard drive unless I can run the old programs on the old OS (Like the old Hypercard stacks).

I’ve been trying to load an image of the installation disk (.dmg) onto an external firewire drive.

I did it using Terminal and the “sudo asr” command, copied that .dmg file, and the partition on my hard drive looks like and behaves like an installation disk (formatted the Hard Drive with Mac OS Extended, Journaled, Apple Partition map format, not GUID).

When I hook it up to the firewire port and boot the G4 holding the “Option” key down, it doesn’t bring up anything on the screen where you would select which drive/volume you want to boot from.

Is this an issue with trying to build this from an Intel-based Mac? I’d love to just run the installer and put it onto that hard drive on a partition, but I can’t run that installer on an Intel-based Mac.

boot – Black screen both at normal and safe mode on windows 8.1

After my system finished scanning and repairing I got a black screen with no cursor and keyboard commands were not working. I tried many solutions on the internet but all didn’t work. I tried a solution that requires me to get into safe mode and uninstall some devices but when I try to log to safe mode,I see the same black screen . Please any idea on how to fix this black screen of death without losing my files?