Updating linux kernel broke my computer

up vote
1
down vote

favorite

Today I updated the linux kernel to 4.8.12-2 using pacman -Suy. Next time I tried to turn on my computer, I got the following error:

Starting vmlinuz-linux
Using load options 'ro root=UUID=1d7....... initrd=initramfs-linux.img'
EFI stub: ERROR: Failed to read file
Trying to load files to higher address
EFI stub: ERROR: Failed to read file

Using an arch live usb, I backed up /boot/vmlinuz-linux and installed version 4.8.11-1. Now, when I try to boot, only the lts version shows up in the rEFInd submenu (both lts and non-lts used to show up). When I try to edit /boot/EFI/refind/refind.conf, I get an input/output error.

Please help me. I am totally lost at this point. Just hoping my laptop isn't lost.

asked Dec 8 '16 at 5:17

Marcel

1201116

Chroot in, make sure / and /boot are mounted, and rerun the upgrade. In all likelihood, /boot was not mounted during your last upgrade.
â€“Â jasonwryan
Dec 8 '16 at 5:33

@jasonwryan /boot was definitly mounted. If it were not, wouldn't the upgrade have had no effect anyway?
â€“Â Marcel
Dec 8 '16 at 5:48

No, it would have just installed the kernel to the wrong place, which would lead to the situation you are describing.
â€“Â jasonwryan
Dec 8 '16 at 5:53

Ok I will try that. Thank you.
â€“Â Marcel
Dec 8 '16 at 5:53

I tried that and it didn't work. My exact commands were mount /dev/sda1 /mnt; mount /dev/sda2 /mnt/boot; arch-chroot /mnt; pacman -Suy
â€“Â Marcel
Dec 8 '16 at 5:59

add a commentÂ |Â

up vote
1
down vote

favorite

Today I updated the linux kernel to 4.8.12-2 using pacman -Suy. Next time I tried to turn on my computer, I got the following error:

Starting vmlinuz-linux
Using load options 'ro root=UUID=1d7....... initrd=initramfs-linux.img'
EFI stub: ERROR: Failed to read file
Trying to load files to higher address
EFI stub: ERROR: Failed to read file

Please help me. I am totally lost at this point. Just hoping my laptop isn't lost.

asked Dec 8 '16 at 5:17

Marcel

1201116

Chroot in, make sure / and /boot are mounted, and rerun the upgrade. In all likelihood, /boot was not mounted during your last upgrade.
â€“Â jasonwryan
Dec 8 '16 at 5:33

@jasonwryan /boot was definitly mounted. If it were not, wouldn't the upgrade have had no effect anyway?
â€“Â Marcel
Dec 8 '16 at 5:48

No, it would have just installed the kernel to the wrong place, which would lead to the situation you are describing.
â€“Â jasonwryan
Dec 8 '16 at 5:53

Ok I will try that. Thank you.
â€“Â Marcel
Dec 8 '16 at 5:53

I tried that and it didn't work. My exact commands were mount /dev/sda1 /mnt; mount /dev/sda2 /mnt/boot; arch-chroot /mnt; pacman -Suy
â€“Â Marcel
Dec 8 '16 at 5:59

add a commentÂ |Â

up vote
1
down vote

favorite

Today I updated the linux kernel to 4.8.12-2 using pacman -Suy. Next time I tried to turn on my computer, I got the following error:

Starting vmlinuz-linux
Using load options 'ro root=UUID=1d7....... initrd=initramfs-linux.img'
EFI stub: ERROR: Failed to read file
Trying to load files to higher address
EFI stub: ERROR: Failed to read file

Please help me. I am totally lost at this point. Just hoping my laptop isn't lost.

asked Dec 8 '16 at 5:17

Marcel

1201116

Today I updated the linux kernel to 4.8.12-2 using pacman -Suy. Next time I tried to turn on my computer, I got the following error:

