Fedora fails to boot during upgrade from 25 to 26

Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
I followed the command line instructions in this guide and ran the following commands:
sudo dnf upgrade --refresh
sudo dnf install dnf-plugin-system-upgrade
sudo dnf system-upgrade download --releasever=26
After running sudo dnf system-upgrade reboot I selected the most recent Fedora option from GRUB (or rather let it automatically select it): Fedora (4.12.13-200.fc25.x86_64) 25 (Workstation Edition)
Doing this I get a few errors like this and it fails to boot at all:
[ 0.959745] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170303/psargs-364)
[ 0.959856] ACPI Error: Method parse/execution failed [_SN.PCI0-SAT0.SPT5._GTF] (Node ffff97e80e170e60), AE_NOT_FOUND (20170303/psparse-543)
I've tried googling these errors but have not had much luck finding similar cases.
I can boot into bash by adding init=/bin/bash to the boot script and the disk Fedora is installed on seems to work fine there.
fedora boot upgrade
add a comment |Â
up vote
2
down vote
favorite
I followed the command line instructions in this guide and ran the following commands:
sudo dnf upgrade --refresh
sudo dnf install dnf-plugin-system-upgrade
sudo dnf system-upgrade download --releasever=26
After running sudo dnf system-upgrade reboot I selected the most recent Fedora option from GRUB (or rather let it automatically select it): Fedora (4.12.13-200.fc25.x86_64) 25 (Workstation Edition)
Doing this I get a few errors like this and it fails to boot at all:
[ 0.959745] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170303/psargs-364)
[ 0.959856] ACPI Error: Method parse/execution failed [_SN.PCI0-SAT0.SPT5._GTF] (Node ffff97e80e170e60), AE_NOT_FOUND (20170303/psparse-543)
I've tried googling these errors but have not had much luck finding similar cases.
I can boot into bash by adding init=/bin/bash to the boot script and the disk Fedora is installed on seems to work fine there.
fedora boot upgrade
2
It's odd that the most recent available kernel is a F25 kernel after update, not an F26 one.
â mattdm
Oct 3 '17 at 17:30
I thought so too, but the guide does mention this: "With the dnf-plugin-system-upgrade package, your system reboots into the current kernel installed for Fedora 25; this is normal." Also note that this is during the upgrade. It has not yet completed since the upgrade should happen once the OS is loaded.
â mjuopperi
Oct 3 '17 at 19:49
Oh, yes -- sorry, I didn't realize it had failed that early.
â mattdm
Oct 3 '17 at 19:53
I'm not sure those errors are really the problem. Are there any other messages?
â mattdm
Oct 3 '17 at 21:33
No, just more errors like the second one I wrote down. Do you have any tips for debugging this further? I can get to bash, so I can probably read some logs. Just not sure where to look.
â mjuopperi
Oct 4 '17 at 8:06
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I followed the command line instructions in this guide and ran the following commands:
sudo dnf upgrade --refresh
sudo dnf install dnf-plugin-system-upgrade
sudo dnf system-upgrade download --releasever=26
After running sudo dnf system-upgrade reboot I selected the most recent Fedora option from GRUB (or rather let it automatically select it): Fedora (4.12.13-200.fc25.x86_64) 25 (Workstation Edition)
Doing this I get a few errors like this and it fails to boot at all:
[ 0.959745] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170303/psargs-364)
[ 0.959856] ACPI Error: Method parse/execution failed [_SN.PCI0-SAT0.SPT5._GTF] (Node ffff97e80e170e60), AE_NOT_FOUND (20170303/psparse-543)
I've tried googling these errors but have not had much luck finding similar cases.
I can boot into bash by adding init=/bin/bash to the boot script and the disk Fedora is installed on seems to work fine there.
fedora boot upgrade
I followed the command line instructions in this guide and ran the following commands:
sudo dnf upgrade --refresh
sudo dnf install dnf-plugin-system-upgrade
sudo dnf system-upgrade download --releasever=26
After running sudo dnf system-upgrade reboot I selected the most recent Fedora option from GRUB (or rather let it automatically select it): Fedora (4.12.13-200.fc25.x86_64) 25 (Workstation Edition)
Doing this I get a few errors like this and it fails to boot at all:
[ 0.959745] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170303/psargs-364)
[ 0.959856] ACPI Error: Method parse/execution failed [_SN.PCI0-SAT0.SPT5._GTF] (Node ffff97e80e170e60), AE_NOT_FOUND (20170303/psparse-543)
I've tried googling these errors but have not had much luck finding similar cases.
I can boot into bash by adding init=/bin/bash to the boot script and the disk Fedora is installed on seems to work fine there.
fedora boot upgrade
fedora boot upgrade
edited Oct 3 '17 at 17:29
Jeff Schaller
32.3k849109
32.3k849109
asked Oct 3 '17 at 16:38
mjuopperi
1364
1364
2
It's odd that the most recent available kernel is a F25 kernel after update, not an F26 one.
â mattdm
Oct 3 '17 at 17:30
I thought so too, but the guide does mention this: "With the dnf-plugin-system-upgrade package, your system reboots into the current kernel installed for Fedora 25; this is normal." Also note that this is during the upgrade. It has not yet completed since the upgrade should happen once the OS is loaded.
â mjuopperi
Oct 3 '17 at 19:49
Oh, yes -- sorry, I didn't realize it had failed that early.
â mattdm
Oct 3 '17 at 19:53
I'm not sure those errors are really the problem. Are there any other messages?
â mattdm
Oct 3 '17 at 21:33
No, just more errors like the second one I wrote down. Do you have any tips for debugging this further? I can get to bash, so I can probably read some logs. Just not sure where to look.
â mjuopperi
Oct 4 '17 at 8:06
add a comment |Â
2
It's odd that the most recent available kernel is a F25 kernel after update, not an F26 one.
â mattdm
Oct 3 '17 at 17:30
I thought so too, but the guide does mention this: "With the dnf-plugin-system-upgrade package, your system reboots into the current kernel installed for Fedora 25; this is normal." Also note that this is during the upgrade. It has not yet completed since the upgrade should happen once the OS is loaded.
â mjuopperi
Oct 3 '17 at 19:49
Oh, yes -- sorry, I didn't realize it had failed that early.
â mattdm
Oct 3 '17 at 19:53
I'm not sure those errors are really the problem. Are there any other messages?
â mattdm
Oct 3 '17 at 21:33
No, just more errors like the second one I wrote down. Do you have any tips for debugging this further? I can get to bash, so I can probably read some logs. Just not sure where to look.
â mjuopperi
Oct 4 '17 at 8:06
2
2
It's odd that the most recent available kernel is a F25 kernel after update, not an F26 one.
â mattdm
Oct 3 '17 at 17:30
It's odd that the most recent available kernel is a F25 kernel after update, not an F26 one.
â mattdm
Oct 3 '17 at 17:30
I thought so too, but the guide does mention this: "With the dnf-plugin-system-upgrade package, your system reboots into the current kernel installed for Fedora 25; this is normal." Also note that this is during the upgrade. It has not yet completed since the upgrade should happen once the OS is loaded.
â mjuopperi
Oct 3 '17 at 19:49
I thought so too, but the guide does mention this: "With the dnf-plugin-system-upgrade package, your system reboots into the current kernel installed for Fedora 25; this is normal." Also note that this is during the upgrade. It has not yet completed since the upgrade should happen once the OS is loaded.
â mjuopperi
Oct 3 '17 at 19:49
Oh, yes -- sorry, I didn't realize it had failed that early.
â mattdm
Oct 3 '17 at 19:53
Oh, yes -- sorry, I didn't realize it had failed that early.
â mattdm
Oct 3 '17 at 19:53
I'm not sure those errors are really the problem. Are there any other messages?
â mattdm
Oct 3 '17 at 21:33
I'm not sure those errors are really the problem. Are there any other messages?
â mattdm
Oct 3 '17 at 21:33
No, just more errors like the second one I wrote down. Do you have any tips for debugging this further? I can get to bash, so I can probably read some logs. Just not sure where to look.
â mjuopperi
Oct 4 '17 at 8:06
No, just more errors like the second one I wrote down. Do you have any tips for debugging this further? I can get to bash, so I can probably read some logs. Just not sure where to look.
â mjuopperi
Oct 4 '17 at 8:06
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f395882%2ffedora-fails-to-boot-during-upgrade-from-25-to-26%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
2
It's odd that the most recent available kernel is a F25 kernel after update, not an F26 one.
â mattdm
Oct 3 '17 at 17:30
I thought so too, but the guide does mention this: "With the dnf-plugin-system-upgrade package, your system reboots into the current kernel installed for Fedora 25; this is normal." Also note that this is during the upgrade. It has not yet completed since the upgrade should happen once the OS is loaded.
â mjuopperi
Oct 3 '17 at 19:49
Oh, yes -- sorry, I didn't realize it had failed that early.
â mattdm
Oct 3 '17 at 19:53
I'm not sure those errors are really the problem. Are there any other messages?
â mattdm
Oct 3 '17 at 21:33
No, just more errors like the second one I wrote down. Do you have any tips for debugging this further? I can get to bash, so I can probably read some logs. Just not sure where to look.
â mjuopperi
Oct 4 '17 at 8:06