Bug ID | 1208944 |
---|---|
Summary | Kernel 6.2.0-1-default does not boot on tumbleweed |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | x86-64 |
OS | openSUSE Tumbleweed |
Status | NEW |
Severity | Critical |
Priority | P5 - None |
Component | Bootloader |
Assignee | screening-team-bugs@suse.de |
Reporter | kesang.neljor@yahoo.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36 Build Identifier: Dear People, The latest kernel does not boot my recently bought new dell laptop. Everything works fine with the older kernels! After a boot with the 6.2.0-1-default: Boot interrupted because it can only find the SSD drive and not the SATA. Fdisk only sees one disk with this kernel. Bootlog: [ TIME ] Timed out waiting for device /dev/disk/by-uuid/3313dbc7-31e4-4ffb-8172-59618fd226fa. [DEPEND] Dependency failed for /dev/disk/by-uuid/3313dbc7-31e4-4ffb-8172-59618fd226fa. [DEPEND] Dependency failed for Swaps. [ TIME ] Timed out waiting for device /dev/disk/by-uuid/90cf849c-a35d-4e49-ae8d-218e83f78b9f. [DEPEND] Dependency failed for /local. [DEPEND] Dependency failed for Local File Systems. journalctl -xb: Mar 04 09:00:38 akshobhya systemd[1]: Starting File System Check on /dev/disk/by-uuid/f495615b-46e7-43e1-bfdc-0bc4f54fdf93... Mar 04 09:00:38 akshobhya systemd[1]: Finished File System Check on /dev/disk/by-uuid/f495615b-46e7-43e1-bfdc-0bc4f54fdf93. Mar 04 09:02:09 akshobhya systemd[1]: Timed out waiting for device /dev/disk/by-uuid/3313dbc7-31e4-4ffb-8172-59618fd226fa. Mar 04 09:02:09 akshobhya systemd[1]: Dependency failed for /dev/disk/by-uuid/3313dbc7-31e4-4ffb-8172-59618fd226fa. Mar 04 09:02:09 akshobhya systemd[1]: Timed out waiting for device /dev/disk/by-uuid/90cf849c-a35d-4e49-ae8d-218e83f78b9f. Will the next kernel be okay or is there some work for me to do? Thank you so much in advance! Peter Reproducible: Always Steps to Reproduce: 1.Reboot into the same kernel 2. 3. Actual Results: Reboot into the same kernel Expected Results: Problem as described Complete boot