Ubuntu Boot Issues
-
@gjacobse said in Linux system maintenance; /boot nearly full:
Running that - manage to not be a member of the
sudo fileSee you can run visudo to add, but still get same error. this is after signing out and back in.
How did you edit that file if you were not in that file?
-
Also, the sudoers file is not an appropriate place to store who is and who is not granted sudo access.
-
@scottalanmiller said in Linux system maintenance; /boot nearly full:
Also, the sudoers file is not an appropriate place to store who is and who is not granted sudo access.
please detail. It's easy enough to revert this file back to original and do 'correctly'.
-
I did all the auto removes and it still did not remove.
From my Googling of the issue, it was a common problem.
-
@gjacobse said in Linux system maintenance; /boot nearly full:
@scottalanmiller said in Linux system maintenance; /boot nearly full:
Also, the sudoers file is not an appropriate place to store who is and who is not granted sudo access.
please detail. It's easy enough to revert this file back to original and do 'correctly'.
The proper way to handle this is to have sudoers tell which group(s) are the one with access. The best group for this is the wheel group as that has been the admin group for UNIX since the beginning of time (IT time, at least.) Then you add yourself to the proper group. The sudoers file itself should not be a hodge podge of access permissions.
-
@BRRABill said in Linux system maintenance; /boot nearly full:
I did all the auto removes and it still did not remove.
From my Googling of the issue, it was a common problem.
Just ran into that same problem. Still showing 98% used.
-
@gjacobse said in Linux system maintenance; /boot nearly full:
@scottalanmiller said in Linux system maintenance; /boot nearly full:
Also, the sudoers file is not an appropriate place to store who is and who is not granted sudo access.
please detail. It's easy enough to revert this file back to original and do 'correctly'.
You should put them in /etc/sudoers.d/
Just create a file with whatever groups/users permissions for that local system.
All of the .d directories are dump directories. It makes it easier to copy configs between systems.
-
@gjacobse said:
@BRRABill said in Linux system maintenance; /boot nearly full:
I did all the auto removes and it still did not remove.
From my Googling of the issue, it was a common problem.
Just ran into that same problem. Still showing 98% used.
I have found with newer versions of Ubuntu (16.04 and 16.10) that "apt-get autoremove" won't remove kernels, but "apt autoremove" will.
-
@brianlittlejohn said in Linux system maintenance; /boot nearly full:
@gjacobse said:
@BRRABill said in Linux system maintenance; /boot nearly full:
I did all the auto removes and it still did not remove.
From my Googling of the issue, it was a common problem.
Just ran into that same problem. Still showing 98% used.
I have found with newer versions of Ubuntu (16.04 and 16.10) that "apt-get autoremove" won't remove kernels, but "apt autoremove" will.
I tried everything online, and nothing worked. I had to remove them manually.
Actually, I think it was so full, it wouldn't run anything.
It was a while ago...
-
Does this seem correct?
Open terminal and check your current kernel:
uname -r
DO NOT REMOVE THIS KERNEL!Next, type the command below to view/list all installed kernels on your system.
dpkg --list | grep linux-image
Find all the kernels that lower than your current kernel. When you know which kernel to remove, continue below to remove it. Run the commands below to remove the kernel you selected.sudo apt-get purge linux-image-x.x.x.x-generic
Finally, run the commands below to update grub2sudo update-grub2
Reboot your system.
-
@gjacobse said in Linux system maintenance; /boot nearly full:
Does this seem correct?
Open terminal and check your current kernel:
uname -r
DO NOT REMOVE THIS KERNEL!Next, type the command below to view/list all installed kernels on your system.
dpkg --list | grep linux-image
Find all the kernels that lower than your current kernel. When you know which kernel to remove, continue below to remove it. Run the commands below to remove the kernel you selected.sudo apt-get purge linux-image-x.x.x.x-generic
Finally, run the commands below to update grub2sudo update-grub2
Reboot your system.
I'm not sure if that worked for me either.
I had to manually remove them.
I did not update grub
-
Any attempt to remove old packages results in:
~$ sudo apt-get purge linux-image-3.13.0-48-generic Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: linux-image-extra-3.13.0-105-generic : Depends: linux-image-3.13.0-105-generic but it is not going to be installed linux-image-generic : Depends: linux-image-3.13.0-105-generic but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). ~~~ -
Have you tried the suggestion yet?
apt-get -f install -
@scottalanmiller said in Linux system maintenance; /boot nearly full:
Have you tried the suggestion yet?
apt-get -f install~$ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: linux-image-3.13.0-105-generic Suggested packages: fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools The following NEW packages will be installed: linux-image-3.13.0-105-generic 0 upgraded, 1 newly installed, 0 to remove and 18 not upgraded. 11 not fully installed or removed. Need to get 0 B/15.3 MB of archives. After this operation, 43.2 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 648954 files and directories currently installed.) Preparing to unpack .../linux-image-3.13.0-105-generic_3.13.0-105.152_amd64.deb ... Done. Unpacking linux-image-3.13.0-105-generic (3.13.0-105.152) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-105-generic_3.13.0-105.152_amd64.deb (--unpack): cannot copy extracted data for './boot/System.map-3.13.0-105-generic' to '/boot/System.map-3.13.0-105-generic.dpkg-new': failed to write (No space left on device) No apport report written because the error message indicates a disk full error dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-105-generic /boot/vmlinuz-3.13.0-105-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-105-generic /boot/vmlinuz-3.13.0-105-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.13.0-105-generic_3.13.0-105.152_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)Yes, and the above is the result.
-
Ah, the issue appears to be that you allowed the disk to fill to a point that the automated tools can no longer manage it.
-
cd into /boot and give us an ls
-
i:/boot$ ls abi-3.13.0-100-generic abi-3.5.0-31-generic config-3.13.0-96-generic memtest86+.bin vmlinuz-3.13.0-100-generic abi-3.13.0-101-generic abi-3.5.0-32-generic config-3.13.0-98-generic memtest86+.elf vmlinuz-3.13.0-101-generic abi-3.13.0-103-generic abi-3.5.0-34-generic grub memtest86+_multiboot.bin vmlinuz-3.13.0-103-generic abi-3.13.0-62-generic abi-3.5.0-37-generic initrd.img-3.13.0-100-generic System.map-3.13.0-100-generic vmlinuz-3.13.0-62-generic abi-3.13.0-95-generic abi-3.5.0-39-generic initrd.img-3.13.0-101-generic System.map-3.13.0-101-generic vmlinuz-3.13.0-95-generic abi-3.13.0-96-generic abi-3.5.0-54-generic initrd.img-3.13.0-103-generic System.map-3.13.0-103-generic vmlinuz-3.13.0-96-generic abi-3.13.0-98-generic config-3.13.0-100-generic initrd.img-3.13.0-62-generic System.map-3.13.0-44-generic vmlinuz-3.13.0-98-generic abi-3.5.0-23-generic config-3.13.0-101-generic initrd.img-3.13.0-95-generic System.map-3.13.0-62-generic abi-3.5.0-27-generic config-3.13.0-103-generic initrd.img-3.13.0-96-generic System.map-3.13.0-95-generic abi-3.5.0-28-generic config-3.13.0-62-generic initrd.img-3.13.0-98-generic System.map-3.13.0-96-generic abi-3.5.0-30-generic config-3.13.0-95-generic lost+found System.map-3.13.0-98-generic -
Should be save to delete all of these. Copy them into /tmp if you are worried. Double check as you go, but these all seem to be unneeded.
abi-3.5.0-31-generic config-3.13.0-96-generic abi-3.5.0-32-generic config-3.13.0-98-generic abi-3.5.0-34-generic abi-3.13.0-62-generic abi-3.5.0-37-generic vmlinuz-3.13.0-62-generic abi-3.13.0-95-generic abi-3.5.0-39-generic vmlinuz-3.13.0-95-generic abi-3.13.0-96-generic abi-3.5.0-54-generic vmlinuz-3.13.0-96-generic abi-3.13.0-98-generic initrd.img-3.13.0-62-generic System.map-3.13.0-44-generic vmlinuz-3.13.0-98-generic abi-3.5.0-23-generic initrd.img-3.13.0-95-generic System.map-3.13.0-62-generic abi-3.5.0-27-generic initrd.img-3.13.0-96-generic System.map-3.13.0-95-generic abi-3.5.0-28-generic config-3.13.0-62-generic initrd.img-3.13.0-98-generic System.map-3.13.0-96-generic abi-3.5.0-30-generic config-3.13.0-95-generic System.map-3.13.0-98-generic -
-
@BRRABill said in Linux system maintenance; /boot nearly full:
Yep, exact issue I had.
YOU LET BOOT GET FULL. Lol. That's another feature, right @scottalanmiller
Not to make an excuse - but as someone who doesn't know much and is trying to learn Linux - I am not sure it can be said that I allowed it to happen.
Therefore - I blame it on the fain.
