Dear bosses, recently met a themselves unable to solve the problem, since the consult everybody, hope to be able to get the answer!

use two pieces of hard disk on the server group 1 raid 0, the remaining pieces of plate are directly connected the raid controller, drive will be shown after the restart repeatedly order:
Such as originally sda disk into SDD,

To this problem I try to use the udev to set operator binding:
The KERNEL=="sd *", SUBSYSTEM=="block", the PROGRAM=="/usr/lib/udev/scsi_id - g - u - d/dev/% k", RESULT=="3600508 e00000000016154eee56eab00e", NAME="asm - disk1", MODE="0660"
The KERNEL=="sd *", SUBSYSTEM=="block", the PROGRAM=="/usr/lib/udev/scsi_id - g - u - d/dev/% k", RESULT=="35000 c5005616feeb", NAME="asm - disk2," MODE="0660"

results suggest the NAME cannot be used to modify the kernel module NAME, access to information that is different from the 2.6 kernel, the 3.10 kernel NAME assignment key can only be used for front-end ports naming, currently don't have to NAME of hard disk,
Refer to the 3.10 kernel under udev handbook: man udev, understanding to the kernel provides a new method: create a symlink,
Then by modifying the rules file, set the matching mode for scsi_id, has been successfully created for each of the hard disk symlink links:
The KERNEL=="sd *", SUBSYSTEM=="block", the PROGRAM=="/usr/lib/udev/scsi_id - g - u - d/dev/% k", RESULT=="3600508 e00000000016154eee56eab00e", SYMLINK +="asm - disk1", MODE="0660"
KERNEL=="sd *", SUBSYSTEM=="block", the PROGRAM=="/usr/lib/udev/scsi_id - g - u - d/dev/% k", RESULT=="35000 c5005616feeb," SYMLINK +="asm - disk2," MODE="0660"

, but now do not know how to realize the binding drive!! Check a lot of information found a symlink concrete is nothing, to drive name what is the role, so want to consult everybody
1, the symlink can do?
2, how to realize the drive of binding, fixed?