[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 27/10/2021 21:01, comrade meowski wrote: > 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. > > Whoah, hold the phones, there's no need for this kinda tone on the list .. it IS a LUG list, not stackoverflow y'know ..
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
-- The Mailing List for the Devon & Cornwall LUG https://mailman.dcglug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq