Re: Boots to grub and references non-existent hd1

[jeff]

 

-----Original Message-----
From: "Andrei Borzenkov" <address@hidden>
Sent: Tuesday, February 24, 2015 7:25pm
To: address@hidden
Cc: address@hidden
Subject: Re: Boots to grub and references non-existent hd1

В Tue, 24 Feb 2015 13:39:46 -0800 (PST)
address@hidden пишет:

>
> @Andrei -
> I apologize if I shouldn't have started a new thread, but I felt I had hit a dead-end with the previous installation and suspected I could move forward with a complete new install with some different parameters. Since it was a new install that was showing slightly different symptoms, I felt it was best to make a break from the old problem and provide a clear description of the current conditions. A summary of the things I changed for this install are listed below.
>
> 1. Increased space allocated to /boot/efi and /boot from 500MB to 550MB each. Why? Just going off of anecdotal information found through Google research. Had no idea if it would help, but had the space available and was doing a re-install anyway so I figured it couldn't hurt to try.
>
> 2. Changed the file system for /boot from fat32 to XFS. Based on your previous recommendation that fat32 was not appropriate.
>
> 3. Had identified where the previous installation did not have a mount point set for /boot that I believe was my error during the install. That was corrected with the new installation.
>
> The are two positive results from making these changes on the new install. I still go directly to a grub prompt, but using SuperGrub2 CD I see the following two changes.
>
> 1. It appears that the LVM module is now being loaded automatically. Previously I had to specifically enable loading the LVM module in order to get the linux kernel to appear in the SuperGrub2 menu list.
>
> 2. The linux kernel is listed in the SuperGrub2 menu list, and when selecting it the system will boot. It was previously not listed until enabling LVM.
>
> I provided the output of ls at the grub prompt because I mistakenly thought that is what you were looking for, since I get a grub error returning when giving it the ls -l command.
>
> grub> ls -l
> error: file '-l' not found.
>

OK, so - can you do

ls (lvm/vg_jab-lv_mintroot)/

Does it work? Can you drill down, e.g. "ls
(lvm/vg_jab-lv_mintroot)/boot?"

I'm using names from your last screenshot/you are listed below; adjust
accordingly.

 

- - - - - - - -

Ok, here is what I get for those queries.

grub> ls (lvm/vg_jab-lv_mintroot)/

error: unknown filesystem.

 

grub> ls (lvm/vg_jab-lv_mintroot)/boot

error: unknown filesystem.

 

Trying a few other options...

grub> ls (hd0, gpt1)

(hd0,gpt1): Filesystem is fat.

 

grub> ls (hd0, gpt2)

(hd0,gpt2): Filesystem is unknown.

 

grub> ls (hd0, gpt3)

(hd0,gpt3): Filesystem is unknown.

 

I am guessing the unknowns are a problem, but I don't know why they are unknown, nor what to do about them.

 

> >
> > Created partitions and lvm logical volumes in GParted and command line from SystemRescueCD prior to install
> >
> > /dev/sda1 550MB /boot/efi fat32 set boot and esp flags
> >
> > /dev/sda2 550MB /boot XFS
> >
> > /dev/sda3 2.73TB LVM PV
> > left 100MB unallocated at the end of the LVM partition
> >
> > volume group vg_jab
> >
> > lv_mintroot 8GB / XFS
> >
> > lv_mintvar 4GB /var XFS
> >
> > lv_mintswap 2GB [swap]
> >
> > lv_minthome 80GB /home XFS
> >
> > lv_mintgis 1000GB /gis XFS
> >
> >