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


Comments

Popular posts from this blog

RHN Satellite Server (spacewalk) repomd.xml not found

"repomd.xml not found" If you add a channel, or if your RHN cache gets corrupted, and one of your guests complains that it cannot find repomd.xml for jb-ews-2-x86_64-server-5-rpm (for example) - you need to rebuild your repodata cache. Normally this is an automated job - which is exemplified by the fact that you have obviously built out your entire Satellite environment and never had to do any of the steps you are about to do. So - some prep work: Open 3 terminals to your Satellite Server and run: # Term 1 cd /var/cache/rhn watch "ls -l | wc -l" # Term 2 pwd cd /var/log/rhn tail -f rhn_taskomatic_daemon.log # Term 3 satellite-sync --channel=jb-ews-2-x86_64-server-5-rpm Once the satellite-sync has completed, you >should< see the count increment by one.  If you are unlucky (like me) you will not. You then need to login to the Satellite WebUI as the satellite admin user. Click on the Admin tab (at the top) Task Schedules (on the left) fin

Install RHEL 7 on old HP DL380 g5

Someone at work had been running RHEL on an HP DL380 G5 and blew it up.  After several attempts at doing an installation that made me conclude the hardware was actually bad... I kept digging for the answer. Attempt install and Anaconda could not find any disks - try a Drivers Disk (dd.img) both cciss and hpsa.   -- once we did that, when the system would reboot it would say it could not find a disk. hmmm. Boot from your installation media and interrupt the startup at grub. Add hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1 to the line starting with linuxefi press CTRL-X to boot. Once the system restarts after the install, you need to once again interrupt the startup and add the line from above. After the system starts, edit /etc/default/grub and add those 2 parameters to the end of the line starting with GRUB_CMDLINE_LINUX (which likely has quiet at the end of the line currently). then run # cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.orig # grub2-mkconfig -o /boot/grub2

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un