You are not logged in.
This is my latest issue. After solving the missing kernel issue and updating the Arch wiki article on my laptop with the fix and thereby getting a fully working Systemd boot menu I booted into Arch hoping to have a fully working system. Instead I get this:
Starting version 249-2-1-arch
:: running hook [udev]
triggering uevents
Waiting 10 seconds for device /dev/disk/by/partuuid/ebcb1e30-7039-e344-bc42-98d2de47eb30
ERROR: device 'PARTUUID=ebcb1e30-7039-e344-bc42-98d2de47eb30' not found. Skipping fsck.
:: mounting 'PARTUUID=ebcb1e30-7039-e344-bc42-98d2de47eb30' on real root
mount: /new_root: can't find PARTUUID=ebcb1e30-7039-e344-bc42-98d2de47eb30.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#Pastebins with output of some commands run that might be useful for debugging (namely the text of the bootloader file and the output of blkid, bootctl status and efibootmgr -v)
Pastebin of output of efibootmgr -v: https://paste.ubuntu.com/p/zSKm3DDjr5/
Pastebin of output of bootctl status: https://paste.ubuntu.com/p/2YvThR95zJ/
Pastebin of output of blkid: https://paste.ubuntu.com/p/CnmwRcBmXw/
pastebin of output of running cat on the bootloader file:https://paste.ubuntu.com/p/jNKP7DxkhT/
I have attempted to regenerate the initramfs with the VMD module enabled and that did not solve this.
Anyone have any ideas? Also, is there any other information I can provide?
Edit: Removed photos and added pastebins and transcription after Loqs referred me to some pastebin clients.
Last edited by PythonLinux (2021-07-27 20:01:12)
Offline
When you are dropped to the rescue shell does /dev/sda exist? I can not read the PARTUUIDs so can not tell if they match. See the tip from pastebin so you can post commands outputs and the contents of files from the live media.
Please do not post oversized images General_guidelines#Pasting_pictures_and_code.
Offline
I was trying to figure out how to do that. Thanks. I'll boot up the usb and post the output on pastebin soon and update the original post.
Last edited by PythonLinux (2021-07-27 01:24:38)
Offline
Is /dev/sda present when you are dropped to the rescue shell?
The PARTUUID matches between the loader config and the output of blkid. So I am wondering if the block device is not detected.
Offline
How can I tell if it's present from the rescue shell? What I generally use from the terminal, lsblk, doesn't work from the rescue shell.
Last edited by PythonLinux (2021-07-27 02:22:22)
Offline
ls /dev/sdaOffline
Thanks. It says
/dev/sda no such file or directory I tried to change it to sdb since that's what it was listed as in lsblk (and I mounted /dev/sdb for the install) but I got the same error for that.
Last edited by PythonLinux (2021-07-27 02:27:10)
Offline
From the rescue shell, is the vmd module loaded?
lsmodIf not, see if it can be loaded:
modprobe vmdOffline
I just checked and the vmd module is listed with the following syntax below the other modules
Module Size Used By
[all the other modules]
vmd 16384 0Offline
If you use the fallback initrd ( initramfs-linux-lts-fallback.img ) does that have the same issue?
From the live media the outputs of the following:
lspci -nnk
lsmod
dmesgOffline
(I never got around to adding the fallback option because I assumed it'd be unnecessary I assume I should do that.) In the meantime here's the outputs from the live media:
lscpi -nnk: https://paste.ubuntu.com/p/6P7FCCtBBV/
lsmod: https://paste.ubuntu.com/p/27dsNP63hH/
dmesg: https://paste.ubuntu.com/p/3sNdv8vXJs/
Also, thank you SO MUCH for telling me that pastebin clients are a thing. This makes my life SO much easier.
Edit: Just made the fallback entry. Same issue with the fallback.
Last edited by PythonLinux (2021-07-27 03:00:25)
Offline
10000:e0:17.0 SATA controller [0106]: Intel Corporation Device [8086:a0d3] (rev 20)
Subsystem: Hewlett-Packard Company Device [103c:883c]
Kernel driver in use: ahci[ 9.027662] ahci 10000:e0:17.0: version 3.0
[ 9.027672] ahci 10000:e0:17.0: can't derive routing for PCI INT A
[ 9.027673] ahci 10000:e0:17.0: PCI INT A: no GSI
[ 9.027741] ahci 10000:e0:17.0: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
[ 9.027743] ahci 10000:e0:17.0: flags: 64bit ncq sntf pm clo only pio slum part deso sadm sds
[ 9.027885] scsi host1: ahci
[ 9.027958] scsi host2: ahci
[ 9.027978] ata1: SATA max UDMA/133 abar m2048@0x52002000 port 0x52002100 irq 144
[ 9.027981] ata2: SATA max UDMA/133 abar m2048@0x52002000 port 0x52002180 irq 144
[ 9.027991] vmd 0000:00:0e.0: Bound to PCI domain 10000
....
[ 9.339195] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 9.339263] ata1: SATA link down (SStatus 0 SControl 300)
[ 9.340467] ata2.00: ATA-10: TOSHIBA MQ04ABF100, JU007C, max UDMA/100
[ 9.340468] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[ 9.341800] ata2.00: configured for UDMA/100
[ 9.341856] scsi 2:0:0:0: Direct-Access ATA TOSHIBA MQ04ABF1 7C PQ: 0 ANSI: 5
[ 9.341948] sd 2:0:0:0: [sdb] Drive-managed SMR disk
[ 9.341951] sd 2:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 9.341952] sd 2:0:0:0: [sdb] 4096-byte physical blocks
[ 9.341956] sd 2:0:0:0: [sdb] Write Protect is off
[ 9.341957] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 9.341971] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
....
[ 9.441105] sdb: sdb1 sdb2 sdb3
[ 9.449874] sd 2:0:0:0: [sdb] Attached SCSI diskFrom the rescue prompt check the output of dmesg to see if there is similar output to that in the code block above.
Have you tried using the linux kernel to see if the issue is limited to the linux-lts kernel?
Offline
I realized you could pipe the output of dmesg to less from the rescue prompt so I can actually check this.
I could not find any similar output about sda/sdb. I did find some SATA related stuff that I think might help. Since I can't use pipe from the rescue mode here's an image (in case I made any transcription mistakes) and a transcription https://ibb.co/Vx6s2DG
[other boot stuff]
[0.615952] ata1: SATA max UDMA/133 abar m2048@0x52002000 port 0x52002100 irq 142
[0.615956] ata2: SATA max UDMA/133 abar m2048@0x52002000 port 0x52002180 irq 142
[0.615958] vmd 0000:00:0e.0: Bound to PCI domain 10000
[0.941680] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[0.952066] ata1: SATA link down (SStatus 0 SControl 300)
[5.987868] ata2.00: qc timeout (cmd 0xec)
[5.989112] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[6.321977] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[16.547868] ata2.00: qc timeout (cmd 0xec)
[16.549092] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[16.549110] ata2: limiting SATA link speed to 3.0 Gbps
[16.881987] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[47.267857] ata2.00: qc timeout (cmd 0xec)
[47.268953] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[47.602039] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[Goes on to talk about the ps/2 controller and the USB and other stuff]I'm going to try to install the plain vanilla kernel (which I tried to avoid cause I was having freezing issues) by chrooting in and adding a boot entry to systemd and will tell you if it works.
Offline
Since I can pastebin from the live usb now and it's much easier to provide information here's the config file I made in /boot/loader/entries https://paste.ubuntu.com/p/9DTwPsbxVc/
The normal kernel does not have this issue and boots up just fine and I was able to log in as root (I've yet to make any other users)
Offline