View previous topic :: View next topic |
Author |
Message |
linux_os2 Apprentice

Joined: 29 Aug 2018 Posts: 264 Location: Zedelgem Belgium
|
Posted: Fri Feb 21, 2025 9:53 am Post subject: ugrd : [/dev/md126p8] Unable to find device mapper |
|
|
compiled dist kernel using installkernel.
dracut was used to create the initrd file.
During boot hangs for some minutes.
Then a lot of messages by dracut.
Then after some time system enters the recovery mode.
the raid device entries are missing.
Looking at the .cofig of the new kernel all raid options are set.
So tried to use ugrd to create an initrd.
During generation following msg is posted:
Code: | ERROR | [/dev/md126p8] Unable to find device mapper device with maj: 259 min: 27 |
|
|
Back to top |
|
 |
linux_os2 Apprentice

Joined: 29 Aug 2018 Posts: 264 Location: Zedelgem Belgium
|
Posted: Fri Feb 21, 2025 3:21 pm Post subject: |
|
|
Was able to create a working initrd with genkernel.
Code: | genkernel --mdadm initramfs |
|
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 54895 Location: 56N 3W
|
Posted: Fri Feb 21, 2025 3:42 pm Post subject: |
|
|
linux_os2,
/dev/md126p8 is a partition on a software raid set. It should not belong to device mapper.
That looks like a bug in ugrd. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
zen_desu Tux's lil' helper

Joined: 25 Oct 2024 Posts: 139
|
Posted: Fri Feb 21, 2025 3:53 pm Post subject: Re: ugrd : [/dev/md126p8] Unable to find device mapper |
|
|
linux_os2 wrote: | compiled dist kernel using installkernel.
dracut was used to create the initrd file.
During boot hangs for some minutes.
Then a lot of messages by dracut.
Then after some time system enters the recovery mode.
the raid device entries are missing.
Looking at the .cofig of the new kernel all raid options are set.
So tried to use ugrd to create an initrd.
During generation following msg is posted:
Code: | ERROR | [/dev/md126p8] Unable to find device mapper device with maj: 259 min: 27 |
|
Can you share the output of "lsblk -f" please?
If you can use a paste service and run "ugrd -d", that would help, especially with the latest 9999 (git) version (v2). I think this may be happening because a that mdraid device with a partition is listed as the "slave" for another volume, which could possibly be a mistake. _________________ µgRD dev
Wiki writer |
|
Back to top |
|
 |
linux_os2 Apprentice

Joined: 29 Aug 2018 Posts: 264 Location: Zedelgem Belgium
|
Posted: Sat Feb 22, 2025 12:19 pm Post subject: Re: ugrd : [/dev/md126p8] Unable to find device mapper |
|
|
zen_desu wrote: | linux_os2 wrote: | compiled dist kernel using installkernel.
dracut was used to create the initrd file.
During boot hangs for some minutes.
Then a lot of messages by dracut.
Then after some time system enters the recovery mode.
the raid device entries are missing.
Looking at the .cofig of the new kernel all raid options are set.
So tried to use ugrd to create an initrd.
During generation following msg is posted:
Code: | ERROR | [/dev/md126p8] Unable to find device mapper device with maj: 259 min: 27 |
|
Can you share the output of "lsblk -f" please?
If you can use a paste service and run "ugrd -d", that would help, especially with the latest 9999 (git) version (v2). I think this may be happening because a that mdraid device with a partition is listed as the "slave" for another volume, which could possibly be a mistake. |
lsblk -f:
Code: | NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
└─sda1 linux_raid_member 1.2 marc:124 a6f4693e-1554-697b-5c93-edf466ac4f07
└─md125 ext4 1.0 05eeba2c-9ab4-4bb2-93ca-85c29bc9d852 66.5T 13% /srv/nfs/home
/home
sdb
└─sdb1 linux_raid_member 1.2 marc:124 a6f4693e-1554-697b-5c93-edf466ac4f07
└─md125 ext4 1.0 05eeba2c-9ab4-4bb2-93ca-85c29bc9d852 66.5T 13% /srv/nfs/home
/home
sdc
└─sdc1 linux_raid_member 1.2 marc:124 a6f4693e-1554-697b-5c93-edf466ac4f07
└─md125 ext4 1.0 05eeba2c-9ab4-4bb2-93ca-85c29bc9d852 66.5T 13% /srv/nfs/home
/home
sdd ddf_raid_member 01.00.00 LSI \x80\x86'\xc3
├─md126
│ ├─md126p1 ntfs Recovery 46B0C283B0C27947
│ ├─md126p2 vfat FAT32 SYSTEM 9030-2F6D
│ ├─md126p3
│ ├─md126p4 ntfs Windows_10 109ED0469ED025CE
│ ├─md126p5 ext4 1.0 Gentoo 1 ceffaa4b-695c-4490-9f9a-38aed1bc40a8
│ ├─md126p6 vfat FAT32 EFI_Gentoo1 3883-62B1 93.7M 1% /boot/efi
│ ├─md126p7 ext4 1.0 Gentoo 2 c9247467-374b-41c2-a72f-57a37d3e6d7b
│ ├─md126p8 ext4 1.0 Gentoo 3 2b656b1f-599a-484c-a4e3-bccd1d540764 46.6G 46% /
│ ├─md126p9 ext4 1.0 LFS sysd 12.0 e6001dff-27e9-4388-b622-26c59ce80085
│ ├─md126p10 ext4 1.0 Ubuntu 24.04 dd12ff4e-9ed6-4d5b-a391-cce9bdcb264d
│ ├─md126p11 ext4 1.0 Ubuntu 22.04 036f6f20-6b01-4d5e-8f42-e55ab46a9009
│ ├─md126p12 ext4 1.0 ISO Sytems d2290b79-34a7-4251-80b7-9f8b024348c2
│ ├─md126p13 ext4 1.0 Clonezilla e102e1d8-37ee-48c9-966e-4dc815b24ee1
│ ├─md126p14 ext4 1.0 Ubuntu Home a6ebbfa2-b4f0-4701-9b69-5e680a245dcc
│ ├─md126p15 vfat FAT32 EFI_W11 62D0-9530
│ ├─md126p16
│ ├─md126p17 ntfs D66A58B46A58935B
│ ├─md126p18 ntfs 802EB1582EB14844
│ ├─md126p19 ext4 1.0 LFS sysd 12.0 DE 6342936d-140d-4051-ad74-fed61623178a
│ ├─md126p20 ext4 1.0 LFS sysd 12.0 NE 6aff57b4-bc71-4e93-8807-db85c7e72d92
│ └─md126p21 ext4 1.0 3f67975d-adfe-461c-8aa3-5446b2c0ea68
├─md127
├─sdd16
├─sdd17 ntfs D66A58B46A58935B
├─sdd18 ntfs 802EB1582EB14844
├─sdd19 ext4 1.0 LFS sysd 12.0 DE 6342936d-140d-4051-ad74-fed61623178a
├─sdd20 ext4 1.0 LFS sysd 12.0 NE 6aff57b4-bc71-4e93-8807-db85c7e72d92
└─sdd21 ext4 1.0 3f67975d-adfe-461c-8aa3-5446b2c0ea68
sde ddf_raid_member 01.00.00 LSI \x80\x86'\xc3
├─md126
│ ├─md126p1 ntfs Recovery 46B0C283B0C27947
│ ├─md126p2 vfat FAT32 SYSTEM 9030-2F6D
│ ├─md126p3
│ ├─md126p4 ntfs Windows_10 109ED0469ED025CE
│ ├─md126p5 ext4 1.0 Gentoo 1 ceffaa4b-695c-4490-9f9a-38aed1bc40a8
│ ├─md126p6 vfat FAT32 EFI_Gentoo1 3883-62B1 93.7M 1% /boot/efi
│ ├─md126p7 ext4 1.0 Gentoo 2 c9247467-374b-41c2-a72f-57a37d3e6d7b
│ ├─md126p8 ext4 1.0 Gentoo 3 2b656b1f-599a-484c-a4e3-bccd1d540764 46.6G 46% /
│ ├─md126p9 ext4 1.0 LFS sysd 12.0 e6001dff-27e9-4388-b622-26c59ce80085
│ ├─md126p10 ext4 1.0 Ubuntu 24.04 dd12ff4e-9ed6-4d5b-a391-cce9bdcb264d
│ ├─md126p11 ext4 1.0 Ubuntu 22.04 036f6f20-6b01-4d5e-8f42-e55ab46a9009
│ ├─md126p12 ext4 1.0 ISO Sytems d2290b79-34a7-4251-80b7-9f8b024348c2
│ ├─md126p13 ext4 1.0 Clonezilla e102e1d8-37ee-48c9-966e-4dc815b24ee1
│ ├─md126p14 ext4 1.0 Ubuntu Home a6ebbfa2-b4f0-4701-9b69-5e680a245dcc
│ ├─md126p15 vfat FAT32 EFI_W11 62D0-9530
│ ├─md126p16
│ ├─md126p17 ntfs D66A58B46A58935B
│ ├─md126p18 ntfs 802EB1582EB14844
│ ├─md126p19 ext4 1.0 LFS sysd 12.0 DE 6342936d-140d-4051-ad74-fed61623178a
│ ├─md126p20 ext4 1.0 LFS sysd 12.0 NE 6aff57b4-bc71-4e93-8807-db85c7e72d92
│ └─md126p21 ext4 1.0 3f67975d-adfe-461c-8aa3-5446b2c0ea68
├─md127
├─sde16
├─sde17 ntfs D66A58B46A58935B
├─sde18 ntfs 802EB1582EB14844
├─sde19 ext4 1.0 LFS sysd 12.0 DE 6342936d-140d-4051-ad74-fed61623178a
├─sde20 ext4 1.0 LFS sysd 12.0 NE 6aff57b4-bc71-4e93-8807-db85c7e72d92
└─sde21 ext4 1.0 3f67975d-adfe-461c-8aa3-5446b2c0ea68
sdf
└─sdf1 linux_raid_member 1.2 marc:124 a6f4693e-1554-697b-5c93-edf466ac4f07
└─md125 ext4 1.0 05eeba2c-9ab4-4bb2-93ca-85c29bc9d852 66.5T 13% /srv/nfs/home
/home
sdg
└─sdg1 swap 1 b4b1cbec-4e1f-4da7-88d7-5ebc50492090 [SWAP]
sdh
└─sdh1 linux_raid_member 1.2 marc:124 a6f4693e-1554-697b-5c93-edf466ac4f07
└─md125 ext4 1.0 05eeba2c-9ab4-4bb2-93ca-85c29bc9d852 66.5T 13% /srv/nfs/home
/home
sdi
└─sdi1 linux_raid_member 1.2 marc:124 a6f4693e-1554-697b-5c93-edf466ac4f07
└─md125 ext4 1.0 05eeba2c-9ab4-4bb2-93ca-85c29bc9d852 66.5T 13% /srv/nfs/home
/home
sdj
sr0
nvme0n1
├─nvme0n1p1 vfat FAT32 E256-F414
├─nvme0n1p2
├─nvme0n1p3 ntfs D66A58B46A58935B
├─nvme0n1p4 ntfs 802EB1582EB14844
├─nvme0n1p5 ext4 1.0 Ubuntu Home a6ebbfa2-b4f0-4701-9b69-5e680a245dcc
├─nvme0n1p6 ext4 1.0 37424a31-ede7-4e94-8636-4d5cfd37785a
└─nvme0n1p7 ext4 1.0 4c886474-e36e-4922-a219-76b290862e0d
|
same result with ugrd 9999 |
|
Back to top |
|
 |
|