During a kickstart install, how are drives mapped? I notice that sata0 is not
always sda. This is especially true when there are very large drives in the
mix.
On 02/18/2013 02:01 PM, Ken Teh wrote:
During a kickstart install, how are drives mapped? I notice that sata0
is not always sda. This is especially true when there are very large
drives in the mix.
The sd* letters are simply handed out in order of enumeration and, as
you noted, is not determ
On Mon, Feb 18, 2013 at 4:01 PM, Ken Teh wrote:
> During a kickstart install, how are drives mapped? I notice that sata0 is
> not always sda. This is especially true when there are very large drives in
> the mix.
It Depends(tm). There are confusing difficulties because the drive
controllers may
If the disks cannot be identified deterministically, then I cannot avoid
making my kickstart installs 2-stepped. Whether I pre-label the disks or
install the system with a single disk and add the second disk after the
install.
I appreciate the situation from the kernel's perspective. Driver load
On Feb 19, 2013, at 13:38 , Ken Teh wrote:
> If the disks cannot be identified deterministically, then I cannot avoid
> making my kickstart installs 2-stepped. Whether I pre-label the disks or
> install the system with a single disk and add the second disk after the
> install.
You could detect
On Mon, Feb 18, 2013 at 07:33:37PM -0700, Orion Poplawski wrote:
> On 02/18/2013 02:01 PM, Ken Teh wrote:
> >During a kickstart install, how are drives mapped? I notice that sata0
> >is not always sda. This is especially true when there are very large
> >drives in the mix.
>
> The sd* letters ar
On 02/19/2013 05:38 AM, Ken Teh wrote:
If the disks cannot be identified deterministically, then I cannot avoid
making my kickstart installs 2-stepped. Whether I pre-label the disks or
install the system with a single disk and add the second disk after the
install.
I appreciate the situation fr
On 02/18/2013 11:06 PM, Nico Kadel-Garcia wrote:
IDE drives used to be listed as "/dev/ide0, /dev/ide1, etc." in
deterministic fashion, but that got tossed out when they started
labeling all drives as /dev/sda to gove access to special SCSI
compatible commands.
Aka 'the libata takeover'.
On 03/04/2013 12:03 PM, Lamar Owen wrote:
This is partially due in EL6 to the use of dracut and it's new initrd
udev-ish system. I have one RHEL 6 box that is hooked to a pretty good-sized
array on fibre-channel; it's fully HA, so there are four paths to any given
LUN. My boot device, a 3Ware 95
On Mon, Mar 04, 2013 at 01:14:20PM -0600, Ken Teh wrote:
>
> I use kickstart to upgrade machines by doing a full install. I reserve the
> system disks so I can wipe them out and reinstall at will.
> ...
> Now that I don't know which disk is which, ...
>
This is an intractable problem - Linux do
On Mon, Feb 18, 2013 at 03:01:00PM -0600, Ken Teh wrote:
>
> During a kickstart install, how are drives mapped?
>
Effectively randomly.
For example, if I run the SL6.3 installer from a USB disk,
sometimes this USB disk is named /dev/sda and the installer puts GRUB
on it, instead of the disks wher
On 03/04/2013 02:14 PM, Ken Teh wrote:
I've seen the same behaviour with my LSI MegaRAIDs and I find it very
disconcerting.
EL6 was supposed to not be as nondeterministic as it has ended up being
(I know, horrible grammar, but gets the point across). Later Fedoras
are worse in this respect.
On 02/19/2013 10:14 AM, Graham Allan wrote:
On Mon, Feb 18, 2013 at 07:33:37PM -0700, Orion Poplawski wrote:
On 02/18/2013 02:01 PM, Ken Teh wrote:
During a kickstart install, how are drives mapped? I notice that sata0
is not always sda. This is especially true when there are very large
drive
On Wed, Feb 20, 2013 at 8:57 AM, Pat Riehecky wrote:
> On 02/19/2013 10:14 AM, Graham Allan wrote:
>> On Mon, Feb 18, 2013 at 07:33:37PM -0700, Orion Poplawski wrote:
>>> On 02/18/2013 02:01 PM, Ken Teh wrote:
During a kickstart install, how are drives mapped? I notice that sata0
is
On 2013/02/21 04:26, Tom H wrote:
On Wed, Feb 20, 2013 at 8:57 AM, Pat Riehecky wrote:
On 02/19/2013 10:14 AM, Graham Allan wrote:
On Mon, Feb 18, 2013 at 07:33:37PM -0700, Orion Poplawski wrote:
On 02/18/2013 02:01 PM, Ken Teh wrote:
During a kickstart install, how are drives mapped? I not
On Wed, Feb 20, 2013 at 07:57:22AM -0600, Pat Riehecky wrote:
> On 02/19/2013 10:14 AM, Graham Allan wrote:
> >On Mon, Feb 18, 2013 at 07:33:37PM -0700, Orion Poplawski wrote:
> >>On 02/18/2013 02:01 PM, Ken Teh wrote:
> >>>During a kickstart install, how are drives mapped? I notice that sata0
> >
I just do this
"
clearpart --all
part /boot --fstype ext3 --size=100
part pv.01 --size=10 --grow
volgroup SystemVG00 pv.01
logvol swap --fstype swap --name=SwapVol01 --vgname=SystemVG00 --size=12288
logvol / --fstype ext4 --name=RootVol --vgname=SystemVG00 --size=5120
logvol /usr --fstype ext4 --na
On Thu, Feb 21, 2013 at 5:41 PM, jdow wrote:
> On 2013/02/21 04:26, Tom H wrote:
>>
>> You can use "list-hardrives" in "%pre" and parse its output.
>>
>> If you want to see what its output looks like, you can install
>> anaconda - although the actual anaconda executable, IIRC, is
>> "list-hardrive
18 matches
Mail list logo
