1 |
On 03/05/2017 04:22 PM, Mick wrote: |
2 |
> On Sunday 05 Mar 2017 16:57:11 Dale wrote: |
3 |
>> thelma@×××××××××××.com wrote: |
4 |
>>> On 03/05/2017 02:33 PM, thelma@×××××××××××.com wrote: |
5 |
[snip] |
6 |
>> |
7 |
>> I'm pretty sure grub uses that file. I've never tested the theory. |
8 |
>> |
9 |
>> Why such a small /boot? My OS is installed on a fairly small 160GB hard |
10 |
>> drive. I made /boot about 400MBs and later wished it was bigger. I |
11 |
>> later wanted to put a ISO image there for sysrescue. If I were to set |
12 |
>> up a new system now with that same size or larger drive, I'd likely make |
13 |
>> /boot 1GB and maybe even 2GBs in size. The amount of space is not that |
14 |
>> large compared to the size of the hard drive. If one is pressed to save |
15 |
>> space that bad on a system, maybe they need a larger drive?? |
16 |
>> |
17 |
>> You mentioned following a guide on that size. I have to ask, just how |
18 |
>> old was that guide? I looked at the Gentoo install guide, it suggests |
19 |
>> 128MBs for /boot, which I think is to small. Whatever guide you were |
20 |
>> using, it must be old and need some updating. I'm not sure I'd follow |
21 |
>> that one until it was. |
22 |
>> |
23 |
>> Dale |
24 |
>> |
25 |
>> :-) :-) |
26 |
> |
27 |
> Yes, back in the GRUB legacy days boot partition was suggested to be something |
28 |
> like 30MB I recall. However, things have moved on and kernels got bigger |
29 |
> since then. |
30 |
|
31 |
Thanks for pointing it out. The box is several years old and as you pointing it out the guidelines those days were 30MB |
32 |
|
33 |
|
34 |
> Despite this, on an old box using GRUB legacy I have 2 kernel images, two |
35 |
> System files, two config files. I also have installed memtest, which in an |
36 |
> isolinux directory on its own is taking up 11MB. My boot partition is 46MB, |
37 |
> but only 33MB is used. If I didn't have memtest installed, then my 2x kernel, |
38 |
> System and config files would fit in less than 20MB. |
39 |
> |
40 |
> Do you have anything else in there you have not accounted for? For example |
41 |
> how large is this /boot/grub/splash.xpm.gz of yours? |
42 |
|
43 |
That file is very small: |
44 |
34K Mar 5 11:46 /boot/grub/splash.xpm.gz |
45 |
|
46 |
> |
47 |
> There's different ways you can hack at this problem: |
48 |
> |
49 |
> 1. What Alan said. |
50 |
> |
51 |
> 2. Tar everything out of the whole installation, resize/delete/recreate |
52 |
> partitions, move everything back. Not as slow and painful as Alan spoke of. |
53 |
> |
54 |
> 3. Create a new partition at the end of the disk, large enough for boot, after |
55 |
> you resize the last partition to free up some space. |
56 |
> |
57 |
> 4. Do not create a new partition for boot, just copy the /boot filesystem into |
58 |
> / and comment out the boot partition from fstab. You'll need to also edit |
59 |
> your /boot/grub/grub.conf |
60 |
|
61 |
I like your solution #4. Will it work? |
62 |
|
63 |
Current fstab: |
64 |
/dev/sda1 /boot ext2 noauto,noatime 1 2 |
65 |
/dev/sda3 / ext4 noatime 0 1 |
66 |
|
67 |
Change to: |
68 |
/dev/sda3 /boot ext4 noatime 0 1 |
69 |
/dev/sda3 / ext4 noatime 0 1 |
70 |
|
71 |
Copy from /dev/sda1 "/boot" to /dev/sda3 /boot |
72 |
|
73 |
grub.conf: |
74 |
kernel /boot/kernel-current root=/dev/sda3 vga=normal |
75 |
|
76 |
Since fstab is pointing to sda3 I don't think I need to change anything. |
77 |
|
78 |
|
79 |
> |
80 |
> 5. Boot with a LiveCD, delete/move old kernel and/or any unnecessary files, |
81 |
> check /boot/grub/grub.conf, reboot. |
82 |
> |
83 |
> Any of the above will work, but some make more sense than others depending on |
84 |
> your use case for this particular installation. |
85 |
> |
86 |
|
87 |
-- |
88 |
Thelma |