Controller is running "dumb", all you can do there is "create raid set" and "delete raid set". I resynced the array yesterday. then shut down. then rebooted to Slackware WITHOUT assembling. Ran mdadm -E. All drives have event count 0.3064. So I reboot to debian. 4 out of 5. Event count on the active drives 0.3066, on the mssing still 0.3064. So the disk was kicked when debian assembled. Why? Only thing I could think of was if the controller wasn't ready when mdadm assembled, but since it's the same chip as the onboard controller they should all be there as soon as sata_sil is loaded. I now put sde on yet another controller and see what happens. -- -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K- w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ b++(+++) DI+++ D- G++ e* h>++ r* y? ------END GEEK CODE BLOCK------ http://www.vorratsdatenspeicherung.de -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