Starting vmlinuz-linux
Using load options 'ro root=UUID=1d7....... initrd=initramfs-linux.img'
EFI stub: ERROR: Failed to read file
Trying to load files to higher address
EFI stub: ERROR: Failed to read file

Please help me. I am totally lost at this point. Just hoping my laptop isn't lost.

kernel boot

asked Dec 8 '16 at 5:17

Marcel

1201116

asked Dec 8 '16 at 5:17

Marcel

1201116

asked Dec 8 '16 at 5:17

Marcel

1201116

asked Dec 8 '16 at 5:17

Marcel

1201116

asked Dec 8 '16 at 5:17

Marcel

1201116

Chroot in, make sure / and /boot are mounted, and rerun the upgrade. In all likelihood, /boot was not mounted during your last upgrade.
â€“Â jasonwryan
Dec 8 '16 at 5:33

@jasonwryan /boot was definitly mounted. If it were not, wouldn't the upgrade have had no effect anyway?
â€“Â Marcel
Dec 8 '16 at 5:48

No, it would have just installed the kernel to the wrong place, which would lead to the situation you are describing.
â€“Â jasonwryan
Dec 8 '16 at 5:53

Ok I will try that. Thank you.
â€“Â Marcel
Dec 8 '16 at 5:53

I tried that and it didn't work. My exact commands were mount /dev/sda1 /mnt; mount /dev/sda2 /mnt/boot; arch-chroot /mnt; pacman -Suy
â€“Â Marcel
Dec 8 '16 at 5:59

add a commentÂ |Â

Chroot in, make sure / and /boot are mounted, and rerun the upgrade. In all likelihood, /boot was not mounted during your last upgrade.
â€“Â jasonwryan
Dec 8 '16 at 5:33

@jasonwryan /boot was definitly mounted. If it were not, wouldn't the upgrade have had no effect anyway?
â€“Â Marcel
Dec 8 '16 at 5:48

No, it would have just installed the kernel to the wrong place, which would lead to the situation you are describing.
â€“Â jasonwryan
Dec 8 '16 at 5:53

Ok I will try that. Thank you.
â€“Â Marcel
Dec 8 '16 at 5:53

I tried that and it didn't work. My exact commands were mount /dev/sda1 /mnt; mount /dev/sda2 /mnt/boot; arch-chroot /mnt; pacman -Suy
â€“Â Marcel
Dec 8 '16 at 5:59

Chroot in, make sure / and /boot are mounted, and rerun the upgrade. In all likelihood, /boot was not mounted during your last upgrade.
â€“Â jasonwryan
Dec 8 '16 at 5:33

@jasonwryan /boot was definitly mounted. If it were not, wouldn't the upgrade have had no effect anyway?
â€“Â Marcel
Dec 8 '16 at 5:48

No, it would have just installed the kernel to the wrong place, which would lead to the situation you are describing.
â€“Â jasonwryan
Dec 8 '16 at 5:53

Ok I will try that. Thank you.
â€“Â Marcel
Dec 8 '16 at 5:53

I tried that and it didn't work. My exact commands were mount /dev/sda1 /mnt; mount /dev/sda2 /mnt/boot; arch-chroot /mnt; pacman -Suy
â€“Â Marcel
Dec 8 '16 at 5:59

add a commentÂ |Â

3 Answers
3

active

oldest

votes

up vote
0
down vote

I faced the same problem. When system update was running, my laptop suddenly turned off (I have no idea why), and when I tried to boot it I saw the same message. I fixed it this way: I booted from rescue flash drive. Then:

wifi-menu - enable wifi network.

mount /dev/sda2 /mnt

arch-chroot /mnt

mount -o rw /dev/sda1 /boot

cd /var/cache/pacman/pkg

pacman -U linux-4.8.12-2-x86_64.pkg.tar.xz

Package was reinstalled. It notified me that there were problems with some file and they were fixed. After that I closed session and unmounted all drives and rebooted. System boots ok now.
Hope this helps.

