Results 1 to 2 of 2
I'm using ClearOS (a RH/Fedora-based distro). Some power issues messed up my boot loader and I had to set GRUB back up. Everything looks like it points to the right ...
- 02-06-2011 #1Just Joined!
- Join Date
- Feb 2011
- Posts
- 1
GRUB Boot Issues
I'm using ClearOS (a RH/Fedora-based distro). Some power issues messed up my boot loader and I had to set GRUB back up. Everything looks like it points to the right place but as soon as GRUB starts to load VMLINUZ, it says "ERROR 15: FILE NOT FOUND". I have 2 hard drives. /dev/sda has a single partition that I use for file storage called /shared. I do not have a separate /boot partition. All partitions except for /shared are on /dev/sdb.
My GRUB root is pointed to HD1,0 which should be correct since "/" (and by extension /boot) is /dev/sdb1. On one side note, when I use Super GRUB, it finds the installation and boots to it with no problems (though I don't have a way to check Super GRUB's settings).
I'm hoping someone has some other ideas.
Here is the info:
1. BOOT ERROR:
root hd1,0
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.6.18-194.8.1.v5 ro root=/dev/sdb1
Error 15: File not found
***NOTE: If I change my kernel root to "root=LABEL=/" I get the same error except of course for the "root=LABEL=/" part
2. DF and FDISK:
DF -
filesystem Mounted On
/dev/sdb /
FDISK -
Device Boot
/dev/sdb1 *
3. FSTAB
LABEL=/ / ext3 defaults 1 1
4. GRUB DEVICES FILE:
In my GRUB devices file, it says:
HD0 /dev/sda
HD1 /dev/sdb
5. BOOT DIRECTORY:
When I boot using the RECOVERY option and list out the /boot directory, I can see that both the VMLINUZ file and INITRD file listed in the grub.conf file are in the directory. Both have RW-R-R for permissions.
6. GRUB.CONF:
default=0
timeout=5
splashimage=(hd1,0)/boot/grub/spalsh.xpm.gz
hiddenmenu
title Linux (2.6.18.194.8.1.v5)
root (hd1,0)
kernel /boot/vmlinuz-2.6.18-194.8.1.v5 ro root=/dev/sdb1
video=vesafb vga=0x313
initrd /boot/initrd-2.6.18-194.8.1.v5.img
***NOTE: Changing the kernel root to "root=LABEL=/" makes no difference.
- 02-08-2011 #2
Try removing the /boot from the kernel and initrd lines.


Reply With Quote