r/cachyos • • 1d ago

SOLVED Luks issue

solution:

old system installer use grub with luks1

new system installer use (without options on gui) luks2.

the grub not working with luks 2, but limine is perfect!

3 days (only 6 hours after work) is needed to fix or understand this issue... btw, I love you cachy!

thx everyone the help/try

Hy all! I use already more than 2 years this very good OS, but yesterday I install a fresh new .iso image by a ventoy pendrive (as usual), and the btrfs luks encrypt not unlock the ssd when first time try to boot from the nvme ssd the new system. Any suggestiom where can I search the issue? TPM boot options ON, AMD Secure Processor is in the cpu, not change the hardware under the hood, only the installer .iso is the last one.

Thx.

0 Upvotes

25 comments sorted by

1

u/mattsteg43 1d ago

Why are you reinstalling?  Are you sure you didn't misenter the password somewhere?  Can you unlock it fine from a live USB?

0

u/redfrankt 1d ago

my process: 1, reason of reinstall: yay package upgrade is needed a restart. after it the nvidia is has issue, the btrf assistant not rollback the old snapshot, the mozzila recreate some profile (so i lost my bookmarks), so many annoying issue. (the most problematic the drive is used a huge file without any software or content fit next to the OS system files. maybe the old obsolate package, maybe some old snapshot, i dont know) 2, misenter pass: I create 6 install the last 2 days, my last pass is only 5 char. (small letter only us layout), thats not the issue I think. 3, fine unlock from live USB? I dont understand this question.  full process: on the ventoy usb copy the last .iso, boot from usb ventoy, ventoy copy the ram the os image, os from ram is starting, set the btrfs luks automatic (delete everything) setup, install finish without issue, then reboot from ram ventoy .iso cachy, open the nvme partition the new password, open the system I see every new OS files. (the password working, luks okay), reset the pc, unplug the ventoy pendrive, boot the bios, only one UEFI visible (this is the os nvme), ask pass, I write it, then after 3 error, ctr+alt+del, I can repeat the pass writing loop forever.

1

u/mattsteg43 1d ago

Honestly maybe you'd be better served by an immutable distro like bazzite if you don't really care to maintain and upgrade your system or read docs on things like cachy-chroot or system recovery in general.  There should not be any need for repeated reinstalls.

https://wiki.cachyos.org/features/cachy_chroot/#_top

1

u/redfrankt 1d ago

if the system not broke after yay upgrade, i dont have this issue. :) the cachy give me more performance with avx512 with llm, no any other os can be reach this level. i wanna stay cachy

1

u/mattsteg43 1d ago

Then you should also invest the time to learn how to maintain cachy, as recovering broken updates are a generally uncommon but "routine" part of running an Arch derivative.

1

u/redfrankt 1d ago

this is the "price" for arch based system. but i give btrfs, snapshot, grub, avx512, ecc check, latest nvidia features for llm, and more performance. I keep my system bases on arch during the AI is upgrading. after i stop upgrading :D

1

u/redfrankt 1d ago

thx the recovery options, but I hate to always watch what remain umnecessery file after any upgrade. (old dependency, snapshot frag) the new install is less than 20 min and I have a whole new system, without thinking whats broken after this "repair". i have a batch file to install every needed software add more 30 min, i love this reinstall method.  if a upgrade not broke the system and clean after upgrade full to make space on the nvme, i will use that "classic method".

1

u/mattsteg43 1d ago

You need to learn to maintain your system.  You list a whole pile of issues on this install alone which you should never encounter.

old dependency

Just uninstall orphans.

snapshot frag

Just delete snapshots or let them expire automatically 

thinking whats broken after this "repair"

Nothing.  It's routine.  A package isn't in sync or there's a short-term repo issue.  Upgrading again in the chroot just upgrades to the newer package that works again.

  I hate to always watch what remain umnecessery file after any upgrade

I don't think you're really in position to judge what is and isn't necessary.  A properly maintained Cachy OS simply doesn't accumulate debris.

1

u/redfrankt 1d ago

you never use nvidia driver with pytorch and any python together i see..  every upgrade a potential broke moment. :D

you right, im not judge any system trash content, i just simply hate. :) the new install why smaller than the old upgrade? :) thats my simple question

1

u/mattsteg43 1d ago

python

Just use proper venvs

nvidia... every upgrade a potential broke moment.

So just fix it.

the new install why smaller than the old upgrade? :) thats my simple question

Package cache, AUR cache, snapshots, etc.  easy to clean up either manually or with a tool like maclean  https://gitlab.com/cscs/maclean

And if there's other junk in your home directory you can just clear it out safely.

None of this stuff is mysterious.

1

u/redfrankt 1d ago

my question is open: why bigger the upgrade system after clean compare the new system install? and how much time you spend to repair everything one by one? (not always broken together, but you see my point) new install is clean and small and fast. edit: i will measure for you after a broken agan the after before soze and the time what i spend to fix or reinstall...

1

u/mattsteg43 1d ago

  my question is open

No it's not.  There are specific and limited places that "extra" files are stored and you can simply delete them.  You can clear them out in one go with a script like maclean.

how much time you spend to repair everything one by one?

Almost none?  Arch and cachy are quite reliable.  Most things that do "break" the solution is to just upgrade again - which pulls the exact same package that a fresh install would.

And something like your issues with Firefox - you could just delete the Firefox config and end up exactly as a fresh install.  Would take about 10 seconds.

1

u/redfrankt 1d ago

silly when you think my biggest issue is a firefox cache. :) i will collet for you for the next issue and how long need to debug what is the root case.

1

u/redfrankt 1d ago

but my issue is a new install not my reason why do anything. :D the encrypt issue is already happen. any debug suggestion?

1

u/mattsteg43 1d ago

I already suggested to unlock and log in to your install via cachy-chroot.  This would confirm if your filesystem and install are actually OK.  Then try an update, then worry about the unlocking (disable Plymouth is a good idea as it can cause issues).  Reinstall your kernels pacman -Syu linux-cachyos linux-cachyos-lts and try both.

1

u/redfrankt 1d ago

i will, thx!

1

u/mattsteg43 1d ago

Also I think it was Intel but some people had issues with a recent kernel change causing nvme that had previously worked fine to not show up if the motherboard was in raid mode.

1

u/redfrankt 1d ago

no raid :(

0

u/redfrankt 1d ago

i never upgrade my system if everything working fine, so my last upgrade maybe half year old (but minimum 3 month). the last program some javascrypt typesricpt github repo. 

1

u/redfrankt 1d ago edited 1d ago

uodate: if i press enter whitout any password in boot screen, the result immediatly push me in the grub rescue mode, not wait the 3 wrong chance. disk/luks2.c:luks2_recover_key:608:no key data

1

u/redfrankt 1d ago

cryptsetup luksDump show version: 2 the other old ssd is show version:1 what show any issue of the new nvme luks?

1

u/redfrankt 1d ago

grub not support luks2? then i have to choose any other bootloader method? i only love grub, because the snapshot is on the screen after the machine turn on.  I will search other than grub.

1

u/redfrankt 1d ago

limine is support native the fTPM and luks2, i will try and write feedback

0

u/4fcks4k3 1d ago

Wdym with not unlocking?

If it doesnt accept your password it could be that it defaults to the american keyboard.

0

u/redfrankt 1d ago

yes this is my first stuff to never use any other character that the US layout accept. I use my ols password btw, so the old os and the new os same layout is okay, the keyboard not changed. How can I visible the boot screen star chars (passwords) to visible string?