Hello,
I have set up an old laptop with alpine (edge) and for a few weeks now
(unfortunately I cannot say since when exactly) it takes quite a while
to prompt for the password for the root partition upon boot. (I have set
up the laptop with full disk encryption with only /boot not being
encrypted.) This is quite annoying.
I disabled silent boot to see what's going on. This is the part of the
log where the boot hangs:
[ 1.701506] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1421a3a8f6f, max_idle_ns: 440795263041 ns
[ 1.701627] clocksource: Switched to clocksource tsc
[ 1.729868] scsi host0: ahci
[ 1.730381] scsi host1: ahci
[ 1.730753] scsi host2: ahci
[ 1.731117] scsi host3: ahci
[ 1.731569] scsi host4: ahci
[ 1.732012] scsi host5: ahci
[ 1.732213] ata1: SATA max UDMA/133 abar m2048@0xe4505000 port 0xe4505100 irq 24
[ 1.732304] ata2: SATA max UDMA/133 abar m2048@0xe4505000 port 0xe4505180 irq 24
[ 1.732390] ata3: DUMMY
[ 1.732453] ata4: DUMMY
[ 1.732517] ata5: SATA max UDMA/133 abar m2048@0xe4505000 port 0xe4505300 irq 24
[ 1.732604] ata6: SATA max UDMA/133 abar m2048@0xe4505000 port 0xe4505380 irq 24
[ 2.044503] ata1: SATA link down (SStatus 0 SControl 300)
[ 2.288173] clocksource: Long readout interval, skipping watchdog check: cs_nsec: 503347556 wd_nsec: 73668891974
[ 2.514896] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2.515226] ata2.00: supports DRM functions and may not be fully accessible
[ 2.515299] ata2.00: ATA-9: Samsung SSD 850 EVO 250GB, EMT03B6Q, max UDMA/133
[ 2.516084] ata2.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 32), AA
[ 2.517186] ata2.00: Features: Trust Dev-Sleep NCQ-sndrcv
[ 2.517569] ata2.00: supports DRM functions and may not be fully accessible
[ 2.519447] ata2.00: configured for UDMA/133
[ 2.529956] scsi 1:0:0:0: Direct-Access ATA Samsung SSD 850 3B6Q PQ: 0 ANSI: 5
[ 2.530827] sd 1:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/233 GiB)
[ 2.530966] sd 1:0:0:0: [sda] Write Protect is off
[ 2.531039] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.531084] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.531240] sd 1:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[ 2.533642] sda: sda1 sda2 sda3 sda4 sda5
[ 2.534160] sd 1:0:0:0: [sda] Attached SCSI disk
[ 2.845422] ata5: SATA link down (SStatus 0 SControl 300)
[ 3.157835] ata6: SATA link down (SStatus 0 SControl 300)
It takes quite a while before showing the "SATA link down (SStatus 0
SControl 300)" messages, so this seems to be the culprit. Is there a way
around this taking so long? Or is this maybe a sign of failing hardware?
Best,
Lukas
On Fri, 26 Apr 2024 18:59:26 +0200
thededem <thededem@thededem.de> wrote:
> Hello,
Hello Lukas,
...
> [sda] Attached SCSI disk [ 2.845422] ata5: SATA link down (SStatus
> 0 SControl 300) [ 3.157835] ata6: SATA link down (SStatus 0
> SControl 300)
>
> It takes quite a while before showing the "SATA link down (SStatus 0
> SControl 300)" messages, so this seems to be the culprit. Is there a
> way around this taking so long? Or is this maybe a sign of failing
> hardware?
to me it looks like a hardware failure at first, but I found this in the
Arch Linux Forum:
https://bbs.archlinux.org/viewtopic.php?id=283906&p=2
Maybe this helps... there it looks like a Kernel update made a SATA
disk unusable with the same error message. The user downgraded the
Kernel and the error was gone. Since I can not reproduce anything here
I don't know if this makes sense but maybe it helps you a bit... ;)
Regards,
Johannes
--
Please do not top post! Answer inline or at the bottom...