| View previous topic :: View next topic |
| Author |
Message |
hal8000
n00b
Joined: 27 Mar 2025
Posts: 13
|
 Posted: Mon Mar 31, 2025 1:13 pm Post subject: Messed up Install System query on dev-disk-by [SOLVED] |
 |
|
Finished my install of Gentoo over 2 days.
Bootloader is Grub in mbr. BIOS not UEFI
Init system is systemd
Cinnamon desktop with Pulseaudo
gentoo-kernel-bin
initramfs created Dracut
Install was stage 3 minimal install with systemd and desktop (780M) :
https://distfiles.gentoo.org/releases/amd64/autobuilds/current-install-amd64-minimal/
Hardware Intel i5 CPU 2.8G, 8G DDR3, old AMD FX5750 graphics
SATA drives.
Im currently running a few other linux distributions and installed Gentoo with 40G /,
60G /home and 16G /swap
| Quote: | cat /etc/fstab
UUID=9b73ae1d-1ce3-454e-ad84-a608c283d14a / xfs rw,relatime 0 1
UUID=e49806ad-9da3-4107-957e-f82e4407e3b9 /home xfs rw,relatime 0 2
#UUID=4b29bccc-4833-4353-ad82-46b56e5f773d none swap sw 0 0 |
My original mistakes were changing the UUID of swap partition, not creating the /etc/fstab properly
(entrries were commented out) resulting in unable to login.
I changed UUID of swap partition back to 4b29bccc-4833-4353-ad82-46b56e5f773d as my other distros
use that partition.
All is working well, desktop reached in under 13 seconds on a SATA hard disk.
| Quote: | systemd-analyze
Startup finished in 1.277s (kernel) + 4.390s (initrd) + 12.660s (userspace) = 18.328s
graphical.target reached after 12.659s in userspace. |
However systemd-analyze blame has 660 entries mainly dev-disk-by-2x
| Quote: | 11.798s dev-disk-by\x2duuid-61a01fd1\x2d4953\x2d405e\x2da6d4\x2db597b41b9410.device
11.798s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d3.0\x2dpart-by\x2dpartlabel-Debian11.device
11.798s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d3.0\x2dpart10.device
11.798s dev-disk-by\x2dpartlabel-Debian11.device
11.798s dev-disk-by\x2did-ata\x2dST1000DM003\x2d1SB10C_Z9A101KS\x2dpart10.device
11.798s dev-sdc10.device
11.798s dev-disk-by\x2did-wwn\x2d0x5000c50087cba496\x2dpart10.device
11.798s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d3.0\x2dpart-by\x2dlabel-Debian.device
11.798s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d3.0\x2dpart-by\x2dpartuuid-146337ff\x2d4922\x2d4100\x2db509\x2dc0be0bd3e769.de>
11.798s dev-disk-by\x2dlabel-Debian.device
11.798s dev-disk-by\x2dpartuuid-146337ff\x2d4922\x2d4100\x2db509\x2dc0be0bd3e769.device
11.798s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d3.0\x2dpart-by\x2dpartnum-10.device
11.798s dev-disk-by\x2ddiskseq-3\x2dpart10.device
--snip--
1.057s dbus.service
978ms lightdm.service
957ms systemd-networkd.service
943ms accounts-daemon.service
726ms systemd-journal-flush.service
623ms systemd-tmpfiles-setup-dev-early.service
473ms systemd-udevd.service
333ms systemd-tmpfiles-setup.service
301ms systemd-modules-load.service
297ms systemd-udev-trigger.service
259ms systemd-remount-fs.service
237ms polkit.service
224ms modprobe@fuse.service
209ms systemd-logind.service
192ms systemd-random-seed.service
189ms upower.service
151ms systemd-sysctl.service
140ms systemd-udev-load-credentials.service
136ms systemd-journald.service
125ms systemd-networkd-persistent-storage.service
118ms initrd-parse-etc.service
107ms dev-hugepages.mount
106ms dev-mqueue.mount
105ms sys-kernel-debug.mount
104ms sys-kernel-tracing.mount
103ms tmp.mount
86ms systemd-tmpfiles-clean.service
82ms alsa-restore.service
82ms kmod-static-nodes.service
82ms modprobe@drm.service
81ms dracut-shutdown.service
66ms systemd-tmpfiles-setup-dev.service
60ms systemd-network-generator.service
57ms systemd-update-utmp.service
57ms dracut-cmdline.service
42ms systemd-user-sessions.service
41ms systemd-vconsole-setup.service
40ms initrd-udevadm-cleanup-db.service
40ms sys-fs-fuse-connections.mount
37ms dracut-pre-udev.service
37ms user-runtime-dir@1000.service
29ms systemd-fsck-root.service
22ms modprobe@configfs.service
21ms initrd-cleanup.service
9ms systemd-sysusers.service
7ms modprobe@dm_mod.service
7ms modprobe@loop.service
|
There are a huge amount of entries starting dev-disk-by-2x
Googling dev-disk-by-2x shows various problems realting to changing UUID of swap and other partitions.
I have commented out my /swap partition but still massive entries.
Reading the Dracut Wiki:
https://wiki.gentoo.org/wiki/Dracut
There is a module called lunmask
Masks LUN devices to select only ones which required to boot
I've added it /etc/dracut.conf.d/ as lunmask.conf
| Quote: |
cat lunmask.conf
add_dracutmodules+=" lunmask "
|
Should lunmask mask the entries in system-analyze blame ?
Can't find a man page for lunmask
I created another initramfs but still get a flood of entries.
I've had the same problem in Fedora, Suse, and Endeavour which
all use Dracut (massive amount of entries ) but not in Arch Linux,
or Linux Mint where the ramdisk is created without dracut.
I would like to suppress entries in systemd for partitions that are not in use, if possible.
Because of all the errors I made in the install, is it better to reinstall?
Its a new Gentoo install, so I have no data to loose.
Thanks in advance..
Last edited by hal8000 on Tue Apr 01, 2025 10:20 pm; edited 2 times in total |
|
| Back to top |
|
 |
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 245
|
| Posted: Mon Mar 31, 2025 3:47 pm Post subject: Re: Messed up Install System query on dev-disk-by |
|
|
| hal8000 wrote: |
I've had the same problem in Fedora, Suse, and Endeavour which
all use Dracut (massive amount of entries ) but not in Arch Linux,
or Linux Mint where the ramdisk is created without dracut.
I would like to suppress entries in systemd for partitions that are not in use, if possible.
Because of all the errors I made in the install, is it better to reinstall?
Its a new Gentoo install, so I have no data to loose.
Thanks in advance.. |
If you want something that does much less, ugrd may do what you want. I think a lot of that stuff is udev stuff, and ugrd avoid using udev. Ugrd will only activate/mount filesystems absolutely needed to boot. Anything else can generally be handled by the "real" init, later.
As a side note, I think \x2d = "-", ascii hex encoded.
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
hal8000
n00b
Joined: 27 Mar 2025
Posts: 13
|
| Posted: Mon Mar 31, 2025 9:03 pm Post subject: |
|
|
| Thank you so much, I'll check this out, and thank you for writing a very well thought out Wiki page. |
|
| Back to top |
|
|
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 245
|
| Posted: Mon Mar 31, 2025 9:59 pm Post subject: |
|
|
| hal8000 wrote: | | Thank you so much, I'll check this out, and thank you for writing a very well thought out Wiki page. |
You're welcome, I hope this can, at the very least, provide another working example to help you see which parts of the boot process are essential. I don't think ugrd will work well with systemd-analyze, like you won't be able to profile each portion of what happens in ugrd, but it shouldn't do anything to obfuscate the start/stop times. When testing, I generally look for lines in the kernel log which indicate when key events happened.
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
hal8000
n00b
Joined: 27 Mar 2025
Posts: 13
|
| Posted: Tue Apr 01, 2025 11:07 am Post subject: |
|
|
Hi zen_desu,
I followed the Wiki page and installed ugrd.
https://wiki.gentoo.org/wiki/UgRD
After the initial ugrd a python error was thrown out, unable to get block ID info.
I copied this on paste bin as its quite long:
https://pastebin.com/mtzhN0D2
I ran command as root and output was produced:
blkid -i /dev/sdc
/dev/sdc: MINIMUM_IO_SIZE="4096" PHYSICAL_SECTOR_SIZE="4096" DISKSEQ="3" LOGICAL_SECTOR_SIZE="512"
So I ran ugrd again and this time it worked and produced a compressed image in /tmp/initramfs as per wiki.
The Wiki does not state what to do with the file in /tmp/initramfs
I backed up my original initramfs.img and renamed the image in /tmp/initramfs as ugrd.img and moved to /boot.
In grub I modified the initrd line to refelect the new initramfs and it worked!
| Code: | | initrd /boot/amd-uc.img /boot/ugrd.img |
All the entries probing disb-by-id are gone.
systemd-analyze blame
| Quote: |
3.312s dev-sdc22.device
2.806s udisks2.service
1.674s alsa-restore.service
1.561s dbus.service
1.486s lightdm.service
1.290s systemd-tmpfiles-setup.service
1.136s user@1000.service
1.018s accounts-daemon.service
972ms systemd-networkd.service
839ms systemd-udevd.service
794ms systemd-journal-flush.service
760ms home.mount
583ms colord.service
508ms systemd-remount-fs.service
422ms systemd-tmpfiles-setup-dev-early.service
369ms systemd-udev-trigger.service
346ms polkit.service
285ms systemd-modules-load.service
275ms modprobe@fuse.service
220ms systemd-udev-load-credentials.service
209ms systemd-random-seed.service
207ms upower.service
194ms systemd-logind.service
126ms systemd-journald.service
100ms dracut-shutdown.service
97ms systemd-tmpfiles-clean.service
93ms systemd-networkd-persistent-storage.service
92ms dev-hugepages.mount
91ms dev-mqueue.mount
90ms sys-kernel-debug.mount
90ms sys-kernel-tracing.mount
87ms tmp.mount
86ms kmod-static-nodes.service
85ms modprobe@configfs.service
82ms modprobe@drm.service
73ms systemd-sysctl.service
63ms systemd-vconsole-setup.service
53ms systemd-update-utmp.service
46ms sys-fs-fuse-connections.mount
44ms systemd-network-generator.service
40ms systemd-tmpfiles-setup-dev.service
34ms systemd-user-sessions.service
27ms sys-kernel-config.mount
25ms user-runtime-dir@1000.service
21ms modprobe@dm_mod.service
|
Does the Wiki Page need updating as per my question in blue?
Anyway will wait to here from you and mark as solved shortly. |
|
| Back to top |
|
|
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 245
|
| Posted: Tue Apr 01, 2025 3:45 pm Post subject: |
|
|
| hal8000 wrote: | Hi zen_desu,
I followed the Wiki page and installed ugrd.
https://wiki.gentoo.org/wiki/UgRD
After the initial ugrd a python error was thrown out, unable to get block ID info.
I copied this on paste bin as its quite long:
https://pastebin.com/mtzhN0D2
I ran command as root and output was produced:
blkid -i /dev/sdc
/dev/sdc: MINIMUM_IO_SIZE="4096" PHYSICAL_SECTOR_SIZE="4096" DISKSEQ="3" LOGICAL_SECTOR_SIZE="512"
So I ran ugrd again and this time it worked and produced a compressed image in /tmp/initramfs as per wiki.
The Wiki does not state what to do with the file in /tmp/initramfs
I backed up my original initramfs.img and renamed the image in /tmp/initramfs as ugrd.img and moved to /boot.
In grub I modified the initrd line to refelect the new initramfs and it worked!
| Code: | | initrd /boot/amd-uc.img /boot/ugrd.img |
All the entries probing disb-by-id are gone.
systemd-analyze blame
| Quote: |
3.312s dev-sdc22.device
2.806s udisks2.service
1.674s alsa-restore.service
1.561s dbus.service
1.486s lightdm.service
1.290s systemd-tmpfiles-setup.service
1.136s user@1000.service
1.018s accounts-daemon.service
972ms systemd-networkd.service
839ms systemd-udevd.service
794ms systemd-journal-flush.service
760ms home.mount
583ms colord.service
508ms systemd-remount-fs.service
422ms systemd-tmpfiles-setup-dev-early.service
369ms systemd-udev-trigger.service
346ms polkit.service
285ms systemd-modules-load.service
275ms modprobe@fuse.service
220ms systemd-udev-load-credentials.service
209ms systemd-random-seed.service
207ms upower.service
194ms systemd-logind.service
126ms systemd-journald.service
100ms dracut-shutdown.service
97ms systemd-tmpfiles-clean.service
93ms systemd-networkd-persistent-storage.service
92ms dev-hugepages.mount
91ms dev-mqueue.mount
90ms sys-kernel-debug.mount
90ms sys-kernel-tracing.mount
87ms tmp.mount
86ms kmod-static-nodes.service
85ms modprobe@configfs.service
82ms modprobe@drm.service
73ms systemd-sysctl.service
63ms systemd-vconsole-setup.service
53ms systemd-update-utmp.service
46ms sys-fs-fuse-connections.mount
44ms systemd-network-generator.service
40ms systemd-tmpfiles-setup-dev.service
34ms systemd-user-sessions.service
27ms sys-kernel-config.mount
25ms user-runtime-dir@1000.service
21ms modprobe@dm_mod.service
|
Does the Wiki Page need updating as per my question in blue?
Anyway will wait to here from you and mark as solved shortly. |
Did you run as root? It generally needs that to do everything. If you run "sudo blkid" first, it should cache info so it can be read by a regular user. Under perfect conditions, ugrd can make images without root, but in practice, some level of access is needed for enumeration of some info.
Unlike dracut, just running ugrd only creates a test image and puts it in /tmp. If you want to install it to a particular path, you can specify it as an argument. Generally, this process is entirely handled by installkernel, so setting the "ugrd" flag on installkernel should be enough for things to work. The idea is that simply running ugrd should have little risk of overwriting actively used boot files ootb. If you'd like to make it write to /boot with no args, you can set the `out_dir` to "/boot" in the config, but again, I generally trust installkernel to handle that. You can also specify a path as the output file arg and it will use the default naming scheme under that path.
As a side note, there have been a variety of improvements made, which are not in a release currently. I'm planning to make a 2.x release soon, but in the mean time, it can be tested by using the 9999 (git) ebuild. This is the build I run on most of my systems.
It would probably help to have that mentioned on the wiki page, I can add that unless you want to
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
hal8000
n00b
Joined: 27 Mar 2025
Posts: 13
|
| Posted: Tue Apr 01, 2025 10:51 pm Post subject: |
|
|
Thank you again for your help. Yes I ran ugrd as root.
The contents of my installkernel are as follows:
cat /etc/portage/package.use/ installkernel
sys-kernel/installkernel grub
sys-kernel/installkernel dracut
sys-kernel/installkernel ugrd
As I'm still getting used to gentoo, not sure if I have have multiple arguments on one line
for package use
e.g
sys-kernel/installkernel grub dracut ugrd
I've marked the post as [solved] Ive signed up to edit the Wiki, but as Ive not read all the
information yet, I think it will be safer if you make the change. |
|
| Back to top |
|
|
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 245
|
| Posted: Wed Apr 02, 2025 12:33 am Post subject: |
|
|
| hal8000 wrote: | Thank you again for your help. Yes I ran ugrd as root.
The contents of my installkernel are as follows:
cat /etc/portage/package.use/ installkernel
sys-kernel/installkernel grub
sys-kernel/installkernel dracut
sys-kernel/installkernel ugrd
As I'm still getting used to gentoo, not sure if I have have multiple arguments on one line
for package use
e.g
sys-kernel/installkernel grub dracut ugrd
I've marked the post as [solved] Ive signed up to edit the Wiki, but as Ive not read all the
information yet, I think it will be safer if you make the change. |
I don't think installkernel should support setting it to use ugrd and dracut, they are mutually exclusive. I'm glad you got it sorted out though!
I can make the change, I encourage you to help with the wiki if you want. I can help correct any issues if there are any. Once you have your head wrapped around the wiki style guidelines (and using the source editor) contributing is very easy. A lot of the things on the wiki can fall out of date, so the more people who are able to edit and keep it current, the better 
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
hal8000
n00b
Joined: 27 Mar 2025
Posts: 13
|
| Posted: Wed Apr 02, 2025 9:30 pm Post subject: |
|
|
OK, I've read the guidelines and using the styles is easy, writing in the third person singular, well that takes a little thinking.
I've added a Tip style paragraph for testing an ugRD image, which should now be viewable on the wiki page.
This is under the heading "Buiding an initramfs manually"
This is my addition to the Wiki Page https://wiki.gentoo.org/wiki/UgRD :
| Quote: |
The new image will be called ugrd-x.x.xx-gentoo-dist.cpio.xz where x.x.xx refers to the current kernel version. To test, copy this file to /boot and change the initrd line in /boot/grub/grub.cfg to reflect the new image. |
I hope you approve, its a great idea, allowing everyone to edit the wiki. |
|
| Back to top |
|
|
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 245
|
| Posted: Wed Apr 02, 2025 9:41 pm Post subject: |
|
|
| hal8000 wrote: | OK, I've read the guidelines and using the styles is easy, writing in the third person singular, well that takes a little thinking.
I've added a Tip style paragraph for testing an ugRD image, which should now be viewable on the wiki page.
This is under the heading "Buiding an initramfs manually"
This is my addition to the Wiki Page https://wiki.gentoo.org/wiki/UgRD :
| Quote: |
The new image will be called ugrd-x.x.xx-gentoo-dist.cpio.xz where x.x.xx refers to the current kernel version. To test, copy this file to /boot and change the initrd line in /boot/grub/grub.cfg to reflect the new image. |
I hope you approve, its a great idea, allowing everyone to edit the wiki. |
That edit looks great to me, and yeah, the main thing to consider is using third person language. Other than that, it's pretty typical "technical writing".
It may help or be relevant to link here: https://github.com/desultory/ugrd/blob/main/docs/bootloader_config.md, and that bootloader config section could probably be updated to have info on installing the file to another location.
If you want to get more into wiki writing, many people are active and happy to help in #gentoo-wiki on libera chat. That tends to be a good place to ask quick questions and get help.
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
hal8000
n00b
Joined: 27 Mar 2025
Posts: 13
|
| Posted: Fri Apr 04, 2025 10:33 am Post subject: |
|
|
I've made another two edits to the page:
https://wiki.gentoo.org/wiki/UgRD
I included a small paragraph on ugRD options, and 'Installing the Ramdisk to an alternate Location'.
However, including an external link, I am finding very difficult.
I was attempting to include Bootloader Configuration to the bottom under "See Also", but I failed.
The difficulty is producing the external link with a descriptive text.. |
|
| Back to top |
|
|
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 245
|
| Posted: Fri Apr 04, 2025 5:16 pm Post subject: |
|
|
| hal8000 wrote: | I've made another two edits to the page:
https://wiki.gentoo.org/wiki/UgRD
I included a small paragraph on ugRD options, and 'Installing the Ramdisk to an alternate Location'.
However, including an external link, I am finding very difficult.
I was attempting to include Bootloader Configuration to the bottom under "See Also", but I failed.
The difficulty is producing the external link with a descriptive text.. |
Thanks for that
Using the source editor, the "See also" section looks like this:
| Code: | == See also ==
* {{See also|Full Disk Encryption}}
* {{See also|Rootfs encryption}}
* {{See also|Dracut}}
[[Category:Initramfs]]
|
The `*` lines form a list, and the `{{}}` indicates a template. The "See also" template's first arg will be the name of another article on the main wiki namespace, so if you wanted to add a See also for `foo` you could add:
If you want to make a link to an external website, you can use the mediawiki link formatter: `[]` so like:
| Code: | | [https://example.com example link] |
An example from the ugrd page:
| Code: | | {{See|More detailed configuration usage is described in the [https://github.com/desultory/ugrd/blob/main/docs/configuration.md project documentation].}} |
(under the configuration section)
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
hal8000
n00b
Joined: 27 Mar 2025
Posts: 13
|
|
| Back to top |
|
|
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 245
|
| Posted: Sat Apr 05, 2025 10:20 pm Post subject: |
|
|
Ah, I think by making a link to a page which doesn't exist using that template, you may have created the page?
I think you want to use "external resources" not "see also" as "see also" is specifically for pages on the same wiki.
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
hal8000
n00b
Joined: 27 Mar 2025
Posts: 13
|
| Posted: Sun Apr 06, 2025 8:52 pm Post subject: |
|
|
Changes sucessful!
https://wiki.gentoo.org/wiki/UgRD
Under configuration, I expanded the "see also" box to include the bootloader config as a bulleted list:
More detailed configuration usage is described in the project documentation.
Additional bootloader examples are also shown on the project Github page.
Removed my broken edit as well.
Hope it gets your approval. |
|
| Back to top |
|
|
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 245
|
| Posted: Sun Apr 06, 2025 9:43 pm Post subject: |
|
|
| hal8000 wrote: | Changes sucessful!
https://wiki.gentoo.org/wiki/UgRD
Under configuration, I expanded the "see also" box to include the bootloader config as a bulleted list:
More detailed configuration usage is described in the project documentation.
Additional bootloader examples are also shown on the project Github page.
Removed my broken edit as well.
Hope it gets your approval. |
It looks good to me, doesn't necessarily need my sign-off or anyone but yours (this is a community project), but I appreciate you putting a lot of effort into making this edit clean
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
hal8000
n00b
Joined: 27 Mar 2025
Posts: 13
|
| Posted: Mon Apr 07, 2025 8:28 pm Post subject: |
|
|
Well one thing, ugRD made a ramdisk and suppressed all my Udev messages and for me, made my systemd easier to manager.
For that reason it was a pleasure to help out editing the Wiki Page.  |
|
| 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
