Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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, the...@sys-concept.com wrote: 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 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. -- Dan Egli From my Test Server
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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. Oh, and it's not initframes, it is INIT RAM FS (no spaces, of course). For Initial Ram Filesystem. :) On 12/12/2020 12:47 PM, the...@sys-concept.com wrote: I took care of this error, it was about cfg80211 enable wireless support (which I don't have) so I disable it in .config. But when I generate initframes I'm getting a warning: genkernel --install --kernel-config=/usr/src/linux/.config initramfs * WARNING... WARNING... WARNING... * Additional kernel parameters that *may* be required to boot properly: * * With support for several ext* filesystems available, it may be needed to * add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters. Which grub file I edit to add support for "rootfstype=ext4" ? -- Dan Egli From my Test Server
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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) 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. Have you actually booted fully? This looks like the situation when mounting root fails and the initramfs drops you to a console? Does mount show that you partitions from fstab have mounted? -- Neil Bothwick Why is bra singular and pants plural? pgpsxihYqwumr.pgp Description: OpenPGP digital signature
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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 away > from EFI in another thread, so we'll just say that should this happen > again, you should wipe with mkfs. instead of just rm -r. >> >> Yes, this machine is new but I run it for a over 10-days, configured >> most of the programs and it was running without much problems. >> Yesterday, I decided to check some parameters in kernel .config so I run: >> genkernel --menuconfig all >> > Next time, just do this: > > cd /usr/src/linux > make menconfig (or nconfig) > >> * Gentoo Linux Genkernel; Version 4.1.2 >> * Using genkernel configuration from '/etc/genkernel.conf' ... >> * Running with options: --kernel-config=/proc/config.gz all >> >> * Working with Linux kernel 5.4.72-gentoo-x86_64 for x86_64 >> * Using kernel config file '/proc/config.gz' ... >> * >> * Note: The version above is subject to change (depends on config and >> status of kernel sources). >> >> * kernel: >> Initializing ... >> * >> Running 'make clean' ... >> * >> --mrproper is set; Making 'make mrproper' ... >> * >> Will ignore kernel config from '/proc/config.gz' >> * in favor of already existing but different kernel config >> * found in '/usr/src/linux/.config' ... >> * > So you are wrong below. As you can see above, genkernel IS using > /usr/src/linux/.config. I'm not 100% certain, but I THINK genkernel will > compare the config files, and prefer the .config if it is present. >> >> Running 'make oldconfig' ... >> * >> Compiling 5.4.72-gentoo-x86_64 bzImage ... >> >> >> When I exit it it started to compile the kernel (it did not finish) I >> pressed >> "CTRL-C" (interrupted). >> I didn't know then, but running genkernel --menuconfig all >> takes configuration from: >> /etc/kernels/kernel-config-5.4.72-gentoo-x86_64 >> >> not from: /usr/src/linux/.config > No, unless /etc/kernels/kernel-config- is NEWER than .config, > and maybe not even then. See above. >> However, NO FILE HAD CHANGED IN /boot >> But this this is the moment, I couldn't boot correctly. > What was the boot error? >> make && make modules_install >> make install >> genkernel --install --kernel-config=/usr/src/linux/.config initramfs >> grub-install --target=x86_64-efi --efi-directory=/boot >> grub-mkconfig -o /boot/grub/grub.cfg >> >> But nothing had changed. So I tired newer kernel: 5.4.80-gentoo-r1-x86_64 >> But this time I run (without interruptions): >> genkernel --menuconfig all >> grub-mkconfig -o /boot/grub/grub.cfg >> >> And again nothing changed, root "/" still mounts "ro" >> >> findmnt >> TARGET SOURCE FSTYPE OPTIONS >> / /dev/nvme0n1p4 ext4 ro,relatime >> >> Normally it should be: >> findmnt >> TARGET SOURCE FSTYPE OPTIONS >> / /dev/sda4 ext4 >> rw,noatime,data=ordered > Looks like it's not getting to the root remount stage. The kernel will > almost always boot in ro mode. So you're probably getting stuck in the > emergency shell. Can you see your device in /dev? Yes, I can see /dev/nvme0n1p4 (this is root partition) brw-rw root disk /dev/nvme0n1p4 >>> Does dmesg show the drive being recognised, corresponding drivers being >>> loaded, partitions and filesystems recognised? >> cat dmesg |grep error >> doesn't show any errors No, no errors in dmesg >> > What's the last 10 or so lines from dmesg when it fails to boot and goes > to what I'm guessing is the emergency shell? >> I'll try to boot GParted and see what comes up. > > > I don't think gparted is your answer. Sounds to me like something is > causing it to fail in the changeover from your initrd to the actual > drive. If that's the case I bet your partitions are fine. Can you show > us the last 10-15 lines printed on the screen before you get stuck? In dmesg, I see some lines at the end like: findsf (728) used greatest stack depth: 14048 bytes left EXT4-fs (nvme0n1p4): mounted filesystem with ordered data mode. Opts: (null) findsf (728) used greatest stack depth: 13896 bytes left awk (735) used greatest stack depth: 13000 bytes left udevd (682) used greatest stack depth: 13792 bytes left
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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 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. >> >> > >
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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 to load regulatory.db >> nvme mvme0: missing or invalid SUBNQN field >> > I'd say, off my head, that your regulatory.db file has gotten corrupted. > I'd suggest booting from a rescue CD, chrooting into your main > partition, and reinstalling your firmware. It mentions the wireless, of > course (cfg80211) but also it looks like either the firmware or the > driver for your nvme system has gotten corrupted. It's obviously > present, but it's complaining about missing information. You may want to > go ahead and re-compile the kernel and the modules.If you're using > genkernel I'd even go so far as to suggest a mrproper. Just to ensure > that EVERYTHING is cleaned out. Then let genkernel rebuild everything. > Another option, although one I dislike for _purely ascetic_ reasons, > would be to just grab the gentoo-kernel-bin package. That's a > precompiled kernel with a lot of stuff enabled as modules. It could very > well be helpful in getting your system back on it's feet. I took care of this error, it was about cfg80211 enable wireless support (which I don't have) so I disable it in .config. But when I generate initframes I'm getting a warning: genkernel --install --kernel-config=/usr/src/linux/.config initramfs * WARNING... WARNING... WARNING... * Additional kernel parameters that *may* be required to boot properly: * * With support for several ext* filesystems available, it may be needed to * add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters. Which grub file I edit to add support for "rootfstype=ext4" ?
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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 SUBNQN field I'd say, off my head, that your regulatory.db file has gotten corrupted. I'd suggest booting from a rescue CD, chrooting into your main partition, and reinstalling your firmware. It mentions the wireless, of course (cfg80211) but also it looks like either the firmware or the driver for your nvme system has gotten corrupted. It's obviously present, but it's complaining about missing information. You may want to go ahead and re-compile the kernel and the modules.If you're using genkernel I'd even go so far as to suggest a mrproper. Just to ensure that EVERYTHING is cleaned out. Then let genkernel rebuild everything. Another option, although one I dislike for _purely ascetic_ reasons, would be to just grab the gentoo-kernel-bin package. That's a precompiled kernel with a lot of stuff enabled as modules. It could very well be helpful in getting your system back on it's feet. -- Dan Egli From my Test Server
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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 away > from EFI in another thread, so we'll just say that should this happen > again, you should wipe with mkfs. instead of just rm -r. >> >> Yes, this machine is new but I run it for a over 10-days, configured >> most of the programs and it was running without much problems. >> Yesterday, I decided to check some parameters in kernel .config so I run: >> genkernel --menuconfig all >> > Next time, just do this: > > cd /usr/src/linux > make menconfig (or nconfig) > >> * Gentoo Linux Genkernel; Version 4.1.2 >> * Using genkernel configuration from '/etc/genkernel.conf' ... >> * Running with options: --kernel-config=/proc/config.gz all >> >> * Working with Linux kernel 5.4.72-gentoo-x86_64 for x86_64 >> * Using kernel config file '/proc/config.gz' ... >> * >> * Note: The version above is subject to change (depends on config and >> status of kernel sources). >> >> * kernel: >> Initializing ... >> * >> Running 'make clean' ... >> * >> --mrproper is set; Making 'make mrproper' ... >> * >> Will ignore kernel config from '/proc/config.gz' >> * in favor of already existing but different kernel config >> * found in '/usr/src/linux/.config' ... >> * > So you are wrong below. As you can see above, genkernel IS using > /usr/src/linux/.config. I'm not 100% certain, but I THINK genkernel will > compare the config files, and prefer the .config if it is present. >> >> Running 'make oldconfig' ... >> * >> Compiling 5.4.72-gentoo-x86_64 bzImage ... >> >> >> When I exit it it started to compile the kernel (it did not finish) I >> pressed >> "CTRL-C" (interrupted). >> I didn't know then, but running genkernel --menuconfig all >> takes configuration from: >> /etc/kernels/kernel-config-5.4.72-gentoo-x86_64 >> >> not from: /usr/src/linux/.config > No, unless /etc/kernels/kernel-config- is NEWER than .config, > and maybe not even then. See above. >> However, NO FILE HAD CHANGED IN /boot >> But this this is the moment, I couldn't boot correctly. > What was the boot error? >> make && make modules_install >> make install >> genkernel --install --kernel-config=/usr/src/linux/.config initramfs >> grub-install --target=x86_64-efi --efi-directory=/boot >> grub-mkconfig -o /boot/grub/grub.cfg >> >> But nothing had changed. So I tired newer kernel: 5.4.80-gentoo-r1-x86_64 >> But this time I run (without interruptions): >> genkernel --menuconfig all >> grub-mkconfig -o /boot/grub/grub.cfg >> >> And again nothing changed, root "/" still mounts "ro" >> >> findmnt >> TARGET SOURCE FSTYPE OPTIONS >> / /dev/nvme0n1p4 ext4 ro,relatime >> >> Normally it should be: >> findmnt >> TARGET SOURCE FSTYPE OPTIONS >> / /dev/sda4 ext4 >> rw,noatime,data=ordered > Looks like it's not getting to the root remount stage. The kernel will > almost always boot in ro mode. So you're probably getting stuck in the > emergency shell. Can you see your device in /dev? >>> Does dmesg show the drive being recognised, corresponding drivers being >>> loaded, partitions and filesystems recognised? >> cat dmesg |grep error >> doesn't show any errors >> > What's the last 10 or so lines from dmesg when it fails to boot and goes > to what I'm guessing is the emergency shell? >> I'll try to boot GParted and see what comes up. > > > I don't think gparted is your answer. Sounds to me like something is > causing it to fail in the changeover from your initrd to the actual > drive. If that's the case I bet your partitions are fine. Can you show > us the last 10-15 lines printed on the screen before you get stuck? The last 10-15 lines are not showing much but there is more (I'm retyping it from the screen) dmesg: (why the line BOOT_IMAGE is Read Only) Kernel command line: BOOT_IMAGE=/vmlinuz-5.7.72-gentoo root=UUID=d3229... ro platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 cfg80211: failed to load regulatory.db nvme mvme0: missing or invalid SUBNQN field usb 3-4: config 1 has an invalid interface number: 2 but nax is 1 usb 3-4: config 1 has no interface number 1
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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: "(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.
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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 that should this happen again, you should wipe with mkfs. instead of just rm -r. Yes, this machine is new but I run it for a over 10-days, configured most of the programs and it was running without much problems. Yesterday, I decided to check some parameters in kernel .config so I run: genkernel --menuconfig all Next time, just do this: cd /usr/src/linux make menconfig (or nconfig) * Gentoo Linux Genkernel; Version 4.1.2 * Using genkernel configuration from '/etc/genkernel.conf' ... * Running with options: --kernel-config=/proc/config.gz all * Working with Linux kernel 5.4.72-gentoo-x86_64 for x86_64 * Using kernel config file '/proc/config.gz' ... * * Note: The version above is subject to change (depends on config and status of kernel sources). * kernel: >> Initializing ... * >> Running 'make clean' ... * >> --mrproper is set; Making 'make mrproper' ... * >> Will ignore kernel config from '/proc/config.gz' *in favor of already existing but different kernel config *found in '/usr/src/linux/.config' ... * So you are wrong below. As you can see above, genkernel IS using /usr/src/linux/.config. I'm not 100% certain, but I THINK genkernel will compare the config files, and prefer the .config if it is present. >> Running 'make oldconfig' ... * >> Compiling 5.4.72-gentoo-x86_64 bzImage ... When I exit it it started to compile the kernel (it did not finish) I pressed "CTRL-C" (interrupted). I didn't know then, but running genkernel --menuconfig all takes configuration from: /etc/kernels/kernel-config-5.4.72-gentoo-x86_64 not from: /usr/src/linux/.config No, unless /etc/kernels/kernel-config- is NEWER than .config, and maybe not even then. See above. However, NO FILE HAD CHANGED IN /boot But this this is the moment, I couldn't boot correctly. What was the boot error? make && make modules_install make install genkernel --install --kernel-config=/usr/src/linux/.config initramfs grub-install --target=x86_64-efi --efi-directory=/boot grub-mkconfig -o /boot/grub/grub.cfg But nothing had changed. So I tired newer kernel: 5.4.80-gentoo-r1-x86_64 But this time I run (without interruptions): genkernel --menuconfig all grub-mkconfig -o /boot/grub/grub.cfg And again nothing changed, root "/" still mounts "ro" findmnt TARGETSOURCE FSTYPE OPTIONS / /dev/nvme0n1p4 ext4 ro,relatime Normally it should be: findmnt TARGET SOURCE FSTYPE OPTIONS //dev/sda4 ext4rw,noatime,data=ordered Looks like it's not getting to the root remount stage. The kernel will almost always boot in ro mode. So you're probably getting stuck in the emergency shell. Can you see your device in /dev? Does dmesg show the drive being recognised, corresponding drivers being loaded, partitions and filesystems recognised? cat dmesg |grep error doesn't show any errors What's the last 10 or so lines from dmesg when it fails to boot and goes to what I'm guessing is the emergency shell? I'll try to boot GParted and see what comes up. I don't think gparted is your answer. Sounds to me like something is causing it to fail in the changeover from your initrd to the actual drive. If that's the case I bet your partitions are fine. Can you show us the last 10-15 lines printed on the screen before you get stuck? -- Dan Egli From my Test Server
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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 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 [snip] >>> >>> Are you sure that fsck message has anything to do with starting the >>> network? It looks like fsck can't find the open command, so there may >>> be something more wrong than just a read-only /. >> >> I'm using now linux-5.4.72-gentoo, grub only. Install boot loader from >> scratch. >> I only use genkernel to install initframes: >> >> genkernel --install --kernel-config=/usr/src/linux/.config initramfs >> >> No, errors during startup in dmesg. So I have very little to go by. >> Trying "touch 1.txt" >> Read-only file system. >> >> I'm using slim, but I can deal with X later on. >> Something happen to this system and I can not fix it, it is a brand new >> installation, but not reliable :-/ > > When you "wiped /boot" did you reformat the partition? If yes, did you > recreate a filesystem label with the same name as used in your /etc/fstab? No, I did not reformat the /boot partition. I just cd to /boot and run: rm -r * > Is this a brand new kernel image + initramfs, or a kernel image which you > have > used at least once before to boot this machine successfully? Yes, this machine is new but I run it for a over 10-days, configured most of the programs and it was running without much problems. Yesterday, I decided to check some parameters in kernel .config so I run: genkernel --menuconfig all * Gentoo Linux Genkernel; Version 4.1.2 * Using genkernel configuration from '/etc/genkernel.conf' ... * Running with options: --kernel-config=/proc/config.gz all * Working with Linux kernel 5.4.72-gentoo-x86_64 for x86_64 * Using kernel config file '/proc/config.gz' ... * * Note: The version above is subject to change (depends on config and status of kernel sources). * kernel: >> Initializing ... * >> Running 'make clean' ... * >> --mrproper is set; Making 'make mrproper' ... * >> Will ignore kernel config from '/proc/config.gz' *in favor of already existing but different kernel config *found in '/usr/src/linux/.config' ... * >> Running 'make oldconfig' ... * >> Compiling 5.4.72-gentoo-x86_64 bzImage ... When I exit it it started to compile the kernel (it did not finish) I pressed "CTRL-C" (interrupted). I didn't know then, but running genkernel --menuconfig all takes configuration from: /etc/kernels/kernel-config-5.4.72-gentoo-x86_64 not from: /usr/src/linux/.config However, NO FILE HAD CHANGED IN /boot But this this is the moment, I couldn't boot correctly. So after several tries I wipe the /boot, I downloaded standard kernel linux-5.4.72-gentoo run as usual: make && make modules_install make install genkernel --install --kernel-config=/usr/src/linux/.config initramfs grub-install --target=x86_64-efi --efi-directory=/boot grub-mkconfig -o /boot/grub/grub.cfg But nothing had changed. So I tired newer kernel: 5.4.80-gentoo-r1-x86_64 But this time I run (without interruptions): genkernel --menuconfig all grub-mkconfig -o /boot/grub/grub.cfg And again nothing changed, root "/" still mounts "ro" findmnt TARGETSOURCE FSTYPE OPTIONS / /dev/nvme0n1p4 ext4 ro,relatime Normally it should be: findmnt TARGET SOURCE FSTYPE OPTIONS //dev/sda4 ext4rw,noatime,data=ordered > Does dmesg show the drive being recognised, corresponding drivers being > loaded, partitions and filesystems recognised? cat dmesg |grep error doesn't show any errors > Does syslog show any relevant errors? Kernel log, nor error entry either. > Does 'mount' or 'findmnt' show all your partitions? Yes, they are all "rw" except the "/" partition /dev/nvme0n1p4 > Are they mounted as rw? > > These are just some steps you could follow to find out at what stage a > problem > may have occurred and what to check/fix to get it booting successfully. > > PS. These days there are precompiled kernels + initramfs available to get a > system booting quickly, like sys-kernel/gentoo-kernel-bin, before you finesse > a slimmer kernel manually later on - should you ever wish to roll your own by > hand. I'll try to boot GParted and see what comes up.
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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 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. > > > > I fell like I'm shooting at a moving target. Are you using genkernel or > > not? Are you using grub or rEFInd? Is there any interesting error in > > dmesg? Is initframes hopefully just a typo for initramfs? When > > booting, can you see what the boot mgr is doing or trying to do? > > > > You say X is not running - are you using (or trying to use) a display > > manager? You might be better off starting without one, and using a > > command line login before adding the complexity of X. > > > > I'll guess the "none" is the hostname as part of your shell prompt. You > > can "fix" that by setting a hostname for the PC. > > > > Are you sure that fsck message has anything to do with starting the > > network? It looks like fsck can't find the open command, so there may > > be something more wrong than just a read-only /. > > I'm using now linux-5.4.72-gentoo, grub only. Install boot loader from > scratch. > I only use genkernel to install initframes: > > genkernel --install --kernel-config=/usr/src/linux/.config initramfs > > No, errors during startup in dmesg. So I have very little to go by. > Trying "touch 1.txt" > Read-only file system. > > I'm using slim, but I can deal with X later on. > Something happen to this system and I can not fix it, it is a brand new > installation, but not reliable :-/ When you "wiped /boot" did you reformat the partition? If yes, did you recreate a filesystem label with the same name as used in your /etc/fstab? Is this a brand new kernel image + initramfs, or a kernel image which you have used at least once before to boot this machine successfully? Does dmesg show the drive being recognised, corresponding drivers being loaded, partitions and filesystems recognised? Does syslog show any relevant errors? Does 'mount' or 'findmnt' show all your partitions? Are they mounted as rw? These are just some steps you could follow to find out at what stage a problem may have occurred and what to check/fix to get it booting successfully. PS. These days there are precompiled kernels + initramfs available to get a system booting quickly, like sys-kernel/gentoo-kernel-bin, before you finesse a slimmer kernel manually later on - should you ever wish to roll your own by hand. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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: >> 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. > > I fell like I'm shooting at a moving target. Are you using genkernel or > not? Are you using grub or rEFInd? Is there any interesting error in > dmesg? Is initframes hopefully just a typo for initramfs? When > booting, can you see what the boot mgr is doing or trying to do? > > You say X is not running - are you using (or trying to use) a display > manager? You might be better off starting without one, and using a > command line login before adding the complexity of X. > > I'll guess the "none" is the hostname as part of your shell prompt. You > can "fix" that by setting a hostname for the PC. > > Are you sure that fsck message has anything to do with starting the > network? It looks like fsck can't find the open command, so there may > be something more wrong than just a read-only /. I'm using now linux-5.4.72-gentoo, grub only. Install boot loader from scratch. I only use genkernel to install initframes: genkernel --install --kernel-config=/usr/src/linux/.config initramfs No, errors during startup in dmesg. So I have very little to go by. Trying "touch 1.txt" Read-only file system. I'm using slim, but I can deal with X later on. Something happen to this system and I can not fix it, it is a brand new installation, but not reliable :-/
Re: [gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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 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. I fell like I'm shooting at a moving target. Are you using genkernel or not? Are you using grub or rEFInd? Is there any interesting error in dmesg? Is initframes hopefully just a typo for initramfs? When booting, can you see what the boot mgr is doing or trying to do? You say X is not running - are you using (or trying to use) a display manager? You might be better off starting without one, and using a command line login before adding the complexity of X. I'll guess the "none" is the hostname as part of your shell prompt. You can "fix" that by setting a hostname for the PC. Are you sure that fsck message has anything to do with starting the network? It looks like fsck can't find the open command, so there may be something more wrong than just a read-only /.
[gentoo-user] fsck.fat 4.1 - File system couldn't be fixed
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.
