[ Date Index ]
[ Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
Re: [LUG] Blinking Problem
- To: David Bell <grimpen@xxxxxxxxxxxxxxxxx>
- Subject: Re: [LUG] Blinking Problem
- From: comrade meowski <mr.meowski@xxxxxxxx>
- Date: Wed, 27 Oct 2021 21:01:22 +0100
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Rjqk3tdKI1zJjLKPX8N7ZauQlGoDN7Xm129YbrY67A0=; b=cGsG9/C/OdNyzjj21eA/e7O83Up9QfMze9ttSyWEy2c7CWzyWNtFS4bQ8QHAWWyVZH/WjdrQjCYuuaCq/yytgO/SBfzg1TAL0JFc1H3dfvSV3yd088T6cYPMo0SNiFkJSMOiFjAvSsvzukgLegbims/FaWxXHa7LoavA4qKDEnFvFTFNq/NFnyirWIo2TRBjDjf7iuubY4C16VxLzXs7Pgp9OdnyqtNo6gbTCvS4HKSJEOilm6Ihz6XBZSMhWkKUNNdqbyLdKnee1F+RlkBD9mTqfJfTWeyTTr9pGGKLITx6tIB1ze2KBvDAySys7DOvD07kIegFI78CRt/X7yOyjw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jvg7X9dOKA9ce6nwQLTdQ8yS/uU9ClAd5CxBjy7jWWwcF+4OxDxGa5H4iutiI86w31xl49uyS/AE5kDQxhUkzdRlGGhv8LkdNFtx4g7lK6vT+KF0xA/rHK15kllEsSHTrJGEfBW9sehvZawMxo2Es5qP/0WnOLgQPIt5my5/1QJnY6dEbQWitp3EP4b+s5VkjI3uxYhe7BSioHk5OWj2q8vC+rs0RsJr4td0+QLJ/RpylqRfGRohPFR907Tbzydg57m2mGgwl9k8Pjouk8ZoXcA8+jXptPAWIT/k7NMtnjnFQmkhmeu5KJFUr54Dez5iv7/wfnDLPyHb1KWRptZ2zw==
- Cc: list@xxxxxxxxxxxxx
- Content-language: en-GB
- Delivered-to: dclug@xxxxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dcglug.org.uk; s=1633856761; h=Sender:Content-Type: Content-Transfer-Encoding:Cc:Reply-To:List-Subscribe:List-Help:List-Post: List-Unsubscribe:List-Id:Subject:MIME-Version:In-Reply-To:From:References:To: Date:Message-ID:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner:List-Archive; bh=fV9/ZisGVTFE0wARPzAR6gRRU0saL4L2VbLUIkI30LA=; b=M/FcP54qo87L6aRmQ7uBjjvLJ cKa01y7B2nr+bk2ioc2A4C/uARAKTB3bm6Jcme2KSmvSajnBEgLz2a+/Br3VLVKxTUNscigH8YmF8 INH9Iopolxetp+A9gxE5DJnjW2tQto42a4CXtsAdmGLtVdCY1E06oOmGm7KdNA3doJD0c=;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=live.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Rjqk3tdKI1zJjLKPX8N7ZauQlGoDN7Xm129YbrY67A0=; b=Xde5jRK1cLXfDSNEG0SNS8a/0vcWrg5PCgX1cC0pzsgPfVl4mGfBOhnLJUq59NehZVruS6ywqsZtWNgGqDwLkLBDcD0l++hjTiYQryTTgELzBFkhfThWywCtqVNDL7Jm83DzHLnbgyYD/+ar7sQ0l821nyE8j2HEvYF3nhDaArYH9kmHi9iReyxyplpLx6DPq3jdrs2QGYqNG3HrN7M3A2tIEZO1WkPDkon74Zr+Cg+LoXhEk8vfLU1epJ5LPQhIoZMXNHNRpmIY8/vSacUz7idLvzV86qju1xyM7sB9jKsL71A8/nMT0GULQxH914NL4ObuezfxvQFVEGTCVozG6Q==
On 27/10/2021 20:22, David Bell wrote:
On Wed, 27 Oct 2021 18:43:09 +0100
comrade meowski <mr.meowski@xxxxxxxx> wrote:
Yes. I would like to know why you've constituted this as a "problem"?
Your computer's operating system unsurprisingly requires periodic
disk access.
For a start in nigh on 30 years I've never had this before. Periodic
disk access is one thing but a regular constant single blink is
something different.
Fair enough but I've been a professional sysadmin for nearly that long
and there's a reason why you're the one posting on the list looking for
help... and I'm the one posting on the list providing answers for your
questions.
This is a conceptual rather than a practical issue: you've jumped to an
entirely unsupported conclusion (something is "wrong" with my SSD) from
the slimmest of high level clues (periodic flashing of the disk access
LED). You have yet to demonstrate any causal connection so this is
invalid reasoning.
The rest of my advice stands: if you really want to know what's at the
bottom of this you'll need to interrogate your system properly using the
correct tools as advised.
Be warned: you are failing to account for well, basically everything.
Your IO scheduler may be batching up disk access to burst more
efficiently to the SSD. A broken systemd timer unit might be simply
firing continuously due to a failed condition in which case it will be
in the logs. A service may have recently changed it's behaviour - by
your own admission you recently upgraded your entire operating system
version.
You are not a magician who can intuit deep hardware issues by glancing
at Das Blinkenlights on the front of your case! Your system has logs and
IO management, tuning and reporting tools for a reason: use them. Read
the SMART data from the SSD. Have you even checked dmesg?
If there is a fault it will be glaringly and immediately obvious -
doubly so if a full on disk failure is imminent. This is Linux remember,
you don't need to pull random unsubstantiated guesses out of the ether.
Ask your computer nicely and it will tell you exactly what it's up to,
you just need to know how to ask it the right questions. Linux has no
secrets from UID 0.
--
The Mailing List for the Devon & Cornwall LUG
https://mailman.dcglug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/listfaq
