Results 1 to 9 of 9
loaded a third harddrive with bsd from cd with mbr but no loader...went in linux to /boot/grub/ and edited in
title freebsd
root (hde,0)
table=/dev/hde
label=freebsd
i'm lost... got the ...
- 06-12-2005 #1Just Joined!
- Join Date
- Jun 2005
- Location
- iowa
- Posts
- 64
grub & freebsd booting problem
loaded a third harddrive with bsd from cd with mbr but no loader...went in linux to /boot/grub/ and edited in
title freebsd
root (hde,0)
table=/dev/hde
label=freebsd
i'm lost... got the bsd book and looked at man on line, both talk about lilo ... forum notes say grub'l work fine... i'm lost
- 06-12-2005 #2Linux Engineer
- Join Date
- Apr 2005
- Location
- Buenos Aires, Argentina
- Posts
- 908
I think you forgot the "kernel /boot/loader" line.
http://www.daemonnews.org/200102/grub.htmlserzsite.com.ar
"All the drugs in this world won\'t save you from yourself"
- 06-12-2005 #3
A standard grub entry for FreeBSD (4.11 anyway) looks something like this:
First hard drive (hd0), first slice (0) in my case. I am not sure if/how this has changed in 5.x.Code:title FreeBSD root (hd0,0,a) kernel /boot/loader
- 06-12-2005 #4Linux Engineer
- Join Date
- Mar 2005
- Posts
- 1,431
I think that's pretty much like 5.x, here's mine for freebsd 5.4:
Code:title FreeBSD 5.4 root (hd0,1,a) kernel /boot/loader boot
- 06-13-2005 #5Just Joined!
- Join Date
- Jun 2005
- Location
- iowa
- Posts
- 64
still no luck
found all this on grub site:
GRUB identifies hard disks by "hd" and floppy disks as "fd" followed by a number starting from 0. In commands, the disk references are always enclosed in parentheses, thus the first hard disk would be referenced as (hd0). Disk partitions are separated from the hard disk by a comma and identified as 0 - 3 for the primary partitions and 4 and up for partitions inside an extended partition. FreeBSD numbers its slices from 1 to 4, and Linux its partitions from 1 to 16, rather than starting at 0, so you'll need to reduce a FreeBSD slice or Linux partition number by one to get the right disk partition number. If the partition is a BSD disklabel "subpartition" in GRUBs terminology, these are separated by a comma and start from 'a'. Thus (hd0,2,a) would point to FreeBSD's /dev/ad0s3a or the 'a' partition of the third slice on the first hard disk.
http://geodsoft.com/howto/dualboot/grub.htm
but still no boot... third drive is on a ultra66 controler card grub error says
error parsing number????
pulled the other two drive out loaded bsd on prim master channel it comes up!!! put the other two back in parsing error
my code:
title freebsd-5.0
root (hde,0,a)
kernel /boot/loader/
still lost!!!!!!!!!!!!!!
- 06-13-2005 #6
For this line
Why hde? If it is third physical drive, shouldn't it be hd2? Maybe that is why it is throwing a number parsing error; e is not a number.Code:root (hde,0,a)
- 06-13-2005 #7Linux Engineer
- Join Date
- Sep 2003
- Location
- Knoxhell, TN
- Posts
- 1,078
unless they've fixed grub, you need to chainload fbsd if you're using UFS2 as your filesystem...
Code:rootnoverify (hd0,0,a) chainloader +1
Their code will be beautiful, even if their desks are buried in 3 feet of crap. - esr
- 06-13-2005 #8Just Joined!
- Join Date
- Jun 2005
- Location
- iowa
- Posts
- 64
oh oh oh!!! fixed now
grub found boot for bsd
was using e as that is what linux's fdisk called it hdeCode:title freebsd-5.0 root (hd2,0,a) kernel /boot/loader
- 06-13-2005 #9Linux Engineer
- Join Date
- Mar 2005
- Posts
- 1,431
Re: oh oh oh!!! fixed now
But linux and grub have different partition "names"... what's in linux called "hda" is under grub called (hd0) and "hdb" is (hd1) and so forth...
Originally Posted by l8forwork


Reply With Quote
