Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #222321 > unrolled thread

Hmmm... /boot is too small. what's the best way to increase it's size?

Back to article view | Back to linux.debian.user

Contents

  Hmmm... /boot is too small. what's the best way to increase it's size? "Rick Thomas" <rick.thomas@pobox.com> - 2020-05-10 05:30 +0200
    Re: Hmmm... /boot is too small. what's the best way to increase it's  size? Andy Smith <andy@strugglers.net> - 2020-05-10 05:40 +0200
      Re: Hmmm... /boot is too small. what's the best way to increase it's  size? Andy Smith <andy@strugglers.net> - 2020-05-10 05:50 +0200
      Re: Hmmm... /boot is too small. what's the best way to increase it's  size? The Wanderer <wanderer@fastmail.fm> - 2020-05-10 06:00 +0200
        Re: Hmmm... /boot is too small. what's the best way to increase it's  size? elvis <elvis@dogonfire.com> - 2020-05-11 07:50 +0200
    Re: Hmmm... /boot is too small. what's the best way to increase  it's size? Charles Curley <charlescurley@charlescurley.com> - 2020-05-10 06:40 +0200
      Re: Hmmm... /boot is too small. what's the best way to increase it's size? "Rick Thomas" <rick.thomas@pobox.com> - 2020-05-10 09:10 +0200
        Re: Hmmm... /boot is too small. what's the best way to increase it's size? "Rick Thomas" <rick.thomas@pobox.com> - 2020-05-10 11:30 +0200
          Re: Hmmm... /boot is too small. what's the best way to increase it's  size? Andrei POPESCU <andreimpopescu@gmail.com> - 2020-05-10 12:30 +0200
            Re: Hmmm... /boot is too small. what's the best way to increase it's size? "Rick Thomas" <rick.thomas@pobox.com> - 2020-05-10 13:30 +0200
              Re: Hmmm... /boot is too small. what's the best way to increase it's  size? Andrei POPESCU <andreimpopescu@gmail.com> - 2020-05-11 08:10 +0200
    Re: Hmmm... /boot is too small. what's the best way to increase it's  size? "Will Mengarini" <seldon@eskimo.com> - 2020-05-10 07:20 +0200
      Re: Hmmm... /boot is too small. what's the best way to increase it's  size? Andrei POPESCU <andreimpopescu@gmail.com> - 2020-05-10 09:10 +0200
      Re: Hmmm... /boot is too small. what's the best way to increase it's size? "Rick Thomas" <rick.thomas@pobox.com> - 2020-05-10 09:20 +0200
      Re: Hmmm... /boot is too small. what's the best way to increase it's  size? David Christensen <dpchrist@holgerdanske.com> - 2020-05-10 10:20 +0200
        Re: Hmmm... /boot is too small. what's the best way to increase it's size? "Rick Thomas" <rick.thomas@pobox.com> - 2020-05-10 11:30 +0200
          Re: Hmmm... /boot is too small. what's the best way to increase it's size? rhkramer@gmail.com - 2020-05-10 14:00 +0200
          Re: Hmmm... /boot is too small. what's the best way to increase it's  size? David Christensen <dpchrist@holgerdanske.com> - 2020-05-10 21:40 +0200
            Re: Hmmm... /boot is too small. what's the best way to increase it's size? "Rick Thomas" <rick.thomas@pobox.com> - 2020-05-11 01:20 +0200
              Re: Hmmm... /boot is too small. what's the best way to increase it's  size? elvis <elvis@dogonfire.com> - 2020-05-11 07:40 +0200
              Re: Hmmm... /boot is too small. what's the best way to increase it's  size? David Christensen <dpchrist@holgerdanske.com> - 2020-05-11 09:40 +0200
            Re: Hmmm... /boot is too small. what's the best way to increase it's  size? Andrei POPESCU <andreimpopescu@gmail.com> - 2020-05-11 08:20 +0200
              Re: Hmmm... /boot is too small. what's the best way to increase it's  size? David Christensen <dpchrist@holgerdanske.com> - 2020-05-11 10:20 +0200
                Re: Hmmm... /boot is too small. what's the best way to increase it's  size? Andrei POPESCU <andreimpopescu@gmail.com> - 2020-05-11 15:10 +0200
          Re: Hmmm... /boot is too small. what's the best way to increase it's  size? Tom Dial <tddial@comcast.net> - 2020-05-11 06:10 +0200
      Re: Hmmm... /boot is too small. what's the best way to increase it's  size? Greg Wooledge <wooledg@eeg.ccf.org> - 2020-05-11 13:40 +0200
        Re: Hmmm... /boot is too small. what's the best way to increase  it's size? Celejar <celejar@gmail.com> - 2020-05-11 16:30 +0200
          Re: Hmmm... /boot is too small. what's the best way to increase it's  size? David Wright <deblis@lionunicorn.co.uk> - 2020-05-11 18:30 +0200
            Re: Hmmm... /boot is too small. what's the best way to increase  it's size? Celejar <celejar@gmail.com> - 2020-05-11 18:50 +0200
    Re: Hmmm... /boot is too small. what's the best way to increase it's  size? David Wright <deblis@lionunicorn.co.uk> - 2020-05-10 16:20 +0200
      Re: Hmmm... /boot is too small. what's the best way to increase it's size? Sven Hartge <sven@svenhartge.de> - 2020-05-10 16:40 +0200
        Re: Hmmm... /boot is too small. what's the best way to increase it's  size? David Wright <deblis@lionunicorn.co.uk> - 2020-05-10 17:20 +0200
    Re: Hmmm... /boot is too small. what's the best way to increase it's  size? Jonathan Dowland <jon+debian-user@dow.land> - 2020-05-14 11:30 +0200

