grub doesn't know ufs filesystem

Micah micahjon at ywave.com
Thu Dec 15 07:17:50 PST 2005


Roberto Nunnari wrote:
> One more note.. let's call 'bad' the pc that grub doesn't
> like and ok the others.. and note that the two pc have
> identical disk drives.. so..
> 
> bad# fdisk
> ******* Working on device /dev/ad0 *******
> parameters extracted from in-core disklabel are:
> cylinders=29777 heads=16 sectors/track=63 (1008 blks/cyl)
> 
> Figures below won't work with BIOS for partitions not in cyl 1
> parameters to be used for BIOS calculations are:
> cylinders=29777 heads=16 sectors/track=63 (1008 blks/cyl)
> 
> Media sector size is 512
> Warning: BIOS sector numbering starts with sector 1
> Information from DOS bootblock is:
> The data for partition 1 is:
> sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
>     start 63, size 30009357 (14653 Meg), flag 80 (active)
>         beg: cyl 0/ head 1/ sector 1;
>         end: cyl 1023/ head 254/ sector 63
> The data for partition 2 is:
> <UNUSED>
> The data for partition 3 is:
> <UNUSED>
> The data for partition 4 is:
> <UNUSED>
> 
> 
> ok# fdisk
> ******* Working on device /dev/ad0 *******
> parameters extracted from in-core disklabel are:
> cylinders=29777 heads=16 sectors/track=63 (1008 blks/cyl)
> 
> Figures below won't work with BIOS for partitions not in cyl 1
> parameters to be used for BIOS calculations are:
> cylinders=29777 heads=16 sectors/track=63 (1008 blks/cyl)
> 
> Media sector size is 512
> Warning: BIOS sector numbering starts with sector 1
> Information from DOS bootblock is:
> The data for partition 1 is:
> sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
>     start 63, size 30009357 (14653 Meg), flag 80 (active)
>         beg: cyl 0/ head 1/ sector 1;
>         end: cyl 1023/ head 3/ sector 63
> The data for partition 2 is:
> <UNUSED>
> The data for partition 3 is:
> <UNUSED>
> The data for partition 4 is:
> <UNUSED>
> 
> 
> as you can see, there's a difference in the end head..
> bad says end head is 254, while ok says end head is 3
> Could that be a source of trouble?
> 
> 
> bad# disklabel ad0s1
> # /dev/ad0s1:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>   a:   524288        0    4.2BSD     2048 16384 32776
>   b:  1048576   524288      swap
>   c: 30009357        0    unused        0     0         # "raw" part, 
> don't edit
>   d:   524288  1572864    4.2BSD     2048 16384 32776
>   e:   524288  2097152    4.2BSD     2048 16384 32776
>   f: 27387917  2621440    4.2BSD     2048 16384 28552
> 
> 
> ok# disklabel ad0s1
> # /dev/ad0s1:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>   a:   524288        0    4.2BSD     2048 16384 32776
>   b:   996992   524288      swap
>   c: 30009357        0    unused        0     0         # "raw" part, 
> don't edit
>   d:   524288  1521280    4.2BSD     2048 16384 32776
>   e:   524288  2045568    4.2BSD     2048 16384 32776
>   f: 27387917  2569856    4.2BSD     2048 16384 28552
> 
> 
> the disklabel is essentialy the same.. apart from the
> size of the swap and consequently the offset of the
> rest of the internal partitions..
> 
> Again.. any ideas?
> -- 
> Robi
> 
> Harley D. Eades III wrote:
> 
>> On Wed, 2005-12-14 at 08:36 -0800, Micah wrote:
>>
>>> Roberto Nunnari wrote:
>>>
>>>> Hello list.
>>>>
>>>> Please also reply to my mailbox, as I'm not on the list.
>>>> Thank you.
>>>>
>>>> I have a old grub floppy that I use time to time to
>>>> boot/recover pc with different OS.. Today I wanted to
>>>> boot a freebsd 5.3-RELEASE-p23 box, but to my surprise
>>>> grub reported:
>>>>
>>>> Filesystem type unknown, partition type 0xa5
>>>>
>>>> and thus cannot mount /boot/loader
>>>>
>>>> So I thought I'd make a grub floppy with a recent version,
>>>> but even with version 0.97 things won't change..
>>>>
>>>> # cd /usr/ports/sysutils/grub
>>>> # make install
>>>> # grub
>>>> [ Minimal BASH-like line editing is supported.  For the first word, TAB
>>>>   lists possible command completions.  Anywhere else TAB lists the 
>>>> possible
>>>>   completions of a device/filename. ]
>>>>
>>>> grub> root (hd0,0,a)
>>>> Filesystem type unknown, partition type 0xa5
>>>>
>>>> grub> kernel /boot/loader
>>>>
>>>> Error 17: Cannot mount selected partition
>>>>
>>>> grub> root (hd0, <TAB>
>>>> Possible partitions are:
>>>>   Partition num: 0, [BSD sub-partitions immediately follow]
>>>>     BSD Partition num: 'a',  Filesystem type unknown, partition type 
>>>> 0xa5
>>>>     BSD Partition num: 'b',  Filesystem type unknown, partition type 
>>>> 0xa5
>>>>     BSD Partition num: 'd',  Filesystem type unknown, partition type 
>>>> 0xa5
>>>>     BSD Partition num: 'e',  Filesystem type unknown, partition type 
>>>> 0xa5
>>>>     BSD Partition num: 'f',  Filesystem type unknown, partition type 
>>>> 0xa5
>>>>
>>>> grub> quit
>>>>
>>>> # mount
>>>> /dev/ad0s1a on / (ufs, local, soft-updates)
>>>> devfs on /dev (devfs, local)
>>>> /dev/ad0s1e on /tmp (ufs, local, soft-updates)
>>>> /dev/ad0s1f on /usr (ufs, local, soft-updates)
>>>> /dev/ad0s1d on /var (ufs, local, soft-updates)
>>>> linprocfs on /usr/compat/linux/proc (linprocfs, local)
>>>> devfs on /var/named/dev (devfs, local)
>>>>
>>>> Any hint/thought/advice?
>>>>
>>>> Best regards.
>>>
>>>
>>> I just installed grub from ports and duplicated your test and it 
>>> works fine.  I'd start by checking your installation and making sure 
>>> you don't have any other grubs in your path.  Some of the grubs that 
>>> ship with Linux distros do not support ufs.  Do a find/locate on grub 
>>> to see what turns up.  Do a which grub, you should get 
>>> /usr/local/sbin/grub.  If not, issue /usr/local/sbin/grub from a 
>>> command prompt and duplicate your test.  If that's broken, make sure 
>>> your ports tree is up to date, make sure /usr/ports/devel/autoconf259 
>>> /usr/ports/devel/automake19 /usr/ports/devel/gmake are up to date 
>>> (grub's build dependancies) then
>>> deinstall, clean, and reintsall the grub port.
>>>
>>>
>>> HTH,
>>> Micah
>>> _______________________________________________
>>> freebsd-questions at freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>> To unsubscribe, send any mail to 
>>> "freebsd-questions-unsubscribe at freebsd.org"
>>
>>
>>
>> I can second this, I use grub all the time, as well as test grub2 on
>> FreeBSD and both work great for me.
>>
>> --Harley -----BEGIN GEEK CODE BLOCK-----
>> G: GCS-- d- a? C++++ B- E+++ W+++ N++ w--- X+++ b++ G e* r x+ z+++++
>> ------END GEEK CODE BLOCK------
> 
> 

I don't think that the end head of 254 is a problem, since mine shows 
that too.  Have you tried running fsck on the bad computers?  I wonder 
if it's a disk controller issue?  Maybe the BIOS settings are wrong?  Is 
your BIOS up to date?  If you have any unused space on the bad 
computers, try making a new test partition and see if grub recognizes 
that.  Not sure what else to try after that.

HTH,
Micah


More information about the freebsd-questions mailing list