From: Danny Milosavljevic <dannym@scratchpost.org>
To: Raghav Gururajan <raghavgururajan@disroot.org>
Cc: 43132@debbugs.gnu.org
Subject: bug#43132: [GUIX SYSTEM]: Malfunction
Date: Tue, 1 Sep 2020 09:58:43 +0200 [thread overview]
Message-ID: <20200901095843.2a2fed41@scratchpost.org> (raw)
In-Reply-To: <c0b89bfe-60be-a0e1-3dca-6f93c9fb5c47@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
Hi,
On Mon, 31 Aug 2020 23:04:25 -0400
Raghav Gururajan <raghavgururajan@disroot.org> wrote:
> Hi Danny!
>
> > Usually that means file-system corruption, which very likely was caused by a
> > hardware (disk) problem. I've had it before, and shortly after the disk died.
>
> Oh no! My disk is a SSD, which is only about 2 years old. Isn't that too
> soon?
>
> Btw, is there a tool to check the health of the disk?
Yes--usually it's a program in the disk firmware.
You can steer it and look at what it did using smartctl (in package
smartmontools).
But I'd advise to check dmesg because it could also be a RAM problem, or a
number of other things.
(UNIX also has fsck to check the filesystem, but it already automatically
does that on reboot when problems arised. So little need to manually
fiddle with that)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-01 7:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 9:48 bug#43132: [GUIX SYSTEM]: Malfunction Raghav Gururajan
2020-08-31 9:53 ` Efraim Flashner
2020-08-31 10:01 ` Raghav Gururajan
2020-08-31 10:39 ` Giovanni Biscuolo
2020-08-31 10:48 ` Raghav Gururajan
2020-08-31 11:11 ` Giovanni Biscuolo
2020-08-31 12:07 ` Julien Lepiller
2020-08-31 12:40 ` Giovanni Biscuolo
2020-08-31 21:17 ` Danny Milosavljevic
2020-09-01 3:04 ` Raghav Gururajan
2020-09-01 7:58 ` Danny Milosavljevic [this message]
2020-09-10 7:56 ` Ludovic Courtès
2020-09-14 15:14 ` Maxim Cournoyer
2020-09-14 19:34 ` Ludovic Courtès
2020-09-15 11:51 ` Raghav Gururajan
2020-09-15 13:31 ` Maxim Cournoyer
2020-09-15 22:13 ` Mark H Weaver
2020-09-15 22:38 ` Raghav Gururajan
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200901095843.2a2fed41@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=43132@debbugs.gnu.org \
--cc=raghavgururajan@disroot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).