public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: thelma@sys-concept.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
Date: Sat, 12 Dec 2020 12:49:01 -0700	[thread overview]
Message-ID: <90ea6ab8-a3e9-3836-f16c-38018316d6b6@sys-concept.com> (raw)
In-Reply-To: <e02f743a-0a3f-6484-13c9-6006eb21e49e@googlemail.com>

How to to fix it?  I can bootstrap from USB but what command to run it?

On 12/12/2020 03:59 AM, Tamer Higazi wrote:
> Take systemrescuecd and fix your partitions.
> 
> Let's see what might be the result.....
> 
> 
> best, Tamer
> 
> On 12/11/20 10:36 PM, thelma@sys-concept.com wrote:
>> I wipe the /boot, reinstall kernel, initframes, grub.
>> The system boots, I can login as root but X is not running,
>> the command is displaying:  "(none) /#"
>>
>> When I try to start the network I get:
>> fsck.fat 4.1 (2017-01-24) open: no such file or directory
>> Filesystems couldn't be fixed
>> ERROR: fsck failed to start
>>
>> It seems to me "/" file system mount in "read only" mode.
>> When I try to emerge anything I get: /var/log/emerge.log Read-only file
>> system.
>>
>>
> 
> 


  reply	other threads:[~2020-12-12 19:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 21:36 [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed thelma
2020-12-11 22:06 ` Jack
2020-12-11 22:29   ` thelma
2020-12-11 23:50     ` Michael
2020-12-12  1:16       ` thelma
2020-12-12  7:32         ` Dan Egli
2020-12-12 18:48           ` thelma
2020-12-12 19:25             ` Dan Egli
2020-12-12 19:47               ` thelma
2020-12-13  0:04                 ` Dan Egli
2020-12-12 20:24           ` thelma
2020-12-12 10:59 ` Tamer Higazi
2020-12-12 19:49   ` thelma [this message]
2020-12-13  0:06     ` Dan Egli
2020-12-12 22:40 ` Neil Bothwick
2020-12-13  3:07   ` [gentoo-user] [SOLVED] fsck.fat 4.1 - File system couldn't be fixed [SOLVED] thelma
2020-12-13  6:00     ` Victor Ivanov
2020-12-13  7:42       ` thelma
2020-12-13  7:57         ` [gentoo-user] How to config nullmailer bobwxc
2020-12-13 13:33         ` [gentoo-user] [SOLVED] fsck.fat 4.1 - File system couldn't be fixed [SOLVED] Victor Ivanov
2020-12-14  6:07           ` thelma
2020-12-14 12:06             ` Michael
2020-12-13 14:17         ` Michael
2020-12-13 14:33           ` Neil Bothwick
2020-12-13 15:02           ` Victor Ivanov
2020-12-13 16:52             ` Neil Bothwick
2020-12-14  5:41           ` Thomas Mueller
     [not found]           ` <20201214054146.415BCE0A03@pigeon.gentoo.org>
2020-12-14 10:02             ` Michael
     [not found]           ` <20201214054146.0CC61E09F5@pigeon.gentoo.org>
2020-12-14 10:09             ` Wols Lists

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=90ea6ab8-a3e9-3836-f16c-38018316d6b6@sys-concept.com \
    --to=thelma@sys-concept.com \
    --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