-
-
Notifications
You must be signed in to change notification settings - Fork 16
grml2usb: No space left on device is confusing #93
Copy link
Copy link
Open
Description
Just tried to install a Grml ISO to my USB device for booting and received:
at 2026-02-12 15:50:29 +01:00 ❯ sudo grml2usb --fat16 /srv/isos/grml-full-daily20260212build616unstable-amd64.iso /dev/sdb1
Executing grml2usb version ***UNKNOWN***
Choosing syslinux as bootloader
Using syslinux as bootloader
Checking for boot flag
Are you sure you want to format the specified partition with fat16? y/N y
Note: you can skip this question using the option --force
Formating partition with fat16 filesystem
mkfs.fat 4.2 (2021-01-31)
Using ISO /srv/isos/grml-full-daily20260212build616unstable-amd64.iso
Identified grml flavour "grml-full-amd64".
Copying files. This might take a while....
rsync: [receiver] write failed on "/tmp/grml2usbgs8fh9lq/boot/grmlfullamd64/initrd.img": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(381) [receiver=3.2.7]
rsync: [sender] write error: Broken pipe (32)
Fatal: could not install /tmp/grml2usba94qcq0o/boot/grmlfullamd64
Cleaning up before exiting...
I was confused:
❯ df -h /tmp
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg0--tranquility-rootfs 20G 17G 2,1G 89% /
It turned out that the destination device was the problem
❯ sudo parted /dev/sdb p
Model: Generic MassStorageClass (scsi)
Disk /dev/sdb: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 1000MB 999MB primary fat16 boot, lba
Maybe we can check the free space before trying to write and warn the user?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels