[SOLVED] Can't mount /boot. Unknown file system vfat.

[skitches]

I'm not sure if it has gotten to the point where I should just wipe the hard drive and restart.

https://imgur.com/a/slDbfi1

I tried to use wgetpaste to copy and paste here but It's not working. I spent the entire day trying to get it to work. I'm not sure where all of these problems stemmed from. I was basically done with the installation and was about to boot into the desktop but then I had an issue with udev and solving that just created problem after problem.

My wifi/ethernet enp30s0 randomly dissapeared. There used to be a light when I plugged in my ethernet cable now theres no light
I tried to attach a screenshot of ifconfig
Ifconfig shows nothing anymore so I did ifconfig -a and it showed eth0 so I tried connecting to eth0 and it doesn't work at all.
My idea was to just compile another kernel and hopefully it will fix all this
I did make menuconfig to do custom kernel. The original kernel is genkernel
I get the settings and did make && make modules_install && make install
And got error after: -bash: modules_install: command not found
So I can't even use the new kernel
I did eselect kernel list and it wasn't there
I tried to switch into the second kernel to see if it would fix anything. Nope
I try to mount into /boot and now I get unknown filesystem vfat and read only system

I'm still trying to get wgetpaste to work. I hope the images show enough for now

[Zucca]

Looks like your root partition is read-only, thus you cannot make any changes.
You might try

[NeddySeagoon]

skitches,

Welcome to the forums.

Its very rarely that reinstalling Gentoo fixes anything. It won't here.

Your error message

[skitches]

[skitches]

[Hu]

Yes, the shown command remounts the filesystem read-write only until shutdown, so that you can make changes to apply whatever other fixes are needed. It is not expected to persist across reboots. For that, you need to make use of the read-write access to fix the problem(s) that caused root to be read-only.

[Zucca]

[NeddySeagoon]

skitches,

Your problem is your kernel and its modules mismatch. The kernel and its modules are from two different kernel builds.
The kernel detects this and refuses to load the mismatching modules. The VFAT module error is in your image but there are others too.
The rest of the install is good, so there is no need to do it all again, just the kernel build and install.

The trick is to get into a position to do just the kernel rebuild.

You do that by doing the mounting and chroot steps from the handbook and nothing else.
Making partitions, filesystems or unpacking a stage3 will all destroy the good work so far.

Once you are back in the chroot, you are running your Gentoo install on top of the kernel and services provided by the boot media.
Now you can fix just the kernel.

As Zucca says,

[skitches]

Alright update

I figure out how to boot back into livecd.
I do everything normally following the handbook, etc, in the live cd till I get to the kernel
I'm trying to do custom kernel so I do make menuconfig and configure it carefully
and the make && make modules_install && make install
everything goes smoothly

kernel starts compiling
think to myself that the headache is over



https://imgur.com/a/wcYverB

30 minutes after It starts compiling It stops and I get this weird

sh ./arch/x86/boot/install.sh 5.15.80-gentoo \ arch/x86/boot/bzimage System.map "/boot"

I do eselect kernel list and the new kernel isn't there.

[skitches]

[skitches]

While i put the usb back in to get on the live cd
it wouldn't let me go into chroot right away
and it wouldn't let me go into usr/src/linux to compile the kernel
So I thought that I should get another tarball and unpack it.

Would unplugging the usb save everything that was on the system or too late?

[NeddySeagoon]

skitches,

Unpacking the tarball to your Gentoo install overwrites everything there.
If you have done that, your existing install is gone.

Going back to your most recent image, the kernel built and installed.
You exited the chroot, so your kernel is at /mnt/gentoo/usr/src/linux, not /usr/src/linux.
That's normal.

When the live media is running you have two installs, one inside the other.
The outer one is the live media, which is just a toolkit, the inner one, at /mnt/gentoo, which is your install.
When you do

[Zucca]

Like Neddy said:

[skitches]

I'm now having a problem when I load into system
it's saying
Loading Linux 5.15.00 gentoo.....
it's been stuck on it for 10 minutes with nothing happening

[skitches]

[NeddySeagoon]

skitches.

Your kernel is missing frambuffer support, or your DRM kernel module is configured as <*> and missing firmware, or both.

When you leave the chroot after completing your install. You have two different Gentoo installs on your system.
The one you have just completed is on the permanent storage in your system.
The other is the live USB. When you shut down and unplug it, you only have the Gentoo install you have just done.

When the boot fails and you plug the liveUSB in to rescue you non booting Gentoo, your install is still there but its not attached to the liveUSB gentoo yet.
That's what mounting your filesystem tree at /mnt/gentoo does.

Mount your root partition at /mnt/gentoo.
Mount your boot partition at /mnt/gentoo/boot ... the order matters.
Mount /proc /dev and /sys under /mnt/gentoo/ just as the handbook describes.
This is attaching your Gentoo install to the liveCD a piece at a time, so you can fix it.

When you have completed the mounts, do the chroot part of the handbook and your Gentoo will be there, just as it was when you left the chroot.

You may find The PC Boot Process of interest.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[pietinger]

[skitches]

[quote="pietinger"]

[skitches]

[NeddySeagoon]

skitches,

eselect is only a valid command inside the chroot.

Outside of the chroot, use

[pietinger]