| View previous topic :: View next topic |
| Author |
Message |
dpaddy
Apprentice
Joined: 25 Jun 2008
Posts: 160
|
 Posted: Tue Jun 25, 2024 9:06 pm Post subject: [SOLVED] boot fails: systemd_udev and unknown filesystem.. |
 |
|
I managed to fail (for the third time) an attempt to install gentoo. I conjecture that I somehow installed systemd despite attempting to avoid it. I am too old and tired to begin again for the fourth time. Hopefully someone can help with a fix so I can avoid that.
Booting fails with
| Quote: | Starting systemd_udev version 254
mount: /sysroot: unknown filesystem type 'xfs' |
I'm guessing that systemd-utils is something I inadvertently installed by mistake
| Code: |
livecd /usr/src/linux # emerge --depclean --verbose sys-apps/systemd-utils
Calculating dependencies... done!
sys-apps/systemd-utils-254.13 pulled in by:
virtual/libudev-251-r2 requires >=sys-apps/systemd-utils-251[udev,abi_x86_64(-)]
virtual/tmpfiles-0-r5 requires sys-apps/systemd-utils[tmpfiles]
virtual/udev-217-r7 requires sys-apps/systemd-utils[udev]
>>> No packages selected for removal by depclean
livecd /usr/src/linux # emerge -vp virtual/libudev
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 1.04 s (backtrack: 0/20).
[ebuild R ] virtual/libudev-251-r2:0/1::gentoo USE="-systemd" ABI_X86="(64) -32 (-x32)" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
* IMPORTANT: 18 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
livecd /usr/src/linux # emerge -vp virtual/tmpfiles
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 1.04 s (backtrack: 0/20).
[ebuild R ] virtual/tmpfiles-0-r5::gentoo USE="-systemd" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
* IMPORTANT: 18 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
livecd /usr/src/linux # emerge -vp virtual/udev
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 1.05 s (backtrack: 0/20).
[ebuild R ] virtual/udev-217-r7::gentoo USE="-systemd" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
* IMPORTANT: 18 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
livecd /usr/src/linux # equery u sys-apps/systemd-utils
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for sys-apps/systemd-utils-254.13:
U I
- - abi_x86_32 : 32-bit (x86) libraries
+ + acl : Add support for Access Control Lists
- - boot : Enable systemd-boot (UEFI boot manager)
- - kernel-install : Enable kernel-install
+ + kmod : Enable kernel module loading via sys-apps/kmod
- - python_single_target_python3_10 : Build for Python 3.10 only
- - python_single_target_python3_11 : Build for Python 3.11 only
+ + python_single_target_python3_12 : Build for Python 3.12 only
- - secureboot : Automatically sign efi executables using user specified key
- - sysusers : Enable systemd-sysusers
- - test : Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)
+ + tmpfiles : Enable systemd-tmpfiles
+ + udev : Enable systemd-udev (userspace device manager)
- - ukify : Enable systemd-ukify
|
The above indicates (or so I thought) that whatever pulls in sys-apps/systemd-utils has USE="-systemd" so I have no clue as to why sys-apps/systemd-utils was pulled in (though perhaps I emerged it by mistake). In any case, attempting to remerge sys-apps/systemd-utils with flags -tmpfiles -udev (as they make reference to systemd) fails -- though I can't imagine why I would want it anyhow, and I am afraid to attempt removing all of virtual/libudev, virtual/tmpfiles, virtual/udev, and sys-apps/systemd-utils.
My ruminations regarding sys-apps/systemd-utils is likely BS as I don't know what I'm doing 
Last edited by dpaddy on Tue Jun 25, 2024 11:18 pm; edited 1 time in total |
|
| Back to top |
|
 |
pingtoo
Veteran
Joined: 10 Sep 2021
Posts: 1248
Location: Richmond Hill, Canada
|
| Posted: Tue Jun 25, 2024 9:31 pm Post subject: |
|
|
dpaddy,
This is a quick respond, just to help reduce stress.
Don't worry about systemd-utils for now, I think it is part of stage3, it should have correct USE flag. (if you wish to know more about this, we can discuss it later)
Do you actually use xfs for your root file system?
Can you share your kernel command line?
I am guessing you use some kind of kernel build/install (i.e. genkernel or dracut, etc) so does it also generated a initramfs file? |
|
| Back to top |
|
|
dpaddy
Apprentice
Joined: 25 Jun 2008
Posts: 160
|
| Posted: Tue Jun 25, 2024 9:58 pm Post subject: |
|
|
Disks are as follows
| Code: |
Disk /dev/sdb: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000NM019B-2TG
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: B89829F6-D6BB-4F54-92CB-060A0B6537B7
Device Start End Sectors Size Type
/dev/sdb1 2048 6293503 6291456 3G EFI System
/dev/sdb2 6293504 140511231 134217728 64G Linux swap
/dev/sdb3 140511232 11721045134 11580533903 5.4T Linux root (x86-64)
---------------------------------------------------------------------------
livecd ~ # gdisk -l /dev/sdb
GPT fdisk (gdisk) version 1.0.9
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 11721045168 sectors, 5.5 TiB
Model: ST6000NM019B-2TG
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): B89829F6-D6BB-4F54-92CB-060A0B6537B7
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 2048, last usable sector is 11721045134
Partitions will be aligned on 2048-sector boundaries
Total free space is 0 sectors (0 bytes)
Number Start (sector) End (sector) Size Code Name
1 2048 6293503 3.0 GiB EF00
2 6293504 140511231 64.0 GiB 8200
3 140511232 11721045134 5.4 TiB 8304
---------------------------------------------------------------------------
livecd ~ # lsblk -f /dev/sdb
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sdb
├─sdb1 vfat FAT32 EB14-1558
├─sdb2 swap 1 bebaf74b-087a-443a-b770-208475cd4854
└─sdb3 xfs 5273f9a6-2f0a-4433-99b8-b1f58d7ef38d 5.4T 0% /mnt/gentoo
|
I performed Manual configuration of the kernel, followed by | Code: | | make && make modules_install |
and then
According to Gentoo Linux amd64 Handbook: Installing Gentoo: | Quote: | | Installkernel can automatically generate an initramfs when installing the kernel if the dracut USE flag is enabled |
and I have sys-kernel/installkernel installed | Code: | livecd /usr/src/linux # emerge -vp sys-kernel/installkernel
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 1.05 s (backtrack: 0/20).
[ebuild R ] sys-kernel/installkernel-38::gentoo USE="dracut grub (-efistub) -refind -systemd -systemd-boot -uki -ukify" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB |
Moreover
| Code: | livecd /usr/src/linux # ls /boot
System.map-6.6.30-gentoo config-6.6.30-gentoo grub initramfs-6.6.30-gentoo.img vmlinuz-6.6.30-gentoo
|
I'm using grub
| Code: | livecd /usr/src/linux # emerge -vp sys-boot/grub
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 1.54 s (backtrack: 0/20).
[ebuild R ] sys-boot/grub-2.12-r4:2/2.12-r4::gentoo USE="fonts nls sdl themes truetype -device-mapper -doc -efiemu -libzfs -mount (-test) -verify-sig" GRUB_PLATFORMS="efi-64 -coreboothistory -efi-32 -emu -ieee1275 (-loongson) -multiboot -pc -qemu (-qemu-mips) -uboot -xen -xen-32 -xen-pvh" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
|
and | Code: | (chroot) livecd /opt # more /etc/default/grub
# Copyright 1999-2020 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
#
# To populate all changes in this file you need to regenerate your
# grub configuration file afterwards:
# 'grub-mkconfig -o /boot/grub/grub.cfg'
#
# See the grub info page for documentation on possible variables and
# their associated values.
GRUB_DISTRIBUTOR="Gentoo"
# Default menu entry
#GRUB_DEFAULT=0
# Boot the default entry this many seconds after the menu is displayed
#GRUB_TIMEOUT=5
#GRUB_TIMEOUT_STYLE=menu
# Append parameters to the linux kernel command line
#GRUB_CMDLINE_LINUX=""
#
# Examples:
#
# Boot with network interface renaming disabled
GRUB_CMDLINE_LINUX="rootfstype=xfs net.ifnames=0"
#
# Boot with systemd instead of sysvinit (openrc)
# GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd"
# Append parameters to the linux kernel command line for non-recovery entries
#GRUB_CMDLINE_LINUX_DEFAULT=""
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal.
# Note that you can use only modes which your graphic card supports via VBE.
# You can see them in real GRUB with the command `vbeinfo'.
#GRUB_GFXMODE=640x480
# Set to 'text' to force the Linux kernel to boot in normal text
# mode, 'keep' to preserve the graphics mode set using
# 'GRUB_GFXMODE', 'WIDTHxHEIGHT'['xDEPTH'] to set a particular
# graphics mode, or a sequence of these separated by commas or
# semicolons to try several modes in sequence.
#GRUB_GFXPAYLOAD_LINUX=
# Path to theme spec txt file.
# The starfield is by default provided with use truetype.
# NOTE: when enabling custom theme, ensure you have required font/etc.
#GRUB_THEME="/boot/grub/themes/starfield/theme.txt"
# Background image used on graphical terminal.
# Can be in various bitmap formats.
#GRUB_BACKGROUND="/boot/grub/mybackground.png"
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to kernel
#GRUB_DISABLE_LINUX_UUID=true
# Comment if you don't want GRUB to pass "root=PARTUUID=xxx" parameter to kernel
GRUB_DISABLE_LINUX_PARTUUID=false
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY=true
# Uncomment to disable generation of the submenu and put all choices on
# the top-level menu.
# Besides the visual affect of no sub menu, this makes navigation of the
# menu easier for a user who can't see the screen.
#GRUB_DISABLE_SUBMENU=y
# Uncomment to play a tone when the main menu is displayed.
# This is useful, for example, to allow users who can't see the screen
# to know when they can make a choice on the menu.
#GRUB_INIT_TUNE="60 800 1"
|
|
|
| Back to top |
|
|
dpaddy
Apprentice
Joined: 25 Jun 2008
Posts: 160
|
| Posted: Tue Jun 25, 2024 11:17 pm Post subject: |
|
|
I'm a complete idiot... the kernel was not built for xfs. Recompiled with proper setting and boots fine now. Sorry to be wasting everyones time  |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22672
|
| Posted: Wed Jun 26, 2024 12:18 am Post subject: |
|
|
| dpaddy wrote: | | The above indicates (or so I thought) that whatever pulls in sys-apps/systemd-utils has USE="-systemd" so I have no clue as to why sys-apps/systemd-utils was pulled in (though perhaps I emerged it by mistake). In any case, attempting to remerge sys-apps/systemd-utils with flags -tmpfiles -udev (as they make reference to systemd) fails -- though I can't imagine why I would want it anyhow, and I am afraid to attempt removing all of virtual/libudev, virtual/tmpfiles, virtual/udev, and sys-apps/systemd-utils. |
Removing virtuals via emerge --depclean should be safe, though I expect that Portage will refuse your request. Standard system builds require tmpfiles and udev. You will need to go a fair distance out of your way to eliminate them.
As to systemd-utils, we have had quite a few threads where people get very upset over this package. This package is not systemd. It is a collection of programs that the systemd maintainers decided to absorb into systemd, but which can be built and used independently of systemd. Some, such as udev, are sufficiently entrenched on modern systems that removing it will require substantial compromises on functionality elsewhere. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Installing Gentoo
