Re: Grub2 install with / on lvm

[Andrei Borzenkov]

В Mon, 9 Feb 2015 12:09:39 -0800 (PST)
address@hidden пишет:

> 
> 1.  /boot/efi/EFI/ubuntu/grub.cfg  contains the following:
> search.fs_uuid 27ae300a-06fd-44f6-bf66-97c42e1c2052 root 
> lvmid/030tOx-2dEO-kglk-6Wbk-c553-ica7-DZhMdW/Sk4ZIt-sHBd-n1DK-DgRK-7MWH-FYAv-NLwmA7
>  
> set prefix=($root)'/boot/grub'
> configfile $prefix/grub.cfg
> 
> 
> > Well, it still defaults to using shim for secure boot. This hints that
> > grubx64.efi is not dynamically created at run time. When you run
> > whatever program your distro use to update bootloader - is time stamp
> > of grubx64.efi updated? Does it itself change?
> 
> 2.  The time stamp on grubx64.efi is Feb. 4th, which I trace back to when I 
> manually ran grub-install after my initial installation.  The initial 
> installation occurred on Feb. 2nd, and that is what my /boot/efi and 
> /boot/grub directories are time stamped.  I rebooted the box this morning 
> after being off all weekend.  I hope that answers your question, if not I am 
> not sure of the question.

Now I'm a bit confused. Your configuration looks OK. Do you have any
issues booting right now?

