-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suddenly "no space left on device" where EFI partition is #2767
Comments
The crucial part is
so there is no space left on those device where initrd.cgz should be copied to Nowadays /tmp/ is often on a tmpfs which is usually on RAM,
By default up to ReaR 2.6 it uses the traditional Unix/Linux In current ReaR master code (i.e. what will be released as ReaR 2.7) |
Nope. Doesn't fix it. Exact same error. I've added
Notice how |
Ah!
This is from our current GitHub master code. So where it copies to is the mountpoint of an EFI partition See in usr/share/rear/conf/default.conf You could specify e.g. 1 GiB with Alternatively you may try to reduce the size of the ReaR initrd
(see the descriptions in usr/share/rear/conf/default.conf) |
Relax-and-Recover 2.6 / 2020-06-17
Zorin OS 15.3 (bionic)
OUTPUT=USB
BACKUP=NETFS
BACKUP_URL=usb:///dev/disk/by-label/REAR-000
PC hardware, x86 compatible, UEFI
grub-install (GRUB) 2.02-2ubuntu8.21+zorin1
My system's primary (and only) HD is a Samsung EVO 500GB NVMe
I successfully perform at format:
The process fails when I try to create a rescue image:
rear -v mkrescue
The log was of no additional help:
I succeeded in the past when the destination disk was a Crucial MX500 SSD
I tried it today (with that SSD) and it failed with the "no space" error.
I re-ran the format process, tried again, same error.
I then switched to a brand new, never used WD BLUE 1TB SSD
Same error: ... no space
The text was updated successfully, but these errors were encountered: