@gary might be right here.
If the Mint installer made a mess of setting up the disk, eg wrote grub in the wrong place, it would fail to boot.
Two options to try
try another Linux which uses a different installer ( eg LMDE)
partition the disk first by hand using gparted. This requires some experience.
I think I would be running smartctl on that disk… just to be sure.
My guess is that it is an installer problem, but thst is only a guess.
What is the best thing we can get @davg to do to try and diagonose?
I think I would opt for try installing another distro. I think @davg could handle that.
Either command line or using menu tool with screen shot to see what is going on
There have been issues with mint 22 but only read about them not seen any to comment on, something about the kernal in the last release. Lmde uses a older version i think
Thanks, we needed to try that.
That means my guess of an installer problem is probably wrong.
Could you try 2 things
find a linux on a usb that has smartctl… use it to check your disk for faults
get gparted on a usb and have a look at what that lmde install put on your disk… look for an EFI partition (or a bios-grub partition if it is gpt and legacy boot), a root partition with someting in it, a boot flag on any partition
I hope there is no secure boot involved? How old is this laptop? Has it run linux previously?
That HP support link says restore bios settings to default. That is a bit drastic, but we may be forced to try it.
the installer writes everything on the disk properly
There is only one possibility left
When you do grub-install ( or when the linux installer does it for you), two things happen
it writes grub to the disk
it sends a message to the BIOS telling it that a disk has had a bootloader added to it. The BIOS uses that info , and adds the disk to its boot menu
Now, it seems that in your case , the BIOS code is corrupted, and it is either not receiving the message, or not acting on it. So the disk does not get into the boot menu.
What can we do ? Four things in order of seriousness
check the CMOS battery. The BIOS needs it to retain settings.
set the BIOS back to factory default settings… this might fix the code. Then you need to reinstall or redo update-grub, and see if the BIOS gets the message
failing that, upgrade the BIOS… ie get a whole new set of bios code
failing that, the NVRAM must be faulty… not storing the code properly
These are the partition I run with Gentoo on a mbr disc, only difference is this is a HDD spinner drive, where yours is an SSD!
Do not know how old your laptop is, or what it had, for hardware, but if you have replaced the original drive with that SSD, then the hardware just might not be detecting the SSD, at reboot. Have there been any bios upgrades released for your laptop?
@abu
I had a similar Dell laptop, but instead of taking the “Linux route” I left the W7 Home Premium installed. I then downloaded a W10 ISO and a W11 ISO, use 7z to extract both to separate folders and replaced the W10 installer with the W11 installer, mounted the hacked W10 ISO, from within W7 and have been running W11 ever since.
I get security updates but I do not do feature updates, and when W11 ceases to run, I will then retire the laptop.
Notice that @Daniel_Phillips has a boot flag on the /boot partition.
That is required for legacy boot
If you dont have a /boot partition, the boot flag should be on the / partition.
Check that you have that.
Legacy boot will not work without it.
Sorry I just noticed @Daniel_Phillips has posted the same comment
In our walk-in repair shop, people give us their old machines to renovate and pass on to those who need them.
Recently, I had problems getting LM21.3 then LM 22 to boot on 3 HP portables that are recent by our standards (less than about 8 years). I can’t say much because there may be faults that are hard to detect, but I’m getting too old to do all the geek stuff mentioned here.
To run my CNC workshop machine, I bought directly from Lenovo an entry-level Ideacentre dated 2020. It refused to install Ubuntu or Mint, and Lenovo replied that it wasn’t designed for Linux, despite the fact that in the past they have sold PCs with Linux.
I don’t want to sound paranoid, but I’m beginning to wonder whether some of this might form part of a subtle anti-FOSS strategy. The thought occurred to me when looking up one of the flagrant design faults in LibreOffice, which are fatal for many potential uses, and never get fixed. This is the latest in a chain of more than 20 related bug reports that started in 2012 or earlier: https://bugs.documentfoundation.org/show_bug.cgi?id=46448
I wonder if a total format of the hard disk and removal of all partitions so in effect it is a new disk would help. If the problem is within the bootable area of the disk this would either flag sectors not to use or clear errors