I updated Manjaro with pamac before the holidays and everything seemed fine. I remember even restarting the system to make sure the installation was successful. Now I’m coming back from the holidays and I cannot turn on the desktop. The BIOS menu shows up saying that the system cannot find any bootable devices.
Can you please provide any help? How to debug this issue further?
Increase your chances of solving your issue:
Difficulty: ★☆☆☆☆
Strong of its many members, the Manjaro support forum can provide you help whenever you have an issue with your Manjaro installation. But in order to work efficiently, we shall also ask you to commit to a few things.
Keep calm and read
First some basics: whenever you need to troubleshoot, chances are the solution is already under your nose.
Find error messages
Very often when an applications crashes, and sometimes when it misbehaves, it prints an error message somewhere.
…
Provide Information:
Welcome to Manjaro!
To allow all of us helpful people on this forum TO HELP YOU, we need some basic information about your system. This probably means you described the symptoms of your problem, but now we need some more information to know where the origin of your issue is exactly.
Someone else probably linked you to this tutorial, so if you’re reading this in response to a question, please click the link above this text to bring you to the full and unabridged text of the tutorial…
Maybe when you boot into a live usb or ISO you could gather this information
On a liveUSB, list all the drives and partitions seen by the system.
lsblk -af
Following the recommendations in the second link, and running the command from a live USB…
[manjaro@manjaro ~]$ inxi --admin --verbosity=7 --filter --width
System:
Kernel: 5.8.16-2-MANJARO x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
driver=free nouveau.modeset=1 i915.modeset=1 radeon.modeset=1
misobasedir=manjaro misolabel=MANJARO_KDEM_2012 quiet systemd.show_status=1
apparmor=1 security=apparmor
Desktop: KDE Plasma 5.19.5 tk: Qt 5.15.1 wm: kwin_x11 dm: SDDM
Distro: Manjaro Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: TUF B360M-PLUS GAMING/BR v: Rev X.0x
serial: <filter> UEFI: American Megatrends v: 2401 date: 03/22/2019
Memory:
RAM: total: 31.28 GiB used: 1.28 GiB (4.1%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
Topology: 8-Core model: Intel Core i7-9700 bits: 64 type: MCP
arch: Kaby Lake family: 6 model-id: 9E (158) stepping: D (13) microcode: D6
L2 cache: 12.0 MiB bogomips: 48016
Speed: 800 MHz min/max: 800/4700 MHz Core speeds (MHz): 1: 800 2: 800 3: 800
4: 800 5: 800 6: 800 7: 800 8: 800
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_capabilities
arch_perfmon art avx avx2 bmi1 bmi2 bts clflush clflushopt cmov constant_tsc
cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts erms est f16c
flush_l1d fma fpu fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify
ibpb ibrs ibrs_enhanced ida intel_pt invpcid invpcid_single lahf_lm lm mca
mce md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe
pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pts rdrand
rdseed rdtscp rep_good sdbg sep smap smep smx ss ssbd sse sse2 sse4_1 sse4_2
ssse3 stibp syscall tm tm2 tsc tsc_adjust tsc_deadline_timer vme x2apic
xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds mitigation: TSX disabled
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: NVIDIA TU116 [GeForce GTX 1660] vendor: ASUSTeK driver: nouveau
v: kernel bus ID: 01:00.0 chip ID: 10de:2184
Display: x11 server: X.Org 1.20.9 compositor: kwin_x11
driver: modesetting,nouveau alternate: fbdev,nv,vesa display ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
OpenGL: renderer: llvmpipe (LLVM 10.0.1 256 bits) v: 3.3 Mesa 20.1.8
compat-v: 3.1 direct render: Yes
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
v: kernel alternate: snd_soc_skl,snd_sof_pci bus ID: 00:1f.3
chip ID: 8086:a348
Device-2: NVIDIA TU116 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:1aeb
Device-3: Logitech OrbiCam type: USB driver: snd-usb-audio,uvcvideo
bus ID: 1-2:2 chip ID: 046d:0892 serial: <filter>
Sound Server: ALSA v: k5.8.16-2-MANJARO
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k
port: efa0 bus ID: 00:1f.6 chip ID: 8086:15bc
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: dynamic noprefixroute scope: global
IP v6: <filter> type: noprefixroute scope: link
WAN IP: <filter>
Drives:
Local Storage: total: 14.56 GiB used: 277.7 MiB (1.9%)
ID-1: /dev/sda type: USB vendor: Generic model: Flash Disk size: 14.56 GiB
block size: physical: 512 B logical: 512 B serial: <filter> rev: 8.07
scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Message: No Optical or Floppy data was found.
RAID:
Message: No RAID data was found.
Partition:
ID-1: / raw size: N/A size: 23.46 GiB used: 277.7 MiB (1.2%) fs: overlay
source: ERR-102 label: N/A uuid: N/A
ID-2: /run/miso/bootmnt raw size: 2.21 GiB size: <superuser/root required>
used: <superuser/root required> fs: iso9660 dev: /dev/sda1
label: MANJARO_KDEM_2012 uuid: 2020-10-19-13-24-36-00
Swap:
Alert: No Swap data was found.
Unmounted:
ID-1: /dev/sda2 size: 4.0 MiB fs: vfat label: MISO_EFI uuid: 2AD3-DF12
USB:
Hub: 1-0:1 info: Full speed (or root) Hub ports: 16 rev: 2.0 speed: 480 Mb/s
chip ID: 1d6b:0002
Device-1: 1-2:2 info: Logitech OrbiCam type: Video,Audio
driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s
chip ID: 046d:0892 serial: <filter>
Device-2: 1-10:3 info: Shenzhen Rapoo Rapoo 2.4G Wireless Device
type: Mouse,Keyboard driver: hid-generic,usbhid interfaces: 3 rev: 2.0
speed: 12 Mb/s chip ID: 24ae:2010
Device-3: 1-11:4 info: Alcor Micro Flash Drive type: Mass Storage
driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s
chip ID: 058f:6387 serial: <filter>
Hub: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 3.1 speed: 10 Gb/s
chip ID: 1d6b:0003
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 speed: 480 Mb/s
chip ID: 1d6b:0002
Hub: 4-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 speed: 10 Gb/s
chip ID: 1d6b:0003
Sensors:
System Temperatures: cpu: 27.8 C mobo: N/A gpu: nouveau temp: 35 C
Fan Speeds (RPM): N/A gpu: nouveau fan: 912
Info:
Processes: 220 Uptime: 18m Init: systemd v: 246 Compilers: gcc: N/A
Packages: pacman: 1054 lib: 282 Shell: Bash v: 5.0.18 running in: konsole
inxi: 3.1.05
[manjaro@manjaro ~]$ lsblk -af
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
loop0 squashfs 4.0 0 100% /run/miso/sfs/livefs
loop1 squashfs 4.0 0 100% /run/miso/sfs/mhwdfs
loop2 squashfs 4.0 0 100% /run/miso/sfs/desktopfs
loop3 squashfs 4.0 0 100% /run/miso/sfs/rootfs
loop4
loop5
loop6
loop7
sda iso9660 Joliet Extension MANJARO_KDEM_2012 2020-10-19-13-24-36-00
├─sda1 iso9660 Joliet Extension MANJARO_KDEM_2012 2020-10-19-13-24-36-00 0 100% /run/miso/bootmnt
└─sda2 vfat FAT12 MISO_EFI 2AD3-DF12
The live USB is with Kernel 5.8, but I was using kernel 5.10 due to my NVIDIA GPU.
Any recent update that could have caused this problem with the m2 drive?
The drive doesn’t show up, that’s bad news…
This is likely hardware related:
Faulty drive?
Try putting the drive in another computer you know it works.
Faulty connection?
Check the power line is correctly plugged in the drive.
Check the drive is correctly plugged in the M.2 slot.
Try switching your drive with another you know it works.
Try using another M.2 port.
Faulty motherboard?
Try connecting another drive through M.2/SATA/USB.
Isn’t the drive shown in the output? What is the sda that is shown?
Once i had to remove my RAM and reapply it to get it working.
These are gold-plated contacts, but that is no guarantee that you will never experience a contact problem.
I removed and plugged the ssd m.2 back on the motherboard again and it worked. It was a connection problem apparently.
system
Closed
January 7, 2022, 9:29am
11
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.