My SSD RAID setup just doesn't "feel" right for the following reasons:
Computer Specs:
Results of lsblk:
lsblk
Anyone want to weigh in on issues they see?
- sdb and sdc only show at 238G. These are 256G drives
256×10^9÷1024^3=238,418579102
Why are hard drives never as large as advertised?
lsblk's representation is correct. Posting text output of commands like lsblk as text or code is much more appreciated by the way.
- There are two /boot's per RAID drive. One is /boot/EFI. When I boot my device I'm presented with 6-7 options for booting. Should be just 2-3.
I'm not sure about your setup, a dm software raid should represent both disks as one to processes like update-grub, but it reads like another grub.cfg is also picked up, a screenshot or photo of the grub menu might help clarifying things. You could add GRUB_DISABLE_OS_PROBER=true to /etc/default/grub to not look for other operating systems bootloaders and run update-grub to see if that helps.
- My boot partition is full and i'm getting errors.
Which errors exactly? No it's not always obvious and there may be the cause of you other problems buried deep down there.
Your setup looks complex (dm-raid, efi and boot partitions, LVM on LUKS with nested cryptswap), are you sure do need all of this and that you want to main all of the possible breakage (distribution upgrades)? My guess is you checked all of the boxes in the installer after setting up dm-raid before, not knowing the implications and also possibly setting up encryption twice (LUKS + eCryptfs).
Instead of dm-raid you could use LVM or btrfs' RAID functionality, though I have been unable to get a working system using the desktop install media for the past few hours testing LVM and btrfs individually several times.
There is one advice I can give: You won't need more than 100MB¹ for the UEFI partition. You could create a new FAT16 partition mark it as boot and esp in gparted and copy the data from the backup of the old partition onto the new one. This will gain you 412 MB more space for the boot partition. Since 488 MB seems to be the default for all LVM setups on Ubuntu you should check why the partition got filled up, usually old kernels are removed automatically on recent releases and you can also remove them with apt autoremove.
apt autoremove fixed my /boot partition issue. Removed all the old kernels, now no more error.
GRUB_DISABLE_OS_PROBER=true and running update-grub could probably remove then but there is not much to worry about these entries.
Oct 9, 2016 at 21:02