Linux

57549 readers

930 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

[SOLVED] is this not enough boot space on debian 13? (lemmy.ml)

submitted 6 days ago* (last edited 6 days ago) by arsus5478@lemmy.ml to c/linux@lemmy.ml

12 comments fedilink hide all child comments

apparently my problem is I cannot update initramfs:

update-initramfs: Generating /boot/initrd.img-6.12.41+deb13-amd64 zstd: error 70 : Write error : cannot write block : No space left on device

After checking KDE Partition Manager for /boot and /boot/efi both have free space left:

/boot size: 488 MiB

/boot used: 396.26 MiB

/boot/efi size: 512 MiB

/boot/efi used: 10.52 MiB

dpkg -l | grep linux-image | awk '{print$2}' shows:

linux-image-6.1.0-37-amd64

linux-image-6.1.0-38-amd64

linux-image-6.12.41+deb13-amd64

linux-image-amd64

I am now using debian 13 on linux-image-6.1.0-38-amd64 because linux-image-6.12.41+deb13-amd64 won't load from grub2. I don't want to get rid of linux-image-6.1.0-37-amd64 till I solve this issue

you are viewing a single comment's thread
view the rest of the comments

[–] arsus5478@lemmy.ml 1 points 6 days ago (1 children)

or offline partition shrinking, moving after a data backup if you have personal files you care about

what you are saying is: copy all your data to another drive, expand the boot partition shrinking the main storage drive and then copying back?

[–] jrgd@lemmy.zip 1 points 6 days ago (1 children)

More or less yes, minus the copying files back if the operation was successful. You must be careful shrinking partitions as it is very easy to destroy them, and I'd have to guess the partition layout looks vaguely (EFI System Partition (/boot/efi), Boot (/boot), Root (/), ...), which would require shrink and move of the partition before or after /boot. If you're unfamiliar with shrinking a partition, a bit of reading into how it is done for your filesystem will be required. Different setups, ext4, btrfs, lvm, LUKS, etc. will have different requirements.

[–] FrostyPolicy@suppo.fi 3 points 6 days ago* (last edited 6 days ago) (2 children)

Use Gparted boot disk. It's a nice GUI program. It can resize partitions on the fly with data on them. It will move data within a partition if needed. I have successfully used it on XFS and BTRFS, YMMV. The usual advice of backup anything important is valid.

[–] frongt@lemmy.zip 1 points 6 days ago

Although it's a bit dated, so I don't think it supports luks in the GUI. You might have to use it as a visual reference and do it via the command line.

[–] arsus5478@lemmy.ml 1 points 6 days ago (1 children)

is gparted better than KDE partition manager? or gnome's?

[–] FrostyPolicy@suppo.fi 1 points 6 days ago

Haven't used those but probably pretty similar.