Re: Installation fails to recognize SSD

Path	csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	KCB Leigh <kcbl2003@yahoo.co.uk>
Newsgroups	linux.debian.user
Subject	Re: Installation fails to recognize SSD
Date	Fri, 13 May 2022 22:20:01 +0200
Message-ID	<EmJVv-fhap-7@gated-at.bofh.it> (permalink)
References	<EmJVv-fhap-9@gated-at.bofh.it>
X-Mailbox-Line	From debian-user-request@lists.debian.org Fri May 13 20:18:20 2022
Old-Return-Path	<kcbl2003@yahoo.co.uk>
X-Amavis-Spam-Status	No, score=-0.089 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, BODY_8BITS=1.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO_END_DIGIT=0.25, FVGT_m_MULTI_ODD=0.02, RCVD_IN_DNSWL_NONE=-0.0001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
X-Policyd-Weight	NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .yahoo. - helo: .sonic307-54.consmr.mail.ir2.yahoo. - helo-domain: .yahoo.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5
X-Sonic-Dkim-Sign	v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1652472178; bh=dZclJOP9Yi93f028Y5Tf3L/YdPEcWNy2MnM9qLUx4id=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=ig0wgFCVBAepNTN71LB+sFqzOjTdfFCkonlZrWuDkmwUVVHlPNmfewAYucAExQxeO2h7cLt837yGPhWEmH1JMqjyaa/c0hnvBj6SrGxFF5NYQX3+zWVZ9DhMppwW8FTwike656J2p6+YfmLmkxZFMoBkM0rb0uYpnn16fhckMCTrDhtOqqbvbzU20+zlKR/i0hgx7VbcUPGqdHsbSt/RG5NMi6N6Dn0OHdLr22GeSNloEzTU0QG/ui7EIymh73TZp1xXdG4ITvsauZUowP4IpsGb/L619y2Ab6sxTTossewWm9O5g2O+m3V2D3cnejIQ4AGQiYXZ4mNmhrMF7h0/7g==
X-Ymail-Osg	sDVlYRQVM1kl3NiY3PSW_ubbPjyOvxsGP5mTzPt0Ks2ijkzRTO_LNJDUWQC3DC7 LhAXXgIm9D4yDR1DQVKylFdxZQ3mKXV9PapBxwdELgBFQ.Pxhb7IOV7lx0HZ7Cfv86z.7cfdCdgk JzRjxBy7N_6dZOZF1DmGZpPRXqX9wIBg6O6ih4.NQ2F44HWcbJD6mzxiPjKb9F9vRAOIDskDlSbM LPPwo2wIGBwVe3om3Slk6jbbzZzwdQhmNjao49LllMPG0cY.jEMF4sfMDYGRplPeyDOWgzl8aG3o z2qkp62NKEuK7JCkzkWHSM9FND4MzhDwuxqhzp_zQwUDmzVMDUnAYoRMM759LAjoBzKc63PRI1IT LbH9DVMKRjvMHWZHkI5bpJDUHWoLlUhgfZavu3y5NHWmBXVYwvbwqy9_QS1Kctt31w.0y9J3ZemU 8wonHe5gPrdyVE8QPIwTJkp7UweZuLdXdrBKx80hE6ue.tS5M9i6sD9gww2htpFycxTAKZDQuRgU VOKTjXzFbh8XsNk5Qtl_kpY4dY_CYDKzvAPgqhZvnr4LG3McQ5lJyZUZanqKLkAhlZAgIULY1h3o SQF99TRN3STtRMJmfTcAO4O4G83SbsesyR2IMp7c20pV40ymfhBbuWdqZ7b8yVGtyABTqvmky5S0 CbdNefLmBcTb3R3G3hGzBOX2fIfwjpKhbeKd8dDohPiF2jNqFwcxrRJOXYV8ZxN_BrVW.AgDGabh jkDhQLpy8KyRHqS05_5m1VUu5Ft3Uig5RktGF6gE.Hlqx8SD2J_W5GWtl2lEhryMLVduICHxKKbb 3Uly5yABKraMmBdC8nxLvi2AXfdPJMgANrpd4Xcx8.uFkdeVy_r2l1HugEFnVgRBrVrvqLByPmFJ wdCqWJCIEI3vNltnus7tV.iltPXFPQt0.e.WjO0rv.A2ikO9lonljwycJfIhH8IP0_TQ1jKrLMwS D7qjZZVwfmK4in.U5lugjxUtB0CaZvRoacIPkoCKixWgQJnQulgVTlR0SrwzUKWO7NXMQxlC9rmF S5DT50bKA1pRwzJrObfX2p06l3bezCRf0f63d1FRZwXjz7crmlu2ZcIJhnatg4zsIW7P4OoCtPow EQvsyvA9q6LpEnu5RzB46HZMGFjKmhMCpcaOpn_pNe1_PGWySSbc.JXxlPw5R42kBZrCr7q_aiZY MHBgXZvH9VGQqovmCKx0wp5gfWqmOOYVwR2sHggVzgpjVCM.2ItQTprO1.Tf4vee_0id1mdY5Ha2 70HnLSN0d8E4p2QwtpTVDURSUQdMh8549ERMT0baPV9OFr3.f9KgUGqEfzZgPLaeNWkWfdNHdHLT Lntvzf3a6K3m7juFWQpr91FdKO_3t9qpPoqgNHjppGv3LPL7fGw9XKMyg7hNtJEkabO7_DLTI2nn fCnuxcdONCJunMKJIdzvvtm8RQgg8FpYCPLrOSUrWsU89ZwBb2vOVfZMbtTrX.8hA6cQfe.AvxN6 1OqVHhWyNb1Bd9iZKd6VW68_3D3kHMV8XcJOt7J5Kiqu2Z8OGtx1g6lRPq4Z5SfGhu7YowjzWiuu ZsfSmexY2wnwBfYQqtILrOpSUn1_bXpbCjF6BdfS2ZpiiwZvW8BgCD2DKQ9cLahn2au95BXDN2WP bb5.AS6CUcG_gYUMdZ8wuQHV.RmvZ7LmZQ1kJ4DWG5whhTn0nqJIihCAlKzyULmU1O82jZ6ZMsWG Q.yizj1kpQUZgBjq0.ckYxBYE4JXQbxMsM4FEBF7WlHRnKe_dR_myRWy7ApwGce5M241dsN7AKX3 bYhw4o1ggi8Jjvarf7J9VuEX1CFSXxdnxnCDuxSCVfr0RqNFcbMfQEWzsIBwe.CMbvZRK.TjZ6KG PP0cFQyuQrZw.1BTwAph3vGLHj3jLw.RiKvqc2tqEo4fpbaHeFgWVI6L6.0VwJk.Jj3NWTdUY70p NdJfLXHJ2sU0NG6N12d8ce7AXzH4RmgpIwtW_uHX.pBfuqfoXxZZCW8oMlEMVWooi52HA4mf1cyW glxhFtQZRf7XfjcTPVvT3v_IXOGtVA0bxWt.1ueYnr21BP.w_4CPDswevo9EsDk56qkoc5q8sFDP WSstywRStoSuQw_6KHGO5YsgDWyRqd0gnI1_omIjTYV43nBEhiOrMZC2vM.Sap_UulsIiAl5ioAZ Tc_SIy9OxNZEeoEnk40IrADyIWWEReATp0w5GAShDseYtNURUOqWsg1USW3FWOdw5QpDgsVNu98. dw6CMOAyTTxI3MKDbXaPcFbdasG8UUdMM.i7XXB8Fnnk-
X-Sonic-Mf	<kcbl2003@yahoo.co.uk>
Reply-To	KCB Leigh <kcbl2003@yahoo.co.uk>
MIME-Version	1.0
Content-Type	text/plain; charset=UTF-8
Content-Transfer-Encoding	quoted-printable
X-Mailer	WebService/1.1.20188 YMailNorrin
X-Mailing-List	<debian-user@lists.debian.org> archive/latest/789079
List-ID	<debian-user.lists.debian.org>
List-URL	<https://lists.debian.org/debian-user/>
List-Archive	https://lists.debian.org/msgid-search/1424966414.5156725.1652472375927@mail.yahoo.com
Approved	robomod@news.nic.it
Lines	94
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Fri, 13 May 2022 20:06:15 +0000 (UTC)
X-Original-Message-ID	<1424966414.5156725.1652472375927@mail.yahoo.com>
X-Original-References	<1424966414.5156725.1652472375927.ref@mail.yahoo.com>
Xref	csiph.com linux.debian.user:248171

Show key headers only | View raw

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

Back to linux.debian.user | Previous | Next | Find similar | Unroll thread

Thread

Re: Installation fails to recognize SSD KCB Leigh <kcbl2003@yahoo.co.uk> - 2022-05-13 22:20 +0200

csiph-web