Page 1 of 2  [1] 2  Next page →

#222321 — Hmmm... /boot is too small. what's the best way to increase it's size?

I recently did a "apt update ; apt upgrade" and it died for lack of space in /boot when trying to install the latest kernel.

I purged a couple of old kernel packages (still present in the 'stable' repo, so they weren't obsolete) to make enough space and tried again.  Worked this time, but I would have liked to have the old kernels around as fallbacks just in case of a regression...

Here's the disk layout:

rbthomas@milli:~$ lsblk
NAME                  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                     8:0    0 111.8G  0 disk 
├─sda1                  8:1    0   512M  0 part /boot/efi
├─sda2                  8:2    0   244M  0 part /boot
└─sda3                  8:3    0 111.1G  0 part 
  ├─debian--vg-root   253:0    0    28G  0 lvm  /
  ├─debian--vg-swap_1 253:1    0   7.9G  0 lvm  [SWAP]
  └─debian--vg-home   253:2    0  75.2G  0 lvm  /home
sdb                     8:16   1   239G  0 disk 
└─sdb1                  8:17   1   239G  0 part /media/rbthomas/Spare
mmcblk0               179:0    0 238.3G  0 disk 
└─mmcblk0p1           179:1    0 238.3G  0 part /media/rbthomas/Downloads
rbthomas@milli:~$ 

rbthomas@milli:~$ df -HTP | grep -v tmpfs
Filesystem                  Type      Size  Used Avail Use% Mounted on
/dev/mapper/debian--vg-root ext4       30G  9.9G   19G  36% /
/dev/sda2                   ext2      248M   78M  158M  34% /boot
/dev/sda1                   vfat      536M  144k  536M   1% /boot/efi
/dev/mapper/debian--vg-home ext4       79G  4.4G   71G   6% /home
/dev/sdb1                   ext4      252G   63M  239G   1% /media/rbthomas/Spare
/dev/mmcblk0p1              ext4      251G   63M  238G   1% /media/rbthomas/Downloads
rbthomas@milli:~$ 


What's the best way to increase the size of /boot ?

I can easily create a gig or so of space by a shrink/resize of /home, but how do I add that space to /dev/sda2 ?

I can't just move up the end of /dev/sda2 = start of /dev/sda3 without backing up and restoring, can I?


Any suggestions would be appreciated.
Rick

[toc] | [next] | [standalone]

#222322 — Re: Hmmm... /boot is too small. what's the best way to increase it's size?

Hi Rick,

On Sat, May 09, 2020 at 08:05:48PM -0700, Rick Thomas wrote:
> What's the best way to increase the size of /boot ?

There is no easy way. If you boot into a live/rescue environment and
run parted you *may* be able to shrink your LVM and grow your /boot
but it's a procedure fraught with danger; make sure you have
excellent backups first.

I am not 100% sure that parted can handle partitions that are used
as LVM PVs.

> I can easily create a gig or so of space by a shrink/resize of /home, but how do I add that space to /dev/sda2 ?

This won't work because your /home is an LVM logical volume. Its
actual extents could be all over sda3.

> I can't just move up the end of /dev/sda2 = start of /dev/sda3 without backing up and restoring, can I?

parted can move partitions about, so if you run it from outside your
install and it does support LVM PV then it might work. You'd
basically have to shift everything up the disk, making your PV
(sda3) slightly smaller in the process.

I really wouldn't like to try it myself. With the backup that you'll
need you may as well just reinstall as even if parted can do this it
will take some time for it to rewrite all that data.

This is a great example of why it's not good to be stingy with the
size of /boot.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#222324 — Re: Hmmm... /boot is too small. what's the best way to increase it's size?

Another thought that is maybe a little outside the box: If your BIOS
supports booting from USB or media slot then you could maybe make a
new boot partition on one of those devices and switch to booting
from that from now on.

Ties up a USB or media slot forever of course, but possibly an
acceptable compromise.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#222325 — Re: Hmmm... /boot is too small. what's the best way to increase it's size?

[Multipart message — attachments visible in raw view] — view raw

On 2020-05-09 at 23:36, Andy Smith wrote:

> Hi Rick,
> 
> On Sat, May 09, 2020 at 08:05:48PM -0700, Rick Thomas wrote:
>> What's the best way to increase the size of /boot ?
> 
> There is no easy way. If you boot into a live/rescue environment and 
> run parted you *may* be able to shrink your LVM and grow your /boot 
> but it's a procedure fraught with danger; make sure you have 
> excellent backups first.
> 
> I am not 100% sure that parted can handle partitions that are used as
> LVM PVs.
> 
>> I can easily create a gig or so of space by a shrink/resize of
>> /home, but how do I add that space to /dev/sda2 ?
> 
> This won't work because your /home is an LVM logical volume. Its 
> actual extents could be all over sda3.
> 
>> I can't just move up the end of /dev/sda2 = start of /dev/sda3
>> without backing up and restoring, can I?
> 
> parted can move partitions about, so if you run it from outside your 
> install and it does support LVM PV then it might work. You'd 
> basically have to shift everything up the disk, making your PV (sda3)
> slightly smaller in the process.
> 
> I really wouldn't like to try it myself. With the backup that you'll 
> need you may as well just reinstall as even if parted can do this it 
> will take some time for it to rewrite all that data.

In theory I *think* it should be possible to shrink /home, shrink the
LV, shrink the PV, then expand /boot - but the practice may be quite
different from the theory.

https://unix.stackexchange.com/questions/479545/how-to-shrink-a-physical-volume
has detailed instructions on how to do one part of the process, and
indicates that gparted can indeed handle LVM PVs - but whether it's
suitable for the actual scenario at hand here probably depends on how
you've got your PVs and LVs set up, and I don't know enough about that
to make a recommendation, aside from being very careful with backups no
matter what.

(I'm also up late, so don't necessarily trust me to have things right at
the moment; double-check before going ahead, and if in doubt, don't.)

> This is a great example of why it's not good to be stingy with the 
> size of /boot.

Definitely. My current system started out with around 4-8 TB of usable
space (across all partitions, after RAID overhead) when I first built
it, and I have fully 22GB allocated to /boot. That's ridiculous overkill
- even 1GB would probably have been more than I'm likely to ever need
here, and 2GB would definitely have - but I'd far rather have erred on
the side of too much than too little.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#222357 — Re: Hmmm... /boot is too small. what's the best way to increase it's size?

Old ways die hard, disk space is cheap! these days

On 10/5/20 1:53 pm, The Wanderer wrote:
> On 2020-05-09 at 23:36, Andy Smith wrote:
>
>> Hi Rick,
>>
>> On Sat, May 09, 2020 at 08:05:48PM -0700, Rick Thomas wrote:
>>> What's the best way to increase the size of /boot ?
>> There is no easy way. If you boot into a live/rescue environment and
>> run parted you *may* be able to shrink your LVM and grow your /boot
>> but it's a procedure fraught with danger; make sure you have
>> excellent backups first.
>>
>> I am not 100% sure that parted can handle partitions that are used as
>> LVM PVs.
>>
>>> I can easily create a gig or so of space by a shrink/resize of
>>> /home, but how do I add that space to /dev/sda2 ?
>> This won't work because your /home is an LVM logical volume. Its
>> actual extents could be all over sda3.
>>
>>> I can't just move up the end of /dev/sda2 = start of /dev/sda3
>>> without backing up and restoring, can I?
>> parted can move partitions about, so if you run it from outside your
>> install and it does support LVM PV then it might work. You'd
>> basically have to shift everything up the disk, making your PV (sda3)
>> slightly smaller in the process.
>>
>> I really wouldn't like to try it myself. With the backup that you'll
>> need you may as well just reinstall as even if parted can do this it
>> will take some time for it to rewrite all that data.
> In theory I *think* it should be possible to shrink /home, shrink the
> LV, shrink the PV, then expand /boot - but the practice may be quite
> different from the theory.
>
> https://unix.stackexchange.com/questions/479545/how-to-shrink-a-physical-volume
> has detailed instructions on how to do one part of the process, and
> indicates that gparted can indeed handle LVM PVs - but whether it's
> suitable for the actual scenario at hand here probably depends on how
> you've got your PVs and LVs set up, and I don't know enough about that
> to make a recommendation, aside from being very careful with backups no
> matter what.
>
> (I'm also up late, so don't necessarily trust me to have things right at
> the moment; double-check before going ahead, and if in doubt, don't.)
>
>> This is a great example of why it's not good to be stingy with the
>> size of /boot.
> Definitely. My current system started out with around 4-8 TB of usable
> space (across all partitions, after RAID overhead) when I first built
> it, and I have fully 22GB allocated to /boot. That's ridiculous overkill
> - even 1GB would probably have been more than I'm likely to ever need
> here, and 2GB would definitely have - but I'd far rather have erred on
> the side of too much than too little.


And yet your 22GB hasn't cracked the $1 mark on a cost effective drive.







-- 
All that glitters has a high refractive index.

[toc] | [prev] | [next] | [standalone]

#222326 — Re: Hmmm... /boot is too small. what's the best way to increase it's size?

On Sat, 09 May 2020 20:05:48 -0700
"Rick Thomas" <rick.thomas@pobox.com> wrote:

> Filesystem                  Type      Size  Used Avail Use% Mounted on
> /dev/mapper/debian--vg-root ext4       30G  9.9G   19G  36% /
> /dev/sda2                   ext2      248M   78M  158M  34% /boot

Odd. That should be good for more than three kernels. I have:

root@jhegaala:~# df /boot/
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda5       226M   92M  119M  44% /boot
root@jhegaala:~#

with three kernels.

My /boot is ext4, but I doubt that makes enough difference to matter.
My installation is not EFI. Would that make the difference?

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#222329

On Sat, May 9, 2020, at 9:10 PM, Charles Curley wrote:
> On Sat, 09 May 2020 20:05:48 -0700
> "Rick Thomas" <rick.thomas@pobox.com> wrote:
> 
> > Filesystem                  Type      Size  Used Avail Use% Mounted on
> > /dev/mapper/debian--vg-root ext4       30G  9.9G   19G  36% /
> > /dev/sda2                   ext2      248M   78M  158M  34% /boot
> 
> Odd. That should be good for more than three kernels. I have:
> 
> root@jhegaala:~# df /boot/
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/sda5       226M   92M  119M  44% /boot
> root@jhegaala:~#
> 
> with three kernels.
> 
> My /boot is ext4, but I doubt that makes enough difference to matter.
> My installation is not EFI. Would that make the difference?

The figures above are *after* I deleted the two previous kernel versions.  So yes, there's plenty of space there when this is taken.  It looks like each kernel/initrd combo takes 75-80 MB so three of them could take as much as 240 MB, just a bit beyond the space available.

Stay well and stay safe!
Rick

[toc] | [prev] | [next] | [standalone]

#222333

So... Here's another question:

Why is the default size of /boot, as created by the installer, so small?  Disk (even SSD) is cheap enough these days that the default size could be as much as a GB without great pain.

Has this been thought about by the PTBs?  Was there a discussion of possibly raising the default?  Maybe I missed it...

Stay safe and stay healthy!
Rick

[toc] | [prev] | [next] | [standalone]

#222337 — Re: Hmmm... /boot is too small. what's the best way to increase it's size?

[Multipart message — attachments visible in raw view] — view raw

On Du, 10 mai 20, 02:02:45, Rick Thomas wrote:
> So... Here's another question:
> 
> Why is the default size of /boot, as created by the installer, so 
> small?  Disk (even SSD) is cheap enough these days that the default 
> size could be as much as a GB without great pain.
> 
> Has this been thought about by the PTBs?  Was there a discussion of 
> possibly raising the default?  Maybe I missed it...

A quick search in the BTS reveals #893886 and #951709 (both fixed in 
git).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#222338

On Sun, May 10, 2020, at 3:22 AM, Andrei POPESCU wrote:
> On Du, 10 mai 20, 02:02:45, Rick Thomas wrote:
> > So... Here's another question:
> > 
> > Why is the default size of /boot, as created by the installer, so 
> > small?  Disk (even SSD) is cheap enough these days that the default 
> > size could be as much as a GB without great pain.
> > 
> > Has this been thought about by the PTBs?  Was there a discussion of 
> > possibly raising the default?  Maybe I missed it...
> 
> A quick search in the BTS reveals #893886 and #951709 (both fixed in 
> git).

Thanks for the pointers, Andrei!   Do you think those changes will get into Bullseye before it's released?
Rick

[toc] | [prev] | [next] | [standalone]

#222358 — Re: Hmmm... /boot is too small. what's the best way to increase it's size?

[Multipart message — attachments visible in raw view] — view raw

On Du, 10 mai 20, 04:03:29, Rick Thomas wrote:
> On Sun, May 10, 2020, at 3:22 AM, Andrei POPESCU wrote:
> > On Du, 10 mai 20, 02:02:45, Rick Thomas wrote:
> > > So... Here's another question:
> > > 
> > > Why is the default size of /boot, as created by the installer, so 
> > > small?  Disk (even SSD) is cheap enough these days that the default 
> > > size could be as much as a GB without great pain.
> > > 
> > > Has this been thought about by the PTBs?  Was there a discussion of 
> > > possibly raising the default?  Maybe I missed it...
> > 
> > A quick search in the BTS reveals #893886 and #951709 (both fixed in 
> > git).
> 
> Thanks for the pointers, Andrei!   Do you think those changes will get 
> into Bullseye before it's released?

