> 
> Ok, quick comparison to my results...
> 
> grub> root (hd0,0)
>  Filesystem type is ext2fs, partition type 0x83
> 
> grub> setup (hd0)
>  Checking if "/boot/grub/stage1" exists... no
>  Checking if "/grub/stage1" exists... yes
>  Checking if "/grub/stage2" exists... yes
>  Checking if "/grub/e2fs_stage1_5" exists... yes
>  Running "embed /grub/e2fs_stage1_5 (hd0)"...  16
> sectors are embedded.
> succeeded
>  Running "install /grub/stage1 (hd0) (hd0)1+16 p
> (hd0,0)/grub/stage2
> /grub/menu.lst"... succeeded
> Done.
> 
> 
> Hmm, this is weird.  My e2fs_stage1_5 takes 16
> sectors, but yours takes
> 22....that doesn't seem right.  I could understand a
> 1 or 2 sector
> difference if we are using different versions of
> grub.
> 
> Let's compare grub versions and stage files:
> 
> carcharias rjf # qpkg -I -v grub
> sys-boot/grub-0.96-r1 *
> 
> carcharias rjf # ls -l /boot/grub/stage1
> /boot/grub/e2fs_stage1_5
> /boot/grub/stage2
> -rw-r--r--  1 root root   8052 Apr 22 02:07
> /boot/grub/e2fs_stage1_5
> -rw-r--r--  1 root root    512 Apr 22 02:07
> /boot/grub/stage1
> -rw-r--r--  1 root root 105576 Apr 22 02:07
> /boot/grub/stage2
> 
> carcharias rjf # md5sum /boot/grub/stage1
> /boot/grub/e2fs_stage1_5
> /boot/grub/stage2
> fec478948a06cc1fb7339a2cd3e26663  /boot/grub/stage1
> 96451f2a81e2cbf4d1c41cf4b61787e0 
> /boot/grub/e2fs_stage1_5
> d69594a75e5b72df86f03df6d5d7fbd3  /boot/grub/stage2
> 
> Also, how did you format /boot?  Could you post the
> output of "dumpe2fs
> -h /dev/hda2"?
> 
> -Richard


-rw-r--r--  1 root root  11264 May 29 16:49
/boot/grub/e2fs_stage1_5
-rw-r--r--  1 root root    512 May 29 16:49
/boot/grub/stage1
-rw-r--r--  1 root root 137004 May 29 16:49
/boot/grub/stage2

fec478948a06cc1fb7339a2cd3e26663  /boot/grub/stage1
1fad9fe77029e1e89c85c8f8484d6851 
/boot/grub/e2fs_stage1_5
913c881bb93faeaa723aca98bd65843e  /boot/grub/stage2

Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:         
2384cca4-8bb8-4bb9-8c23-2c1e93ff0ece
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      filetype sparse_super
Default mount options:    (none)
Filesystem state:         not clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              7968
Block count:              31752
Reserved block count:     1587
Free blocks:              28257
Free inodes:              7932
First block:              1
Block size:               1024
Fragment size:            1024
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         1992
Inode blocks per group:   249
Filesystem created:       Mon May 23 13:45:44 2005
Last mount time:          Tue May 31 18:13:07 2005
Last write time:          Tue May 31 18:13:07 2005
Mount count:              19
Maximum mount count:      29
Last checked:             Mon May 23 13:45:44 2005
Check interval:           15552000 (6 months)
Next check after:         Sat Nov 19 13:45:44 2005
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Default directory hash:   tea
Directory Hash Seed:     
ebb0f0be-1fc5-43c0-97d0-a384ace470f6

livecd / # qpkg -I -v grub
bash: qpkg: command not found
 
but #grub     

GNU GRUB  version 0.94  (640K lower / 3072K upper
memory)

checksums don't match but neither do versions.

not sure how to interpret tune2fs. 

Come to think of it when it came time to format
/dev/hda2 I had first tried reiserfs since that was
how I formatted /boot on my other gentoo(2004.3) box,
a K6-2, and it seemed to work OK. On this box(2005.0),
a Sempron3100, when I tried to format as reiserfs the
program balked(don't recall the exact circumstances)
so I just did it as ext2 as the 2005.0 handbook
suggested to do in the first place. 

Only thing I can think of for now.



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-- 
gentoo-user@gentoo.org mailing list

Reply via email to