SCIENTIFIC-LINUX-USERS Archives

March 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Urs Beyerle <[log in to unmask]>
Reply To:
Urs Beyerle <[log in to unmask]>
Date:
Tue, 15 Mar 2011 21:22:33 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
On 03/14/2011 07:35 PM, Tom H wrote:
> On Sun, Mar 13, 2011 at 3:16 PM, Urs Beyerle<[log in to unmask]>  wrote:
>> On 03/13/2011 07:46 PM, Tom H wrote:
>>> Usually md devices are renamed/renumbered when "/etc/mdadm.conf" has
>>> "HOMEHOST<system>" set and the metadata in the superblock has a
>>> different homehost value.
>> The file /etc/mdadm.conf does not exist on the LiveCD. Therefore the md
>> devices should not be renamed...?
>>
>> Bluejay, do you see /etc/mdadm.conf, if you boot your system with the
>> LiveCD?
> I've checked the Live CD that I have and it doesn't have
> "/etc/mdadm.conf". The install that I made with the Live CD does have
> one though, which I find confusing because I thought (incorrectly it
> seems) that a Live CD install is made from the same image as the Live
> CD itself. It doesn't have "HOMEHOST<system>" but it is set to
> automount some arrays.

In SL6, the LiveCD install first copies the LiveCD image to hard drive. Afterwards anaconda is finishing the install which includes to create /etc/mdadm.conf:

# mdadm.conf written out by anaconda

This was not the case for SL5 and SL4 LiveCD, where the install was just a copy of the running LiveCD to hard drive.

ATOM RSS1 RSS2