> 
> Jeff
> 
> 
> 
> -----Original Message-----
> From: "Andrei Borzenkov" <address@hidden>
> Sent: Monday, February 9, 2015 11:54am
> To: address@hidden
> Cc: address@hidden
> Subject: Re: Grub2 install with / on lvm
> 
> В Mon, 9 Feb 2015 11:09:14 -0800 (PST)
> address@hidden пишет:
> 
> > Sorry for the top posting.
> > 
> > 1.  Secure boot is NOT enabled.
> > 
> > 2.  I have the following directory structure and files under boot
> > /boot/efi/EFI/ubuntu
> > grub.cfg
> 
> What is in this grub.cfg?
> 
> > grubx64.efi
> > MokManager.efi
> > shimx64.efi
> > 
> > 3.  Output of efibootmgr -v
> > 
> > BootCurrent: 0008
> > Timeout: 2 seconds
> > BootOrder: 0000,0008,0001,0002,0003,0004,0007
> > Boot0000* ubuntu    
> > HD(1,800,fa000,efdf8fb6-08fd-45bc-b62c-ab9bc39721ee)File(\EFI\ubuntu\shimx64.efi)
> 
> Well, it still defaults to using shim for secure boot. This hints that
> grubx64.efi is not dynamically created at run time. When you run
> whatever program your distro use to update bootloader - is time stamp
> of grubx64.efi updated? Does it itself change?
> 
> > Boot0001* Diskette Drive    BIOS(1,0,4469736b6574746520447269766500)AMBO
> > Boot0002* Internal HDD      BIOS(2,0,496e7465726e616c2048444400)AMBO
> > Boot0003* USB Storage Device        
> > BIOS(5,0,5553422053746f726167652044657669636500)AMBO
> > Boot0004* CD/DVD/CD-RW Drive        
> > BIOS(3,0,50343a20484c2d44542d5354204456442b2f2d525720474842304e20202000)AMBO
> > Boot0005  Onboard NIC       BIOS(6,0,4f6e626f617264204e494300)AMBO
> > Boot0007* Onboard NIC       BIOS(6,0,4f6e626f617264204e494300)AMBO
> > Boot0008* UEFI: HL-DT-ST DVD+/-RW GHB0N     
> > ACPI(a0341d0,0)PCI(1f,2)03120a000400ffff0000CD-ROM(1,11a6,1680)AMBO
> > BootFFFA* Internal Shell            
> > Vendor(5990c250-676b-4ff7-8a0d-529319d0b254,)
> > BootFFFB* Diagnostic Boot           
> > Vendor(5990c250-676b-4ff7-8a0d-529319d0b254,)
> > BootFFFC* Temporary Boot Menu       
> > Vendor(5990c250-676b-4ff7-8a0d-529319d0b254,)
> > BootFFFD* Graphic Setup             
> > Vendor(5990c250-676b-4ff7-8a0d-529319d0b254,)
> > BootFFFE* Text Setup                
> > Vendor(5990c250-676b-4ff7-8a0d-529319d0b254,)
> > 
> > 
> > Jeff
> > 
> > 
> > -----Original Message-----
> > From: "Andrei Borzenkov" <address@hidden>
> > Sent: Monday, February 9, 2015 10:51am
> > To: address@hidden
> > Cc: address@hidden
> > Subject: Re: Grub2 install with / on lvm
> > 
> > В Mon, 9 Feb 2015 08:51:37 -0800 (PST)
> > address@hidden пишет:
> > 
> > > The results of the bootinfoscript output is located here.
> > > 
> > > http://pastebin.com/EUyueeG1
> > > 
> > 
> > From grub point of view it looks just fine - it detects XFS and LVM and
> > creates correct boot.cfg. is secure boot enabled on your system? What
> > is content of /boot/efi/ubuntu? Could you show "efibootmgr -v" output
> > (I probably should add it to bootinfoscript ...)?
> > 
> > > Jeff
> > > 
> > > 
> > > -----Original Message-----
> > > From: "Andrei Borzenkov" <address@hidden>
> > > Sent: Saturday, February 7, 2015 9:15am
> > > To: address@hidden
> > > Cc: address@hidden
> > > Subject: Re: Grub2 install with / on lvm
> > > 
> > > В Sat, 7 Feb 2015 09:03:38 -0800 (PST)
> > > address@hidden пишет:
> > > 
> > > > Ok, I learned something new here.  What would be a better choice for 
> > > > the filesystem for /boot.  I am using xfs for everything else.
> > > 
> > > I usually use ext2 if it is separate partition. Otherwise xfs should
> > > work if /boot is not separate filesystem and is on root.
> > > 
> > > > 
> > > > Grub was installed using the standard OS installation in Linux Mint 17. 
> > > >  I haven't had much luck getting good knowledgable detailed answers 
> > > > there; more speculation and hypotheses.  It is good to know that grub 
> > > > install would normally include the LVM driver, so it is possible that 
> > > > Mint installation is not recognizing that I am using LVM.  Is there a 
> > > > grub config file that would identify the drivers that are pulled in, 
> > > > and I would be able to see if the driver for LVM is included.  I don't 
> > > > want to get into hand editing grub configuration files to get my system 
> > > > running.  I would prefer to have it automatically the right way, I just 
> > > > want to understand what it did in case it helps find or fix a bug in 
> > > > the Mint installation.
> > > 
> > > There are two pieces here. One is core.img that is loaded initially. It
> > > includes grub modules (drivers) needed to access /boot/grub.
> > > Unfortunately there is no easy way to see them. Another step is loading
> > > operating system files. It is in /boot/grub/grub.cfg and you should
> > > actually see "insmod lvm" there.
> > > 
> > > > 
> > > > After I booted the system from the SuperGrub2 disk, I did run 
> > > > grub-install /dev/sda just to see what would happen (since I was 
> > > > considering re-installing anyway).  If I recall it ran without error, 
> > > > but still wouldn't boot and had the same reference to hd1.
> > > 
> > > it may happen if you have incorrect /boot/grub/device.map. If you have
> > > it, remove it. It is not needed by grub unless you have very unusual
> > > configuration and have to work around some problem.
> > > 
> > > It may be useful to provide output of running
> > > https://github.com/arvidjaar/bootinfoscript/raw/master/bootinfoscript
> > > Upload it to pastebin or like.
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Help-grub mailing list
> > > address@hidden
> > > https://lists.gnu.org/mailman/listinfo/help-grub
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Help-grub mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/help-grub
> 
> 
> 
> 
> _______________________________________________
> Help-grub mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/help-grub