Re: Corrupt root filesystem

To: debian-user@lists.debian.org
Subject: Re: Corrupt root filesystem
From: Andy Smith <andy@strugglers.net>
Date: Fri, 7 Jul 2023 18:30:50 +0000
Message-id: <[🔎] ZKhZ2sNI5owL7HS8@use>
In-reply-to: <[🔎] CAJrFWkd62w+ooMGt7C8Q-nnYyanPRM_OahTgKzf+P-xN-ZD4FQ@mail.gmail.com>
References: <[🔎] CAJrFWkc5uxD0E=siEZv+-zFzd9bmv_voFJtr+dyfw5WwuEk9tw@mail.gmail.com> <ZKgthe/Tkr8gJQwX@use> <CAJrFWkfJzynyHK0A-1ODgRhppap+cOmrqt_BupzthpaynTMFng@mail.gmail.com> <[🔎] CAJrFWkd62w+ooMGt7C8Q-nnYyanPRM_OahTgKzf+P-xN-ZD4FQ@mail.gmail.com>

Hi Mick,

On Fri, Jul 07, 2023 at 06:28:55PM +0100, Mick Ab wrote:
> Sorry, I should have said that fsck was manually run on the root
> file system (as advised by the error message) each time that the
> error occurred. On both occasions, the system was rebooted okay.

If you're actually interested in getting advice then I recommend
that you start giving more information such as what actual messages
you see, what exactly you did, how you did it and what result you
got when you did.

Regards,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Reply to:

Follow-Ups:
- Re: Corrupt root filesystem
  - From: John Covici <covici@ccs.covici.com>

References:
- Corrupt root filesystem
  - From: Mick Ab <recoverymail123890@gmail.com>
- Re: Corrupt root filesystem
  - From: Andy Smith <andy@strugglers.net>
- Re: Corrupt root filesystem
  - From: Mick Ab <recoverymail123890@gmail.com>

Prev by Date: Re: why bookworm isn't called deb12?
Next by Date: Re: Corrupt root filesystem
Previous by thread: Re: Corrupt root filesystem
Next by thread: Re: Corrupt root filesystem
Index(es):
- Date
- Thread