edited Dec 9 '16 at 14:40

Tomasz

8,41552560

answered Dec 9 '16 at 14:27

Taras

101

add a commentÂ |Â

up vote
0
down vote

Somehow, my esp got corrupted. After backing everything up and running S.M.A.R.T. tests to make sure it wasn't a hardware issue, I reformatted the esp and reinstalled rEFInd:

 mkfs.fat -F32 /dev/sda2
 refind-install --usedefault /dev/sda2
 cd /var/cache/pacman/pkg
 pacman -U linux-4.8.12-2-x86_64.pkg.tar.xz
 mkinitcpio -p linux

answered Dec 12 '16 at 17:51

Marcel

1201116

add a commentÂ |Â

up vote
0
down vote

Just found out that EFI stub: ERROR: failed to read file. (at least in my case) actually refers specifically to initrd (which had been nuked by an unplanned shutdown during updates).

someone changed the message to 'generalize' the code at some point.

edited Sep 8 at 5:45

Tejas

1,77621837

answered Sep 7 at 21:38

Jamie Pate

1011

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f328859%2fupdating-linux-kernel-broke-my-computer%23new-answer', 'question_page');

);

Post as a guest

Name

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

up vote
0
down vote

wifi-menu - enable wifi network.

mount /dev/sda2 /mnt

arch-chroot /mnt

mount -o rw /dev/sda1 /boot

cd /var/cache/pacman/pkg

pacman -U linux-4.8.12-2-x86_64.pkg.tar.xz

edited Dec 9 '16 at 14:40

Tomasz

8,41552560

answered Dec 9 '16 at 14:27

Taras

101

add a commentÂ |Â

up vote
0
down vote

wifi-menu - enable wifi network.

mount /dev/sda2 /mnt

arch-chroot /mnt

mount -o rw /dev/sda1 /boot

cd /var/cache/pacman/pkg

pacman -U linux-4.8.12-2-x86_64.pkg.tar.xz

edited Dec 9 '16 at 14:40

Tomasz

8,41552560

answered Dec 9 '16 at 14:27

Taras

101

add a commentÂ |Â

up vote
0
down vote

wifi-menu - enable wifi network.

mount /dev/sda2 /mnt

arch-chroot /mnt

mount -o rw /dev/sda1 /boot

cd /var/cache/pacman/pkg

pacman -U linux-4.8.12-2-x86_64.pkg.tar.xz

edited Dec 9 '16 at 14:40

Tomasz

8,41552560

answered Dec 9 '16 at 14:27

Taras

101

wifi-menu - enable wifi network.

mount /dev/sda2 /mnt

arch-chroot /mnt

mount -o rw /dev/sda1 /boot

cd /var/cache/pacman/pkg

pacman -U linux-4.8.12-2-x86_64.pkg.tar.xz

edited Dec 9 '16 at 14:40

Tomasz

8,41552560

answered Dec 9 '16 at 14:27

Taras

101

edited Dec 9 '16 at 14:40

Tomasz

8,41552560

edited Dec 9 '16 at 14:40

Tomasz

8,41552560

edited Dec 9 '16 at 14:40

Tomasz

8,41552560

answered Dec 9 '16 at 14:27

Taras

101

answered Dec 9 '16 at 14:27

Taras

101

answered Dec 9 '16 at 14:27

Taras

101

add a commentÂ |Â

up vote
0
down vote

Somehow, my esp got corrupted. After backing everything up and running S.M.A.R.T. tests to make sure it wasn't a hardware issue, I reformatted the esp and reinstalled rEFInd:

 mkfs.fat -F32 /dev/sda2
 refind-install --usedefault /dev/sda2
 cd /var/cache/pacman/pkg
 pacman -U linux-4.8.12-2-x86_64.pkg.tar.xz
 mkinitcpio -p linux

