File Check Start caused âNo Bootable Device Foundâ on Fedora 28 [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
Background Info
1.) I'm still very new to Linux and Fedora in general, so if someone gives a possible solution just know I will likely ask follow up questions partially out of not knowing what to do and partially out of trying to learn.
2.) I've tried solving this issue myself to the best of my ability, and by looking around the internet to no avail - including checking older posts here on StackExchange.
3.) I had been running Fedora 28 on an Acer Nitro V laptop.
Actual Issue
This issue started around Friday night when I downloaded the latest set of OS updates through the "Software" application that comes with the Fedora OS (equivalent to "$ sudo dnf update" I believe). I powered off my laptop after the updates were downloaded, but upon starting my laptop the next morning I faced an issue where every attempt to login into one of my system's workstations (including rescue mode) was met with an ungodly long process that simply read:
A start job is running for File System Check on /dev/disk/by-uuid/"laptop-specific-file" (some time elapsed / no limit)
I simply let the process run over the course of something like 5-6 hours - come this morning it finally finished, but upon starting my laptop an even worse issue emerged.
Upon my laptop booting up I was met with a "No Bootable Device Found" message. Thinking it was some issue with my BIOS I checked my boot options to find no boot options even listed. Searching around the internet I tried a couple different solutions like this to no avail either.
I then created a LiveUSB from my old desktop to see if that could help - luckily it did - upon booting into the LiveUSB and rifling through my files I discovered all my files and partitions are still intact as they were before this whole debacle started.
The issue now is I simply don't know what to do. I'd like to think there is a way to reinstall Fedora through the LiveUSB and "reconnect it" with my old partitions (if that makes sense) - but I'm not experienced enough to know if that's even possible. My other guess is to simply nuke my HDD, reinstall Fedora, and start from scratch (that wouldn't be too much of an issue since I backup most of my files from the Live USB or in the cloud).
What course of action could I take to solve this issue?
fedora filesystems boot
closed as too broad by Rui F Ribeiro, schily, slm⦠Jul 29 at 22:33
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
up vote
1
down vote
favorite
Background Info
1.) I'm still very new to Linux and Fedora in general, so if someone gives a possible solution just know I will likely ask follow up questions partially out of not knowing what to do and partially out of trying to learn.
2.) I've tried solving this issue myself to the best of my ability, and by looking around the internet to no avail - including checking older posts here on StackExchange.
3.) I had been running Fedora 28 on an Acer Nitro V laptop.
Actual Issue
This issue started around Friday night when I downloaded the latest set of OS updates through the "Software" application that comes with the Fedora OS (equivalent to "$ sudo dnf update" I believe). I powered off my laptop after the updates were downloaded, but upon starting my laptop the next morning I faced an issue where every attempt to login into one of my system's workstations (including rescue mode) was met with an ungodly long process that simply read:
A start job is running for File System Check on /dev/disk/by-uuid/"laptop-specific-file" (some time elapsed / no limit)
I simply let the process run over the course of something like 5-6 hours - come this morning it finally finished, but upon starting my laptop an even worse issue emerged.
Upon my laptop booting up I was met with a "No Bootable Device Found" message. Thinking it was some issue with my BIOS I checked my boot options to find no boot options even listed. Searching around the internet I tried a couple different solutions like this to no avail either.
I then created a LiveUSB from my old desktop to see if that could help - luckily it did - upon booting into the LiveUSB and rifling through my files I discovered all my files and partitions are still intact as they were before this whole debacle started.
The issue now is I simply don't know what to do. I'd like to think there is a way to reinstall Fedora through the LiveUSB and "reconnect it" with my old partitions (if that makes sense) - but I'm not experienced enough to know if that's even possible. My other guess is to simply nuke my HDD, reinstall Fedora, and start from scratch (that wouldn't be too much of an issue since I backup most of my files from the Live USB or in the cloud).
What course of action could I take to solve this issue?
fedora filesystems boot
closed as too broad by Rui F Ribeiro, schily, slm⦠Jul 29 at 22:33
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Background Info
1.) I'm still very new to Linux and Fedora in general, so if someone gives a possible solution just know I will likely ask follow up questions partially out of not knowing what to do and partially out of trying to learn.
2.) I've tried solving this issue myself to the best of my ability, and by looking around the internet to no avail - including checking older posts here on StackExchange.
3.) I had been running Fedora 28 on an Acer Nitro V laptop.
Actual Issue
This issue started around Friday night when I downloaded the latest set of OS updates through the "Software" application that comes with the Fedora OS (equivalent to "$ sudo dnf update" I believe). I powered off my laptop after the updates were downloaded, but upon starting my laptop the next morning I faced an issue where every attempt to login into one of my system's workstations (including rescue mode) was met with an ungodly long process that simply read:
A start job is running for File System Check on /dev/disk/by-uuid/"laptop-specific-file" (some time elapsed / no limit)
I simply let the process run over the course of something like 5-6 hours - come this morning it finally finished, but upon starting my laptop an even worse issue emerged.
Upon my laptop booting up I was met with a "No Bootable Device Found" message. Thinking it was some issue with my BIOS I checked my boot options to find no boot options even listed. Searching around the internet I tried a couple different solutions like this to no avail either.
I then created a LiveUSB from my old desktop to see if that could help - luckily it did - upon booting into the LiveUSB and rifling through my files I discovered all my files and partitions are still intact as they were before this whole debacle started.
The issue now is I simply don't know what to do. I'd like to think there is a way to reinstall Fedora through the LiveUSB and "reconnect it" with my old partitions (if that makes sense) - but I'm not experienced enough to know if that's even possible. My other guess is to simply nuke my HDD, reinstall Fedora, and start from scratch (that wouldn't be too much of an issue since I backup most of my files from the Live USB or in the cloud).
What course of action could I take to solve this issue?
fedora filesystems boot
Background Info
1.) I'm still very new to Linux and Fedora in general, so if someone gives a possible solution just know I will likely ask follow up questions partially out of not knowing what to do and partially out of trying to learn.
2.) I've tried solving this issue myself to the best of my ability, and by looking around the internet to no avail - including checking older posts here on StackExchange.
3.) I had been running Fedora 28 on an Acer Nitro V laptop.
Actual Issue
This issue started around Friday night when I downloaded the latest set of OS updates through the "Software" application that comes with the Fedora OS (equivalent to "$ sudo dnf update" I believe). I powered off my laptop after the updates were downloaded, but upon starting my laptop the next morning I faced an issue where every attempt to login into one of my system's workstations (including rescue mode) was met with an ungodly long process that simply read:
A start job is running for File System Check on /dev/disk/by-uuid/"laptop-specific-file" (some time elapsed / no limit)
I simply let the process run over the course of something like 5-6 hours - come this morning it finally finished, but upon starting my laptop an even worse issue emerged.
Upon my laptop booting up I was met with a "No Bootable Device Found" message. Thinking it was some issue with my BIOS I checked my boot options to find no boot options even listed. Searching around the internet I tried a couple different solutions like this to no avail either.
I then created a LiveUSB from my old desktop to see if that could help - luckily it did - upon booting into the LiveUSB and rifling through my files I discovered all my files and partitions are still intact as they were before this whole debacle started.
The issue now is I simply don't know what to do. I'd like to think there is a way to reinstall Fedora through the LiveUSB and "reconnect it" with my old partitions (if that makes sense) - but I'm not experienced enough to know if that's even possible. My other guess is to simply nuke my HDD, reinstall Fedora, and start from scratch (that wouldn't be too much of an issue since I backup most of my files from the Live USB or in the cloud).
What course of action could I take to solve this issue?
fedora filesystems boot
asked Jul 29 at 15:48
Nate Hofmann
62
62
closed as too broad by Rui F Ribeiro, schily, slm⦠Jul 29 at 22:33
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as too broad by Rui F Ribeiro, schily, slm⦠Jul 29 at 22:33
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes