I hit a kernel panic after the upgrade.
The fix was easy enough for me to find and correct, out of space in the efi part due to windows dual boot stuff in there too. I removed the old kernel rebuilt and I was good.
I wo der how many people hit that and were stumped.
My 2 concerns to date are
1 just a bad file manager. Its dumbed down for people and I hate it.
2 lack of support for veracrypt volumes.
13 Comments
ryannathans@aussie.zone · 1 pts · 21d
How big is your EFI partition?
LordCrom@lemmy.world · 1 pts · 21d
The default from 22.04, 457 iirc. The new kernel needed just 10 for mb to build without error.
ryannathans@aussie.zone · 1 pts · 21d
Ah yeah 24.04 upps that to minimum 1gb
jbrains@sh.itjust.works · 1 pts · 21d
I spent hours on this spread over days, because I wasn't sure about the safety of resizing partitions and I found recovery software (Clonezilla, for example) difficult to learn about. Consequently, I felt very tentative and it took me a long time to feel comfortable even trying to fix the problem.
Once I finally felt like my data was safe, fixing the problem seemed straightforward.
I still don't know how to do a bootable backup on Linux. I'm tired of being told it's easy and not being pointed a guide that shows clearly how to do it. 🤷
LordCrom@lemmy.world · 1 pts · 20d
Well, any USB will boot a Linux os, then you justcneed to mount your drive and chroot to get your original system data back. That's kinda how I fixed my out of space issue. Is yhatxwhat you're after? I can help with that
jbrains@sh.itjust.works · 1 pts · 18d
That's what I concluded. It's not a bootable backup, but it's pretty good. Here is the dilemma I encountered last time.
I used Clonezilla.
In clone mode, I'm told that it's unwise to mount the external drive, because the partitions have the same IDs as the ones on my internal drive. I'm supposed to disable my internal drive, but System76's Lemur Pro doesn't give me that option.
In image mode, I'm told to recover by restoring the image. To where, exactly? My internal drive is over half full.
🤷
So how am I actually supposed to use this?
LordCrom@lemmy.world · 1 pts · 18d
Gotcha.
First off, I thought sys76 gave lifetime support. Did you try them?
And correct, do not mount clonezilla to the host. If you used a bootable USB with clonezilla, you can use that to restore an image as well.
So let's start with this, what error do you get when booting?
What were you on version wise, and what are you truing to upgrade to.
And can you give me whatever steps you remember doing that sparked your booting problem, if any.
jbrains@sh.itjust.works · 1 pts · 17d
First, thanks. And no, I haven't tried their support yet, because the situation hadn't become urgent enough yet.
I can restore an image, but that doesn't let me test, unless I restore to yet another external drive with enough space, then chroot to it, I guess. I didn't have another 1 TB drive at hand to try.
I didn't try to boot to the clone, because I read a warning about booting with two different connected drives having the same UUID. I wouldn't use my daily drive laptop to try that out in case something serious went wrong. All I found online were vague warnings and I wasn't prepared to ignore them. Also, I know software, and I could imagine some potentially serious errors due to optimistic assumptions in software about the uniqueness of drive UUIDs.
I can't disable my laptop's internal drive through BIOS and I'm not prepared to open the machine to physically disconnect the drive.
That's where I am now. It looks like the best option to test would be to backup to an image on USB drive A, then restore to USB drive B, then boot to a live installation and chroot. I mean... OK, but that's not what I hoped for from a so-called bootable backup.
Am I missing something obvious? Am I making a clearly invalid assumption?
LordCrom@lemmy.world · 2 pts · 16d
The real problem here is that you are not trusting the backup tool you selected. You are right to be paranoid of course....I am. Testing the backups is something we all should do on a schedule.
You don't want to restore the entire image for fear it won't work, and currently have no other option to test it.
Leap of faith with your untested restore is not adviseable either.
Ugh. Either you need to find another machine with enough space to teat the restore 1st, disconnect the drive and mount,.... Don't know how you could proceed otherwise.
jbrains@sh.itjust.works · 1 pts · 16d
Thank you. Of the folks who have engaged me over the past few years trying to find an adequate backup system, you're the first to tell me that I'm indeed not missing anything and that this cannot be made to work the way I'm expecting. I find that comforting.
Now I have a way to move forward: to back up a 1 TB drive, I can partition a 2 TB drive in half, back up to an image on one, restore that image to the other, chroot, and check that that worked.
Wasteful, but workable.
Thank you.
LordCrom@lemmy.world · 1 pts · 15d
You're welcome. Like many, I dumpster dive for a lot of my equip. If you van getcyohr hands on almost any other machine with large enough drive, that would be good enough to test your clonezilla restore.
On my daily driver, I use nextcloud for document/photo sync so that I immediately have 2 copies. Then a weekly backup to external storage 1 time per week of my home folder.
Remember to test the backups every so often. Make sure you keep a copy of data offsite too(fire,theft,etc)
And its morbid, but I left instructions for my kids on how to gain access to backups in case I'm gone so they can keep pics and bids from my stash.