Re: Installation fails to recognize SSD
Message-id: <[🔎] [🔎] alpine.DEB.2.21.2205121632130.1910@Asus1>
In-reply-to: <[🔎] [🔎] CAP1wdQsgJZY9x=8+OLByxjGguXJFdASTne0YYyG1MH3JiC8+Xg@mail.gmail.com>
References: <[🔎] [🔎] CAP1wdQs=a4HhZV4k8PG=_RJOxLht4PNm9H69unGATAHxUSYk5Q@mail.gmail.com> <[🔎] [🔎] d93c2fb1-7ec4-2935-7855-0b6f68bf0ab7@holgerdanske.com> <[🔎] [🔎] CAP1wdQsgJZY9x=8+OLByxjGguXJFdASTne0YYyG1MH3JiC8+Xg@mail.gmail.com>
I really want to thank you all for this advice: it solved a problem with which I've been struggling for MONTHS!!
My Computer: ACER ASPIRE 514-54
BIOS/UEFI SETUP: INSYDE vers. 1.17
Internal Storage:
- HDD0: 256GB Western Digital WDC PC SN530 SDBPNPZ-256G-1114 NVMe solid state storage (SSD)
- HDD1: 1000GB Western Digital Blue WDC WD10SPZX-00Z10T0 Hard disk (HDD)
Operating System. installed on USB stick:
- Linux cpe-67-241-65-193 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 GNU/Linux
(Debian 11, installed from the CD image with non-free firmware)
MY PROBLEM: was somewhat different to Mr Bruno Schneiders: whilst the internal NVMe drive on my machine
WAS visible to the DEBIAN installer & DEBIAN OS on external drives connected to USB ports, the INTERNAL
HARD DISK was not visible to either, & booting the machine with any DEBIAN OS took a long time (the delay
occurred before the fsck step of the boot process). The reason that the boot process took so long is that the machine
could not access the pci bridge (10000:e0:1c.4) & hence, could not access the SATA controller (10000:e0:17.0):
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 1.138746] pcieport 10000:e0:1c.4: can't derive routing for PCI INT A
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 1.138747] nvme 10000:e1:00.0: PCI INT A: no GSI
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 1.141351] ahci 10000:e0:17.0: version 3.0
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 1.141360] ahci 10000:e0:17.0: can't derive routing for PCI INT A
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 1.141360] ahci 10000:e0:17.0: PCI INT A: no GSI
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 1.141446] ahci 10000:e0:17.0: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 1.141448] ahci 10000:e0:17.0: flags: 64bit ncq sntf pm clo only pio slum part deso sadm sds
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 1.141618] scsi host0: ahci
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 1.141701] scsi host1: ahci
resulting in repeated unsuccessful attempts to access the drive:
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 6.656323] ata1.00: qc timeout (cmd 0xec)
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 6.657434] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 6.972824] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 17.152287] ata1.00: qc timeout (cmd 0xec)
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 17.153480] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 17.153495] ata1: limiting SATA link speed to 3.0 Gbps
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 17.468760] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Mar 5 12:53:33 cpe-67-241-65-193 kernel: [ 48.128329] ata1.00: qc timeout (cmd 0xec)
After reading your advice, I went to the MAIN menu of the InsydeH2O setup utility, typed Control-S as Mr Felmon Davis suggested.
This caused the option:
VMD Controller [Enabled]
to appear (Intel Volume Management Device). This is a different option to the one described by Mr David Christiansen, but
when I disabled this, the internal hard disk was visible to the DEBIAN OS, & there were no delays during the boot process!
I had noticed that the UBUNTU OS WAS able to access the internal hard disk, because it used some method to access the
pci bridge 'behind VMD':
UBUNTU: 10000:e0:1c.4: enable ASPM for pci bridge behind vmd
but I did not know how to access the VMD setting until I read your posts. I am VERY GRATEFUL FOR YOUR HELP!!
With many thanks,
Ken
Reply to: