Hi Jeff,
I had RAID settings in no less than three places in my BIOS. The one that
did the trick was under the disk itself. It said something like "IDE
emulation" and I selected Native. Now, in your case, you have an LSI card
and would like to keep using the RAID feature. I did not care about that,
so I'm afraid I'm out of my area of expertise. I do agree with needing to
reinstall once you change the disk drive type. It did not matter for me
because I was doing a bare-bones Debian install while I was trying to debug
the problems.
I'm glad you are having good luck with SuperGrub2. I'm not sure if GnuGrub
is going to know about the LSI card. The fact you made it to
grub>
is very encouraging, however.
-Chris
Quoting [email protected]:
@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.
I am not sure why it doesn't work on my system, if it should. The top
of my grub screen says GNU GRUB version 2.02~beta2-9ubuntu1. Is there
some other way for me to provide the information you are looking for?
Doing an ls at grub now does not show reference to hd1, so I am
wondering if I possibly had a USB stick plugged in when I ran it
previously. Although I was more detailed in my notes this time and
there is no indication that I would have plugged in a USB stick to do
anything yet immediately after the first boot.
@Chris -
When I rebooted I looked at my BIOS settings and under the category
SATA Operations there are four options (disabled, ATA, AHCI, and RAID
On). My system currently has the RAID On option selected. Looking at
my product manual it states that AHCI would have been the factory
default. I don't see in my notes that I changed it, but I could have
and didn't get it into my notes. I had tried some previous
installations using the Intel motherboard firmware RAID before getting
the LSI hardware RAID card I have installed now, so I could have changed
that setting then. Looking up information about those settings it
appears that AHCI would be the setting I want, but am not sure it would
make a difference now that my drives are connected to the LSI card. Any
idea if it matters. Also I saw references that I would need to do an OS
re-install after changing that setting, although I think most of those
discussions were about Windows systems and not Linux.
Jeff
-----Original Message-----
From: "Andrei Borzenkov" <[email protected]>
Sent: Monday, February 23, 2015 7:39pm
To: [email protected]
Cc: [email protected]
Subject: Re: Boots to grub and references non-existent hd1
You just asked exactly the same question couple of weeks ago. Did
anything change since then? Why did you need to create new thread for
this?
I reviewed information you provided earlier, in particular strange
$prefix value, and I believe this can happen when grub cannot find its
root device. As it sees LVM devices it means XFS driver is probably
missing from grub image. I asked you to show output of "ls -l" that
would confirm it and you show just output of plain "ls" which does not
show this information.
В Mon, 23 Feb 2015 15:04:31 -0800 (PST)
[email protected] пишет:
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.
_______________________________________________
Help-grub mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-grub
