Arch Linux

pixie

Member

Registered: 2024-02-28

Posts: 8

/boot is full, I'm scared of losing data when resizing

Hey there

I've been on arch for a couple weeks, and my boot partition filled up for whatever reason. So, obvious solution is to resize it, but I'm scared of losing data on my main partition...

How do I do it safely?

```
(parted) print
Model: ATA SanDisk SD8SN8U5 (scsi)
Disk /dev/sda: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size   File system  Name                  Flags
1      1049kB  538MB  537MB  fat32        EFI System Partition  boot, esp
2      538MB   512GB  512GB  ext4
```

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: /boot is full, I'm scared of losing data when resizing

I wouldn't say that's the obvious solution. What filled it up?

pixie

Member

Registered: 2024-02-28

Posts: 8

Re: /boot is full, I'm scared of losing data when resizing

I wouldn't say that's the obvious solution. What filled it up?

No idea... I've sort of avoided messing with my partitions, because I had a mildly traumatic experience at 10 trying to install Ubuntu dual boot and erasing my entire drive X(

Sorry for the dumb question, but whats the best way to figure out if theres any junk on it?

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: /boot is full, I'm scared of losing data when resizing

Start with the basics. https://man7.org/linux/man-pages/man1/ls.1.html

pixie

Member

Registered: 2024-02-28

Posts: 8

Re: /boot is full, I'm scared of losing data when resizing

Start with the basics. https://man7.org/linux/man-pages/man1/ls.1.html

I think I did the right command? It looks like initramfs-linux-fallback.img.tmp is the largest, is it safe to remove?

ls /boot -sh

4.0K EFI
4.0K grub                                 
177M initramfs-linux-fallback.img.tmp                   
138M initramfs-linux.img
56M initramfs-custom.img           
13M vmlinuz-linux
115M initramfs-linux-fallback.img

Last edited by pixie (2024-02-28 16:36:35)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: /boot is full, I'm scared of losing data when resizing

initramfs-linux.img is absolutely massive, too. What version of mkinitcpio are you running, and what's initramfs-custom.img? What's /etc/mkinitcpio.conf look like?

pixie

Member

Registered: 2024-02-28

Posts: 8

Re: /boot is full, I'm scared of losing data when resizing

initramfs-linux.img is absolutely massive, too. What version of mkinitcpio are you running, and what's initramfs-custom.img? What's /etc/mkinitcpio.conf look like?

This is the only part of the mkinitcpio.conf I edited:

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

Now that I think about it, I think the partition full errors started when I had to mess with stuff to get Hyprland working....

I'm running mkinitcpio 37.3

Also, I have no idea what the custom img is...

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,231

Re: /boot is full, I'm scared of losing data when resizing

The minimal necessity for wayland ist to set the nvidia-drm.modeset=1 kernel parameter, that does not on it's own necessitate the use of nvidia as part of the initramfs but it's considered generally a good idea if a graphical session should be started directly during boot. I don't think you can decrease the size with the nvidia modules trivially. You did remove the kms hook from mkinitcpio as well right (as reccommended in the nvidia installation instructions)? That way you can avoid a bunch of unnecessary foss drivers/firmwares getting included. You can probably remove the custom image if you don't know where it's from, and the tmp image is definitely safe to remove until you manage to run mkinitcpio without errors.

pixie

Member

Registered: 2024-02-28

Posts: 8

Re: /boot is full, I'm scared of losing data when resizing

The minimal necessity for wayland ist to set the nvidia-drm.modeset=1 kernel parameter, that does not on it's own necessitate the use of nvidia as part of the initramfs but it's considered generally a good idea if a graphical session should be started directly during boot. I don't think you can decrease the size with the nvidia modules trivially. You did remove the kms hook from mkinitcpio as well right (as reccommended in the nvidia installation instructions)? That way you can avoid a bunch of unnecessary foss drivers/firmwares getting included. You can probably remove the custom image if you don't know where it's from, and the tmp image is definitely safe to remove until you manage to run mkinitcpio without errors.

I deleted the custom image, no problems and it freed up enough space for me to do what I needed. Thank you