Bootloop after change hardrive

Hardware
1

Hello everyone,

I invested in a librem 13 version 2 (Purism). After trying PureOS, I returned to Debian.
I also changed the original hard drive which only had a capacity of 80GB for another of 250GB.

But only here … after installing Debian on this new disk, I find myself with a redundant and tiring problem: intermittently, the blocking of bios and grub.

The problem exists according to several scenarios:

1
The laptop turns on,
The bios starts,
The laptop remains blocked after starting the bios and does not reach the grub

2
The laptop turns on,
The bios starts,
The grub starts (and allows the selection of different images)
The core loading remains frozen

3
The laptop turns on,
The bios starts,
The grub starts (and allows the selection of different images)
The loading of the core follows its short
Debian starts by offering to enter partition decryption password

You will understand, scenario 3 and the one I prefer: smiley :.

In order to reach scenario 3, I sometimes do 2, 3 or even 4 or 5 times to enter the sacrosanct command of ctrl + alt + delete (so dear to me since my childhood: smiley :).

Also, I have the impression, that the bios is badly stored in a place … I updated it to its latest version (coreboot). But since I changed my hard drive, wouldn’t there be a problem …?

However, I would like this problem to stop. And call on your acquaintances.

You will find below the result of the fdisk -l command

`Disque /dev/sda : 223,6 GiB, 240057409536 octets, 468862128 secteurs
Modèle de disque : XXXXXXXXX
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d’E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d’étiquette de disque : dos
Identifiant de disque : XXXXXXXXX

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sda1 * 2048 499711 497664 243M 83 Linux
/dev/sda2 501758 468860927 468359170 223,3G 5 Étendue
/dev/sda5 501760 468860927 468359168 223,3G 83 Linux

La partition 2 ne commence pas sur une frontière de cylindre physique.

Disque /dev/mapper/sda5_crypt : 223,3 GiB, 239783116800 octets, 468326400 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d’E/S (minimale / optimale) : 4096 octets / 4096 octets

Disque /dev/mapper/XXXXXXX–vg-root : 215,4 GiB, 231278116864 octets, 451715072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d’E/S (minimale / optimale) : 4096 octets / 4096 octets

Disque /dev/mapper/XXXXXXX–vg-swap_1 : 7,9 GiB, 8501854208 octets, 16605184 secteurs
Unités : secteur de 1 × 512 = 512 octets
ille de secteur (logique / physique) : 512 octets / 4096 octets
taille d’E/S (minimale / optimale) : 4096 octets / 4096 octets`

Thx for your help

2

Nobody to help me.
Maybe, I can give more informations…

3

this sounds like an issue with the hard drive itself, have you tried reverting to the original drive?

4

First of all, a big thank you, @MrChromebox , for taking an interest in my problem.
no i haven’t tried … but is there any way to test the hard drive and understand what is not working?
I admit that I am a little lazy to dismantle the computer and test the old disk …
Couldn’t it be a problem with bios, EFI or things like that?

5

I would try that first, it’s relatively easy and deterministic. If the old drive works, then the issue is the new drive and you can run various utilities on it to try and determine the issue. if the old drive doesn’t work, then we can look at firmware and other issues external to the drive itself.

6

I tried with the original hard drive and I have no problem starting …
but where does this problem come from? I also tried my hard drive with other laptops and I have no bootloop problem.
Isn’t there security implemented with coreboot? compatibility issue?
What are the possible tests to detect where the problem is coming from? And why does this problem only occur on my librem 13 …?

7

$ sudo hdparm -N /dev/223,6_GiB

I guess that on your SSD: HPA is enabled. If using Kingston SSD, read intensive one, you might find this article helpful (to choose your course of action). As well, you should already be aware that my answer is unofficial. Official one is here:

8

Sorry, but I don’t understant your command line I try this
/dev/sda
and I had
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 468862128/1(468862128?), HPA setting seems invalid (buggy kernel device driver?)

1 Like
9

Good job, but poor result. My drive output is as following:
max sectors = 1000215216/1000215216, HPA is disabled

Now is bit late for myself and your case scenario is something new to me but as first let us both read this topic from forums.gentoo.org, as good starting point, I think. Second reading is here, take a good sleep and inform us in which direction you want to go/proceed.

10

I updated the bios (version 4.12). And since, everything works!

2 Likes