Hello enlightened ones! I did a fresh install of Bodhi 5.0-legacy deleting a working version 4.5. It worked fine so I did a full update. When booting up for the first time after updating, my passphrase response was "bad password" which kept me locked out of the disk. I did lots of searching and thought that maybe because I selected a 101 keyboard layout when it's really 104 that might have caused it but I see now, that probably wouldn't matter. I was about to start over when I tried the "recovery mode" boot option. Everything checked out ok and when it asked for my password I gave it a try and it logged me in! Can anyone shed some light on this situation as it does make boot up more of a hassel and I wouldn't be able to reboot (and I'd rather not have to start over and possibly have the same issue). Thank you for your time! /Used custom built 32 bit PC, 2007 Asus motherboard, ACPI bios not updated/ Peace

Which password is this?
User login?
Disk encryption?
Something else?
Does the password contain special characters?

I don't know if this is related to an old bug in Bodhi. But at one time, it wouldn't let you log in if your password had certain symbols in it. I thought it had been fixed. But if you use symbols in your password, change it to something without symbols just to check.

Thanks for replying! Stated more concisely : my fully encrypted disk only recognizes the passphrase in recovery mode. Other info, no special characters used - I validated MD5 hash before installing. Thanks Randy4bodhi for passing that info along, I was thinking of changing the passphrase anyway but after searching how, I thought I should wait for now, cause of various warnings and my lack of expertise. At least now it's usable, no problem with the graphic drivers etc. / peace

Now it's usable normally, no need to boot into recovery mode?
So the problem "fixed itself"?

No, It's the same as ever. I'm just mentioning that at least I can actually use it, in recovery mode, when for instance, evidently the graphics might need a standard boot. It seems to function the same as if I had booted normally , but boot up is a hassel. Has anyone ever heard of a half working password? Thanks / peace

I don't have much experience with disk encryption, and none with full encryption.
I do get prompted during early boot process to enter a password, that's just white text on black, no GUI.
Is it the same for you? And that's where it sometimes fails? Does it say anything beyond "bad password" when it fails?
A screenshot might be helpful.
Can you somehow narrow down when it fails and when not?

This is the standard boot I'm offered, and it always fails. Power button on, then after the Asus motherboard logo screen, the first screen (black with white text) gives the options of F1 to continue, Delete to enter setup. I hit F1 then I get a black screen with small white text (entering something about Specter) then the main log in screen (like on the live version, a mostly green beehive mesh background) appears with a window with a lock, and the text (please unlock disk sda5_crypt) After inserting my passphrase, the dots (password markers) dissapear. In white text at the bottom of the screen it says (exactly): cryptsetup(sda5_crypt):cryptsetup failed,bad password or option? Gotta go for now, I'll document what works later cause it had the strange result, today only, of reading the date as May 20, 2018, keeping me from being able to use Chromium or Midori. I rebooted and I think I hit Delete when boot was at the second black screen (showing Specter) then it gave me the option of logging in from there. I still went to recovery mode as usual and this time the date was correct, so I am able to post this reply now. Thanks / peace

- seems like BIOS is not configured after the system board battery replace. Or the battery is expired (when the date/time is not preserved between reboots).

my wife's dell started doing that so i hit f1 and continue. i never saw that before but figured it was the onboard battery. everything works fine after that beep beep beep boot.

Thanks, both of you! It's a 13 yr. old CMOS battery. It would maybe answer why; the whole time I used version 4.5 I always had to wait a while after boot for the date + time to auto-update before I could surf. However, in this fresh install of 5.0, I opted for being online to have auto detection of date + time in setup hoping I wouldn't have any issues and it worked fine for a cupple of weeks - even no apparent waiting for auto-update. But yesterday it failed to update - the wifi was connected but I just sat there trying in vain to reset date + time. But now I've finally found Swami Control Panel, and it looks like I could manually set date + time if necessary. I did set the date + time in bios and when I managed to log on, the time + date were from yesterday's boot. Soon, the auto-update worked but in the taskbar the time is correct and the day is yesterday. Oh, cool, it just updated the day(after about an hour) It's 7.23 AM and all is swell. /peace

For modern OSes jumping date/time may cause some sort of confusion, especially in cryptography. The best solution is to replace the expired battery with new one.

Interesting, I'll replace the battery first and see if that affects the encrypted disk logon issue. If it's still the same, I'll be asking for advice for the simplest way to change the password - perhaps use GNOME Disk Utillity? Thanks for your input, it's much appreciated! / peace

There is a funny story:
- Give a chicken broth to the patient!
- Good, but it will not cure it...
- But it will not harm it too!

Replacing expired onboard battery is a smart step anyway.

Please look about the similar situation with disk encryption trouble:

https://askubuntu.com/questions/1034...grade-to-18-04

Maybe it will useful.