[SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

konf · 2021-01-04 13:26:54

UPDATE AS SOLVED:

Thanks for your interest in this post. The two problems are now solved as described below:

1) Failed to mount /boot & emergency mode

Turns out when downgrading kernel from a installation medium I forgot to mount /boot, it resulted in two kernels of different versions with and without /boot being mounted.

Solution: first just mount /root and removing the improperly installed kernel, then mount /boot and proceed with kernel installation/downgrading.

2) usb error -62 and keyboard not working

This issue went away itself after two days of shutting my macbook down, so I don't know exactly what happened. If you have similar experience please join the discussion!

ORIGINAL POST:

Hi,

Last night I upgraded linux and linux-headers to 5.10.4, then first I ran into the problem of keyboard not working, leaving me stuck at tty1 with the following error message:

[   12.727618] usb 2-3: device not accepting address 2, error -62
[ similar num] usb 2-3: device not accepting address 3, error -62
[ similar num] usb 2-3: device not accepting address 4, error -62
[ similar num] usb 2-3: device not accepting address 5, error -62
[ similar num] usb usb2-port3: unable to enumerate USB device

Then I did a list of things that lead to the error of

[FAILED] Failed to mount /boot...[DEPEND] Dependency failed for Local File Systems.

, followed by the message of "You are in emergency mode", then again the usb error -62 that rendered keyboard unusable except for the power button.

The list of things I did:

At first at tty1, I somehow logged in i3 fast enough before the usb error message showed up and downgraded kernel to 5.10.3. It didn't help, and afterwards the keyboard was not working even if I had logged into i3.
Since I was stuck at the emergency mode screen with the keyboard unusable, I boot into a USB installation medium and tried downgrading to 5.9.*, full system upgrade, and reinstalling all packages. Nothing worked.
Then I installed LTS kernel using Franklin Yu's answer on Stack Exchange, still the same, and I might have additional problems to solve since I uninstalled the stable kernel...

I'm using a late-2013 rMBP, UEFI dual boot with macOS.

parted -l:

Disk /dev/sda: 500GB
Partition Table: gpt
Disk Flags:
Number  Start      End       Size      File system   Name                         Flags
1       20.5kB     210MB     210MB     fat32         EFI System Partition         boot, esp
2       210MB      60.3GB    60.1GB
4       60.3GB     500GB     440GB     ext4                                       msftdata

lsblk -f

NAME  FSTYPE  FSVER    LABEL    UUID                                  FSAVAIL       FSUSE%    MOUNTPOINT
sda1  vfat    FAT32    EFI      67E3-17ED
sda2  apfs                      0ee7b776-7b30-408b-98c3-a67519ce1030
sda4  ext4    1.0               48f5256e-bb11-48ec-82cc-d4eb6a14a5ff  134.5G        61%       /

Please help! Let me know if you need more info, thanks in advance!

Last edited by konf (2021-01-07 08:46:32)

seth · 2021-01-04 14:11:07

The symptoms (certainly "Then I did a list of things that lead to the error of") smell a hell lot like you forgot to mount the boot partition or are booting from the root partition but in any event, installed and running kernel fall apart.
Compare

uname -a
pacman -Qs linux

Error 32 is a timeout and the device or plug could be physically damaged, but you don't seem to encouter the problem/error w/ the installation iso, do you?

Last edited by seth (2021-01-04 14:11:18)

konf · 2021-01-04 14:23:22

seth wrote:

The symptoms (certainly "Then I did a list of things that lead to the error of") smell a hell lot like you forgot to mount the boot partition or are booting from the root partition but in any event, installed and running kernel fall apart.
Compare
uname -a
pacman -Qs linux
Error 32 is a timeout and the device or plug could be physically damaged, but you don't seem to encouter the problem/error w/ the installation iso, do you?

Where should I run uname -a? Because when booting into the installation iso, its output is always

Linux archiso 5.10.3-arch1-1 #SMP PREEMPT...

, which is the current version for download.

pacman -Qs linux

returns linux-lts and linux-lts-headers 5.4.86.1, among others.

Yeah, the usb error -62 and keyboard thing goes away within the installation iso and macOS, only happens when trying to boot into arch. It could very possible be physical damage, the laptop is seven years old after all.

Last edited by konf (2021-01-04 14:29:52)

seth · 2021-01-04 14:35:44

We're gonna need that for the installed system…

From the archiso, mount the root partition of the installed system and try

mount sda4 /mnt
file /mnt/boot/vmlinuz-linux

Then mount the boot partition to /mnt/boot and check again

mount sda1 /mnt/boot
file /mnt/boot/vmlinuz-linux

If you've a kernel in the mounted and unmounted /mnt/boot, that's generally a bad sign.

konf · 2021-01-04 14:44:22

seth wrote:

We're gonna need that for the installed system…
From the archiso, mount the root partition of the installed system and try
mount sda4 /mnt
file /mnt/boot/vmlinuz-linux
Then mount the boot partition to /mnt/boot and check again
mount sda1 /mnt/boot
file /mnt/boot/vmlinuz-linux
If you've a kernel in the mounted and unmounted /mnt/boot, that's generally a bad sign.

No wonder I was so confused by the uname command! And keyboard is currently dead for the installed system...

I've got two kernels... the first output is the LTS kernel I installed as mentioned in the list, the second outputs:

