Correction -- after booting in the "break=mount" scenario my ATA (not SATA) drives are still identified as /dev/sda and /dev/sdb according to /proc/mdstat:
root@heimdall:~# cat /proc/mdstat Personalities : [raid1] ... md1 : active raid1 sda5[0] sdb5[1] 497856 blocks [2/2] [UU]
The same holds true for the "let it fail" and "sleep 10" boot scenarios. I guess this is a new feature.
I hadn't noticed this previously, since the Feisty system I've been working with most uses SATA, and SATA has always shown up as SCSI.
Correction -- after booting in the "break=mount" scenario my ATA (not SATA) drives are still identified as /dev/sda and /dev/sdb according to /proc/mdstat:
root@heimdall:~# cat /proc/mdstat
Personalities : [raid1]
...
md1 : active raid1 sda5[0] sdb5[1]
497856 blocks [2/2] [UU]
The same holds true for the "let it fail" and "sleep 10" boot scenarios. I guess this is a new feature.
I hadn't noticed this previously, since the Feisty system I've been working with most uses SATA, and SATA has always shown up as SCSI.