Yes. It should be available soon in the daily and weekly images.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#222327 — Re: Hmmm... /boot is too small. what's the best way to increase it's size?

* Rick Thomas <rick.thomas@pobox.com> [20-05/09=Sa 20:05 -0700]:
> [...] died for lack of space in /boot [...]

Long ago I stopped bothering with a separate /boot, and behold, I yet
live.  ISTR the Debian installer doesn't default to creating one either.

If you really want a bastion filesystem for booting, I suggest it be /
(say 8G), because that'll also give you /bin, /lib, /etc, etc, without
which you can't troubleshoot system horkage anyway.  Then you can
put /home and /usr on the beta release of FunkyFS and have fun.  I'd
also put /tmp on the same partition as /home, because when I want to
rm $junk I typically do it with mv -t/tmp $junk for safety, which on
the same filesystem just edits directory entries, but on a different
one actually copies $junk, meh.  Make sure your bastion filesystem has
enough room for /var/spool; shouldn't be a problem unless you're one
of those people who likes 30G mailboxes, or are running a news server.

Stay safe, back up your files, and wash your hands.

> rbthomas@milli:~$ lsblk
> NAME                  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
> sda                     8:0    0 111.8G  0 disk
> +-sda1                  8:1    0   512M  0 part /boot/efi
> +-sda2                  8:2    0   244M  0 part /boot
> +-sda3                  8:3    0 111.1G  0 part
>   +-debian--vg-root   253:0    0    28G  0 lvm  /
>   +-debian--vg-swap_1 253:1    0   7.9G  0 lvm  [SWAP]
>   +-debian--vg-home   253:2    0  75.2G  0 lvm  /home
> sdb                     8:16   1   239G  0 disk
> +-sdb1                  8:17   1   239G  0 part /media/rbthomas/Spare
> mmcblk0               179:0    0 238.3G  0 disk
> +-mmcblk0p1           179:1    0 238.3G  0 part /media/rbthomas/Downloads
> rbthomas@milli:~$
>
> rbthomas@milli:~$ df -HTP | grep -v tmpfs
> Filesystem                  Type Size Used Avail Use% Mounted on
> /dev/mapper/debian--vg-root ext4  30G 9.9G   19G  36% /
> /dev/sda2                   ext2 248M  78M  158M  34% /boot
> /dev/sda1                   vfat 536M 144k  536M   1% /boot/efi
> /dev/mapper/debian--vg-home ext4  79G 4.4G   71G   6% /home
> /dev/sdb1                   ext4 252G  63M  239G   1% /media/rbthomas/Spare
> /dev/mmcblk0p1              ext4 251G  63M  238G   1% /media/rbthomas/Downloads
> rbthomas@milli:~$
>
> What's the best way to increase the size of /boot?

