i am attaching screen prints of the data from boot-repair to this email.

Attached Thumbnails

       

If I'm understanding the purpose of running boot repair, it was to see if any problems could be discerned on the usb. You don't show any information on a flash drive in the boot repair output. Most likely that was because you didn't have it plugged in. Everything in the boot repair output refers to a 500GB SSD which has your Ubuntu 22.04 OS on it.

THe boot repair page is at the link below. Go to it and scroll down the page to the section Using Boot Repair. As you will it is explained that you get an option to click Create BootInfo Summary which you shoul use as well as an option to upload it. You then simply post the link you are given here. You can run boot repair again from a terminal now that you have it installed, use the command below. Make certain the usb in question is plugged in first.

https://help.ubuntu.com/community/Boot-Repair

If your only current problem is that you cannot boot the USB with Ubuntu on it but were able to previously, I would suggest that if you have multiple USB ports, you try different ones or all of them. If the Lubuntu USB works, try using that USB port. If you've done that already, then I would suggest you try the USB on another computer. If it fails on another computer or other computers, then the USB is probably bad.

1 members found this post helpful.

here is the url: https://paste.ubuntu.com/p/sZy6ZX7BKd/

it says the same thing the first report did as far as suggested repair, but i dont understand any other part of the thing.

actually i wasnt sure myself what looking at the boot repair was going to do, i didnt even realize it was for the usb because i have always in the back of my mind that there is a serious fault in my laptop. if i find that the usb is bad, it could easily have done some damage to the laptop during the install i would think, and then maybe the boot repair would be able to fix that, too.

but now that 22.04.1 is out, i wouldnt even need to use that flash. the only value in finding out what is wrong with it is that it may be due to something i did wrong and it would save me from doing it again. or if i find that a certain program/software was used did something wrong (i know that happens too) i can use something else next time. i can download the iso and make another flash for a backup. actually i think there is a way to get it right off the computer, but i am afraid that would be too much for me to follow.

there is no one i know who has a computer that i could go to for help-most people over here use smart phones, not computers. ..and one year i had to find the script myself from the internet to set up wvdial to get the modem to work on cdma. the guy at the shop where i bought the computer asked me to give it to him so he could give it to the one guy he knew that lived in this city where i am that actually has linux and he couldnt get his modem to work.

The more recent boot repair output shows info on the flash drive beginning at line 29, which probably is the source of your problem, not core.img file found. Beginning at line 90, you will see more detailed information on the USB shown as sda.

I thought your problem was with the 20.04 flash drive but boot repair shows the drive has 22.04 on it (Line 112). Did you have the correct flash drive attached?

It seems a bit odd that whatever software you used to create the bootable USB created 2 windows partitions. I dont' generally use any of these software programs but I don't recall seeing that before. Some software (mkusb) creates the 1st partition on the drive as ntfs so it can be shared with windows but not 2 windows partitions. There is no problem booting an iso from an ntfs partition but it is just odd to me to see 2 windows partitions on it.

If this flash isn't booting properly it is likely the missing core.img file. Is this the correct flash?

1 members found this post helpful.

Is fastboot and secure boot disable in firmware/bios?

the two flashes i have are 22.04, one lubuntu and one ubuntu. i once had 20.04 for both of them, but i formatted them to be used again and both are now 22.04. i may have in one of my previous posts mistakenly referred to 20.04 when i meant to say 22.04, i tend to forget what year it is. so for the record i only have two live boot usb now and both are 22.04- one lubuntu and one ubuntu.

my intention is to stay with 22.04, i see no reason to leave it yet...but i had downloaded the lubuntu just so i could use that if i suddenly decided 22,04 ubuntu was too buggy.

the trouble is, with the ubuntu usb i dont remember for sure how it was created. the lubuntu was definitely done on usb-creator, (formerly known as startup disk creator, or some such other name), which i had to install because it wasnt included in the 'minimal' option which i always choose. but they both ended up in the same way, even though they may not have been created with the same software... or so it looks like in the screen from the 'disk' utility i have now on my laptop.

