Robin Atwood wrote:
On Wednesday 16 Jul 2008, Rob van der Heij wrote:
On Wed, Jul 16, 2008 at 12:32 PM, Robin Atwood <[EMAIL PROTECTED]> wrote:
I think the problem is that my target device is /dev/md1 which is not a
real disk, it's a pseudo-device manufactured by the mdadm command from
two real partitions.
That sure is a problem. But since you don't write to the boot
partition a lot, could you not just maintain the two identical copies
yourself?
That's what I am beginning to think. :( I was hoping someone on the list has
tried this and has a definitive answer.
-Robin
--
----------------------------------------------------------------------
Robin Atwood.
"Ship me somewheres east of Suez, where the best is like the worst,
Where there ain't no Ten Commandments an' a man can raise a thirst"
from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
fwiw, grub has been patched to work with RAID. A quick grep of the (Red
Hat) RPM changelog shows:
- add dmraid support (
[snip]
- Always install in MBR for raid1 /boot/
[snip]
- reworked much of how the RAID1 support in grub-install works.
Not sure how hard it would be to implement this in zipl.
--
Brad Hinson <[EMAIL PROTECTED]>
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198
www.redhat.com/z
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
