Re: Cannot Boot After Doing system-upgrade

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Saturday, October 13, 2018 5:42:15 PM EDT Chris Murphy wrote:
> On Sat, Oct 13, 2018 at 1:30 PM, Garry T. Williams
> <gtwilliams@xxxxxxxxx> wrote:
> > On Saturday, October 13, 2018 3:12:44 PM EDT Samuel Sieb wrote:
> >> On 10/13/18 10:39 AM, Garry T. Williams wrote:
> >> 
> >> > What am I doing wrong here that I cannot boot after a
> >> > system-upgrade?
> >>
> >> "Doesn't boot" is no information.  What exactly is happening?
> >
> > Sorry, the boot record is gone.
> 
> You determined this how?

The machine did not boot the Fedora OS.  Instead, it booted the OS on
/dev/sda.

Of course, I attempted to boot from the Fedora disk by using the boot
device configuration screen by hitting F12 during reboot.  This
failed.  (A photograph of the error would have been a good idea.)

I assumed that the reason was the boot record was missing.

> >I happen to have another system on
> >
> > the same machine and that system boots instead of the Fedora
> > system before my recovery actions.  When I forced a boot from
> > the fedora system using the machine's boot selection screen, it
> > fails.  (No diagnostic information in the BIOS setup screen --
> > just won't boot.  I was forced to specify the USB Live system to
> > start a recovery.)
> 
> Screen shots or cell photo of the failure might be useful because
> failure/won't boot doesn't tell us what is happening. And what is
> happening is a hint as to what the source of the problem is, how to
> prevent it, and how to fix it. But "won't boot" is not much to go
> on.

Understood.

> Is this BIOS or UEFI? From any other Linux, what do you get for
> 'parted -l u s p'  or "fdisk -l" ? And what do you get for
> 'efibootmgr -v' ?

This is useful.  I will try to document these results when I upgrade
to F30, if the same happens again.

The fdisk -l did show what I expected it to show:

Disk /dev/sda: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4B21E327-DFE8-4105-AA9B-FEFF8AE8439F

Device         Start        End   Sectors   Size Type
/dev/sda1       2048    1026047   1024000   500M EFI System
/dev/sda2    1026048    7317503   6291456     3G Microsoft basic data
/dev/sda3    7317504  933572607 926255104 441.7G Linux filesystem
/dev/sda4  933572608 1000214527  66641920  31.8G Linux swap

Disk /dev/sdb: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9114D615-2FD0-4CF1-A601-DAD4507F6254

Device       Start        End   Sectors   Size Type
/dev/sdb1     2048     411647    409600   200M EFI System
/dev/sdb2   411648    2508799   2097152     1G Linux filesystem
/dev/sdb3  2508800 1000214527 997705728 475.8G Linux LVM

Admittedly, this is output from the now-recovered system, but I can
attest that the same was displayed when the command was done using the
Ubuntu system that loaded from /dev/sda.

> > The system-upgrade somehow wiped out my boot record on /dev/sdb.
> 
> "boot record" is a BIOS term, so this could mean the code on LBA 0
> or in the MBR gap or BIOS Boot partition has been stepped on; but
> dnf system upgrade doesn't have such an ability. In fact it's a bit
> of a security and bug endurance problem that 'grub2-install' isn't
> run on BIOS upgrades. Whereas on UEFI the bootloader binaries on
> the EFI System partition are replaced during updates, so what
> you're describing might be a GRUB bug.

OK, the system was able to boot from /dev/sdb only after I reinstalled
grub2-efi and shim.

I assumed that was what restored the boot record (or whatever it's
called).

(I was able to boot normally from Fedora immediately before doing the
dnf system-upgrade.  A reinstall was not accepted by dnf, so I used
update instead.)

> But the details you're giving only lead to speculation so you need
> to provide specifics, just won't boot is identical to what happens
> to a computer without a drive at all.

Well, I will not be so fast to restore, if it occurs again (f30).

Thank you for your suggestions.  I am sorry for the assumptions I
made.

For what it's worth now:

garry@vfr$ efibootmgr -v
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0000,0003,0004,0005,0006,0007,0008,0009
Boot0000  ubuntu        HD(1,GPT,3252a9ab-23eb-4fd4-9d11-6dc13c6f50ec,
0x800,0xfa000)/File(\EFI\ubuntu\shimx64.efi)
Boot0002* Fedora        HD(1,GPT,0534ef43-afb9-409c-8dc8-a1eff1e396ef,
0x800,0x64000)/File(\EFI\fedora\shim.efi)
Boot0003* UEFI: SanDisk Extreme 0001    PciRoot(0x0)/Pci(0x14,0x0)/
USB(17,0)/HD(1,MBR,0x3cb5dbe1,0x16960,0x2990)..BO
Boot0004* Diskette Drive        BBS(Floppy,Diskette Drive,0x0)..BO
Boot0005* P0: SK hynix SC300 SATA 512GB BBS(HD,P0: SK hynix SC300 SATA 
512GB ,0x0)..BO
Boot0006* P2: INTEL SSDSC2KF512H6 SATA 5        BBS(HD,P2: INTEL 
SSDSC2KF512H6 SATA 5,0x0)..BO
Boot0007* USB Storage Device    BBS(USB,SanDisk Extreme 0001,0x0)..BO
Boot0008* CD/DVD/CD-RW Drive    BBS(CDROM,P1: PLDS DVD+/-RW DU-8A5LH    
,0x0)..BO
Boot0009  Onboard NIC   BBS(Network,IBA CL Slot 00FE v0106,0x0)..BO
Boot000B* P2: INTEL SSDSC2KF512H6 SATA 5        BBS(HD,P2: INTEL 
SSDSC2KF512H6 SATA 5,0x0)..BO
garry@vfr$ sudo parted -l u s p
[sudo] password for garry:
Model: ATA SK hynix SC300 S (scsi)
Disk /dev/sda: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system     Name                  
Flags
 1      1049kB  525MB   524MB   fat32           EFI system partition  
boot, esp
 2      525MB   3747MB  3221MB  fat32           Basic data partition  
msftdata
 3      3747MB  478GB   474GB   ext4
 4      478GB   512GB   34.1GB  linux-swap(v1)                        
swap


Model: ATA INTEL SSDSC2KF51 (scsi)
Disk /dev/sdb: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name                  
Flags
 1      1049kB  211MB   210MB   fat16        EFI System Partition  
boot, esp
 2      211MB   1285MB  1074MB  ext4
 3      1285MB  512GB   511GB                                      lvm


Warning: The driver descriptor says the physical block size is 2048 
bytes, but
Linux says it is 512 bytes.
Ignore/Cancel? i
Model: SanDisk Extreme (scsi)
Disk /dev/sdc: 251GB
Sector size (logical/physical): 2048B/512B
Partition Table: mac
Disk Flags:

Number  Start   End     Size    File system  Name   Flags
 1      2048B   10.2kB  8192B                Apple
 2      47.4MB  52.8MB  5448kB               EFI
 3      52.8MB  64.8MB  12.0MB               EFI


garry@vfr$

-- 
Garry T. Williams


_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux