Why the boot partition is full?
When doing automatic or manual updates, i gets a error "boot partition full; is necessary at least xxx mb of space.".
I installed UBUNTU from zero on a empty SSD 500Gb disk and use the default values for partitions. Why the system requires more space for upgrades when this disk has more than 370Gb free? Why the system reserved so few space knwing it will e necessarin nar future updates? I can increase space at boot partition without reinstalling all?
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
"This is probably where the 1GB recommendation mentioned seems to address. A few hundred extra MB given to /boot may avoid many problems."
Revision history for this message
|
#2 |
For diagnostic purposes, what is the output of the commands (to be executed in a terminal window)
uname -a
lsb_release -crid
df -h | grep -e 'boot' -e '/$'
ls -l /boot
Revision history for this message
|
#3 |
The answers to these commands are:
jubeda@
uname: operando extra «a»
Pruebe 'uname --help' para más información.
jubeda@
Linux Enterprise 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
jubeda@
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy
jubeda@
rpool/ROOT/
bpool/BOOT/
/dev/sdb1 511M 7,1M 504M 2% /boot/efi
jubeda@
total 100530
-rw-r--r-- 1 root root 270051 jun 21 16:38 config-
drwxr-xr-x 3 root root 4096 ene 1 1970 efi
drwxr-xr-x 4 root root 4096 jul 13 08:46 grub
lrwxrwxrwx 1 root root 28 jul 6 16:50 initrd.img -> initrd.
-rw-r--r-- 1 root root 88171292 jul 7 09:54 initrd.
lrwxrwxrwx 1 root root 28 jul 6 16:43 initrd.img.old -> initrd.
-rw-r--r-- 1 root root 182800 feb 6 2022 memtest86+.bin
-rw-r--r-- 1 root root 184476 feb 6 2022 memtest86+.elf
-rw-r--r-- 1 root root 184980 feb 6 2022 memtest86+
-rw------- 1 root root 6438424 jun 21 16:38 System.
lrwxrwxrwx 1 root root 25 jul 5 06:53 vmlinuz -> vmlinuz-
-rw------- 1 root root 12220712 jun 21 16:43 vmlinuz-
lrwxrwxrwx 1 root root 25 jul 5 06:53 vmlinuz.old -> vmlinuz-
jubeda@
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
_______
De: <email address hidden> <email address hidden> en nombre de Manfred Hampl <email address hidden>
Enviado: viernes, 14 de julio de 2023 14:30
Para: <email address hidden> <email address hidden>
Asunto: Re: [Question #707295]: Why the boot partition is full?
Your question #707295 on initramfs-tools in Ubuntu changed:
https:/
Manfred Hampl requested more information:
For diagnostic purposes, what is the output of the commands (to be
execute in a terminal window)
uname a
lsb_release -crid
df -h | grep -e 'boot' -e '/$'
ls -l /boot
--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https:/
You received this question notification because you asked the question.
Revision history for this message
|
#4 |
bpool/BOOT/
Your /boot partition has been allocated in a far too small size.
Nowadays at least one GB is recommended, but you have just a quarter of that.
("... and use the default values for partitions") How and when did you install that system initially? I am not aware of any installer that recommends that size.
You seem to be using ZFS, what is the output of
zpool list
Revision history for this message
|
#5 |
You can uninstall memtest to free space but yes it is tiny.
What is the output of;
df -Th
Revision history for this message
|
#6 |
The answer to the comand is:
jubeda@
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
bpool 1.88G 1.58G 301M - - 38% 84% 1.00x ONLINE -
rpool 460G 96.2G 364G - - 34% 20% 1.00x ONLINE -
jubeda@
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
_______
De: <email address hidden> <email address hidden> en nombre de Manfred Hampl <email address hidden>
Enviado: viernes, 14 de julio de 2023 17:10
Para: <email address hidden> <email address hidden>
Asunto: Re: [Question #707295]: Why the boot partition is full?
Your question #707295 on initramfs-tools in Ubuntu changed:
https:/
Status: Open => Needs information
Manfred Hampl requested more information:
bpool/BOOT/
Your /boot partition has been allocated in a far too small size.
Nowadays at least one GB is recommended, but you have just a quarter of that.
("... and use the default values for partitions") How and when did you install that system initially? I am not aware of any installer that recommends that size.
You seem to be using ZFS, what is the output of
zpool list
--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https:/
You received this question notification because you asked the question.
Revision history for this message
|
#7 |
The answer is:
jubeda@
S.ficheros Tipo Tamaño Usados Disp Uso% Montado en
tmpfs tmpfs 1,6G 2,2M 1,6G 1% /run
rpool/ROOT/
tmpfs tmpfs 7,8G 100K 7,8G 1% /dev/shm
tmpfs tmpfs 5,0M 4,0K 5,0M 1% /run/lock
rpool/USERDATA/
rpool/USERDATA/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
/dev/sdd1 ext4 458G 70G 365G 16% /home/jubeda/
/dev/md0 ext4 3,6T 1,6T 1,9T 45% /home/jubeda/
bpool/BOOT/
/dev/sdb1 vfat 511M 7,1M 504M 2% /boot/efi
tmpfs tmpfs 1,6G 1,7M 1,6G 1% /run/user/1000
jubeda@
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
_______
De: <email address hidden> <email address hidden> en nombre de actionparsnip <email address hidden>
Enviado: sábado, 15 de julio de 2023 3:30
Para: <email address hidden> <email address hidden>
Asunto: Re: [Question #707295]: Why the boot partition is full?
Your question #707295 on initramfs-tools in Ubuntu changed:
https:/
actionparsnip requested more information:
You can uninstall memtest to free space but yes it is tiny.
What is the output of;
df -Th
--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https:/
You received this question notification because you asked the question.
Revision history for this message
|
#8 |
bpool 1.88G 1.58G 301M - - 38% 84% 1.00x ONLINE -
It seems that you have reserved 1.8 GB space for the BOOT pool, but only allocated 300M for the partition.
Extending the /boot partition by the space that has already been reserved should help.
(the command might be something like "zpool online -e bpool/BOOT", but I do not have enough knowledge of the details of zfs to be sure)
Revision history for this message
|
#9 |
I have tried it, but it needs a device on the command:
jubeda@
[sudo] contraseña para jubeda:
missing device name
usage:
online [-e] <pool> <device> ...
jubeda@
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
_______
De: <email address hidden> <email address hidden> en nombre de Manfred Hampl <email address hidden>
Enviado: sábado, 15 de julio de 2023 12:10
Para: <email address hidden> <email address hidden>
Asunto: Re: [Question #707295]: Why the boot partition is full?
Your question #707295 on initramfs-tools in Ubuntu changed:
https:/
Status: Open => Answered
Manfred Hampl proposed the following answer:
bpool 1.88G 1.58G 301M - - 38% 84% 1.00x ONLINE -
It seems that you have reserved 1.8 GB space for the BOOT pool, but only allocated 300M for the partition.
Extending the /boot partition by the space that has already been reserved should help.
(the command might be something like "zpool online -e bpool/BOOT", but I
do not have enough knowledge of the details of zfs to be sure)
--
If this answers your question, please go to the following page to let us
know that it is solved:
https:/
If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https:/
You received this question notification because you asked the question.
Revision history for this message
|
#10 |
Look online for guides on how to extend the disk. It can be done live as you have used a decent disk setup.
Revision history for this message
|
#11 |
And my disk partitions are this:
[cid:2fe91131-
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
_______
De: Javier Ubeda Moret <email address hidden>
Enviado: sábado, 15 de julio de 2023 13:06
Para: <email address hidden> <email address hidden>
Asunto: RE: [Question #707295]: Why the boot partition is full?
I have tried it, but it needs a device on the command:
jubeda@
[sudo] contraseña para jubeda:
missing device name
usage:
online [-e] <pool> <device> ...
jubeda@
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
_______
De: <email address hidden> <email address hidden> en nombre de Manfred Hampl <email address hidden>
Enviado: sábado, 15 de julio de 2023 12:10
Para: <email address hidden> <email address hidden>
Asunto: Re: [Question #707295]: Why the boot partition is full?
Your question #707295 on initramfs-tools in Ubuntu changed:
https:/
Status: Open => Answered
Manfred Hampl proposed the following answer:
bpool 1.88G 1.58G 301M - - 38% 84% 1.00x ONLINE -
It seems that you have reserved 1.8 GB space for the BOOT pool, but only allocated 300M for the partition.
Extending the /boot partition by the space that has already been reserved should help.
(the command might be something like "zpool online -e bpool/BOOT", but I
do not have enough knowledge of the details of zfs to be sure)
--
If this answers your question, please go to the following page to let us
know that it is solved:
https:/
If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https:/
You received this question notification because you asked the question.
Revision history for this message
|
#12 |
What is the output of the command
sudo zpool list -v
Revision history for this message
|
#13 |
This is the output:
jubeda@
[sudo] contraseña para jubeda:
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
bpool 1.88G 1.58G 301M - - 38% 84% 1.00x ONLINE -
557d10db-06 1.88G 1.58G 301M - - 38% 84.3% - ONLINE
rpool 460G 95.6G 364G - - 34% 20% 1.00x ONLINE -
557d10db-07 460G 95.6G 364G - - 34% 20.8% - ONLINE
jubeda@
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
_______
De: <email address hidden> <email address hidden> en nombre de Manfred Hampl <email address hidden>
Enviado: sábado, 15 de julio de 2023 15:15
Para: <email address hidden> <email address hidden>
Asunto: Re: [Question #707295]: Why the boot partition is full?
Your question #707295 on initramfs-tools in Ubuntu changed:
https:/
Status: Open => Needs information
Manfred Hampl requested more information:
What is the output of the command
sudo zpool list -v
--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https:/
You received this question notification because you asked the question.
Revision history for this message
|
#14 |
What is the output of the command
sudo zfs get all bpool/BOOT/
(Remark: if you reply by e-mail, then please remove the original mail before responding. It fills your question document https:/
Revision history for this message
|
#15 |
Here the answer:
jubeda@
[sudo] contraseña para jubeda:
NAME PROPERTY VALUE SOURCE
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
jubeda@
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
Revision history for this message
|
#16 |
bpool/BOOT/
It seems that a lot of backup copies (snapshots) have been created which fill up the disk and leave not enough space for the "real" data.
What is the output that you receive for the command
sudo zfs list -t snapshot
Revision history for this message
|
#17 |
Your are right; too many copies:
jubeda@
[sudo] contraseña para jubeda:
NAME USED AVAIL REFER MOUNTPOINT
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
bpool/BOOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/ROOT/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
rpool/USERDATA/
jubeda@
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
_______
De: <email address hidden> <email address hidden> en nombre de Manfred Hampl <email address hidden>
Enviado: sábado, 15 de julio de 2023 23:10
Para: <email address hidden> <email address hidden>
Asunto: Re: [Question #707295]: Why the boot partition is full?
Your question #707295 on initramfs-tools in Ubuntu changed:
https:/
Status: Open => Needs information
Manfred Hampl requested more information:
bpool/BOOT/
It seems that a lot of backup copies (snapshots) have been created which
fill up the disk and leave not enough space for the "real" data.
What is the output that you receive for the command
sudo zfs list -t snapshot
--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https:/
You received this question notification because you asked the question.
Revision history for this message
|
#18 |
I recommend that you delete old snapshots.
Due to the fact that I do not use zfs myself, I cannot give a command for this. Please do a web search yourself.
Potential search terms: zfs delete snapshot, zfs destroy, ...
Revision history for this message
|
#19 |
I searched information and used zfs destroy for deleting all snapshoots.
After this, updates don't works and gives me new error (not as the previous):
jubeda@
[sudo] contraseña para jubeda:
Obj:1 https:/
Obj:2 https:/
Obj:3 https:/
Obj:4 http://
Obj:5 https:/
Obj:6 http://
Obj:7 http://
Obj:8 https:/
Des:9 http://
Descargados 108 kB en 2s (54,2 kB/s)
Leyendo lista de paquetes... ¡Error!
E: flAbsPath on /var/lib/
E: No pude abrir el fichero - open (2: No existe el archivo o el directorio)
E: Problem opening
E: No se pudieron analizar o abrir las listas de paquetes o el archivo de estado.
jubeda@
If you don't understand spanish, it says: "file don't exists" for the /var/lib/
I think the previous errors corrupted the update files. I will try to rebuild it and report.
some idea?
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
Revision history for this message
|
#20 |
After some trys....i see the path /var/lib/dpkg was not in system and, of course, the "status" file within it, was not too.
jubeda@Enterprise:$ sudo mkdir /var/lib/dpkg
jubeda@
jubeda@
jubeda@
This creates the path and file that update don't find.
After this, "sudo apt update" and "sudo apt upgrade" don't gives me error.
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
_______
De: <email address hidden> <email address hidden> en nombre de Francisco Javier Ubeda Moret <email address hidden>
Enviado: domingo, 16 de julio de 2023 10:05
Para: <email address hidden> <email address hidden>
Asunto: Re: [Question #707295]: Why the boot partition is full?
Your question #707295 on initramfs-tools in Ubuntu changed:
https:/
Status: Answered => Open
You are still having a problem:
I searched information and used zfs destroy for deleting all snapshoots.
After this, updates don't works and gives me new error (not as the
previous):
jubeda@
[sudo] contraseña para jubeda:
Obj:1 https:/
Obj:2 https:/
Obj:3 https:/
Obj:4 http://
Obj:5 https:/
Obj:6 http://
Obj:7 http://
Obj:8 https:/
Des:9 http://
Descargados 108 kB en 2s (54,2 kB/s)
Leyendo lista de paquetes... ¡Error!
E: flAbsPath on /var/lib/
E: No pude abrir el fichero - open (2: No existe el archivo o el directorio)
E: Problem opening
E: No se pudieron analizar o abrir las listas de paquetes o el archivo de estado.
jubeda@
If you don't understand spanish, it says: "file don't exists" for the
/var/lib/
I think the previous errors corrupted the update files. I will try to
rebuild it and report.
some idea?
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
--
You received this question notification because you asked the question.
Revision history for this message
|
#21 |
On previous messages, i reported that "sudo apt update" and "sudo apt-upgrade" don´t gave me errors.
"sudo apt-get update" and "sudo apt-get upgrade" works ok too.
But all this is working at terminal; the automated upgrade from desktop hangs when y try it and i cannot see what is the problem.
[cid:9ee33b2c-
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
Revision history for this message
|
#22 |
Finally all working ok:
The problem was that the path /var/lib/
Corrected creting it using:
cd /var/lib/dpkg
sudo mkdir updates
All ok now. Problems with space while updating are corrected.
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
_______
De: Javier Ubeda Moret <email address hidden>
Enviado: domingo, 16 de julio de 2023 10:34
Para: <email address hidden> <email address hidden>
Asunto: RE: [Question #707295]: Why the boot partition is full?
On previous messages, i reported that "sudo apt update" and "sudo apt-upgrade" don´t gave me errors.
"sudo apt-get update" and "sudo apt-get upgrade" works ok too.
But all this is working at terminal; the automated upgrade from desktop hangs when y try it and i cannot see what is the problem.
[cid:9ee33b2c-
-------
Francisco Javier Úbeda Moret
Urbanización la Torrecilla, chalet 1
47250 Mojados, Valladolid (España)
email: <email address hidden>
Revision history for this message
|
#23 |
Attaching an image to the mail does not work, nobody can see it.
If you want to show a screenshot or other image, then you must upload it to some image hosting service (e.g. imgur.com or similar) and paste the link into a comment in your question document.
Can you help with this problem?
Provide an answer of your own, or ask Francisco Javier Ubeda Moret for more information if necessary.