if the missing thing is the problem, would it be worth repairing, or even would it be possible?

should i do a boot-repair on the lubuntu flash and see if it comes out the same way? but still that might be comparing apples and oranges, because one has done an installation (ubuntu) and the lubuntu i have only run once in the 'try it' option. i dont know if that could make a difference...i mean could the usb have gotten corrupted while i was using it to install? or would something like that only have happened during creating it?

i worry if using a corrupted usb live boot could actually harm the computer-it wouldnt be worth the risk.

i dont think i even have fastboot on this machine. some of these things i have looked at so many times and then i think i got the right thing and i delete the notes on the things i was looking at so as not to get confused.

secure boot is enabled-but as far as i know it already was before when i used it to install. and fastboot i hadnt even heard of at that time.

i can see on my list of the options under security in the hp bios, secure boot is there but nothing about fast boot or quick start. i was even checking the tpm chip, the monitor, nvidia, so many things i have seen mentioned as a possible problem but so far i cant find anything wrong.

i had another idea-what if my hub is bad? i have found that some things dont work in it, and when i was using it i always had it plugged into the hub-i mean whenever i used the flash usb's, they have always been plugged into the hub. i just thought of that today and lately i have been having troubles with my mouse, so i unplugged it from the hub and put it directly into the port. but it is too soon to see if that is the problem for the mouse.

and i also wondered about the current, because it is very unstable here, but i thought the laptop cord had a thing in it that would regulate it. currently i am testing another problem by using the laptop with the battery to see if i can find out whether that helps something else. the wiring here in the buildings, at least in the city where i live, are very...they are done inventively, or innovatively, not by the book if you know what i mean. and i had to have a ground wire put in one place where i lived because nobody apparently uses those either. it is a wonder i can do anything, but everything works. the internet too is unstable and undependable, but it works well enough for the purpose of everything that i do. but i dont know how much those things apply to affecting electronic devices. i had one of those black boxes when i had my desktop, but i didnt think it was necessary for laptops.

I don't know why the core.img file would be missing. That is more than unusual. You would have to rewrite the usb by putting a new iso file on it.

If you have hibernation on your windows, you will find it under Power setting when booted into windows. Doing an online search for disable hibernation on windows should get you a number of sites. Link below is one.

https://www.cnet.com/tech/computing/...in-windows-10/

Microsoft site below.

https://docs.microsoft.com/en-us/tro...le-hibernation

1 members found this post helpful.

Yes, the problem could be your plugged into a hub and not straight into the USB port.

1 members found this post helpful.

I did a check using "startup disk creater" to put a current ubuntu iso on to a usb and I get the same message with similar partition layout. The usb boots in both legacy and uefi mode without any problems.
excerpts from the boot-repair text where sdb is the usb:

i dont have windows-i only had it for two weeks when i first bought this hp and it was installed on it and i was using the old dell computer i had with ubuntu 18.04. it took me two weeks to be sure everything was going to work on the hp with my ubuntu install that i ditched the dell. i dont want to convert anybody, but linux has everything i want and i have been more than satisfied with it since 2008. there is always a solution, and if i cant do it or cant find it, there is always an alternative version that will work for me.

so you are saying that the boot-repair report does not show anything to indicate that my ubuntu 22.04 flash should not work? i havent run boot-repair on the lubuntu usb, but if you already show the same error it must be there.


my lubuntu flash will boot, but maybe it wont install right...i dont know. and it may not boot again if i try it again and it may not work after having been used to install once either, i can only say it did boot once and did not many times. i was concentrating on the ubuntu flash.

i am beginning to believe that i couldnt have used usb-creator to make the ubuntu flash, because if i had to install it on the hp i couldnt have had it before on the 18.04 i had on the dell. therefore, i had no choice but to use either windows (which i may have been convinced to use by the argument that it would install better on the hp since hp had windows at the time and that because of 18.04 not being modern enough to create a boot drive with the current technology of uefi) or the old 18.04, if the argument had failed to convince me.

