1 |
----- Original Message ----- |
2 |
>From: Beso |
3 |
>To: gentoo-amd64@l.g.o |
4 |
>Sent: Saturday, May 17, 2008 2:04 PM |
5 |
>Subject: Re: [gentoo-amd64] new clean rebuild |
6 |
|
7 |
<snip><beso discussed rebuild> |
8 |
|
9 |
>2008/5/17 Mark Knecht markknecht@×××××.com |
10 |
said in part in reply: |
11 |
|
12 |
>1) Mask >grub-0.97.r4 for now. |
13 |
|
14 |
Recommend not doing the step above. |
15 |
|
16 |
In contrast to my experience a week ago when ext2/ext3 filesystems were |
17 |
being built with INODE_SIZE=128 (in spite of a default INODE_SIZE=256 in |
18 |
the /etc/mke2fs.conf file}; yesterday, an up-to-date mke2fs was honoring |
19 |
the default setting and producing ext2/ext3 filesystems with |
20 |
INODE_SIZE=256. |
21 |
If one runs mke2fs as suggested in the handbook to create a filesystem for |
22 |
use as /boot the filesystem will have INODE_SIZE=256. Therefore |
23 |
grub-0.97.r4 and older will not be able to setup a stage 1/stage1.5/stage2 |
24 |
capable of loading /boot. At the point the handbook follower finds that grub |
25 |
0.97.4 is reporting: |
26 |
<quote> |
27 |
grub> setup (hd0) |
28 |
Checking if "/boot/grub/stage1" exists... no |
29 |
Checking if "/grub/stage1" exists... no |
30 |
|
31 |
Error 2: Bad file or directory type |
32 |
<unquote> |
33 |
The valid recovery choices then will be: |
34 |
a) unmask grub, emerge grub (version 0.97.5 or newer), run grub and setup |
35 |
the desired drive |
36 |
or |
37 |
b) move or copy /boot and subdirectories to another partition, remake the |
38 |
filesystem specifying INODE_SIZE=128, return /boot and subdirectories to the |
39 |
remade partition, run grub setup the desired drive. |
40 |
|
41 |
<snip><Mark suggested rebuild techniques><beso further discussed/replied> |
42 |
|
43 |
Beso said in part in reply: |
44 |
|
45 |
>ps. i've never had any problems with grub, unless the fact that i'm not |
46 |
>able to rebuild it with the grubfx >image (as the opensuse version). |
47 |
|
48 |
I've played extensively with grub 0.97-r5 in the last 10 days and it is not |
49 |
a problem. |
50 |
Should also be noted that emerging/installing grub has no affect on the |
51 |
ability to boot an existing installation. Effects are not felt until grub or |
52 |
grub-install is run or grub.conf is edited. |
53 |
-- |
54 |
dott. ing. beso |
55 |
|
56 |
-- |
57 |
gentoo-amd64@l.g.o mailing list |