udevd-work report error on boot software raid1

Issues related to applications and software problems

udevd-work report error on boot software raid1

Postby McGabo » 2012/02/16 15:53:12

I have a fresh build of minimal CentOS 6.2 on my server.
I built the OS on a set of software mirrors created in the OS install process.
The system boots and works fine, but I get the following two errors at boot time:

From /var/log/boot.log
Code: Select all
Welcome to CentOS
Avvio di udev: udevd-work[395]: error opening ATTR{/sys/devices/virtual/block/md0/queue/iosched/slice_idle} for writing: No such file or directory
udevd-work[395]: error opening ATTR{/sys/devices/virtual/block/md0/queue/iosched/quantum} for writing: No such file or directory
                                                           [  OK  ]


No other message appear.
I have made many times software RAID 1 in Centos 5 and I never had any problem.
I have read many posts but I haven't found nothing usefull.
Surely I have a simple error, but I don't know what or where is it.

Here some detail about raid configuration:

/dev/md0 /boot
/dev/md1 swap
/dev/md2 /

cat /proc/mdstat
Code: Select all
Personalities : [raid1]
md0 : active raid1 sda1[0] sdb1[1]
      255988 blocks super 1.0 [2/2] [UU]
     
md2 : active raid1 sda3[0] sdb3[1]
      153934780 blocks super 1.1 [2/2] [UU]
      bitmap: 1/2 pages [4KB], 65536KB chunk

md1 : active raid1 sda2[0] sdb2[1]
      2096120 blocks super 1.1 [2/2] [UU]
     
unused devices: <none>


mdadm --detail /dev/md0
Code: Select all
/dev/md0:
        Version : 1.0
        Creation Time : Wed Feb 15 17:21:56 2012
        Raid Level : raid1
        Array Size : 255988 (250.03 MiB 262.13 MB)
        Used Dev Size : 255988 (250.03 MiB 262.13 MB)
        Raid Devices : 2
        Total Devices : 2
        Persistence : Superblock is persistent

    Update Time : Thu Feb 16 15:44:51 2012
          State : clean
          Active Devices : 2
          Working Devices : 2
          Failed Devices : 0
          Spare Devices : 0

           Name : Ade:0  (local to host Ade)
           UUID : d9d724ff:24f7177e:35323cdf:368bcfff
          Events : 19

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       17        1      active sync   /dev/sdb1


mdadm --detail /dev/md2
Code: Select all
/dev/md2:
        Version : 1.1
        Creation Time : Wed Feb 15 17:21:59 2012
        Raid Level : raid1
        Array Size : 153934780 (146.80 GiB 157.63 GB)
        Used Dev Size : 153934780 (146.80 GiB 157.63 GB)
        Raid Devices : 2
        Total Devices : 2
        Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Thu Feb 16 16:46:05 2012
          State : active
          Active Devices : 2
          Working Devices : 2
          Failed Devices : 0
          Spare Devices : 0

           Name : Ade:2  (local to host Ade)
           UUID : 948f56c7:284db924:bf8e44e3:cb5ebc85
           Events : 1326

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync   /dev/sda3
       1       8       19        1      active sync   /dev/sdb3
McGabo
 
Posts: 2
Joined: 2012/02/16 14:55:00

udevd-work report error on boot software raid1

Postby pschaff » 2012/02/17 12:44:46

Welcome to the CentOS fora. Please see the recommended reading for new users linked in my signature.

The message may be disconcerting, but I see nothing in the later data you show to indicate a problem with the RAID. Am I missing something?
pschaff
Retired Moderator
 
Posts: 18277
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America

Re: udevd-work report error on boot software raid1

Postby McGabo » 2012/02/17 13:47:30

Everything works fine thanks, but I want to know why udev displays this message.
I do not understand because it shows that error on md0 and not on md2.
The two directories:
/sys/devices/virtual/block/md0/queue/iosched/
/sys/devices/virtual/block/md2/queue/iosched/
not exist in the filesystem, but udev displays the error "No such file or directory" only on md0 device.
Why?

Thanks for your attention and sorry for my poor English
McGabo
 
Posts: 2
Joined: 2012/02/16 14:55:00

Re: udevd-work report error on boot software raid1

Postby Vaughan » 2013/03/11 00:52:55

I know that this is an old post, but the same thing started happening to my system when I replaced a failing hard-drive in my raid-1 array with a ssd drive. Apparently it relates to I/O tuning which can be setup in CentOS6.

I refer the interested to this url: https://access.redhat.com/knowledge/doc ... in-io.html
Vaughan
 
Posts: 16
Joined: 2009/10/19 22:00:44


Return to CentOS 6 - Software Support

Who is online

Users browsing this forum: No registered users and 2 guests