From: pj@7.invalid.com   
      
   On 1/4/24 15:02, Carlos E.R. wrote:   
   > On 2024-01-04 02:52, panorain wrote:   
   >> I have a Lenovo m-91p SFF desktop computer. I attached a 128GB   
   >> Kingston ssd as the only hdd. I installed openSUSE TW on the computer   
   >> with LUKS encryption and I believe I enabled within YaST2 > Boot Code   
   >> Options > Trusted Boot Support. I updated the computer with "zypper   
   >> dup" powercycled and things were really working well as far as the   
   >> speed of the cpu etc.   
   >>   
   >> I then put the computer away for a year and the LUKS password was   
   >> documented correctly. I took the computer out of storage and was   
   >> attempting to unlock the disk at Grub2 menu a number of times with a   
   >> incorrect variation of the LUKS password. I finally realized that I   
   >> was attempting the wrong password and referenced the correct password.   
   >> By that time I had powercycled many times and removed all but 1 of the   
   >> 4 DIMMS from the board to get to POST and unencrypt LUKS and login to   
   >> KDE. I updated the machine with the "zypper dup", I decided to then   
   >> powercycle the machine (a very large number of updates).   
   >>   
   >> After powercycling the machine it was blank no POST let alone a Grub2   
   >> boot menu. I removed the remaining DIMM and then attempted a series or   
   >> variations with the existing 4 DIMMS with no luck to even access BIOS   
   >> or see a POST displayed. If all DIMMS are removed there is a series of   
   >> audible beeps heard in a round robin sort of sounding (around and   
   >> around).   
   >>   
   >> I attempted to attach the afflicted ssd to a functional desktop   
   >> machine operating under openSUSE TW. The device is listed/shown with   
   >> "lsblk" The ssd is not able to be mounted manually through GUI in KDE   
   >> or manually from bash terminal Incorrect password is displayed time   
   >> after time. I have tried attaching a PS/2 style keyboard to the   
   >> functioning desktop and loading into TW then trying the proper   
   >> documented password with no joy.   
   >>   
   >> I attached the afflicted ssd as the sole/only ssd to the known   
   >> functional machine. I powered on the desktop and was displayed   
   >> TrustedGRUB2 No TPM found Error.   
   >>   
   >> My questioning for you is: did my multiple attempts to enter an   
   >> incorrect LUKS password time after time (after taking the computer out   
   >> of storage) cause a possible mainboard failure or perhaps a DIMM   
   >> failure? The computer/machine is not posting whatsoever.   
   >   
   > I don't think so.   
   >   
   >> As I have said earlier in my message I was finally able to enter the   
   >> correct LUKS passphrase with 1 DIMM 2GB in size then update the   
   >> machine. Upon powercycling the machine there was absolutely no post   
   >> let alone a Grub2 unlock key displayed.   
   >>   
   >> Can I maybe reinstall a fresh grub2 on the drive?   
   >>   
   >> I welcome your thoughts on this and do understand that I am not an   
   >> advanced user. I understand that I made a somewhat poor judgment   
   >> mistake by not verifying the exact LUKS password after removing the   
   >> machine from storage.   
   >   
   > There are more tests you can do.   
   >   
   > Hot plug the Kingston SSD to an already running computer, and attempt to   
   > open the partitions when prompted.   
   >   
   > Attempt to boot the Lenovo m-91p SFF with a different media, non encrypted.   
   >   
   >   
   > And you could ask instead on the openSUSE mail list or forum.   
   >   
   >   
   Is openSUSE Tumbleweed hot plugging enabled by default? Is there a way   
   to see if hot plugging is enabled? The last time the mentioned medium   
   was updated was after usr merge (I think). I do know, the medium has   
   little critical data on it. In the very least it is an interesting   
   experiment to try and mount. I did attach a PS/2 keyboard in order to   
   really be certain the LUKS passphrase was being keyed in correctly. I   
   may post this on the mailing list soon. Thanks for your input on this also.   
      
   -pj   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)