Greetings -
 
I am continuing testing my new Linux Mint installation that only boots to a 
grub prompt.  After some assistance here a few weeks ago I decided to do a 
fresh installation, which appears to have resolved a few of my issues but not 
all of them.  My system specs are:
 
Dell Precision 3610
LSI MegaRAID SAS 9271-8i raid controller
Two 3TB drives configured in RAID 1
Single drive recognized by BIOS and Mint Installer as /dev/sda
 
Before doing the fresh installation, I used SystemRescueCD to wipe the drives 
of previous installation using the following commands
root#  dd if=/dev/zero of=/dev/sda bs=512 count=1
root#  shred -vfz -n 3 /dev/sda
 
 
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
 
 
Upon first boot the system went immediately to a grub prompt screen.  Using 
SuperGrub2 disk the linux mint kernel appears in the menu and selecting it 
results in the system fully booting.  I have not made any changes to the system 
and have just tried to view and probe for diagnostic information at this point. 
 I have included links to my diagnostic information below.  Most everything 
looks fine from my untrained eye, except the reference to hd1 on the grub 
settings screen shot.  Since the BIOS and the installer only recognized 
/dev/sda as present, I don't know what is providing the reference to hd1 on the 
grub screen, especially since I wiped the drive before beginning the 
installation.  Could this possibly be due to the 100MB of unallocated space I 
left at the end of my raid disk?  The bootinfoscript output shows reference to 
/dev/sdb but that is the USB stick that was plugged in to the system to run the 
script.  I can keep doing different installations to try different things, but 
I don't want to just try random things without some direction in testing 
something specific.  I have not tried a manual grub-install yet as I didn't 
want to mess with anything that might identify the original problem.
 
If someone can give me pointers as to what to look for, or to try next I would 
appreciate it.  You may cc me directly as I am only subscribed to the daily 
digest.  Thanks.
 
Jeff
 
bootinfoscript output
[ http://pastebin.com/nrxXgfcE ]( http://pastebin.com/nrxXgfcE )
 
efibootmgr -v output
[ http://pastebin.com/aBQyjVZt ]( http://pastebin.com/aBQyjVZt )
 
ScreenShots
grub settings
[ http://ibin.co/1sgmwx6hwi6M ]( http://ibin.co/1sgmwx6hwi6M )
 
EFI/ubuntu directory
[ http://ibin.co/1sgnKzdVDaNF ]( http://ibin.co/1sgnKzdVDaNF )
 
boot/grub directory
[ http://ibin.co/1sgnef9yG2FH ]( http://ibin.co/1sgnef9yG2FH )
 
boot directory
[ http://ibin.co/1sgnw9BHBQXS ]( http://ibin.co/1sgnw9BHBQXS )
_______________________________________________
Help-grub mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-grub

Reply via email to