The last time I signed off of Fedora 25, I opted to install updates.
Now it boots to a minimal grub menu, with no listing of kernel choices. I'm sorry to say I haven't understood grub well for about 10 years. But I looked up some guides to using the menu (without success).
If I type 'exit,' I am able to boot Windows, which is dual installed. But I guess Grub can't find a kernel to boot, and I suppose it can't find its own config?
I tried things like
boot (which said I needed to tell it a kernel to use first) linux (which I thought was a way to load a kernel, but I just get "error: command 'linux' not found") ls (which can see the partitions, but can't tell what fs they are using, for the most part).
Seems like the ls is kind of the issue--with the exception of one ext2 partition (swap I guess) and one FAT (Windows), grub can't read the filesystems on the disk, so I can't tell it what kernel to boot.
Can anyone provide any guidance?
FYI, this is an HP Envy laptop, if that helps.
Thanks, Matt
On Mon, 4 Sep 2017 13:48:00 -0400 Matt Morgan minxmertzmomo@gmail.com wrote:
The last time I signed off of Fedora 25, I opted to install updates.
I don't understand this. Updating the system requires that it be running, in order to download the packages, and install them. Is this some kind of GUI functionality? Did you power down the system during the update? Have you successfully performed an update like this before?
Now it boots to a minimal grub menu, with no listing of kernel choices. I'm sorry to say I haven't understood grub well for about 10 years. But I looked up some guides to using the menu (without success).
This sounds like the boot record for grub on the drive was damaged. Or the location it is pointing to in no longer valid.
If I type 'exit,' I am able to boot Windows, which is dual installed. But I guess Grub can't find a kernel to boot, and I suppose it can't find its own config?
I tried things like
boot (which said I needed to tell it a kernel to use first) linux (which I thought was a way to load a kernel, but I just get "error: command 'linux' not found") ls (which can see the partitions, but can't tell what fs they are using, for the most part).
Seems like the ls is kind of the issue--with the exception of one ext2 partition (swap I guess) and one FAT (Windows), grub can't read the filesystems on the disk, so I can't tell it what kernel to boot.
Something has damaged the filesystem from the sounds of it. I wonder if it is just a coincidence that this happened during an update.
Can anyone provide any guidance?
FYI, this is an HP Envy laptop, if that helps.
Is it possible the drive has gone bad?
Is there a way for you to boot a rescue CD or a live CD (or USB)? Then you could run diagnostics / investigate from a running system.
On Mon, Sep 4, 2017 at 6:00 PM, stan stanl-fedorauser@vfemail.net wrote:
On Mon, 4 Sep 2017 13:48:00 -0400 Matt Morgan minxmertzmomo@gmail.com wrote:
The last time I signed off of Fedora 25, I opted to install updates.
I don't understand this. Updating the system requires that it be running, in order to download the packages, and install them. Is this some kind of GUI functionality? Did you power down the system during the update? Have you successfully performed an update like this before?
I don't understand what it is either. I think it may have been new with F25. I don't believe I had ever used it before.
Now it boots to a minimal grub menu, with no listing of kernel choices. I'm sorry to say I haven't understood grub well for about 10 years. But I looked up some guides to using the menu (without success).
This sounds like the boot record for grub on the drive was damaged. Or the location it is pointing to in no longer valid.
If I type 'exit,' I am able to boot Windows, which is dual installed. But I guess Grub can't find a kernel to boot, and I suppose it can't find its own config?
I tried things like
boot (which said I needed to tell it a kernel to use first) linux (which I thought was a way to load a kernel, but I just get "error: command 'linux' not found") ls (which can see the partitions, but can't tell what fs they are using, for the most part).
Seems like the ls is kind of the issue--with the exception of one ext2 partition (swap I guess) and one FAT (Windows), grub can't read the filesystems on the disk, so I can't tell it what kernel to boot.
Something has damaged the filesystem from the sounds of it. I wonder if it is just a coincidence that this happened during an update.
Can anyone provide any guidance?
FYI, this is an HP Envy laptop, if that helps.
Is it possible the drive has gone bad?
Is there a way for you to boot a rescue CD or a live CD (or USB)? Then you could run diagnostics / investigate from a running system.
Yes, I set up a F26 boot usb and just installed F26 on top of the existing root. It boots now; the grub options at boot are all messed up but I can work on that.
Thanks for the good suggestions!
On Mon, 4 Sep 2017 18:35:13 -0400 Matt Morgan minxmertzmomo@gmail.com wrote:
Yes, I set up a F26 boot usb and just installed F26 on top of the existing root. It boots now; the grub options at boot are all messed up but I can work on that.
Doesn't sound like it was the drive, at least. Glad to hear you got it working, for some definition of working. Still troubling that it occurred in the first place.
If you are using grub2 (legacy boot), you could cd into the /boot/grub2 directory and run grub2-mkconfig -o grub.cfg to have grub re-scan the drives to find bootable partitions and put them into a new boot menu. I'm not sure of the comparable procedure for EFI.
Thanks for the good suggestions!
You're welcome.
On 09/04/2017 03:00 PM, stan wrote:
On Mon, 4 Sep 2017 13:48:00 -0400 Matt Morgan minxmertzmomo@gmail.com wrote:
The last time I signed off of Fedora 25, I opted to install updates.
I don't understand this. Updating the system requires that it be running, in order to download the packages, and install them. Is this some kind of GUI functionality? Did you power down the system during the update? Have you successfully performed an update like this before?
Updates, at least through Gnome Software, are now done offline. The packages are all downloaded and prepared ahead of time and then the system is rebooted into the update mode to install them.
On 09/05/2017 01:32 AM, Samuel Sieb wrote:
Updates, at least through Gnome Software, are now done offline. The packages are all downloaded and prepared ahead of time and then the system is rebooted into the update mode to install them.
For me, at least, that's another reason I'm glad I don't use Gnome. I update my system every morning while I'm making breakfast, restart any programs that have been updated and only reboot for a new kernel. I see no reason why my system shouldn't be available while I'm updating it, and one of the things I like about Linux is that it's designed to be up and running 24/7, without constant reboots. YMMV, and if you use Gnome it certainly does, but that's how I look at it.
On 09/05/2017 01:48 AM, Joe Zeff wrote:
On 09/05/2017 01:32 AM, Samuel Sieb wrote:
Updates, at least through Gnome Software, are now done offline. The packages are all downloaded and prepared ahead of time and then the system is rebooted into the update mode to install them.
For me, at least, that's another reason I'm glad I don't use Gnome. I update my system every morning while I'm making breakfast, restart any programs that have been updated and only reboot for a new kernel. I see no reason why my system shouldn't be available while I'm updating it, and one of the things I like about Linux is that it's designed to be up and running 24/7, without constant reboots. YMMV, and if you use Gnome it certainly does, but that's how I look at it.
I use Gnome and I still do my updates directly online with dnf. It's your choice how you do them.
On 09/05/2017 04:56 PM, Samuel Sieb wrote:
On 09/05/2017 01:48 AM, Joe Zeff wrote:
On 09/05/2017 01:32 AM, Samuel Sieb wrote:
Updates, at least through Gnome Software, are now done offline. The packages are all downloaded and prepared ahead of time and then the system is rebooted into the update mode to install them.
For me, at least, that's another reason I'm glad I don't use Gnome. I update my system every morning while I'm making breakfast, restart any programs that have been updated and only reboot for a new kernel. I see no reason why my system shouldn't be available while I'm updating it, and one of the things I like about Linux is that it's designed to be up and running 24/7, without constant reboots. YMMV, and if you use Gnome it certainly does, but that's how I look at it.
I use Gnome and I still do my updates directly online with dnf. It's your choice how you do them.
Allow me to add my $0.02 to this tangential discussion which offers no solution or guidance to the OP.
I don't use GNOME on a regular basis. But all of this is NBD (No Big Deal) in my opinion. The only thing Gnome is now doing is downloading updates in the background as you work. This way they will be ready to install when you decide to install them. Either by using dnf, a method I also prefer, or upon rebooting.
Some folks, like our friend Bob G, have a usage limit and may have to pay extra when data is downloaded during prime-time. So, they may not want to have the updates downloaded in the background. That isn't a problem either as it is easy to disable with
gsettings set org.gnome.software download-updates false
Certainly none of this helps Matt. But, based on what he said I don't think it would have made any difference if the update happened during a reboot (unless he or something like a power-failure interrupted it) or if done via dnf.
Sorry Matt. I really don't know what to tell you with certainty. But, I suppose I would start by telling folks exactly what you see when you type "ls". Is there a /boot directory, for example? If so, what are the contents. I've not run into any difficulties with grub. But then again, I don't do anything like dual booting to Windows, or encrypted partitions.
On Tue, 2017-09-05 at 01:48 -0700, Joe Zeff wrote:
On 09/05/2017 01:32 AM, Samuel Sieb wrote:
Updates, at least through Gnome Software, are now done offline. The packages are all downloaded and prepared ahead of time and then the system is rebooted into the update mode to install them.
For me, at least, that's another reason I'm glad I don't use Gnome. I update my system every morning while I'm making breakfast, restart any programs that have been updated and only reboot for a new kernel. I see no reason why my system shouldn't be available while I'm updating it, and one of the things I like about Linux is that it's designed to be up and running 24/7, without constant reboots. YMMV, and if you use Gnome it certainly does, but that's how I look at it.
+1 (including the part about updating while making breakfast :-)
poc