The usb has a fat32 filesystem, you might have used rufus or yumi within windows. Using dd in linux doesn't create a fat32 filesystem and I don't think etcher does either.
If it was yumi, that may be the problem, at one time yumi had issues booting in uefi mode.

sorry-wrong usb...i am awake now, attached the right print....
(the fat 32 is my file storage or backup drive, which i happened to have plugged in at the time.)

i didnt use rufus, i looked at it but i didnt like it so i didnt download it. i had decided on etcher but i dont remember for sure if i downloaded it and later deleted it...

at the moment i am getting two icons for the flash drive, one says writable...how come that happens sometimes?

Attached Thumbnails

 

i will have to read over this-i went to the previous page and it is more basic, i have to start from the beginning. i have to be really careful here because it is more advanced and complex than anything i ever attempted, and i dont understand how anything in my laptop could be unmounted. the concept can only be applied to devices that are attached or plugged in (in my mind or limited understanding/knowledge of the subject).

once i actually accidentally hit 'format' and i had selected the hard drive by mistake, not the usb. i was lucky because nothing happened, maybe there is something to protect it. but i am capable of making some fatal mistakes. i can still think pretty good, but i am slow and sometimes my attention wanders off...(76 years old). too bad there isnt a filecheck program for human beings.

It looks like dd was used to install the iso to /dev/sda1 instead of /dev/sda. When using dd to install iso to usb, dd to whole drive not to a partition.

rufus is my go-to for putting iso on to a usb in windows, it has never failed me.

You don't need to find it if you selected the Create BootInfo Summary option. The purpose of this is to upload the file to share with others so you can get help from more experienced users. When boot repair finished, you should have seen a pop-up asking if you wanted to upload it. This is stated explicitly on the boot repair page under Using Boot Repair near the bottom of the page.

You can't run fsck on a mounted partition. Mounted simply means accessible. If you are booted into Ubuntu installed on the hard drive, you can't run fsck on the system partition but you can run it on another drive. If you boot an OS from a flash drive with the intention of running fsck, you can run the df -h command to show all mounted partitions. If you want to use the Ubuntu or Lubuntu flash drive to run fsck, run df -h to see if the installed / (root filesystem) partition on the hard drive is mounted. If it is, you need to unmount it before running fsck.

There are quite a few log files in /var. You can open a terminal and run: ls /var/log to see a list of all of them. There are boot.log files which you might check. If you navigate to the /var/log directory in a file manager, you will see all these files and some of them will have a red x which means you need root (sudo) permissions to access them. If you look at these in a file manager, you will see that many have numbers in the file name. If there is no number, that is the most recent file and if you right click on one of these icons and click properties, it will show a date. The higher the number the older the file.

If you have a flash drive which you used to put your iso file on to boot your install (Ubuntu, Lubuntu or whatever), a very simple way to use it again is with GParted. When you open GParted, go to the upper right of the window and click the down arrow to select the usb device which will then show any partitions in the usb drive. The size of the drive will show so check that so you don't use your internal drive. Then click on the Device tab at the top of the GParted window and you will see an option to Create partition table. Select either gpt or msdos, whichever you want. If any partitions are mounted on the device, it will show a message so you need to unmount. You will then be able to use the usb drive again for any purpose.

I'm not sure what your problem is now as you indicated earlier you can now boot from the flash drive. Is it just being unable to access the BIOS options? The focus seems to have changed to reusing your flash drive?

I was also confused earlier, see post 19 and 20, the op is trying to figure out why the ubuntu flash drive doesn't boot anymore.

colorpurple and yancek-
sorry to confuse anybody, i probably should have started two separate threads. i did have two problems, one being not able to get into the bios to change the boot sequence and the other was that i couldnt boot with my flash drive.

the way it stands now is that i will be able to get to the boot sequence if i have to, but i have determined that i dont need to in order to boot with the flash. it automatically did for the original install, and it does when i use the lubuntu flash, so maybe the boot sequence was changed when i was fooling around or maybe that is integrated into the installer as a onetime change or option.

now i know i can boot with the lubuntu flash, but i have the flash i used to install ubuntu 22.04 on the hp laptop and i want to be able to use it in case i have to do a fresh install. but when i tried to look at it it acted weird and got hung up and i was afraid to try it again.

several things have changed since i started this thread. one is i have learned a lot so far and i thank everyone who has contributed to that.

second, i think i may have been unpgraded to 22.04.1 on the 11th or 12th...i mean i know i do have the .1 version now. i ran updates on that day and i can see a definite change in the log i have been keeping for a different problem with login, and it seems it may have had an effect in that respect. it may have done other things to help me that i have not yet discovered.

but i have always suspected there is a big possibility there was something wrong with the install of 22.04. i would like to know what it was, especially if somehow i did something wrong, so i dont do it again. but since i dont remember how i did it ...what can i say.