and since i dont recall what the software looked like on windows, i suspect i had to have used ubuntu 18.04 and its simple disk utility, nothing fancy and nothing installed. i had to research how to format my existing usb drives first, which took me a lot of time because sometimes it didnt work, and i had to research how to create the boot flash and i would have chosen what i thought would work based on whether or not i understood it and felt comfortable doing it. i think i would have avoided using windows unless i felt it was definitely impossible to create a live boot flash on a modern windows machine that would work on current linux.

i really admire your short and concise replies, and i only wish i was able to do that instead of having to tell you a lot of things that may not matter-but i am afraid of leaving something out which may seem irrelevant to me and may be the key to the problem.

then i think i better try the ubuntu 22.04 drive flash to boot without using the hub...

i dont want to be interrupted, and i have to do something else at the moment...then i will get back to this as soon as i comfortably can.

i did try using boot-repair for the ubuntu 22.04 live boot flash but it didnt boot.
i also tried it with the computer unplugged to the electricity and it also did not boot.

i ran another boot-repair for the ubuntu flash boot when it was not plugged into the hub, but into the laptop directly, and the report looks the same with the same suggested repair at the end as the others.
https://paste.ubuntu.com/p/wKDHxKxFjQ/

i rechecked the bios screen that shows boot options and it is set at OS Boot Manager, then USB FLash Drive/USB Hard Disk, USB CCD/DVD ROM drive, USB Network Adapter ignored. that is when the flash was not plugged in-i didnt think it would be changed depending on what was plugged in, so i didnt try it that way.

i rechecked and i know Secure Boot is Enabled. i dont think it would help to disable it because the lubuntu flash did boot with it enabled, and the original install of ubuntu also was with it enabled.

i looked up the "core.img can not be found at this location" remark, and i think it might only be relevant to dual boot systems, or maybe to the problems there are with dual boot systems (one being windows which overwrites things at every boot). that would be my uneducated guess, anyway.

also i was confused by the following section from the boot-repair report:
===================================== UEFI =====================================

BIOS/UEFI firmware: F.21(15.21) from AMI
The firmware is EFI-compatible, and is set in EFI-mode for this installed-session.
SecureBoot enabled but mokutil says: SecureBoot enabled - Please report this message to boot.repair@gmail.com.

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0001,0002,9999
Boot0000* ubuntu HD(1,GPT,2e95f23e-320f-4b7e-8b26-24bd8890873f,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* Windows Boot Manager HD(1,GPT,9fe5945a-1990-4832-95f7-5ec21955d376,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...&................
Boot0002* Solid State Disk PciRoot(0x0)/Pci(0xe,0x0)/NVMe(0x1,00-26-B7-68-59-20-A1-90)/HD(1,GPT,2e95f23e-320f-4b7e-8b26-24bd8890873f,0x800,0x100000)..BO
Boot9999* USB Drive (UEFI) PciRoot(0x0)/Pci(0x1d,0x0)/USB(16,0)..BO


at the beginning it says 'set in efi mode', i thought it was supposed to be uefi, but i dont know. and what about the cryptic message about secureboot?-should i be notifying boot-repair?

the other strange thing is that the boot order here is comparable to what i find when i use efibootmanager and contradicts what is in the bios screen. how can that be? is hp bios wrong or is linux wrong?



so i dont have any more ideas, other than trying to create a new ubuntu live boot flash for 22.04.1 and see if that works, and i could use usb-creator again, because i have it...or i could try something else if you all think it would be more reliable. i know rufus is only for windows, and i have heard users post that they have had problems with etcher. i also know some of them can be very complicated, and i know nothing about partitioning or anything else-just write from iso to usb. like the old cd-burners used to do.

i also tried using esc followed by f10 several times to get to the bios screen, but it just doesnt work on my hp. manufacturers cant make the same thing twice i guess, everything has to be different. so i still am able to get in, and i think my success rate is improving-at least my confidence is growing.