By creating a reliable backup and reformatting the disk to
the new format.  I've never found it to be cost-effective
to try anything else.  I don't even upgrade to new releases
anymore; I just nuke everything and do a fresh install.

> I can easily create a gig or so of space by a shrink/resize
> of /home, but how do I add that space to /dev/sda2?
>
> I can't just move up the end of /dev/sda2 = start of
> /dev/sda3 without backing up and restoring, can I?
>
> Any suggestions would be appreciated.

Consider the time you've spent posing this question, waiting for the
answers, and reading them.  Dump and reload might've finished already.

-- 
                 Will Mengarini  <seldon@eskimo.com>
         Free software: the Source will be with you, always.
This will be a memorable month -- no matter how hard you try to forget it.
    --Unix fortune cookie

[toc] | [prev] | [next] | [standalone]

#222330 — Re: Hmmm... /boot is too small. what's the best way to increase it's size?

[Multipart message — attachments visible in raw view] — view raw

On Sb, 09 mai 20, 22:05:40, Will Mengarini wrote:
> * Rick Thomas <rick.thomas@pobox.com> [20-05/09=Sa 20:05 -0700]:
> > [...] died for lack of space in /boot [...]
>
> Long ago I stopped bothering with a separate /boot, and behold, I yet
> live.  ISTR the Debian installer doesn't default to creating one 
> either.

