Hi Giuseppe, I've done it, but the log files are not there. Looks like udev does not call this activate script at all.
The block devices do exist, I've seen these in busybox: brw-rw---- 1 root disk 8, 0 2008-10-02 15:54 /dev/sda brw-rw---- 1 root disk 8, 1 2008-10-02 15:54 /dev/sda1 brw-rw---- 1 root disk 8, 2 2008-10-02 15:54 /dev/sda2 brw-rw---- 1 root disk 8, 3 2008-10-02 15:54 /dev/sda3 brw-rw---- 1 root disk 8, 4 2008-10-02 15:54 /dev/sda4 brw-rw---- 1 root disk 8, 16 2008-10-02 15:54 /dev/sdb brw-rw---- 1 root disk 8, 17 2008-10-02 15:54 /dev/sdb1 brw-rw---- 1 root disk 8, 18 2008-10-02 15:54 /dev/sdb2 brw-rw---- 1 root disk 8, 19 2008-10-02 15:54 /dev/sdb3 brw-rw---- 1 root disk 8, 20 2008-10-02 15:54 /dev/sdb4 Also /dev/disk/... was present. I now suspect the ENV{ID_FS_USAGE}=="raid" option in udev rules file. How should udev supposed to know if a disk is "raid"? Maybe I should rename something to this "raid"? See below my raid settings: [EMAIL PROTECTED]:~# dmraid -r /dev/sdb: ddf1, ".ddf1_disks", GROUP, ok, 390361088 sectors, data@ 0 /dev/sda: ddf1, ".ddf1_disks", GROUP, ok, 390361088 sectors, data@ 0 [EMAIL PROTECTED]:~# dmraid -s *** Group superset .ddf1_disks --> Active Subset name : ddf1_system size : 390361088 stride : 128 type : mirror status : ok subsets: 0 devs : 2 spares : 0 Hm, should name be here "raid", instead of "ddf1_system"? Thanks, Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]