From: Hund <lists_gentoo@linuxkompis.se>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] routine maintenance.
Date: Thu, 18 Feb 2021 09:20:54 +0100 [thread overview]
Message-ID: <B512B8A9-2845-422F-B826-81CA5D9E4B22@linuxkompis.se> (raw)
In-Reply-To: <14373b3e-e971-bed4-c70c-6de111dd63fe@verizon.net>
>My waterblock is clogged again, down to a trickle of flow, not bad
>enough to be dangerous at idle but I've had to order some fresh O-rings
>from Germany and will need to rebuild the damn thing again.
Unless you're a hardcore overclocker, there's really no reason to bother with it, especially not today with modern hardware that's running cool with pretty weak cooling to begin with. :)
>Any thoughts about running a drive this old, and what I should be
>looking at as a replacement?
No matter how old or new your disk is, keep your backups current and in working shape.
If it's old, I would just keep an extra eye on the S.M.A.R.T. status and replace it when it's getting close to dying. If you're lucky it will last you for a long time and if you're unlucky it could die any day, which is also to true for any disk.
>Root is a 256gb SATA Samsung SSD, no concerns about lifespan on that
>drive. I hadn't heard of M.2 yet when I bought it...
A SSD is just fine. You're not gaining any performance with a M.2 disk anyway.
--
Hund
next prev parent reply other threads:[~2021-02-18 8:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14373b3e-e971-bed4-c70c-6de111dd63fe.ref@verizon.net>
2021-02-18 6:54 ` [gentoo-user] routine maintenance Alan Grimes
2021-02-18 8:20 ` Hund [this message]
2021-02-18 9:38 ` antlists
2021-02-18 11:10 ` Peter Humphrey
2021-02-18 11:12 ` J. Roeleveld
2021-02-18 20:14 ` Peter Humphrey
2021-02-18 20:42 ` Frank Steinmetzger
2021-02-18 22:13 ` Alan Grimes
2021-02-18 13:12 ` Michael
2021-02-18 15:07 ` John Covici
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B512B8A9-2845-422F-B826-81CA5D9E4B22@linuxkompis.se \
--to=lists_gentoo@linuxkompis.se \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox