How to grow LVM ext2 (UEFI) boot partition/dev/sda1 ubuntu15.10 standalone install

гm в complete newb when it ты ешь to Linux схвати в whole, currently taking в Linux-101 class... so I decided to dive into it and rid my laptop of Вин-8 ;-)

After much trouble with BIOS configurations,

I was able to clean install Ubuntu 15.10 (не other ВЫ present in the Ард Дриве) and decided to использовал the LVM partition option because it was supposed to be easier to manage partitions for future growth, надбавку the process was automated by the installer.

Everything working great until I was trying to install the latest security update перечитайте for Ubuntu, and received an ошибка message advising that my boot partition was almost full and that I could run "вспотел apt-get clean" to free up some space, but that did not work.

I have found in this and other форумы many answered questions that пахал very сходный to минировал but none пахал specifically addressing в ext2 LVM UEFI partition mounted at/boot. And at this point гm really confused about what is the correct way to address this issue.

I suspect it в мае boil down to purging the contents of/boot leaving only the newest kernel and last known working kernel, but I have не Разрабатывает how to identify the last working kernel from the newest one.

  • Should I try to несоздавал the size of/dev/sda1 mounted at/boot?

(I believe is at maximum size according to Gparted) (231MiB max - 155Mib used)

  • Should I try to purge the contents of/boot? and if so, what is the correct way to do that?

(I believe the following info май be helpful)

oscc@oscc-X551MA:~ $ ls/boot

abi-4.2.0-16-generic lost+found

abi-4.2.0-21-generic memtest86 +. bin

abi-4.2.0-22-generic memtest86 +. elf

config-4.2.0-16-generic memtest86 + _ multiboot.bin

config-4.2.0-21-generic System.map-4.2.0-16-generic

config-4.2.0-22-generic System.map-4.2.0-21-generic

grub System.map-4.2.0-22-generic

initrd.img-4.2.0-16-generic vmlinuz-4.2.0-16-generic

initrd.img-4.2.0-21-generic vmlinuz-4.2.0-21-generic

initrd.img-4.2.0-22-generic vmlinuz-4.2.0-22-generic

oscc@oscc-X551MA:~ $ uname-r

4.2.0-22-generic

oscc@oscc-X551MA:~ $ uname - в

Linux oscc-X551MA 4.2.0-22-generic #27-Ubuntu SMP Ту Дек 17 22:57:08 всеобщее скоординированное время 2015 x86_64 x86_64 x86_64 GNU/Linux

  • How хан this problem be avoided in the future?
1
задан 6 January 2016 в 07:03

0 ответов

Другие вопросы по тегам:

Похожие вопросы: