Stuck on "GRUB_" Screen - Will boot from Live CD "Boot from first hard disk" option
I know that there have been many other people that have been having this problem, as I have spent the past few days browsing through forums and google searches trying to figure this out. I am new to Linux, and am working with a Ubuntu 8.10 distro on this particular system, a Toshiba M30-YSJ (Linked to show specs, if it really matters). The only changes to this system is adding in another 512 MB stick of RAM.
So here is my problem, or as much of it as I can figure out. I've gone through and set up grub to install on the MBR of the HD, as I only want this system to boot to Ubuntu. While re-installing the OS, hoping that an option in the loader might fix this issue, I noticed that the hard drive was being identified as a SCSI drive. (This seems weird to me, but I think it's shown itself as part of the problem) As in the title, the system will boot fine if I boot off of the ubuntu disk, then select "Boot from first hard disk" option. I boot into the harddrive and can make changes.
What I can see from looking at some of the files in the system... (I'm typing this out by hand on a different system, so please ignore any typos, and omitted the UUID's to save my sanity)
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
UUID=~~~~~~~~~ / ext3 relatime,errors=remount-ro 0 1
UUID=~~~~~~~~~ none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
So what I see here, by the /dev/sda1, and from what I read, is that the HD is regarded as a SCSI drive, right?
Now, when I load into grub in the terminal, any attempt to set the grub root to (sd0,0) or (sd0,1)... results in an Error 23: Error while parsing number.
However, when I enter in root (hd0,0), no error is generated, and a 'setup (hd0)' command returns:
Checking if "boot/grub/stage1" exists... yes
Checking if "boot/grub/stage2" exists... yes
Checking if "boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
Running "install /boot/grub/stage1 (hd0) (hd0)1_16 p (hd0,0) /boot/grub/stage2 /boot/grub/menu.lst"... succeeded
Upon rebooting, my system seems to remain at the same place, stuck on the GRUB_ screen, with booting from the CD option "Boot from first hard disk" working fine,and showing the GRUB prompts as it boots.
So if anyone out there can lend assistance, it would be greatly appreciated. In looking at this, might the problem be with my /dev/sda1 drive not being the mounting point for /root? Or has my investigation into this matter taken me on a whole different route?
*Edit - I also saw some comments on a GRUB page that suggested updating the BIOS for the system. It is at the most current one availiable on Toshiba's website, 1.5*
Ubuntu Intrepid actually lists all HDDs as /dev/sd* whether they are IDE, SATA, USB, etc, so it's OK that your HDD is listed as sda. About Grub, Grub is the opposite because it lists all HDDs as (hdX,Y) whether the drive is IDE, SATA, USB, etc; so there is no (sdX,Y) in Grub's Convoluted World. Have you tried reinstalling Grub to the MBR (Master Boot Record) of your HDD using the Super Grub Disk? I've found that sometimes using just a slightly different version of Grub can make a difference in situations like yours where Grub boots only under certain restrictive circumstances, so I would first give Super Grub a try. If that doesn't change anything, how about downloading the Boot Info Script to your Ubuntu desktop, open a terminal (Applications > Accessories > Terminal) and do:
And lastly, what are your HDD-related settings in BIOS? If you can go into your BIOS, try looking for settings like "auto-detect", LBA, CHS, RAID, AHCI/HCI/EHCI vs. IDE, IDE-emulation, ACPI, DMA, etc for your HDD, and please let me know what your current settings are. We can work from there if you want.
Thanks for giving me a hand with this. It's greatly appreciated! So, I downloaded and burned the Super Grub Disk, and ran it on that system. The option that I selected was "GRUB => MBR & !Linux! (1) Auto ;-))) off of the Super Grub Disk options.
This is what it generated:
I went back into SGD into the following menu system:
Choose Language and Help
Fix Boot of GNU/Linux (GRUB)
which then loads the following screen:
After rebooting the system, the problem still remains, so I went ahead and downloaded the Boot Info Script. The results are as follows:
According to all the information from the Boot Info Script, Grub is installed correctly to your sda drive as we would expect. Is there any way you could get a BIOS upgrade for that computer, or is that out of the question? If you can't get a BIOS upgrade, you might have to live with just booting from a CD, but for convenience you could make a dedicated Grub CD that would boot your HDD automatically. That way to boot into Ubuntu, you could just pop your dedicated Grub CD in and away you go. Or another option that might work is if your BIOS supports USB booting, you could install Grub to a USB stick and boot with that. That's about all I can suggest, because without having any HDD BIOS parameters to tweak, it's usually really difficult trying to circumvent strange Grub behavior like you are experiencing (at least in my experience). In case you want to make a dedicated Grub boot CD or USB stick, let me know, and I can give you specific directions.
I hade a simaler prob with a distro detecting my IDE drives as scsi and grub not liking sda on the boot line LOL
I finaley got it to boot by editing /boot/grub/menu.lst to read as folows.
quote from your output
/dev/sda1 * 63 150,255,944 150,255,882 83 Linux
title Ubuntu 8.10, kernel 2.6.27-7-generic
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=b0f2a9a6-528d-47ad-9799-bd7362270628 ro quiet splash
sda1 is the / partition and contains /boot as a sub-folder
quote from your output also shows this
NOTICE the 6.7 changing to 6.8?
me thinks you have a borked partition table.
there could be a number or reasons for this
if you love ubuntu do a clean re-install not a rescue.
a rescue may have stuffed things up...and I see others have suggested a number of things and grub is supposed to be easy to fix...if its a grub issue...but grub can not self solve a borked partition table.
If you agree to take my advice...boot a live cd and do this
open a terminal
create PRIMARY partitions only....I hate ubuntu for deciding to make your extended when you only needed 2 partitions
then boot up your ubuntu.....or get it over and done with and come to sidux heh heh
I just want to say thank you to everyone for all the help!
I was messing around with everything last night, and it does seem to have been an issue with the partions/partition table of the drive. I tried everything down the list till I got to aus9's post, when I went and did a full wipe of the drive, re-did the partition table, and re-installed Ubuntu. After this, the system seems to be booting just fine!
Thanks again for the help! It's been great to see such helpful people on these forums!
sorry for misleading the OP, and glad his issue is resolved.
I did qualify myself by saying ...me thinks.
Now that matter is resolved could you explain....what pratical benefit that info is to any normal user?
So does that measure from the start of the entire drive?
so if /boot partition was 20G in....would you expect to see eg menu at 20/21G
OR does it measure from start of each partition in which case if there was a separate /boot partition the number would be close to 0G?
Thankyou for any help.
Hi Aus9, the script gives the physical location of the boot files from the beginning of the drive, not from the beginning of the partition where they are in. That is intentional, because that info is for troubleshooting when you get a Grub error 18:
I think this (the whole script) is a "good thing" - the more info we have when trying to diagnose, the better.
|All times are GMT -5. The time now is 11:45 PM.|