El Tue, 19 Apr 2011 00:27:15 -0300, Juan Wifi escribió: > el --verbose da esto: > > root@krypton:~# mdadm --verbose --create /dev/md0 --level=raid1 > --raid-devices=2 /dev/sda /dev/sdb > mdadm: super1.x cannot open /dev/sda: Device or resource busy > mdadm: failed container membership check > mdadm: device /dev/sda not suitable for any style of array > root@krypton:~# > > y no hay caso...
Prueba a crear el raid desde un sistema LiveCD a ver qué te dice, así descartas un problema con el "md" de Debian que ya sería raro, pero quién sabe... :-? Otra cosa... en la wikipedia apuntan algo sobre este mensaje de error: *** http://en.wikipedia.org/wiki/Mdadm#Known_problems Known problems A common error when creating RAID devices is that the dmraid-driver has taken control of all the devices that are to be used in the new RAID device. Error-messages like this will occur: mdadm: Cannot open /dev/sdb1: Device or resource busy Typically, the solution to this problem involves adding the "nodmraid" kernel parameter to the boot loader config. Another way this error can present itself is if the device mapper has its way with the drives. Issue 'dmsetup table' see if the drive in question is listed. 'dmsetup remove <drive id>' will remove the drive from device mapper and the "Device or resource busy" error will go away as well. *** Mira a ver si algunas de estas dos sugerencias aplican en tu caso. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
