Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-12 Thread Dan Egli
If you have a rescue cd, then you do just what I see you've already done. run fsck against the file sytem and let it fix any errors. As to being in read only mode, HOPEFULLY that's fixed, but if not you can try manually remounting your filesystem: mount / -o remount,rw On 12/12/2020 12:49 PM,

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-12 Thread Dan Egli
You want to add it to the default command line in /etc/default/grub, if it's needed. Frankly, as long as you have ext4 support built in to your kernel (not a module) then I don't think you need it. I've gotten similar warnings on my machines and they've never had a problem loading the root FS. 

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-12 Thread Neil Bothwick
On Fri, 11 Dec 2020 14:36:51 -0700, the...@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)

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-12 Thread thelma
On 12/12/2020 12:32 AM, Dan Egli wrote: > Actually, you have an error or two below. > > On 12/11/2020 6:16 PM, the...@sys-concept.com wrote: >> No, I did not reformat the /boot partition. I just cd to /boot and run: >> rm -r * > Probably better to wipe the file system. But you talk about moving

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-12 Thread thelma
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, the...@sys-concept.com wrote: >> I wipe

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-12 Thread thelma
On 12/12/2020 12:25 PM, Dan Egli wrote: > Hmmm, looks like a missing or corrupted firmware file is failing to > load. Observe: > > On 12/12/2020 11:48 AM, the...@sys-concept.com wrote: >> >> platform regulatory.0: Direct firmware load for regulatory.db failed >> with error -2 >> cfg80211: failed

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-12 Thread Dan Egli
Hmmm, looks like a missing or corrupted firmware file is failing to load. Observe: On 12/12/2020 11:48 AM, the...@sys-concept.com wrote: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 cfg80211: failed to load regulatory.db nvme mvme0: missing or invalid

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-12 Thread thelma
On 12/12/2020 12:32 AM, Dan Egli wrote: > Actually, you have an error or two below. > > On 12/11/2020 6:16 PM, the...@sys-concept.com wrote: >> No, I did not reformat the /boot partition. I just cd to /boot and run: >> rm -r * > Probably better to wipe the file system. But you talk about moving

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-12 Thread Tamer Higazi
Take systemrescuecd and fix your partitions. Let's see what might be the result. best, Tamer On 12/11/20 10:36 PM, the...@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:

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-11 Thread Dan Egli
Actually, you have an error or two below. On 12/11/2020 6:16 PM, the...@sys-concept.com wrote: No, I did not reformat the /boot partition. I just cd to /boot and run: rm -r * Probably better to wipe the file system. But you talk about moving away from EFI in another thread, so we'll just say

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-11 Thread thelma
On 12/11/2020 04:50 PM, Michael wrote: > On Friday, 11 December 2020 22:29:12 GMT the...@sys-concept.com wrote: >> On 12/11/2020 03:06 PM, Jack wrote: >>> On 12/11/20 4:36 PM, the...@sys-concept.com wrote: I wipe the /boot, reinstall kernel, initframes, grub. The system boots, I can

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-11 Thread Michael
On Friday, 11 December 2020 22:29:12 GMT the...@sys-concept.com wrote: > On 12/11/2020 03:06 PM, Jack wrote: > > On 12/11/20 4:36 PM, the...@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

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-11 Thread thelma
On 12/11/2020 03:06 PM, Jack wrote: > On 12/11/20 4:36 PM, the...@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:

Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-11 Thread Jack
On 12/11/20 4:36 PM, the...@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

[gentoo-user] fsck.fat 4.1 - File system couldn't be fixed

2020-12-11 Thread thelma
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