Agreed.

> If you really want a bastion filesystem for booting, I suggest it be /
> (say 8G), because that'll also give you /bin, /lib, /etc, etc, without
> which you can't troubleshoot system horkage anyway.  Then you can
> put /home and /usr on the beta release of FunkyFS and have fun.

Booting without /usr is not supported anymore and with usrmerge most of 
the stuff from / was moved to /usr anyway.

Unless you want to keep /usr read-only (except for package upgrades) 
and/or share it between systems there is no real need to have it on a 
separate partition.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#222331

> Consider the time you've spent posing this question, waiting for the
> answers, and reading them.  Dump and reload might've finished already.

True, but I wouldn't have learned half so much and wouldn't have had a third so much had so much fun learning it!

Stay safe!

[toc] | [prev] | [next] | [standalone]

#222332 — Re: Hmmm... /boot is too small. what's the best way to increase it's size?

On 2020-05-09 22:05, Will Mengarini wrote:
> * Rick Thomas <rick.thomas@pobox.com> [20-05/09=Sa 20:05 -0700]:

>> What's the best way to increase the size of /boot?
> 
> By creating a reliable backup and reformatting the disk to
> the new format.  I've never found it to be cost-effective
> to try anything else. 

+1


> I don't even upgrade to new releases
> anymore; I just nuke everything and do a fresh install.

