@b-9
There may be various options, depending on how comfortable you are with the
command line.
You could try to build a custom initramfs image with diagnostic tools, boot
from it and dump the necessary info to a USB drive for example. Or clone the
ubuntu kernel git repository and use git
@ishinberg0 I am having the same issue on an alienware aurora r6 after
the upgrade to 5.4.0-48
I would like to file a new bug report for this. How do I go about
generating any debug info when I have a blank screen after grub menu?
--
You received this bug notification because you are a member
@ishinberg0, as achille-fouilleul wrote, this is probably a different bug.
A few questions you can ask to make sure of that:
- Do you get any error message at all?
- Which nvme items do you see in /dev when in BusyBox, and which ones when you
boot normally using kernels that work for you?
- Do
@ishinberg0
The issue ami, crysman and I had was related to a specific NVMe
controller (PCI IDs 126f:2263). 5.4.0-48 fixed it for ami and I at
least. I guess your issue is different; I suggest you file a new bug
report with details about your system (dmesg, lspci output etc.).
--
You received
Sorry to be a buzz kill but this bug started affecting **after** upgrading to
5.4.0-48.
5.4.0-47 works fine. I'm running on top of Dell XPS 9700.
Any ideas/help are much advised.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
My pc also could not find/see my NVME device after ubuntu update. As a result
it could not boot to the system.
The following is the Nvme storage:
```
~$ sudo nvme list
Node Model
/dev/nvme0n1 INTEL SSDPEKKW512G8
```
Problem has been
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894378
Title:
Cannot boot after updating kernel to version
The new kernel, 5.4.0-48, indeed solves the problem.
Thanks for all the comments!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894378
Title:
Cannot boot after updating kernel to
@Achille
```
$ sudo lspci | grep Motion
6d:00.0 Non-Volatile memory controller: Silicon Motion, Inc. Device 2263 (rev
03)
```
according to `sudo nvme list` output, it is /dev/nvme0n1 Model
TS256GMTE110S
If I understood correctly, next update will fix the issue (?)
--
You received this bug
Thanks for your comments, @crysman and @achille-fouilleul.
I'm glad there is an upcoming fix, and hope it is released before long.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894378
@crysman I have a NUC too. Is your nvme controller a Silicon Motion, Inc.
Device 2263 (rev 03) (126f:2263)?
It seems this controller somehow deviates from the specification.
The commit I mentioned above (ea43d9709f) made the driver stricter, causing it
to reject the device.
A fix is available
no, this is improbable to be related because when 5.4.0-42 is booted,
these messages are there id `dmesg`, too.
I've made this workaround so far:
1) sudo nano /etc/default/grub
* GRUB_TIMEOUT=5
* GRUB_DEFAULT=saved
* GRUB_SAVEDEFAULT=true
2) sudo update-grub
so booting 5.4.0-42 now and waiting
PS: I've noticed several nvme related info on boot screen:
`nvme nvme0: missing or invalid SUBNQN field.`
...
and after 3 lines there is:
`nvme nvme0: Identify descriptors failed (2)`
could it be related?
--
You received this bug notification because you are a member of Kernel
Packages, which
At work, we got quite recently one machine hanging on "ALERT! ... UUID
does not exist ..." with kernels 5.4.0-45 and 5.4.0-47. Only 5.4.0-42 is
booting now.
Adding `rootdelay=5` does not help.
I've already updated BIOS to latest version (from 2020-07), does not help.
The machine is also using
Same problem for me, 5.4.0-45 and -47 kernels fail to detect my nvme drive
while -42 boots fine.
According to git bisect the issue was introduced by commit
e958cbb11ed6f58dac5bbfba481631ff0f567c7d (upstream
ea43d9709f727e728e933a8157a7a7ca1a868281).
** Attachment added: "BISECT_LOG"
** Description changed:
After the kernel update from version 5.4.0-42 to version 5.4.0-45 a few
days ago, the boot process is ending in a BusyBox shell. Apparently it
cannot properly identify my M.2 NMVe SSD device where my root partition
- is. Indeed, it is not listed in /dev. For now, I'm
5.4.0-45 5.4.0-47 encounters the same problem, you must use 5.4.0-42 to
boot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894378
Title:
Cannot boot after updating kernel to version
** Description changed:
After the kernel update from version 5.4.0-42 to version 5.4.0-45 a few
days ago, the boot process is ending in a BusyBox shell. Apparently it
cannot properly identify my M.2 NMVe SSD device where my root partition
is. Indeed, it is not listed in /dev. For now, I'm
18 matches
Mail list logo
