[Info-vax] booting on a single disk from a shadowset
Jan-Erik Soderholm
jan-erik.soderholm at telia.com
Sat Feb 13 06:18:23 EST 2016
Den 2016-02-13 kl. 11:04, skrev Phillip Helbig (undress to reply):
> In article <ba8cf374-2a87-49da-b8a9-8901a2ac853e at googlegroups.com>, Tom
> Adams <tadamsmar at gmail.com> writes:
>
>> On Friday, February 12, 2016 at 3:08:55 AM UTC-5, Phillip Helbig (undress to reply) wrote:
>>> In article <Z4NC8wkAhles at eisner.encompasserve.org>,
>>> koehler at eisner.nospam.decuserve.org (Bob Koehler) writes:
>>>
>>>> In article <94e01af7-f13e-4387-bc85-5d6bc76f3f83 at googlegroups.com>, Tom Adams <tadamsmar at gmail.com> writes:
>>>>>
>>>>> The question is: Is there a quick way to get the system to book as a
>>>>> shadow-set on dka100 when dka0 (the master member) is gone?
>>>>
>>>> Change the dip switch (or whatever) that sets the unit number?
>>>
>>> Better: put both members in BOOTDEF_DEV. This also takes care of the
>>> case that one of the members has died---it can then boot from the other
>>> one automatically.
>>
>> Do you also need to put both members in BOOT_DEV?
>
> As long as both are there, no. It will boot from the one in BOOTDEF_DEV
> and the other member will be added during boot. If the primary member
> fails, then it won't boot from the other one...
What is "the primary member" ??
Note that BOOTDEF_DEV can have multiple entries.
Why shouldn't it try to boot from the next entry
in BOOTDEF_DEV?
More information about the Info-vax
mailing list