Thanks for your suggestions Gene. With the entire screen shown I could see the writing at the top right corner, it began with “busybox” ect. And this text and prompt was beneath it (initramis)_

I messed around with the advance options and these were the results:

Inodes that were part of a corrupted orphan link list

dev/sda5: unexpected inconsistency; run fsck manually. (without -a or -p options)

failure: file system check of the root file system failed.

The root file system on/dev/sda5 requires a manual fsck

fsck from until-linux 2.34

Thanks

Thank you Gene and Bruce. It took me a while of wading through “fixes” that didn’t work, even some posts that claimed you can’t fix the initramfs_ with recent versions of Ubuntu. And Bruce, there wasn't an issue with lost data, because I use several computers I back up all new data to a usb drive in real time that I move from computer to computer, and then painstakingly transfer to 2 external HDs once in a while. Can't remember why I quit using time shift. And I used to also have a back up OS on an external drive that I could just copy, which I'm gonna do again after this experience.

Here is the fix that finally worked in case anyone is interested.

Actually the solution is easy just write the command of fsck /dev/sdax like the below and give Y if the console ask for fixing something:

(initramfs) fsck /dev/sda1

or

(initramfs) fsck /dev/sdaX

X specifies mounted disk part number.

If you don't want to manually press 'y' every time it asks for a fix, you can also run the command with the -y option.

(initramfs) fsck /dev/sdaX -y

take care you all, thanks again for your suggestions

Charles
 
You’re welcome.

Charles

 

You’re welcome.

 

The only other suggestion I have is that when you get it fixed, back up your system so that if this happens again, you can restore. 

 

This issue has exceeded my technical abilities with Linux.  I hope some other person in the CLUG can help you.

 

Gene

 

From: cochiselinux-bounce@freelists.org <cochiselinux-bounce@freelists.org> On Behalf Of Charles Breaux
Sent: Sunday, May 29, 2022 6:14 PM
To: cochiselinux@freelists.org
Subject: [cochiselinux] (initramis)_ instead of booting

 

Thanks for your suggestions Gene. With the entire screen shown I could see the writing at the top right corner, it began with “busybox” ect. And this text and prompt was beneath it (initramis)_

 

When I entered cat/partitions, or bilkid at the prompt I received the message that they were not found. When I entered fsck at the prompt, nothing happened, and the (initramis)_ reappeared.

 

Devi, anyone, please help, i don't want to have to go through a clean install  and set everything up again.

I messed around with the advance options and these were the results:

Inodes that were part of a corrupted orphan link list

dev/sda5: unexpected inconsistency; run fsck manually. (without -a or -p options)

failure: file system check of the root file system failed.

The root file system on/dev/sda5 requires a manual fsck

fsck from until-linux 2.34

Thanks