CentOS - Feb 2012 - install detecting disk as sdb not sda

I am trying to install 6.2 on a machine.
I am using PXE as I have done so a number of times.

My hard disk is being detected as sdb and not sda.
My kickstart config is wanting it at sda.

There are no other disks in the unit. It has and SD slot and an esata
although BIOS does not appear to have a disable for either of those devices.

Is there anyway to "force" the disk to sda ?
or find out what its detecting at sda and disable that from the PXE boot 
line?

Doing " dmesg | grep sda" does say SCSI removable disk.

So how can I tell linux to NOT include that when installing?

Thanks,

jerry

On 02/03/2012 12:24 PM, Jerry Geis wrote:
> I am trying to install 6.2 on a machine.
> I am using PXE as I have done so a number of times.
>
> My hard disk is being detected as sdb and not sda.
> My kickstart config is wanting it at sda.
>
> There are no other disks in the unit. It has and SD slot and an esata
> although BIOS does not appear to have a disable for either of those 
> devices.
>
> Is there anyway to "force" the disk to sda ?
> or find out what its detecting at sda and disable that from the PXE 
> boot line?
>
> Doing " dmesg | grep sda" does say SCSI removable disk.
>
> So how can I tell linux to NOT include that when installing?
>
> Thanks,
>
> jerry
Using the kernel boot option "nousb" lets me install.
However, that also stops my usb keyboard from working.

I just need to know how to block the usb-storage driver from loading.
I tried "rdblacklist=usb-storage" but that did not work.

What am I missing? Thanks,

Jerry

Hello Jerry,


On Fri, 03 Feb 2012 12:24:14 -0500 Jerry Geis <geisj at pagestation.com>
wrote:
> I am trying to install 6.2 on a machine.
> I am using PXE as I have done so a number of times.
> 
> My hard disk is being detected as sdb and not sda.
> My kickstart config is wanting it at sda.
> 
> There are no other disks in the unit. It has and SD slot and an esata
> although BIOS does not appear to have a disable for either of those
devices.
> 
> Is there anyway to "force" the disk to sda ?
> or find out what its detecting at sda and disable that from the PXE boot 
> line?
> 
> Doing " dmesg | grep sda" does say SCSI removable disk.
> 
> So how can I tell linux to NOT include that when installing?
I noticed that behaviour with my CentOS6 (installed and kept up-to-date
using yum). This happened since kernel kernel-2.6.32-220.el6.x86_64 and
furthers updates. Was working as expected (my laptop's hdd mounted as
sda) with previous kernels, up to kernel-2.6.32-131.21.1.el6.x86_64.

I wonder if that behaviour, and the *change* of behaviour is an issue
that should be reported, and how to handle it on installed systems!
For now, I'm either booting w/ no USB disk plugged, or booting
a 2.6.32-131 kernel.


Regards,

-- 
wwp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL:
<http://lists.centos.org/pipermail/centos/attachments/20120203/f9dfe4e3/attachment-0005.sig>

On Feb 3, 2012, at 1:34 PM, wwp <subscript at free.fr> wrote:
> Hello Jerry,
> 
> 
> On Fri, 03 Feb 2012 12:24:14 -0500 Jerry Geis <geisj at
pagestation.com> wrote:
> 
>> I am trying to install 6.2 on a machine.
>> I am using PXE as I have done so a number of times.
>> 
>> My hard disk is being detected as sdb and not sda.
>> My kickstart config is wanting it at sda.
>> 
>> There are no other disks in the unit. It has and SD slot and an esata
>> although BIOS does not appear to have a disable for either of those
devices.
>> 
>> Is there anyway to "force" the disk to sda ?
>> or find out what its detecting at sda and disable that from the PXE
boot
>> line?
>> 
>> Doing " dmesg | grep sda" does say SCSI removable disk.
>> 
>> So how can I tell linux to NOT include that when installing?
> 
> I noticed that behaviour with my CentOS6 (installed and kept up-to-date
> using yum). This happened since kernel kernel-2.6.32-220.el6.x86_64 and
> furthers updates. Was working as expected (my laptop's hdd mounted as
> sda) with previous kernels, up to kernel-2.6.32-131.21.1.el6.x86_64.
> 
> I wonder if that behaviour, and the *change* of behaviour is an issue
> that should be reported, and how to handle it on installed systems!
> For now, I'm either booting w/ no USB disk plugged, or booting
> a 2.6.32-131 kernel.
You can try disabling USB disk support in the bios.

-Ross

Hello Reindl,


On Fri, 03 Feb 2012 23:19:26 +0100 Reindl Harald <h.reindl at
thelounge.net> wrote:
> 
> 
> Am 03.02.2012 23:02, schrieb wwp:
> > An aspect of the problem w/ that behaviour change introduced w/ recent
> > kernel updates, is that some mount mapping tables (fstab for instance)
> > are broken if they rely on mount order (sda, hda, etc.) instead of
> > device ID or label.
> 
> if they are doing so they are broken all the time by design
> 
> the last 10 years i saw no single machine not using LABEL and
> the last 4 years no single one not using UUID, even in my RAID10
> i can plug any disk whereever i want
Interesting.. my habits seem very old then :-).

A long time after setting up my CentOS6, I decided to create a
partition in extended area for my personal data, and to automount it at
boot.

This is done in fstab with:
  /dev/sda8 /storage/data    ext4    noatime,nodiratime  0 0
(see how I rely on sda, silly me!)

I grabbed the UUID from `lshal` and replaced it in fstab:
  UUID=005374e2_5c18_437d_84d8_8069868fe54e   ext4    noatime,nodiratime  0 0

.. no luck, it doesn't automount at boot. I think I'll have to
investigate or get another brain update.


Regards,

-- 
wwp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL:
<http://lists.centos.org/pipermail/centos/attachments/20120203/f50e29ec/attachment-0005.sig>

Hello wwp,

On Fri, 2012-02-03 at 23:31 +0100, wwp wrote:
> I grabbed the UUID from `lshal` and replaced it in fstab:
>   UUID=005374e2_5c18_437d_84d8_8069868fe54e   ext4    noatime,nodiratime  0
0
> 
> .. no luck, it doesn't automount at boot. I think I'll have to
> investigate or get another brain update.
Or just add the mount point to that entry :) .

Regards,
Leonard.

-- 
mount -t life -o ro /dev/dna /genetic/research