hi! running a framework laptop and the mint installation i have on one of my usb cards is not booting, so i thought i'd try to boot into a live environment and run boot-repair on it. on the mint cinnamon 22.3 iso, i'm having trouble installing the ppa:yannubuntu/boot-repair because trying to add the apt repository is saying that "this PPA does not support noble" even though on the ubuntu site (https://launchpad.net/~yannubuntu/+archive/ubuntu/boot-repair) it clearly does. what should i do?
#struggling to boot into my mint usb
141 messages · Page 1 of 1 (latest)
Boot repair is already on the Mint ISO, don't allow it to attempt to update as ppa.launchpad.net doesn't seem to respond now
oh!! i see it! thank you!
ive not used this before - what should i expect to see or do after running it?
might i still have to resort to updating grub via mounting the drive in the live iso?
You could use it to create a summary report and post the URL here
You installed Mint to a USB drive?
i'll post the url when it's done updating/running!
i did, yes - one of these https://frame.work/ca/en/products/storage-expansion-card-2nd-gen
Framework
Ultra high speed storage, available in two capacities. With a USB 3.2 Gen 2 interface, both the 1TB (2nd Gen) and 250GB (2nd Gen) cards reach 1000 MB/s read and 800 MB/s write speeds. Both are fast enough to run apps and even boot an operating system from, and you can plug them into other computers
run lsblk -f while you're at it , in terminal, and show result. make sure terminal is wide first
or lsblk -o name,model,label,fstype,size,partuuid,mountpoint
The USB may be dead
oh dear - my live media froze LOL but it's sda1 as ext4
for real? it's fairly new too...
show full result. reboot to live or real OS if needed
if your real OS is Linux, anyway
let me pull it up on nobara
yeah, show this one.
If you want to see the boot repair summary https://dpaste.com/94GBG72MZ
ensure your modular cardreader this is firmly plugged in, and wit card in it
All I see is a NVME with Nobara/Fedora and Windows and the other drive is most likely the Mint ISO
guessing sda is the Nobara drive
it is not
anyway the report is very cluttered and i dont feel like sifting.
so show the line I put. i just edited it
yep yep, just a sec
NAME MODEL FSTYPE SIZE PARTUUID MOUNTPOINT
sda 250GB Card 232.9G
├─sda1 ext4 203.1G f0bea170-01
├─sda2 1K f0bea170-02
└─sda5 swap 29.8G f0bea170-05
zram0 swap 8G [SWAP]
nvme0n1 WD Blue SN570 1TB 931.5G
├─nvme0n1p1 vfat 100M b4918bb4-6de7-417b-acd1-5a2d12894a52 /boot/efi
├─nvme0n1p2 16M 79a725f8-0580-4db3-89e9-35e9c8d4022a
├─nvme0n1p3 ntfs 306.6G e89edb75-eaf9-46df-a18a-9aef539a73ff
├─nvme0n1p4 ntfs 746M 4703c6c8-3435-42c7-a9ae-e7d215b01bbd
├─nvme0n1p5 ext4 2G 0cbd406a-8e69-438c-9ce2-397ae8df9370 /boot
└─nvme0n1p6 btrfs 622.1G 8a599c4f-b57f-4032-a201-b11a12385e77 /home```
/dev/sda must be where Mint was
that lines up with my understanding, yes
ya model says 250 GB Card
however, there's no EFI partition on it
open up kde partition manager.
select sda
sudo parted -l
shit i dont have spectacle/screenshot program on this install
best way to fix this is either turn off the nvme port in BIOS, or unplug the card. or fix the module on a different pc with easily unpluggable other drives
boot live stick, and after having made an efi partition on the 250 gig, u run boot repair
this should be the relevant data:
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 218GB 218GB primary ext4
2 218GB 250GB 32.0GB extended lba
5 218GB 250GB 32.0GB logical linux-swap(v1) swap```
there's no efi
yeah... i wonder what happened to it ?_?
either boot thing thing in legacy mode (if framework has CSM) or redo the install or move stuff around
oh. i know what probably happened
the mint loader is lying on your source computer
wherever u made it.
SURPRISE!!!
when i installed mint on the drive, it probably put everything it needed for booting on my nvme
i wiped my nvme recently
Boot0000* Fedora HD(1,GPT,b4918bb4-6de7-417b-acd1-5a2d12894a52,0x800,0x32000)/File(\EFI\fedora\shim.efi) File(.䍒) Boot0001* Fedora HD(1,GPT,b4918bb4-6de7-417b-acd1-5a2d12894a52,0x800,0x32000)/File(\EFI\fedora\shimx64.efi) Boot0002* Windows Boot Manager HD(1,GPT,b4918bb4-6de7-417b-acd1-5a2d12894a52,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494```
those three entries, and only those three, boot from the nvme ESP currently
do you want to redo or take time to move a partition on this card?
i'd like to not lose what i have on the drive
so we can try to resize partition and stuff as necessary on the drive?
29.8G of swap?
I suggest a 200 MiB EFI System partition (fat32) at the start of this drive (250 gig drive)
is it umount /dev/sda1 to unmount?
u can just r-click in the kde ptn mgr
should have unmount option. r-click the lock icon
gotcha, unmounted
Filename Type Size Used Priority
/dev/zram0 partition 8388604 0 100```
delete the swap inside the extended partition
okie, it's unallocated
delete the extended partition
done
i should just drag it over to the end of the space?
u couild but id rather see it first, untouched
put in the 'free space before' 300 MiB
and press Tab once
then hit ok, and show pic
looks proper. now find the apply button and let it work
may take a while since over 50 MiB of data has to shift.
seems right
yes click apply
do we need to recreate the swap after?
later, make a few gigs swap partition at the very end of drive. dont need extended partition
yes, and edit that sda1 OS's fstab file
what's on sda1, Mint?
yep!
it will fail to boot if u leave the old swap UUID in there
makes sense, so just provide the fstab the new one from lsblk
so make sure to open the correct fstab.. (in /etc/ of sda1)
and change it to the new swap's UUID of new swap partition
you'll still need to do boot repair with manual options , to force a GRUB install onto this new EFI partition that hasn't yet been made, but will be
once sda1 has moved, right click the 300 MiB free space and do new partition : primary, Fat32 , label: ESP_Portable
and flag it with esp and boot flags.
best put the flags with gparted from live environment
okay! so after this moving operation finishes
- create
extendedpartition to fill the space at the end of the drive - create
linuxswappartition under thatextendedpartition - grab the uuid from
lsblk -f - edit
sda1's/etc/fstabto use that new uuid for its swap - run boot repair and use the manual options to write a new grub install into that 300mb efi patition
before any of this, make the Fat 32 one i mentioned
gotcha!
what do you mean by this?
the live boot with the boot repair tool. it should have gparted app
and in terms of flags specifically for the swap stuff, could i just copy what it has here?
oh ok - just make the partitions and its good to go as a swap
just sudo blkid and get the new UUID for the new swap
you must choose 'linux swap' as a formatting option
you may want to consider turning off the NVME in the UEFI storage/advanced settings. before booting live
so that the grub repair ONLY sees linux mint
yeah i can try that! the moving process just finished so let me create the EFI partition
ESP_Portable is one character too long for the naming field, but it's just a label so it shouldn't matter, right?
yes
and now i can make an extended linuxswap partition at the end and set the new uuid in fstab
and then restart into the live environment for the grub repair
does only root have permissions for the extended partition or does everyone?
BIOS: nvme off
liv: esp and boot flag for new esp
boot repair:advanced> grub location
i would assume only root, right?
g2g
https://dpaste.com/8GMULMFLH this is the output of boot repair, it says it was successful (also "Locked-NVram detected, please do not forget to make your UEFI firmware boot on the sda2/efi/ubuntu/grubx64.efi")
but it seems successful!! i booted without my nvme in and it went into GRUB, and although it's misnamed ("Ubuntu" instead of Linux Mint Xia whatever) it booted into the install!! thank you so mnuch @cedar smelt đź©·
and thank you @low whale as well for earlier diagnostics!!
Good to see it works again
good, if you're in mint now on sda, then check that swap is active there. swapon -s
seems to be detected at least - the command lists the correct partition with the correct size, used 0 priority -2
good.
thanks so much for all y'alls help!