Skip to main content

Using Kickstart (anaconda) on Dell with multiple internal disks

A number of our machines have multiple VDs created (i.e. 2 x 75GB for OS, 2 x 146GB for application).

After building an R910 with multiple VDs I discovered that /boot and <SWAP> were on the 75GB device, and the OS was on the 146GB device.  I wanted everything on the 75GB.

<excerpt from kickstart profile>

# STORAGE CONFIGURATION
zerombr yes
clearpart --all --initlabel
bootloader --location=mbr --driveorder=sda,sdb --append="nousbstorage"
part /boot --fstype ext4 --size=512 --asprimary --onbiosdisk=81
part pv.1 --size=1 --grow --onbiosdisk=81
volgroup VolGroup00 pv.1
logvol swap --fstype swap --name=LogVol00 --vgname=VolGroup00 --recommended
logvol / --fstype ext4 --fsoptions=noatime --name=LogVol01 --vgname=VolGroup00 --size=1024 --grow
#logvol / --fstype ext4 --fsoptions=noatime --name=LogVol01 --vgname=VolGroup00 --size=10240
</excerpt>

I had found numerous recommendations to deal with this situation.

  • nousbstorage - doesn't really seem to do anything, but there may be background stuff going on that I do not see/recognize
  • onbiosdisk - this option is pay-dirt.  However, most of the documentation I found did not explain what the option was doing or how to configure it.
- onbiosdisk -
http://en.community.dell.com/techcenter/os-applications/w/wiki/linux-installer-magic.aspx
As you can see from my own example, I did not get as complex as the Dell provided example.

I would like to include is how I was able to determine that Interrupt value (0x81).

Unfortunately you have to start a Kickstart that is ultimately doomed to fail to get the view (above).  Once the Kickstart has proceeded far enough that you are able to hit ALT-F2, do so.  Then run the find command shown in the image.  If you cd to that directory and do an ls -l it will provide a better identifier of which edd device is linked to.  (I may try to grab another screenshot showing that association.)
# find /dev/disk/by-id/
# fdisk -l | grep Disk


Labels:

Comments

Post a Comment

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more