Boot works, Reboot doesn't

When did you start to have the issue? Was there any version of a Linux system that rebooted correctly?

Regarding the SATA port: do you have any option in the BIOS?
I’ve seen laptops which were by default set to something RAID like function, not pure AHCI.
Ironically this made Windows much more hard to install (special Windows driver was needed), Linux worked flawlessly.
Setting the SATA mode to AHCI made it work with both Windows and Linux, and it was unnecessary to install a special driver for Win.
If you have any option like that, maybe try to toggle it.

3 Likes

I already tried, and it worked then. But it’s a boot, not a reboot, or did I miss something?

1 Like

I can select SATA speed 3.0 or 6.0 Gbps and SATA device mode IDE or AHCI. Nothing else.

2 Likes

Just boot the live USB, mount the internal SSD, then reboot into the live again:
is the SSD still accessible?

I’d keep the AHCI, but I assume speed is set to fastest possible. What if you limit to 3Gbps?

1 Like

I thought that you could try reboot from the USB. Only grub with OS-prober in that USB

2 Likes

Do you still have the hard disk ?
No matter which linux is on it, could you replace the drive and see if you have the same issues.

Thi would establish if the fault in connected to the ssd or motherboard

1 Like

Yes. I’ve changed the boot order so that the stick comes before the SSD. Rebooting from the live system works, which means the SSD is still present.

Nope. I tried, even if I don’t like driving with the attached brakes. :wink:

3 Likes

Oops!
I did what you suggested; obviously I was wrong.
It works with the former HDD having LMDE5 Elsie on it. :worried:

2 Likes

@abu
I keep repeating this.
Is there anything we can do to give the disk more time to initialize when you reboot?
If there is nothing appropriate in the bios, can we somehow put a delay in the reboot command?

What do you see if you do strace reboot
Maybe script it to trap output

script reboot.out
strace reboot
3 Likes

Now the question: If you put LMDE5 onto the SSD, does it work as it should, or shows the symptom?
That would narrow down the problem to older/newer kernel versus HDD/SSD.

2 Likes

I think it already was on the SSD earlier, and I won’t do this again. Sorry.

1 Like

Did it reboot then nicely?

1 Like

I’d say no, IIRC. I think the issue was already there.

1 Like

There is no such thing in the BIOS settings.

1 Like

That clearly means to me the culprit is the BIOS reboot mechanism, as it can’t correctly cooperate with the SSD. Still could keep up with the HDD.

1 Like

There have been reports of SSD’s with an MBR not behaving well.
Does the linux partition have a boot flag? That is necessary with MBR.
One could try moving the partitions ( use gparted) so there is a small space ( eg 1Mb) at the start of the disk ( ie between the MBR and the first partition.

1 Like

Yes it has that flag. I saw it on the fdisk output.

There’s a 2MB gap. That should be enough.

So I have no more ideas to try at the moment :frowning:

2 Likes

I hope you can see something; I cannot.

reboot.out

1 Like

Otherwise it wouldn’t boot at all, right?

I had a similar idea; give it a try.

1 Like
unlink("/run/systemd/reboot-param")     = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/proc/1/root", 0x7fffb54aa410, 0) = -1 EACCES (Permission denied)
geteuid()                               = 1000**strong text**

There is a lot of systemd stuff… mainly missing files
Have you ever used a non-systemd distro in that machine?

I dont like that ‘Permission denied’… did you run reboot as root?

Strace only logs system calls… there may be other things happening.

Note what Laszlo said… leave that 2Mb gap there.
Maybe move swap and make Linux the first partition

1 Like