Received: from mail.xw3.org (a.xw3.org [5.252.226.107]) by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id 1E30822039A for <~alpine/users@lists.alpinelinux.org>; Mon, 29 Apr 2024 10:43:24 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 3980F940547 for <~alpine/users@lists.alpinelinux.org>; Mon, 29 Apr 2024 12:43:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hanez.org; s=dkim; t=1714387402; h=from:subject:date:message-id:to:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=t4VMEoDKmdhYYpY0t8HiytcYwwEf3edIzbq4c4GH0Kc=; b=Ufaot6wfOtGaufzFRtYKKz5bDelUxbG/VDjkt5l5D1jqaR6N/Zm8hncXw1l496iNmhNjhK rHtVWdc8/iXpz7dsZoa6NqUjWUOf625ocAo404B8wroBWPzaUKV4qREy1i8I94DuA5Zy+t NXRHQv8ki+UJuBDOKRhu/USABGJnlVmH4OmsPV6nTwMyedFCZRP+ff96vjzdvoldP083KA QNml57JOlG0k/2RJjFUg2al3VZ8d9MFcl0BF9HuN86Tn/uKqw8XEheJr0lWREdeodMdPY1 HCFpdZXr0jKasJE2LXa81O1wMcurIumGPKB2n0Cb3kQVvUyhUNSaVxnYOGX9AQ== Date: Mon, 29 Apr 2024 12:43:21 +0200 From: Johannes Findeisen To: ~alpine/users@lists.alpinelinux.org Subject: Re: Long time to prompt for luks password on boot Message-ID: <20240429124321.71ca2581@jupiter> In-Reply-To: <0aa75c72-698b-4b52-88cd-33dab37c66c4@thededem.de> References: <0aa75c72-698b-4b52-88cd-33dab37c66c4@thededem.de> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Last-TLS-Session-Version: TLSv1.3 On Fri, 26 Apr 2024 18:59:26 +0200 thededem 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...