|
From: | jeff |
Subject: | Re: Boots to grub and references non-existent hd1 |
Date: | Tue, 24 Feb 2015 13:39:46 -0800 (PST) |
@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" <address@hidden>
Sent: Monday, February 23, 2015 7:39pm
To: address@hidden
Cc: address@hidden
Subject: Re: Boots to grub and references non-existent hd1
[Prev in Thread] | Current Thread | [Next in Thread] |