answered Dec 12 '16 at 17:51

Marcel

1201116

add a commentÂ |Â

up vote
0
down vote

Somehow, my esp got corrupted. After backing everything up and running S.M.A.R.T. tests to make sure it wasn't a hardware issue, I reformatted the esp and reinstalled rEFInd:

 mkfs.fat -F32 /dev/sda2
 refind-install --usedefault /dev/sda2
 cd /var/cache/pacman/pkg
 pacman -U linux-4.8.12-2-x86_64.pkg.tar.xz
 mkinitcpio -p linux

answered Dec 12 '16 at 17:51

Marcel

1201116

add a commentÂ |Â

up vote
0
down vote

Somehow, my esp got corrupted. After backing everything up and running S.M.A.R.T. tests to make sure it wasn't a hardware issue, I reformatted the esp and reinstalled rEFInd:

 mkfs.fat -F32 /dev/sda2
 refind-install --usedefault /dev/sda2
 cd /var/cache/pacman/pkg
 pacman -U linux-4.8.12-2-x86_64.pkg.tar.xz
 mkinitcpio -p linux

answered Dec 12 '16 at 17:51

Marcel

1201116

Somehow, my esp got corrupted. After backing everything up and running S.M.A.R.T. tests to make sure it wasn't a hardware issue, I reformatted the esp and reinstalled rEFInd:

 mkfs.fat -F32 /dev/sda2
 refind-install --usedefault /dev/sda2
 cd /var/cache/pacman/pkg
 pacman -U linux-4.8.12-2-x86_64.pkg.tar.xz
 mkinitcpio -p linux

answered Dec 12 '16 at 17:51

Marcel

1201116

answered Dec 12 '16 at 17:51

Marcel

1201116

answered Dec 12 '16 at 17:51

Marcel

1201116

answered Dec 12 '16 at 17:51

Marcel

1201116

add a commentÂ |Â

up vote
0
down vote

Just found out that EFI stub: ERROR: failed to read file. (at least in my case) actually refers specifically to initrd (which had been nuked by an unplanned shutdown during updates).

someone changed the message to 'generalize' the code at some point.

edited Sep 8 at 5:45

Tejas

1,77621837

answered Sep 7 at 21:38

Jamie Pate

1011

add a commentÂ |Â

up vote
0
down vote

Just found out that EFI stub: ERROR: failed to read file. (at least in my case) actually refers specifically to initrd (which had been nuked by an unplanned shutdown during updates).

someone changed the message to 'generalize' the code at some point.

edited Sep 8 at 5:45

Tejas

1,77621837

answered Sep 7 at 21:38

Jamie Pate

1011

add a commentÂ |Â

up vote
0
down vote

Just found out that EFI stub: ERROR: failed to read file. (at least in my case) actually refers specifically to initrd (which had been nuked by an unplanned shutdown during updates).

someone changed the message to 'generalize' the code at some point.

edited Sep 8 at 5:45

Tejas

1,77621837

answered Sep 7 at 21:38

Jamie Pate

1011

Just found out that EFI stub: ERROR: failed to read file. (at least in my case) actually refers specifically to initrd (which had been nuked by an unplanned shutdown during updates).

someone changed the message to 'generalize' the code at some point.

edited Sep 8 at 5:45

Tejas

1,77621837

answered Sep 7 at 21:38

Jamie Pate

1011

edited Sep 8 at 5:45

Tejas

1,77621837

edited Sep 8 at 5:45

Tejas

1,77621837

edited Sep 8 at 5:45

Tejas

1,77621837

answered Sep 7 at 21:38

Jamie Pate

1011

answered Sep 7 at 21:38

Jamie Pate

1011

answered Sep 7 at 21:38

Jamie Pate

1011

add a commentÂ |Â

draft saved

draft discarded

draft saved

draft discarded

Post as a guest

Name

搜尋此網誌

mjhjmtu