[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#917632: marked as done (bugs.debian.org: During kernel boot the nvme module is not loaded, make the kernel not finding the rootfs)

Your message dated Tue, 1 Jan 2019 15:19:00 -0800
with message-id <20190101231900.urab7yla74blundl@qor.donarmstrong.com>
and subject line Re: Bug#917632: bugs.debian.org: During kernel boot the nvme module is not loaded, make the kernel not finding the rootfs
has caused the Debian Bug report #917632,
regarding bugs.debian.org: During kernel boot the nvme module is not loaded, make the kernel not finding the rootfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
917632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917632
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: bugs.debian.org
Severity: important
Tags: upstream

Dear Maintainer(s),

   * What led up to the situation?

I did an apt upgrade this morning, I'm running testing/unstable. This updated
my kernels to 4.17.0-3-amd64 and 4.19.0-1-amd64. I think the first since a few
months (6 or more, but less then one year).

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

sudo apt update; sudo apt dist-upgrade

   * What was the outcome of this action?

After rebooting to the new kernel booting stuck with some messages about mdadm
looking for a RAID I don't have.

Ultimately the initramfs-shell came up and I found out that there are no block-
devices loaded. /dev/sda* and /dev/nvme* did not exists.

I manually modprobe'd nvme. Followed by CTRL-D and the boot continued.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (602, 'unstable'), (601, 'testing'), (600, 'stable'), (598, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-3-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=en_US:en (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
On Tue, 01 Jan 2019, Patrick Boettcher wrote:
> I fixed my problem with manually running 
> 
>     sudo update-initramfs -u
>     
> I don't why the initial initramfs did not contain the necessary
> "things" to load the nvme-module automatically. Maybe it was the
> constellation of update-packages.

Thanks for the response; I've closed the issue in question.


-- 
Don Armstrong                      https://www.donarmstrong.com

Taxes are not levied for the benefit of the taxed.
 -- Robert Heinlein _Time Enough For Love_ p250

--- End Message ---
Reply to: