[SOLVED] After copying system to SSD, can cold boot but cannot reboot

Shingen · 2023-02-17 04:05:20

I decided to switch from HDD to SSD; As instructed in the top-to-bottom method, I cloned the boot and root partition using rsync, genfstab, chrooted and reinstalled grub. Now I can shutdown and do a cold boot, but when I type reboot, it shuts down and stuck at the boot target selection menu in BIOS.

After repeatedly selecting the grub entry, sometimes it gets into the grub rescue cli:

grub rescue > set
cmdpath='(hd0)/EFI/GRUB'
prefix='(hd0,gpt1)/grub'
root='hd0,gpt1'

I've also tried the reboot kernel parameter in https://bbs.archlinux.org/viewtopic.php?id=273772, it does not work either.

Any help will be appreciated!

Last edited by Shingen (2023-02-19 04:06:25)

seth · 2023-02-17 07:18:58

Does the BIOS have a "fast boot" option, what if you toggle that off?
(No, indeed not windows fast-start, though if there's a parallel windows installation, see the 3rd link below as well)

You did make sure ("cat /proc/cmdline") that the reboot parameter was actually applied?

d.ALT · 2023-02-17 07:30:28

seth wrote:

Does the BIOS have a "fast boot" option, what if you toggle that off?

This.

Also, check for UEFI's firmware updates.
What's your UEFI's Boot Order inside UEFI's Menu Settings?

Post here

# efibootmgr -v

Shingen · 2023-02-17 07:53:50

seth wrote:

Does the BIOS have a "fast boot" option, what if you toggle that off?

The closest option is a "boot mode" between "quick" and "diagnostic", doesn't seem to help. (Thinkpad X220)

d.ALT wrote:

Also, check for UEFI's firmware updates.
What's your UEFI's Boot Order inside UEFI's Menu Settings?

My BIOS is at the latest version, GRUB at the first order, and UEFI only (no legacy boot).

~ $ efibootmgr -v
BootCurrent: 0019
Timeout: 0 seconds
BootOrder: 0019,000C,0006,0007,0008,0009,000A,000B,000D,000E,000F,0010,0011,0012,0013
Boot0000  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
      dp: 04 06 14 00 66 8b 1c 72 6c 42 86 4e 8e 99 34 57 c4 6a b0 b9 / 7f ff 04 00
Boot0001  Boot Menu	FvFile(126a762d-5758-4fca-8531-201a7f57f850)
      dp: 04 06 14 00 2d 76 6a 12 58 57 ca 4f 85 31 20 1a 7f 57 f8 50 / 7f ff 04 00
Boot0002  Diagnostic Splash Screen	FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
      dp: 04 06 14 00 a6 d9 d8 a7 b0 6a eb 4a ad 9d 16 3e 59 a7 a3 80 / 7f ff 04 00
Boot0003  Startup Interrupt Menu	FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
      dp: 04 06 14 00 f4 e6 6e f4 85 47 a3 43 92 3d 7f 78 6c 3c 84 79 / 7f ff 04 00
Boot0004  ME Configuration Menu	FvFile(82988420-7467-4490-9059-feb448dd1963)
      dp: 04 06 14 00 20 84 98 82 67 74 90 44 90 59 fe b4 48 dd 19 63 / 7f ff 04 00
Boot0005  Rescue and Recovery	FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
      dp: 04 06 14 00 60 3f 5d 66 3e ad ad 4c 8e 26 db 46 ee e9 f1 b5 / 7f ff 04 00
Boot0006* USB CD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 86 70 12 96 aa 5a 78 48 b6 6c d4 9d d3 ba 6a 55 / 7f ff 04 00
Boot0007* USB FDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 6f f0 15 a2 88 30 b5 43 a8 b8 64 10 09 46 1e 49 / 7f ff 04 00
Boot0008* ATAPI CD0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35401)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b ae a2 09 0a df de 21 4e 8b 3a 5e 47 18 56 a3 54 01 / 7f ff 04 00
Boot0009* ATA HDD2	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f602)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 02 / 7f ff 04 00
Boot000A* ATA HDD0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 00 / 7f ff 04 00
Boot000B* ATA HDD1	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 01 / 7f ff 04 00
Boot000C* USB HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 33 e8 21 aa af 33 bc 47 89 bd 41 9f 88 c5 08 03 / 7f ff 04 00
Boot000D* PCI LAN	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 78 a8 4a af 2b 2a fc 4e a7 9c f5 cc 8f 3d 38 03 / 7f ff 04 00
Boot000E* ATAPI CD1	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35403)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b ae a2 09 0a df de 21 4e 8b 3a 5e 47 18 56 a3 54 03 / 7f ff 04 00
Boot000F* ATAPI CD2	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35404)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b ae a2 09 0a df de 21 4e 8b 3a 5e 47 18 56 a3 54 04 / 7f ff 04 00
Boot0010  Other CD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35406)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b ae a2 09 0a df de 21 4e 8b 3a 5e 47 18 56 a3 54 06 / 7f ff 04 00
Boot0011* ATA HDD3	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f603)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 03 / 7f ff 04 00
Boot0012* ATA HDD4	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f604)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 04 / 7f ff 04 00
Boot0013  Other HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f606)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 06 / 7f ff 04 00
Boot0014* IDER BOOT CDROM	PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0)
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 16 / 03 01 08 00 00 01 00 00 / 7f ff 04 00
Boot0015* IDER BOOT Floppy	PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0)
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 16 / 03 01 08 00 00 00 00 00 / 7f ff 04 00
Boot0016* ATA HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 / 7f ff 04 00
Boot0017* ATAPI CD:	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b ae a2 09 0a df de 21 4e 8b 3a 5e 47 18 56 a3 54 / 7f ff 04 00
Boot0018* PCI LAN	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 78 a8 4a af 2b 2a fc 4e a7 9c f5 cc 8f 3d 38 03 / 7f ff 04 00
Boot0019* GRUB	HD(1,GPT,0dcd3ebe-5864-b64e-95a2-e8b24451134c,0x800,0x113000)/File(\EFI\GRUB\grubx64.efi)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 30 11 00 00 00 00 00 be 3e cd 0d 64 58 4e b6 95 a2 e8 b2 44 51 13 4c 02 02 / 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 47 00 52 00 55 00 42 00 5c 00 67 00 72 00 75 00 62 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00

seth · 2023-02-17 08:13:35

The closest option is a "boot mode" between "quick" and "diagnostic"

That'd be it.

If you intercept the boot, enter the firmware, hang out there for a bit and the continue, does the reboot work?

Shingen · 2023-02-17 08:36:34

seth wrote:

If you intercept the boot, enter the firmware, hang out there for a bit and the continue, does the reboot work?

No, if I understand correctly I rebooted, entered BIOS, hanged around for 5 min, continue to boot, and it cannot boot.

What I noticed is that the machine takes a really long time to get pass the splash screen before BIOS at reboot. (Not so at the first boot)

Also something that I stumbled upon, when at grub rescue, sometimes ls will only show one entry (hd0), but sometimes it can show these (hd0,gptX) (X=1,2,3). Could this be a hardware issue?

Last edited by Shingen (2023-02-17 08:42:43)

seth · 2023-02-17 08:47:25

https://wiki.archlinux.org/title/Solid_ … leshooting

Look out for ncq errors and make sure to disable ALPM - the SSD will (likely) enter a state during runtime that it cannot recover from w/o a hard reset.

In doubt please post your complete system journal for a boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Shingen · 2023-02-19 04:05:54

seth wrote:

make sure to disable ALPM - the SSD will (likely) enter a state during runtime that it cannot recover from w/o a hard reset.

Thanks, that's the culprit: I added udev rule as instructed in https://wiki.archlinux.org/title/Power_ … Management, change med_power_with_dipm to max_performance, now it reboots.

Arch Linux

#1 2023-02-17 04:05:20

[SOLVED] After copying system to SSD, can cold boot but cannot reboot

#2 2023-02-17 07:18:58

Re: [SOLVED] After copying system to SSD, can cold boot but cannot reboot

#3 2023-02-17 07:30:28

Re: [SOLVED] After copying system to SSD, can cold boot but cannot reboot

#4 2023-02-17 07:53:50

Re: [SOLVED] After copying system to SSD, can cold boot but cannot reboot

#5 2023-02-17 08:13:35

Re: [SOLVED] After copying system to SSD, can cold boot but cannot reboot

#6 2023-02-17 08:36:34

Re: [SOLVED] After copying system to SSD, can cold boot but cannot reboot

#7 2023-02-17 08:47:25

Re: [SOLVED] After copying system to SSD, can cold boot but cannot reboot

#8 2023-02-19 04:05:54

Re: [SOLVED] After copying system to SSD, can cold boot but cannot reboot

Board footer