Boot disk size increase - possible? [SOLVED]

[DanR]

I know it is possible with GParted. Question actually is - have you personally done this before and have Mint survived this torture no problem?

I was surprised to find that my boot disk partition size shown by Disks is as small as 0.5GB when it supposed to be 10 and i remember some other software had shown it 10GB (but may be i mixed it with some other similar 2TB disk) . Do not know how hell this happened during installation. Anyway, is it possible to resize it without damaging the installation? Tired to reinstall different Linuxes already 3d time in a year. Here is the disk map. The next partition is 150GB with 120GB free, next (swap) 256GB does not show free space, and final 1.6TB also has enough free space.



Like one user wrote:
" I don't understand why the Linux default install only creates a 512mb /boot with enough room for two kernels, then tries to keep the old one, doesn't have enough room for the new one, then dies on upgrades. That's so obviously stupid, and that's been true for like a decade. I just don't get it. ". I also do not get it, any current drive has space for many kernels. During decade harddrives increased in size by factor of 10 and in two decade 100x and keep growing same pace, while @#$% still keep using totally retarded sizes, in this case ... 0.025% (!!!)

[Pulegium]

I think it's technically " possible " but I would not recommend it . I tried it years ago and just borked my system . Boot and Root are rather sensitive to being shuffled around a drive .
Default Boot is 512mb because that's plenty big enough . For some strange reason I made a 1GB Boot partition on my current system . At the moment it has 7 kernels in it and is 1.2 % full , so you can stuff a heck of a lot more than 2 kernels in 512 MB . I think the user you quote is misunderstanding something about their installation .
The number of kernels in your Boot partition can be managed from the Update Manager > View > Linux Kernels .
You can set your system to automatically delete old kernels in Update Manager > Edit > Preferences > Automation > Automatic Maintenance > turn on " Remove obsolete kernels and dependencies " .

[DanR]

I have just recently installed Mint, it is basically fresh, couple compilers are there and couple apps, and the boot is more than a half-full. I suspect due to that i can not install anything anymore, all failing. Here is an attempt to install Anydesk:

Code: Select all