/mnt/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 5.10.3-arch1-1 (linux@archlinux) #1 SMP PREEMPT... R0-rootFS, swap_dev 0x0, Normal VGA

seth · 2021-01-04 14:49:35

The lts kernel is in vmlinuz-linux-lts
Please post the actual IO - in doubt feel free to make a photo of your display, upload that at imgur or so and post a link.
Also for "pacman -Qs linux"

konf · 2021-01-04 15:12:40

seth wrote:

The lts kernel is in vmlinuz-linux-lts
Please post the actual IO - in doubt feel free to make a photo of your display, upload that at imgur or so and post a link.
Also for "pacman -Qs linux"

Yep, I might have installed the lts kernel without mounting /boot. It should be causing the double kernel problem, right?

I went on to unmount /mnt/boot and removed the lts kernel, then mount /mnt/boot back to install the stable kernel.

And now the emergency mode is gone and I can reach tty1, but the usb error message and dead keyboard persist, with additional error messages (I'll put them on later)

Then I boot back into the installation iso, and did the 2 commands you mentioned above. This time, before mounting sda1 to /mnt/boot, there's only an intel-ucode.img.

Only after mounting sda1 does vmlinuz-linux appears, among others.

The "pacman -Qs linux" and "file /mnt/boot/vmlinuz-linux" now matches as linux 5.10.3.arch1.1. Does this mean the kernel problem (unable to mount /boot, emergency mode) is solved?

And the additional error messages at tty1:

[...numbers...] xhci_hcd 0000:00:14:0: xHCI host controller not responding, assume dead
[...numbers...] xhci_hcd 0000:00:14:0: HC died; cleaning up
[...numbers...] bcm5974 1-5:1.2: could not read from device
[...numbers...] sd 1:0:0:0: [sdb] Asking for cache data failed
[...numbers...] sd 1:0:0:0: Assuming drive cache: write through
[...numbers...] bcm5974 1-5:1.2: could not read from device
[...numbers...] usb usb2-port3: couldn't allocate usb_device
[...numbers...] usb 1-3-port: couldn't allocate usb_device

seth · 2021-01-04 15:22:50

I'd try to - properly ;-) - re-install the LTS kernel and boot that.
If you've a keyboard there, dump a journal from a previous boot ("sudo journalctl -b -1" for the last one) that reflects the broken condition w/ the 5.10.3 kernel and upload that.
Also "lspci" for the actual model of the host controller (xhci is usb and the entire controller is disfunctional)

konf · 2021-01-04 16:30:53

Thanks so much for walking me through this. Installing the lts kernel is a better choice, and indeed it worked!

Well only partly, but still I got around the error messages and boot into the lts kernel 2 times out of four tries.

I'll dig into the other things you mentioned and update back afterwards.

Next time when downgrading kernel from a live medium I will remember to mount /mnt/boot, that's one of the lessons I've learned today

seth · 2021-01-04 21:43:24

2 times out of four tries

Sounds like a race condition.

Do you have a *hci/usb hand-off setting in the BIOS?
Do you select the kernel at the bootloader or do you automatically boot into a kernel?

konf · 2021-01-05 08:22:08

There's an awfully long time (around 30 seconds) of black screen with just backlight on after powering up the laptop, and

1) I wasn't able to enter macbook's open firmware (BIOS equivalent) by pressing "Alt", "Command", "O" and "F", so I cannot see the setting.

2) It boot straight into the LTS kernel, without showing options (I'm using UEFI)

Thanks for following up!

seth · 2021-01-05 09:37:13

https://wiki.archlinux.org/index.php/Ma … re_booting but I'm not sure skipping the delay will make things more reliable.
You could try to pass "rootdelay=10" to the kernel parameters…

konf · 2021-01-05 10:02:58

Will look into this option!

However, this install (my first one, it's 6 months old) is starting to feel like a hot mess, I looked everywhere but didn't find any information regarding the "usb error -62" as well as the dead keyboard. Fortunately I've got another ThinkPad that works fine with the 5.10.4 kernel, so at least I'm not running out of arch.

Thanks for your help! I need to spend more time dig into those journalctl logs as well as internet searching.

konf · 2021-01-07 08:39:27

seth wrote:

https://wiki.archlinux.org/index.php/Ma … re_booting but I'm not sure skipping the delay will make things more reliable.
You could try to pass "rootdelay=10" to the kernel parameters…

Hi seth,

The usb and keyboard problem mysteriously went away after I switched to the 5.10.4 kernel and shut the laptop down for two days. Before that the journalctl didn't show much besides the -62 error I mentioned above. So I'll go ahead and edit this post as solved.

I'm very glad that my macbook with arch is back on track. Thanks so much for your help!

Arch Linux

#1 2021-01-04 13:26:54

[SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#2 2021-01-04 14:11:07

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#3 2021-01-04 14:23:22

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#4 2021-01-04 14:35:44

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#5 2021-01-04 14:44:22

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#6 2021-01-04 14:49:35

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#7 2021-01-04 15:12:40

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#8 2021-01-04 15:22:50

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#9 2021-01-04 16:30:53

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#10 2021-01-04 21:43:24

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#11 2021-01-05 08:22:08

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#12 2021-01-05 09:37:13

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#13 2021-01-05 10:02:58

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

#14 2021-01-07 08:39:27

Re: [SOLVED] Failed to mount /boot & usb error -62 after 5.10.4 kernel

Board footer