i didnt realize that there is an iso for 22.04.1, so that if i downloaded that and created a new usb flash i could do a fresh install on the laptop without having to worry about any bugs bugs or flubs in the first version that i installed, in case that was the reason for my problems, and i would be updated almost up to the present.

i guess in conclusion i would say that even if i dont find out what might have been wrong or what i did, i would like to have something confirm that the install on the hp is not somehow broken or in need of repair. that way i dont have to do anything more. and if an error or some damage is found, a possible solution would be to just go with downloading a new iso, creating a new flash, and doing a fresh install with that.

what do you guys think i should do at this point?

i didnt upload the Boot Repair file because i didnt understand that i was supposed to.

oh-wow...i was looking around some more and i finally found the var folder in filemanager and the boot repair stuff. they sure hid it good-it was like looking in the legend of zelda.... there is a report and a bootlog. i can attach both to this post...

the other thing is, if i remember right, i did the formatting on the usb by using the disc utility from where i made the screen prints to show the partitions. is that possible? i used to have lubuntu 20.04 on the flash, which i undid with the disc utility and then created the new one for 22.04, but i dont remember where i did that part. i must have formatted the other one too because i used to have a flash for ubuntu 20.04, and must have put ubuntu 22.04 on that. if i created it on this machine there should be a log, right? but i have a feeling that i did it on ubuntu 18.04 just before the dell died.

Attached Files

	Boot-Info_20220818_2252.txt (9.3 KB, 2 views)
	boot-repair.log (17.2 KB, 11 views)

is there a way to move it where it should be? what kind of problems would that cause for me... ?

also, why would it do that? is it because i used an empty usb to create it instead of first making partitions? i had seen the instructions on making partitions, but then i also saw another thing (i could probably find the url) that said after making an empty usb it was ready to go.

i am attaching a screen print of the lubuntu flash-if they are both the same, then that opens a new can of worms, dont it? i have two prints because the thing splits into writable and other sometimes, and i didnt know if that was important...both the flash drives do that sometimes but i dont know why.

Attached Thumbnails

   

It looks like both usbs are done the same way. What software did use to put iso onto the usb?

oh, i asked my friend (i thought she was mad at me) and she remembered, it was startup disk creator, that is for the lubuntu flash. the ubuntu flash i cant be sure because i would have had to make that when i had both computers. but i found some notes that i made the lubuntu flash somewhere between the 8th and 15th of august. i also remember that i had to install the software-i do a minimal install, and it wasnt included. so this is positively how the lubuntu flash was made.

Then you didn't read the instructions on the page, the quote below which is under Using Boot Repair. It's only one page of instructions.

Some software used to create a bootable usb from a Linux system uses the dd command in the background. I've never used Startup Disk Creator o I don't know what it does. Using dd, you would need to write to sda, sdb or whatever the drive is rather than to a partition on the drive.

No, you would need to rewrite it to the flash drive.

This usually happens when a user makes a change in the settings without knowing what it does. I've never used that software so??? You don't generally make any partition using this process as they are not needed.

I'm thinking it might be mkusb that you used to create the usb. The layout of the usb is similar to what mkusb does when creating a live usb with persistence for booting in both uefi and legacy mode.

Balenaetcher method of putting a iso on usb may work, but I don't think it has a persistence option and the usb will be read-only

re: boot-repair
i had attached the two documents to the last email but i dont think that worked...i see there have been no views, and maybe the only things that can be added are images rather than documents. i will attach screen prints to another post.


re:usb creator
i dont think i did anything other than add the file of the .iso that it was to use to create the flash, and from then everything was automatic and it was done really fast.

no, i dont have any mksub software. i now remember installing usb-creator from synaptic. it is the only thing i know of on my hp that i could have used for the lubuntu flash, and it was installed at a later date than the ubuntu flash, so i had no other laptop. the dell broke down again and i just got rid of it.

i think there are sites where you can connect to and they will create flash drives, but i would not be comfortable in doing things like that. i dont even use torrents...i am afraid of being connected to third parties.

so if the two usb's i made were created from the same program, then the ubuntu 22.04 was also done on usb creator. otherwise, i can only say for sure that the lubuntu flash (which works fine, at least in the 'try' option, which is all i have used it for). if there is a possibility the ubuntu flash was not made from the same program that i used to make the lubuntu, then the only other possibility is that it would have been made on ubuntu 18.04 when i still had the dell...or, far less likely, some program windows 11 which i would have been highly resistant to use because i was no longer familiar with anything in windows.

the only other thing in my memory is that there were no choices for me to make that i was unsure of, it was a very simple, fast operation in both cases and didnt cause me any anxiety. i was expecting to run into a problem in understanding how to do it, because the ones i had made before were from other operations, back when there were less things to worry about like legacy and secure boot and partitioning. on top of that, i had never made a flash that would have to be able to be used on windows before, and i wanted it to be able to work on both systems. but it turned out to be no trouble at all.

edit-found print that indicates use of usb creator which may have pertinent information

Attached Thumbnails