Ok, so scripts/local-top/dmraid is actually executed even sooner (right before trying to find the root fs). So it should be the right place. If possible, I would prefer to have a look at /var/log/boot.log instead of syslog. That seems to contain the messages that are interesting in a clearer form.
The messages about "ERROR: Cannot retrieve RAID set information for..." I realize are bogus in most cases. The command used to find info uses -si which limits information to only inactive sets and at least in my case the first call to dmraid-activate with one of the raid disks as an argument will bring up the array already. So subsequent calls will find the same Group already active. But that just as a side note.
Ok, so scripts/ local-top/ dmraid is actually executed even sooner (right before trying to find the root fs). So it should be the right place. If possible, I would prefer to have a look at /var/log/boot.log instead of syslog. That seems to contain the messages that are interesting in a clearer form.
The messages about "ERROR: Cannot retrieve RAID set information for..." I realize are bogus in most cases. The command used to find info uses -si which limits information to only inactive sets and at least in my case the first call to dmraid-activate with one of the raid disks as an argument will bring up the array already. So subsequent calls will find the same Group already active. But that just as a side note.