unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <raghavgururajan@disroot.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 43132@debbugs.gnu.org
Subject: bug#43132: [GUIX SYSTEM]: Malfunction
Date: Mon, 31 Aug 2020 23:04:25 -0400	[thread overview]
Message-ID: <c0b89bfe-60be-a0e1-3dca-6f93c9fb5c47@disroot.org> (raw)
In-Reply-To: <20200831231730.021e45f4@scratchpost.org>


[-- Attachment #1.1: Type: text/plain, Size: 456 bytes --]

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?

> What does "sudo dmesg" show around the time it made it read-only?

Ah, I will have to wait until it happens again.

Regards,
RG.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-09-01  3:07 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 [this message]
2020-09-01  7:58     ` Danny Milosavljevic
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=c0b89bfe-60be-a0e1-3dca-6f93c9fb5c47@disroot.org \
    --to=raghavgururajan@disroot.org \
    --cc=43132@debbugs.gnu.org \
    --cc=dannym@scratchpost.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).