The dmesg doesn’t show anything about it, and I’ve tweaked all the relevant BIOS settings.
1 Like
Well the only things left to tweak are
- boot parameters
- driver modules loaded into kernel
I dont suppose you have a spare SATA cable that you could substitute to check the cable and connections
2 Likes
Did you get similar errors with lmde 4, 5 or just started now ?
At which stage did you change for ssd from hard disk ?
I’ve had issues with ssds on my HTPC. When I add/remove a SSD I need to use efibootmgr to get the boot working.
Maybe it’s similar issue with you? Although you can boot normally, which I couldn’t before fixing as explained in the wiki link (creating a boot entry).
2 Likes
As mentioned above.
Thank you for your suggestion, but I’m afraid this wouldn’t help either. A few months ago, I’ve installed Arch Linux, trying both MBR and UEFI. No way!
2 Likes
What I would try is fiddling with kernel paramteres, especially with reboot related variables.
Such as
reboot= [KNL]
Format (x86 or x86_64):
[w[arm] | c[old] | h[ard] | s[oft] | g[pio]] | d[efault] \
[[,]s[mp]#### \
[[,]b[ios] | a[cpi] | k[bd] | t[riple] | e[fi] | p[ci]] \
[[,]f[orce]
Where reboot_mode is one of warm (soft) or cold (hard) or gpio
(prefix with 'panic_' to set mode for panic
reboot only),
reboot_type is one of bios, acpi, kbd, triple, efi, or pci,
reboot_force is either force or not specified,
reboot_cpu is s[mp]#### with #### being the processor
to be used for rebooting.
What if you add reboot=hard or reboot=cold (these sound promising at the moment) to the startup parameters?
3 Likes
I am sorry but out of ideas, except for a new format and new install, but not convinced it will fix the issue.
Been there, done that. I came across this a few days ago. However, I didn’t find a working combination yet. 
1 Like
It wont. When I installed Arch Linux on a formerly blanked system, I still got the issue.
1 Like
I assume you ran update-grub after modifying /etc/default/grub.
Did you?
A common mistake (sometimes even on my side) to forget it.
cat /proc/cmdline
shows the boot parameters, just to confirm they are there…
If those cold-like reboots don’t work, what about to try reboot=soft or warm?
Maybe… fingers crossed…
2 Likes
Think I will sit and watch the ideas of others to find a solution (hopefully)
Anyway, thanks for trying to help. 
3 Likes
Meanwhile, I tried all of them…
3 Likes
I did not have that issue when I replaced an HD with an SSD?
2 Likes
Dont give up.
You have an MBR disk (not GPT)
I wonder if the MBR is corrupted?
How long is it since you did grub-install to write a new MBR?
I still think your best bet is a timing issue… are you sure you cant find a parameter in the BIOS to set a time delay for the disk to initialize?
3 Likes
Does an older system, like Debian 11 show the same symptoms?
2 Likes
I have an SATA power y-cable which powers two SSDs and when I detach the SSD which only has backups the booting won’t work. I need to press ESC, select boot drive and find the boot file to continue. Otherwise it just reboots after 10sec and the loop continues. Same when I add the backup SSD back to the same y-cable.
It isn’t same problem but just gave my fix if it would help @abu
2 Likes
So you need to manually revise the list of disks in the bios before booting works properly.
I had a case where I interchanged the sata cables connecting 2 disks and the same thing happened. @Daniel_Phillips explained to me that when you disconnect a disk the bios needs to redo its disk information.
@abu’s issue is similar… what is there is not what the bios thinks is there.
But he is not disconnecting anything.
https://superuser.com/questions/420557/mbr-how-does-bios-decide-if-a-drive-is-bootable-or-not
I am starting to wonder if using an MBR partition table on an SSD may be causing the issue. Most people with an SSD would use GPT. I think he has to use legacy boot but that should work with either MBR or GPT.
2 Likes
Remember, I had the issue before replacing the HDD by an SDD, and changing to GPT didn’t help either.
2 Likes
You have had the issue with the original hd and same issue continues with new SSD and you have tried MBR and GPT and changing kernel parameters so is there anything else left than motherboard/ bios issue?
You could try to use a USB stick to boot to grub menu. Then we would see if rebooting works from an USB stick. Just one fat32 partition to a USB and install grub there and try rebooting from it. It would prove something is wrong with the bios finding SSD at reboot.
2 Likes