Bug 30939

Summary: error message in setting up kernel or in running the grub setup?
Product: Mageia Reporter: w unruh <unruh>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal CC: davidwhodgins, lewyssmith
Version: 8   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: kernel? kernel-desktop-5.15.65-1.mga8-1-1.mga8 CVE:
Status comment:

Description w unruh 2022-10-06 04:56:44 CEST
Description of problem: Wile updating a mageia 8 system today, I got a huge series (probably about 40 lines) of errors like
ERROR: pdc: reading /dev/dm-1[Input/outiut error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
I beoive they were occuring at the beginning of setting up the new kernel.
I have no idea what they mean of what /dev/dm-1 is supposed to be. 



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 w unruh 2022-10-06 05:00:32 CEST
Here is the full list, together with the next lines in the installation

ERROR: asr: reading /dev/dm-1[Input/output error]
ERROR: ddf1: reading /dev/dm-1[Input/output error]
ERROR: ddf1: reading /dev/dm-1[Input/output error]
ERROR: hpt45x: reading /dev/dm-1[Input/output error]
ERROR: isw: reading /dev/dm-1[Input/output error]
ERROR: isw: reading /dev/dm-1[Input/output error]
ERROR: isw: reading /dev/dm-1[Input/output error]
ERROR: jmicron: reading /dev/dm-1[Input/output error]
ERROR: lsi: reading /dev/dm-1[Input/output error]
ERROR: nvidia: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: sil: reading /dev/dm-1[Input/output error]
ERROR: via: reading /dev/dm-1[Input/output error]
ERROR: asr: reading /dev/dm-1[Input/output error]
ERROR: ddf1: reading /dev/dm-1[Input/output error]
ERROR: ddf1: reading /dev/dm-1[Input/output error]
ERROR: hpt45x: reading /dev/dm-1[Input/output error]
ERROR: isw: reading /dev/dm-1[Input/output error]
ERROR: isw: reading /dev/dm-1[Input/output error]
ERROR: isw: reading /dev/dm-1[Input/output error]
ERROR: jmicron: reading /dev/dm-1[Input/output error]
ERROR: lsi: reading /dev/dm-1[Input/output error]
ERROR: nvidia: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: sil: reading /dev/dm-1[Input/output error]
ERROR: via: reading /dev/dm-1[Input/output error]
ERROR: asr: reading /dev/dm-1[Input/output error]
ERROR: ddf1: reading /dev/dm-1[Input/output error]
ERROR: ddf1: reading /dev/dm-1[Input/output error]
ERROR: hpt45x: reading /dev/dm-1[Input/output error]
ERROR: isw: reading /dev/dm-1[Input/output error]
ERROR: isw: reading /dev/dm-1[Input/output error]
ERROR: isw: reading /dev/dm-1[Input/output error]
ERROR: jmicron: reading /dev/dm-1[Input/output error]
ERROR: lsi: reading /dev/dm-1[Input/output error]
ERROR: nvidia: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: pdc: reading /dev/dm-1[Input/output error]
ERROR: sil: reading /dev/dm-1[Input/output error]
ERROR: via: reading /dev/dm-1[Input/output error]
Creating: target|kernel|dracut args|basicmodules 
remove-boot-splash: Format of /boot/initrd-5.15.65-desktop-1.mga8.img not recognized
----------------------------------------------------------------------
More information on package mariadb-10.5.17-1.mga8.x86_64

NOTE: MariaDB is installed without root password, it is recommended to set the
root password with the following command as soon as possible:

 # mysql_secure_installation
 press enter at each question except the new root password.

The initscript used to start mysql has been rever
Comment 2 Dave Hodgins 2022-10-06 07:15:40 CEST
/dev/dm-1 is the first block device created by device mapper.
https://en.wikipedia.org/wiki/Device_mapper

Are you using an encrypted file system, raid, lvm, docker, or another one
of the applications listed on the wiki page?

CC: (none) => davidwhodgins

Comment 3 w unruh 2022-10-06 14:53:21 CEST
I have a number of cryptmount files and I bind mount a number of directories into other directories. How do I find out what dm-1 is used for?
Does it matter if I got all those errors?
Comment 4 w unruh 2022-10-06 15:04:59 CEST
I just did an rpm -e on a bunch of old kernels and again got a huge list of those dm-1 input/output errors.

Source RPM: kernel? kernel-desktop-5.15.43-1.mga8-1-1.mga8 => kernel? kernel-desktop-5.15.65-1.mga8-1-1.mga8

Comment 5 sturmvogel 2022-10-06 17:44:42 CEST
You should have a look at "man dmsetup", "man dmraid" or whatever tool you used to setup your crypt/llvm/raid/(whatever) to find the (logical)device dm-1.

This error message can have different causes:
- failing drive
- to small power supply for a drive
- unstable power supply for a drive
- cable problems
- ...
Comment 6 Dave Hodgins 2022-10-06 18:37:29 CEST
I was mistaken above. dm-1 is the second device mapper entry as it starts at dm-0

To figure out which device/partition it is, use "cryptsetup status /dev/dm-1"
and look for the device line.
Comment 7 w unruh 2022-10-06 21:34:07 CEST
>sudo cryptsetup status /dev/dm-1
/dev/dm-1 is active and is in use.
 type:    n/a

That's it. 
For dm-0 I get


>sudo cryptsetup status /dev/dm-0
/dev/dm-0 is active and is in use.
  type:    n/a
  cipher:  aes-cbc-plain
  keysize: 256 bits
  key location: dm-crypt
  device:  /dev/loop0
  loop:    /fastlocal/encrypt/varspoolmail1
  sector size:  512
  offset:  0 sectors
  size:    4096000 sectors
  mode:    read/write
Comment 8 Dave Hodgins 2022-10-06 21:41:15 CEST
What's in /etc/fstab, /etc/crypttab, /etc/cryptmount/cmtab, /etc/lvm/lvm.conf,
and the output of "journalctl -b --no-h|grep -e crypt -e dm-"?
Comment 9 Dave Hodgins 2022-10-06 21:41:42 CEST
Also attach the output of dmesg
Comment 10 w unruh 2022-10-06 23:23:34 CEST
dmesg has nothing at the time that I installed the new kernel, but about an hour earlier ( and also a few days earlier) there were a whole bunch of errors

[2482454.740668] Buffer I/O error on dev dm-1, logical block 3839999, async page read
and about 20 days earlier as well. In Journalctl, there were a 
also a whole bunch of such errors. (again nothing when the kernel was updated)
Sep 14 14:10:02 kernel: Buffer I/O error on dev dm-1, logical block 3839984, async page read
Sep 14 14:10:02 kernel: Buffer I/O error on dev dm-1, logical block 3839984, async page read
Sep 14 14:11:19 kernel: Buffer I/O error on dev dm-1, logical block 3839984, async page read
Sep 14 14:11:21 kernel: Buffer I/O error on dev dm-1, logical block 3839999, async page read
Sep 14 14:11:21 kernel: Buffer I/O error on dev dm-1, logical block 3839999, async page read
Sep 14 14:11:21 kernel: Buffer I/O error on dev dm-1, logical block 3839967, async page read
Sep 14 14:11:21 kernel: Buffer I/O error on dev dm-1, logical block 3839998, async page read
Sep 14 14:11:21 kernel: Buffer I/O error on dev dm-1, logical block 3839999, async page read
Sep 14 14:11:21 kernel: Buffer I/O error on dev dm-1, logical block 3839999, async page read
Sep 14 14:11:21 kernel: Buffer I/O error on dev dm-1, logical block 3839735, async page read
Sep 14 14:11:21 kernel: Buffer I/O error on dev dm-1, logical block 3839999, async page read
Sep 14 14:11:21 kernel: Buffer I/O error on dev dm-1, logical block 3839999, async page read
Sep 14 14:22:50 kernel: Buffer I/O error on dev dm-1, logical block 3839984, async page read
Sep 14 14:23:11 kernel: Buffer I/O error on dev dm-1, logical block 3839984, async page read
Sep 14 14:23:11 kernel: Buffer I/O error on dev dm-1, logical block 3839999, async page read
Sep 14 14:23:11 kernel: Buffer I/O error on dev dm-1, logical block 3839999, async page read




(and similarly today, but all before I installed the new kernel.






None of crypt files are mounted in /etc/fstab. I do it by hand after bootup (a month ago after disk problems)


/etc/crypttab is empty.

/etc/cryptmount has

varspoolmail1 {
    dev=/fastlocal/encrypt/varspoolmail1
    dir=/var/spool/mail
    fstype=ext3
    mountoptions=defaults
    cipher=aes
    keyformat=builtin
    keyfile=/etc/cryptmount/varspoolmail1.key
}
courses {
    dev=/fastlocal/encrypt/courses
    dir=/fastlocal/unruhhome/unruh/encrypt/courses
    fstype=ext3
    mountoptions=defaults
    cipher=aes
    keyformat=builtin
    keyfile=/etc/cryptmount/courses.key
}
unruholdcourses {
    dev=/local/encrypt/unruholdcourses
    dir=/fastlocal/unruhhome/unruh/crypt/oldcourses
    fstype=ext3
    mountoptions=defaults
    cipher=aes
    keyformat=builtin
    keyfile=/etc/cryptmount/unruholdcourses.key
}
coursesnew {
    dev=/local/encrypt/coursesnew
    dir=/fastlocal/unruhhome/unruh/encrypt/coursesnew
    fstype=ext3
    mountoptions=defaults
    cipher=aes
    keyformat=builtin
    keyfile=/etc/cryptmount/coursesnew.key
}


unruhmail {
    dev=/fastlocal/encrypt/unruhmail
    dir=/fastlocal/unruhhome/unruh/mail
    fstype=ext3
    mountoptions=defaults
    flags=trim
    cipher=aes
    keyformat=builtin
    keyfile=/etc/cryptmount/unruhmail.key
}
unruhmail2 {
    dev=/fastlocal/encrypt/unruhmail
    dir=/fastlocal/unruhhome/unruh/mail
    fstype=ext3
    mountoptions=defaults
    flags=trim
    cipher=aes
    keyformat=builtin
    keyfile=/etc/cryptmount/unruhmail1.key
}

unruholdmail {
   dev=/local/encrypt/unruholdmail
   dir=/fastlocal/unruhhome/unruh/oldmail
   fstype=ext4 mountoptions=defaults cipher=aes
   keyformat=builtin
   keyfile=/etc/cryptmount/unruholdmail.key
}
     
u





I assume that dm-1 would be the second of the above, since I mounted them with
cryptmount -a
I just did a grep -r on ~unruh/encrypt/courses which should have read every byte, but found no problems with that in dmesg or in journalctl.
Comment 11 Dave Hodgins 2022-10-07 01:03:08 CEST
What's the output of "ll /dev/mapper" and blkid run as root?
Comment 12 w unruh 2022-10-07 06:21:28 CEST
blkid
for the encrypted partions)


/dev/mapper/varspoolmail1: UUID="19541f35-a700-4119-84b0-7d261c72073a" BLOCK_SIZE="4096" TYPE="ext3"
/dev/dm-2: UUID="71e54ebf-997f-4b76-9583-06c2e7920eb1" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/courses: UUID="e1d3bb86-1bc9-4a38-8f91-6ec36b57c839" BLOCK_SIZE="4096" TYPE="ext3"
/dev/mapper/unruholdcourses: UUID="1e5b41ab-6954-45c0-bd27-c825eac34607" BLOCK_SIZE="4096" TYPE="ext3"
/dev/mapper/coursesnew: UUID="e3a9b440-2fc8-4366-b66a-e294dae44983" BLOCK_SIZE="4096" TYPE="ext3"
/dev/mapper/unruhmail1: UUID="e148ff27-795c-4cc1-b1b0-7a3daf017967" BLOCK_SIZE="4096" TYPE="ext3"
/dev/mapper/unruhmail2: UUID="e148ff27-795c-4cc1-b1b0-7a3daf017967" BLOCK_SIZE="4096" TYPE="ext3"
  
ll /dev/mapper
drwxr-xr-x  2 root root       200 Sep  9 09:13 ./
drwxr-xr-x 21 root root      4600 Sep 14 14:23 ../
crw-------  1 root root   10, 236 Sep  7 12:25 control
brw-------  1 root unruh 252,   3 Sep  7 12:49 courses
brw-------  1 root unruh 252,   5 Sep  7 12:50 coursesnew
lrwxrwxrwx  1 root root         7 Sep 14 14:27 unruhmail -> ../dm-1
brw-------  1 root root  252,   6 Sep  8 18:32 unruhmail1
brw-------  1 root root  252,   7 Sep  9 09:13 unruhmail2
brw-------  1 root unruh 252,   4 Sep  7 12:50 unruholdcourses

I guess I know what dm-1 is now.

And why would it be a soft link?
Comment 13 Dave Hodgins 2022-10-07 07:33:23 CEST
That's not what I was expecting. With one encrypted file system open ...
# ll /dev/mapper
total 0
crw------- 1 root root 10, 236 Oct  6 13:04 control
lrwxrwxrwx 1 root root       7 Oct  6 19:00 luks-0c0b649a-660a-4326-b34b-fbcefa0f9b2f -> ../dm-0

Taking the uuid from the above for dm-0 ...
# blkid|grep 0c0b649a-660a-4326-b34b-fbcefa0f9b2f
/dev/sdf3: UUID="0c0b649a-660a-4326-b34b-fbcefa0f9b2f" TYPE="crypto_LUKS"
/dev/mapper/luks-0c0b649a-660a-4326-b34b-fbcefa0f9b2f: UUID="a7b3cba1-6e35-4b84-ba13-d332ba7aa81a" BLOCK_SIZE="4096" TYPE="ext4"

I just noticed in comment10 unruhmail2 and unruhmail both have the same
device and directory. I'm not sure if that is part of the problem or not.
Comment 14 Lewis Smith 2022-12-18 21:16:49 CET
Is this still an isue?

CC: (none) => lewyssmith

Comment 15 Lewis Smith 2023-11-14 13:13:17 CET
Moribund.

Status: NEW => RESOLVED
Resolution: (none) => OLD