Jordan Uggla points out that his fourth patch in http://lists.gnu.org/archive/html/grub-devel/2009-12/msg00276.html addresses part of this, by at least making grub-reboot not do anything rather than acting like grub-set-default; I'll think about that patch some more but it seems reasonable. Making grub-reboot raise an error immediately is harder but possible. Actually supporting your configuration for grub-reboot is hard and may not ever happen, as it requires writing to the RAID array and GRUB deliberately doesn't implement that right now due to safety concerns.
Jordan Uggla points out that his fourth patch in http:// lists.gnu. org/archive/ html/grub- devel/2009- 12/msg00276. html addresses part of this, by at least making grub-reboot not do anything rather than acting like grub-set-default; I'll think about that patch some more but it seems reasonable. Making grub-reboot raise an error immediately is harder but possible. Actually supporting your configuration for grub-reboot is hard and may not ever happen, as it requires writing to the RAID array and GRUB deliberately doesn't implement that right now due to safety concerns.