installArchives() failed: Selecting previously unselected package libgtkglext1:amd64.
(Reading database ... 
(Reading database ... 5%%
(Reading database ... 10%%
(Reading database ... 15%%
(Reading database ... 20%%
(Reading database ... 25%%
(Reading database ... 30%%
(Reading database ... 35%%
(Reading database ... 40%%
(Reading database ... 45%%
(Reading database ... 50%%
(Reading database ... 55%%
(Reading database ... 60%%
(Reading database ... 65%%
(Reading database ... 70%%
(Reading database ... 75%%
(Reading database ... 80%%
(Reading database ... 85%%
(Reading database ... 90%%
(Reading database ... 95%%
(Reading database ... 100%%
(Reading database ... 590117 files and directories currently installed.)
Preparing to unpack .../libgtkglext1_1.2.0-11_amd64.deb ...
Unpacking libgtkglext1:amd64 (1.2.0-11) ...
Setting up initramfs-tools (0.140ubuntu13.1) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-firmware (20220329.git681281e4-0ubuntu3.13) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-56-generic
I: The initramfs will attempt to resume from /dev/nvme0n1p6
I: (UUID=4c3acfe8-2a2f-418b-8e2e-e1999a4d3f1b)
I: Set the RESUME variable to override this.
zstd: error 25 : Write error : No space left on device (cannot write compressed block) 
E: mkinitramfs failure zstd -q -1 -T0 25
update-initramfs: failed for /boot/initrd.img-5.15.0-56-generic with 1.
dpkg: error processing package linux-firmware (--configure):
 installed linux-firmware package post-installation script subprocess returned error exit status 1
Setting up libgtkglext1:amd64 (1.2.0-11) ...
Setting up linux-image-5.15.0-72-generic (5.15.0-72.79) ...
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-firmware; however:
  Package linux-firmware is not configured yet.

dpkg: error processing package linux-image-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-image-generic (= 5.15.0.72.70); however:
  Package linux-image-generic is not configured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
Processing triggers for initramfs-tools (0.140ubuntu13.1) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-56-generic
I: The initramfs will attempt to resume from /dev/nvme0n1p6
I: (UUID=4c3acfe8-2a2f-418b-8e2e-e1999a4d3f1b)
I: Set the RESUME variable to override this.
zstd: error 25 : Write error : No space left on device (cannot write compressed block) 
E: mkinitramfs failure zstd -q -1 -T0 25
update-initramfs: failed for /boot/initrd.img-5.15.0-56-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Processing triggers for linux-image-5.15.0-72-generic (5.15.0-72.79) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.15.0-72-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-72-generic
I: The initramfs will attempt to resume from /dev/nvme0n1p6
I: (UUID=4c3acfe8-2a2f-418b-8e2e-e1999a4d3f1b)
I: Set the RESUME variable to override this.
zstd: error 25 : Write error : No space left on device (cannot write compressed block) 
E: mkinitramfs failure zstd -q -1 -T0 25
update-initramfs: failed for /boot/initrd.img-5.15.0-72-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.15.0-72-generic (--configure):
 installed linux-image-5.15.0-72-generic package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 linux-firmware
 linux-image-generic
 linux-generic
 initramfs-tools
 linux-image-5.15.0-72-generic
Setting up initramfs-tools (0.140ubuntu13.1) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-firmware (20220329.git681281e4-0ubuntu3.13) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-56-generic
I: The initramfs will attempt to resume from /dev/nvme0n1p6
I: (UUID=4c3acfe8-2a2f-418b-8e2e-e1999a4d3f1b)
I: Set the RESUME variable to override this.
zstd: error 25 : Write error : No space left on device (cannot write compressed block) 
E: mkinitramfs failure zstd -q -1 -T0 25
update-initramfs: failed for /boot/initrd.img-5.15.0-56-generic with 1.
dpkg: error processing package linux-firmware (--configure):
 installed linux-firmware package post-installation script subprocess returned error exit status 1
Setting up linux-image-5.15.0-72-generic (5.15.0-72.79) ...
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-firmware; however:
  Package linux-firmware is not configured yet.

dpkg: error processing package linux-image-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-image-generic (= 5.15.0.72.70); however:
  Package linux-image-generic is not configured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.140ubuntu13.1) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-56-generic
I: The initramfs will attempt to resume from /dev/nvme0n1p6
I: (UUID=4c3acfe8-2a2f-418b-8e2e-e1999a4d3f1b)
I: Set the RESUME variable to override this.
zstd: error 25 : Write error : No space left on device (cannot write compressed block) 
E: mkinitramfs failure zstd -q -1 -T0 25
update-initramfs: failed for /boot/initrd.img-5.15.0-56-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Processing triggers for linux-image-5.15.0-72-generic (5.15.0-72.79) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.15.0-72-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-72-generic
I: The initramfs will attempt to resume from /dev/nvme0n1p6
I: (UUID=4c3acfe8-2a2f-418b-8e2e-e1999a4d3f1b)
I: Set the RESUME variable to override this.
zstd: error 25 : Write error : No space left on device (cannot write compressed block) 
E: mkinitramfs failure zstd -q -1 -T0 25
update-initramfs: failed for /boot/initrd.img-5.15.0-72-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.15.0-72-generic (--configure):
 installed linux-image-5.15.0-72-generic package post-installation script subprocess returned error exit status 1
Top
16 posts • Page 1 of 1

[RIH]

Can you please go
Menu - System Info - Upload system information
& paste the result back here in-between the code tags (</>).

[DanR]

RIH, here it is.
Forgot to say, I have tripple boot, Windows, Ubuntu, Mint, but each OS is on its own hard drive, which simplifies things

Code: Select all

System:
  Kernel: 5.15.0-56-generic x86_64 bits: 64 compiler: gcc v: 11.3.0 Desktop: Cinnamon 5.6.8
    tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING X570-PRO (WI-FI) v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 3001 date: 12/04/2020
Battery:
  Device-1: hidpp_battery_0 model: Logitech M720 Triathlon Multi-Device Mouse serial: <filter>
    charge: 55% (should be ignored) status: Discharging
CPU:
  Info: 16-core model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3 rev: 0 cache:
    L1: 1024 KiB L2: 8 MiB L3: 64 MiB
  Speed (MHz): avg: 3991 high: 4009 min/max: 2200/5980 boost: enabled cores: 1: 3990 2: 4000
    3: 3999 4: 3998 5: 3995 6: 4000 7: 4009 8: 3991 9: 3976 10: 3997 11: 3966 12: 4006 13: 3996
    14: 3998 15: 3997 16: 3998 17: 3990 18: 3998 19: 3978 20: 3995 21: 3978 22: 3973 23: 4000
    24: 3998 25: 3996 26: 3996 27: 3997 28: 3995 29: 3978 30: 3963 31: 3999 32: 3991
    bogomips: 255980
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GA102 [GeForce RTX 3090] vendor: eVga.com. driver: nvidia v: 525.105.17 pcie:
    speed: 2.5 GT/s lanes: 16 ports: active: none off: HDMI-A-1 empty: DP-1,DP-2,DP-3
    bus-ID: 0b:00.0 chip-ID: 10de:2204
  Device-2: HP HP Webcam HD 5210 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-1.2:4
    chip-ID: 03f0:cf07
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4096x2160 s-dpi: 96
  Monitor-1: HDMI-0 res: 4096x2160 dpi: 406 diag: 289mm (11.4")
  OpenGL: renderer: NVIDIA GeForce RTX 3090/PCIe/SSE2 v: 4.6.0 NVIDIA 525.105.17
    direct render: Yes
Audio:
  Device-1: NVIDIA GA102 High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel
    pcie: speed: 16 GT/s lanes: 16 bus-ID: 0b:00.1 chip-ID: 10de:1aef
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    speed: 16 GT/s lanes: 16 bus-ID: 0d:00.4 chip-ID: 1022:1487
  Device-3: HP HP Webcam HD 5210 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-1.2:4
    chip-ID: 03f0:cf07
  Sound Server-1: ALSA v: k5.15.0-56-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 06:00.0 chip-ID: 8086:2723
  IF: wlp6s0 state: down mac: <filter>
  Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 07:00.0 chip-ID: 8086:15f3
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:8 chip-ID: 8087:0029
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 237e
Drives:
  Local Storage: total: 56.39 TiB used: 32.92 TiB (58.4%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN850X 2000GB size: 1.82 TiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 42.9 C
  ID-2: /dev/nvme1n1 vendor: Western Digital model: WDS200T1X0E-00AFY0 size: 1.82 TiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 42.9 C
  ID-3: /dev/nvme2n1 vendor: Western Digital model: WD BLACK SN850X 2000GB size: 1.82 TiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 41.9 C
  ID-4: /dev/sda vendor: Western Digital model: WD161KRYZ-01AGBB0 size: 14.55 TiB
    speed: 6.0 Gb/s serial: <filter>
  ID-5: /dev/sdb vendor: Western Digital model: WD161KRYZ-01AGBB0 size: 14.55 TiB
    speed: 6.0 Gb/s serial: <filter>
  ID-6: /dev/sdc type: USB vendor: HGST (Hitachi) model: HUH721212ALE604 size: 10.91 TiB
    serial: <filter>
  ID-7: /dev/sdd type: USB vendor: HGST (Hitachi) model: HUH721212ALE604 size: 10.91 TiB
    serial: <filter>
Partition:
  ID-1: / size: 136.45 GiB used: 17.69 GiB (13.0%) fs: ext4 dev: /dev/nvme2n1p2
  ID-2: /boot size: 445.9 MiB used: 245.6 MiB (55.1%) fs: ext2 dev: /dev/nvme2n1p1
  ID-3: /boot/efi size: 96 MiB used: 31.1 MiB (32.4%) fs: vfat dev: /dev/nvme1n1p1
  ID-4: /home size: 1.43 TiB used: 1.03 TiB (72.1%) fs: ext4 dev: /dev/nvme2n1p4
Swap:
  ID-1: swap-1 type: partition size: 238.42 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme2n1p3
  ID-2: swap-2 type: partition size: 391.43 GiB used: 0 KiB (0.0%) priority: -3
    dev: /dev/nvme0n1p6
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: nvidia temp: 38 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
  Packages: 2540 apt: 2531 flatpak: 9
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com vera main upstream import backport
    2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/opera-stable.list
    1: deb https: //deb.opera.com/opera-stable/ stable non-free
  Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
    1: deb [arch=amd64] https: //repo.skype.com/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/teamviewer.list
    1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https: //linux.teamviewer.com/deb stable main
Info:
  Processes: 607 Uptime: 3m Memory: 125.7 GiB used: 5.96 GiB (4.7%) Init: systemd v: 249
  runlevel: 5 Compilers: gcc: 11.3.0 alt: 11/12 Client

[AndyMH]

I have resized my / and /home partitions several times without issue. Still wise to have a backup just in case. You need to run gparted booting from your mint install stick because to make changes you have to unmount the partition and you cannot unmount / booting normally.

A 256GB swap partition is just a little OTT.

[DanR]

The multiple running codes easily can grab more memory than the RAM size. In Windows for example sometimes the swap file gets to 300 GB, so 256GB for Linux is good safety precaution.

What is more dangerous to deal with the /boot or / (root) ?

By the way despite i took the strictest route not to install anything on Mint unless it is totally necessary (because Linux can be broken easily and you will spend ages to repair it and at the end will too often fail. You can install 1000 apps in Android with no single problem for years, while just couple will kill Ubuntu and seems Mint too) i still somehow see the whole bunch of kernels in the boot. Four kernels 5.15.* and three 5.19.* (!!!)
The oldest one is the only in use and never ones are also there unused. How the heck they got there?

[AndyMH]

The multiple running codes easily can grab more memory than the RAM size. In Windows for example sometimes the swap file gets to 300 GB, so 256GB for Linux is good safety precaution.

Linux is NOT windows. Your swap partition is approx 254GB too large. A default install uses a 2GB swap file, nothing to stop you having a swap partition but the vast majority of users are quite happy with a small swap file.

What is more dangerous to deal with the /boot or / (root) ?

Both, but I've never had a problem moving / or /home around with gparted, just make sure you have a backup, just in case. You don't need a /boot partition and have created a potential problem for yourself. /boot is where your kernels live, fill it up... You can use the mint update manager to remove old kernels. Keep the current kernel and one previous.

because Linux can be broken easily and you will spend ages to repair it and at the end will too often fail

Depends on the user! Having said if you want to "look under the hood" breaking your system is one way of learning and we have all done it. That is why using timeshift is essential.

[DanR]

I followed Chris Titus and others on the Youtube recommendations for "proper install". Proper or not all these installs broke within months . Even more, some recommended to have Ext2 not Ext4 for the /boot for reliability, and as you can see i followed even such small details. Somehow i missed the control and the boot size came out only 0.5GB while in another my Linux OS it is 10GB. Of course this is excessive given that Linux installation will be broken well before it will be even 20% full, so unreliable and vulnerable they are, and Ubuntu desktop is currently lying in total $@%t, i agree here with Chris. By the way he recommended Mint due to Timeshift (last one is so non-user-friendly and badly made that it chose my 10GB /boot partition from the other OS to store the timeshifts, of course failed because too small size for that and then was unable to remove the pieces of its own junk from it )

As to the swap, for most users indeed it is enough to have it small. But for my tasks small is like 256 or at least 128GB minimum as i run sometimes downsized versions of supercomputer tasks where terabytes RAM and petabytes storage are a norm. And may have several of them loaded, in this case after taking all RAM they go to the swap. Swap is the same concept in Linux and Windows, while implementations could be of course different.

Here are my kernels. As i said confusing is that active is the almost the oldest 5.15 kernel, and in this case how i have to proceed ? Delete all newer ones??? 5.15.0-72, 5.15.0-73, all 5.19.* ????

[AndyMH]

You only have two kernels installed, the one marked active and the other marked installed. Why 5.15.0-56 is showing active and not 5.15.0-72, I have no idea, when you install a kernel update it will automatically use it at the next boot. Maybe because you ran out of space in /boot since it is only 500MB (my boot folder is 600MB used with two kernels installed)?

Do not trust everything you read on the web, some is just plain wrong, others well out of date. For example ext4 has been around since 2006 and ext2 dates back to the late '90's.

Of course this is excessive given that Linux installation will be broken well before it will be even 20% full, so unreliable and vulnerable they are, and Ubuntu desktop is currently lying in total $@%t, i agree here with Chris. By the way he recommended Mint due to Timeshift (last one is so non-user-friendly and badly made that it chose my 10GB /boot partition from the other OS to store the timeshifts, of course failed because too small size for that and then was unable to remove the pieces of its own junk from it

I suggest you change your attitude or go back to windows. The problem is with you not the operating system. Continue with that attitude and you will rapidly run out of people on this forum willing to help you, including me.

[DanR]

To be clear, i like Mint so far despite some initial problems, it was the Timeshift i criticized for not being user friendly and not smart enough. It has even more problems. Which is of course partially excusable because this is kind of new in Linux. Constructive critics by the way is healthy and users have to report more critics and suggestions for improvement. The most critics comes to desktop Ubuntu, the quasi-free OS, but today only lazy do not criticize it. "Quasi" because it will suck your time and/or support funds like a Godzilla. I lost one month in forums with it during last year and finally abandoned it. Server's Ubuntu fits everyone ok.

[Pulegium]

Welp , I guess it's me who is misunderstanding something about their system .
I have a 1GB /Boot partition which currently contains 6 kernels .
According to the Disks app /Boot/efi is 1.2% full .
According to Gparted 11.97 MiB of the /Boot/efi partition is used .
When I look in File system / Boot folder properties it shows 314 items, totaling 690.3 MB .

[linux-rox]

Do not know how hell this happened during installation.

One thing I will tell you: the installer didn't do it. First, the installer only creates a boot partition for an encrypted system. Second, when it does, the LM21 installer creates a boot partition = 1.67 GB. Personally, I suspect user error. Anyway, yes, 500 MB is too small. You might as well take a chance on increasing it. That's what I would do. Well, I wouldn't be in this spot, but if I were, that's what I would do.

By the way, /home at 87.4% full isn't a good idea either. You might want to offload or archive enough stuff to get it below 80%.

[DanR]

linux-rox, thanks for suggestion, yes, the error during install was possible.

But i incline not to resize the boot partition because I afraid very much to loose my current Mint installation and will probably install another Mint in the separate harddrive where my Ubuntu currently is to overwrite it just to have TeamViewer there which fails to install in current Mint. Then i will move my stuff there if all will be as i want it.

("Afraid" because somehow due possible another mistake or not i got very nice feature not seen in my Ubuntu installations when Mint treats my Windows exe files as its own, so i click on them and they just run absolutely same way with all GUI and OpenGL features working like charm as if they were compiled in Linux. I installed Wine of course, but hell knows was it done right way or not, good things are that after install it behaves totally invisible but all things just work)

87% in /home is changing wildly every few days. It could be 87% one today and next day will be 10%. Or you worry about faster wearing out of NVMe ?

So how do you recommend to install Mint right way? Will i damage my multi-boot if overwrite Ubuntu ?

[AndyMH]

Welp , I guess it's me who is misunderstanding something about their system .
I have a 1GB /Boot partition which currently contains 6 kernels .
According to the Disks app /Boot/efi is 1.2% full .
According to Gparted 11.97 MiB of the /Boot/efi partition is used .
When I look in File system / Boot folder properties it shows 314 items, totaling 690.3 MB .

There are two partitions:

• your 1GB /boot partition which contains your linux kernels and

• your EFI partition which mounts at /boot/efi. This contains the bootloader files.

Looking at properties in file manager show the total usage for both your boot and EFI partitions.

In a normal install /boot is just another folder in /.

[linux-rox]

So how do you recommend to install Mint right way?

Sorry, that's a very complex question. One point of advice: simple generally is better than clever. You're trying too hard to be clever.

Will i damage my multi-boot if overwrite Ubuntu ?

Managing multiple boot loaders is always a bit complicated. Main thing (imho) is to make sure the main system has control of Grub. Sometimes you have to reinstall Grub to achieve this. Learn how to install Grub manually, rather than rely on the Boot Repair app.

[DanR]

Today my LM installation broke with no reason at all, i just found that it does react on mouse with terrible delays and stutter, and MPI does not work. Now this topic has already different sense: how completely remove LM and re-install fresh and on this road not to destroy the current triple-boot Windows - Ubuntu - Mint? I do not believe anyone will fix it, i already wasted a lot of time with Ubuntu.

My Ubuntu is also broken with the same symptoms. As LM and Ubuntu are cousins, they seems have same vulnerabilities. Then i will also substitute Ubuntu with something else, Fedora or so.

[linux-rox]

... broke with no reason at all

Funny, I don't have these problems. Indeed, most people don't. Changing cars won't help if you don't pay attention while you're driving.
Conversely, if you start paying attention, that's what will have solved your problem, not changing cars. Good luck.

[DanR]

Thanks for attempt.

Chris Titus said something like this - "you eventually will break your Linux OS, in 6 month or later but it will 100% happen depending on use. Specifically with Ubuntu. And no one will be able to help you. With LM TimeShift you may succeed to recover it. But i personally do not use any of them or anything Debian"

[JerryF]

Thanks for attempt.

Chris Titus said something like this - "you eventually will break your Linux OS, in 6 month or later but it will 100% happen depending on use. Specifically with Ubuntu. And no one will be able to help you. With LM TimeShift you may succeed to recover it. But i personally do not use any of them or anything Debian"

I think you're putting too much faith in Chris Titus. I used to follow him, but not anymore. He is only one guy out of thousands with opinions regarding Linux.

He has some good things to say, but for him to say that "you eventually will break your Linux OS, in 6 month or later but it will 100% happen depending on use..." is ridiculous. I, and I'm sure many others here on the forums, have been running Ubuntu-based distros without breaking the OS.