+1


David

[toc] | [prev] | [next] | [standalone]

#222335

On Sun, May 10, 2020, at 1:17 AM, David Christensen wrote:
> On 2020-05-09 22:05, Will Mengarini wrote:
> > * Rick Thomas <rick.thomas@pobox.com> [20-05/09=Sa 20:05 -0700]:
> >> What's the best way to increase the size of /boot?
> > By creating a reliable backup and reformatting the disk to
> > the new format.  I've never found it to be cost-effective
> > to try anything else. 
> +1

Yeah, that's probably what I'll do.  Fortunately, it's an amd64 machine, so I'll be able to use GRML to do the work.
Enjoy!
Rick

[toc] | [prev] | [next] | [standalone]

#222339

On Sunday, May 10, 2020 05:07:24 AM Rick Thomas wrote:

> > > * Rick Thomas <rick.thomas@pobox.com> [20-05/09=Sa 20:05 -0700]:
> > >> What's the best way to increase the size of /boot?

> Yeah, that's probably what I'll do.  Fortunately, it's an amd64 machine, so
> I'll be able to use GRML to do the work. Enjoy!

Another option: it looks like there is room in your ~240 MB /boot for two 
kernels -- why not back up older kernels to somewhere else (somewhere in 
/home, /, or an external device and just keep the current and the previous 
kernel in /boot.

Then on your next fresh install, make a bigger /boot... (or just leave it in / 
(particularly as I'm not sure of the implications of needing /usr during 
boot)).

[toc] | [prev] | [next] | [standalone]

#222350 — Re: Hmmm... /boot is too small. what's the best way to increase it's size?

On 2020-05-10 02:07, Rick Thomas wrote:
> 
> 
> On Sun, May 10, 2020, at 1:17 AM, David Christensen wrote:
>> On 2020-05-09 22:05, Will Mengarini wrote:
>>> * Rick Thomas <rick.thomas@pobox.com> [20-05/09=Sa 20:05 -0700]:
>>>> What's the best way to increase the size of /boot?
>>> By creating a reliable backup and reformatting the disk to
>>> the new format.  I've never found it to be cost-effective
>>> to try anything else.
>> +1
> 
> Yeah, that's probably what I'll do.  Fortunately, it's an amd64 machine, so I'll be able to use GRML to do the work.


I advise that you put your operating system on one drive and your data 
on other drives (e.g. RAID file server), and that you keep your system 
drive image small enough to fit on a "16 GB" device -- HDD, SSD, USB 
flash drive, SD card, etc..


As for using GRML, I have never heard of it.  The Debian Installer can 
get the job done.  That said, I have about a half dozen machines and 
have been feeling the need for installation and deployment automation. 
I have heard of Puppet more than once.  Lucas [1] recommends Ansible 
[2], so I will probably try that.


David


[1] https://mwl.io/

[2] https://www.ansible.com/

[toc] | [prev] | [next] | [standalone]

#222354

On Sun, May 10, 2020, at 12:30 PM, David Christensen wrote:

> As for using GRML, I have never heard of it.  The Debian Installer can 
> get the job done.  

GRML [1]  says: "Grml is a bootable live system (Live-CD) based on Debian. Grml includes a collection of GNU/Linux software especially for system administrators. Users don't have to install anything on fixed storage. Grml is especially well suited for administrative tasks like installation, deployment and system rescue. Read more..."

There's also Debian Live, which also has all the features I'll need to do a full backup, repartition, and restore.  The installer in rescue mode is more limited than either of these alternatives.

Rick

[1] http://grml.org

[toc] | [prev] | [next] | [standalone]

#222356 — Re: Hmmm... /boot is too small. what's the best way to increase it's size?

On 11/5/20 8:53 am, Rick Thomas wrote:
>
> On Sun, May 10, 2020, at 12:30 PM, David Christensen wrote:
>
>> As for using GRML, I have never heard of it.  The Debian Installer can
>> get the job done.
> GRML [1]  says: "Grml is a bootable live system (Live-CD) based on Debian. Grml includes a collection of GNU/Linux software especially for system administrators. Users don't have to install anything on fixed storage. Grml is especially well suited for administrative tasks like installation, deployment and system rescue. Read more..."
>
> There's also Debian Live, which also has all the features I'll need to do a full backup, repartition, and restore.  The installer in rescue mode is more limited than either of these alternatives.


Buy a cheap SSD and put boot and root on that. A WD green 120GB cost $39 
AUD.




> Rick
>
> [1] http://grml.org
>
-- 
Nuclear weapons can wipe out life on Earth, if used properly

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web