FS#72734 - Kernel 5.15.2 can't find root partiotion (Macbook Pro mid-2009)
Attached to Project:
Arch Linux
Opened by Uldis Dz (putvejs) - Saturday, 13 November 2021, 10:44 GMT
Last edited by Jan Alexander Steffens (heftig) - Monday, 22 November 2021, 00:54 GMT
Opened by Uldis Dz (putvejs) - Saturday, 13 November 2021, 10:44 GMT
Last edited by Jan Alexander Steffens (heftig) - Monday, 22 November 2021, 00:54 GMT
|
Details
Description:
After upgrading Arch system from kernel 5.14.15 to 5.15.2 it stopped booting with error about not finding disk device Additional info: [root@archiso /]# pacman -Qe base 2-2 broadcom-wl 6.30.223.271-343 efibootmgr 17-2 grub 2:2.06-2 intel-ucode 20210608-1 linux 5.15.2.arch1-1 linux-firmware 20211027.1d00989-1 nano 5.9-1 networkmanager 1.32.12-1 openssh 8.8p1-1 Steps to reproduce: After upgrading system with pacman -Suy to kernel 5.15.2 it stopped to recognize root partition. I repeated clean install according to https://wiki.archlinux.org/title/installation_guide and it still doesn't work If boot from USB live disk (kernel version 5.14.15) everything work fine and disk is recognized See boot error: Starting version 249.6-3-arch :: running hook [udev] :: Triggering uevents... Waiting 10 seconds for device /dev/disk/by-uuid/24fc33c2-0682-460b-99fb-1cd2c4eae224 ERROR: device *UUID=248c33c2-0682-460b-99/b-1caZcAeae224'not found. Skipping fsck. mounting *UUID=24fc33c2-0682-460b-998b-1cd2c4eae224'on real root mount: new root: can't find UUID=24fc33c2-0682-460b-99fb-1cd2c4eae224. You are now being dropped into an emergency shell. sh: can't access tty:job control turned off |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Monday, 22 November 2021, 00:54 GMT
Reason for closing: Fixed
Additional comments about closing: linux 5.15.3.arch1-1
Monday, 22 November 2021, 00:54 GMT
Reason for closing: Fixed
Additional comments about closing: linux 5.15.3.arch1-1
dmesg output log is attached.
`[ 16.403940] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)` and following lines seem suspicious.
Downgrading to previous kernel, 5.14.16-arch1-1, also resolved booing issue.
`https://lore.kernel.org/all/87h7ccw9qc.fsf@yujinakao.com/`