I am not sure how to do either of those things, but I have had
problems with the virtual CD and Floppy drives and I believe you can
disable them in the BIOS.  This is a pain, depending on how many you
have, but its something to try :)

There is probably a reason for having them there, but I have never
been clear on what it was.

On Wed, May 7, 2008 at 5:26 PM, Dale Schuster <[EMAIL PROTECTED]> wrote:
> I'm trying to push an image to both Sun Blades x6220 and Dell Blades m600.
>   Both of these different architectures have Virtual CD-Roms and Virtual
>  Floppy drives which are being detected during the install process.  The
>  image was created on a Dell Poweredge 2950 running RedHat Enterprise Linux
>  4 AS.  I enabled UYOK during image creation and the drivers seem to be
>  loading properly for both brands of hardware.
>
>  The failing process seems to be the initial format of the hard disk using
>  DD.
>
>         run_autoinstall_script
>         >>> /scripts/h1.sh
>
>         get_arch
>         enumerate_disks
>         sda
>         sdb
>         sdc
>         DISKS=3
>
>         Partitioning /dev/sda...
>         Old partition table for /dev/sda:
>         Error: Error opening /dev/sda: No medium found
>         dd if=/dev/zero of=/dev/sda bs=512 count=1 || shellout
>         dd: /dev/sda: No medium found
>         Killing off running processes.
>
>
>  And an excerpt from dmesg shows the detection of the CD-Rom.
>
>         scsi0 : SCSI emulation for USB Mass Storage devices
>         Using cfq io scheduler
>           Vendor: AMI       Model: Virtual CDROM     Rev: 1.00
>           Type:   CD-ROM                             ANSI SCSI revision:
>  02
>         USB Mass Storage device found at 3
>         usb 2-5: new full speed USB device using address 4
>         scsi1 : SCSI emulation for USB Mass Storage devices
>           Vendor: AMI       Model: Virtual Floppy    Rev: 1.00
>           Type:   Direct-Access                      ANSI SCSI revision:
>  02
>         Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
>         USB Mass Storage device found at 4
>         scsi2 : ioc0: LSISAS1068E, FwRev=01160100h, Ports=1, MaxQ=268,
>  IRQ=201
>           Vendor: SEAGATE   Model: ST973402SSUN72G   Rev: 0603
>           Type:   Direct-Access                      ANSI SCSI revision:
>  05
>         SCSI device sdb: 143374738 512-byte hdwr sectors (73408 MB)
>         SCSI device sdb: drive cache: write through
>         SCSI device sdb: 143374738 512-byte hdwr sectors (73408 MB)
>         SCSI device sdb: drive cache: write through
>          sdb: unknown partition table
>         Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
>           Vendor: SEAGATE   Model: ST973402SSUN72G   Rev: 0603
>           Type:   Direct-Access                      ANSI SCSI revision:
>  05
>         SCSI device sdc: 143374738 512-byte hdwr sectors (73408 MB)
>         SCSI device sdc: drive cache: write through
>         SCSI device sdc: 143374738 512-byte hdwr sectors (73408 MB)
>         SCSI device sdc: drive cache: write through
>          sdc: sdc1
>         Attached scsi disk sdc at scsi2, channel 0, id 1, lun 0
>         device-mapper: 4.5.5-ioctl (2006-12-01) initialised:
>  [EMAIL PROTECTED]
>         sr0: scsi-1 drive
>         Uniform CD-ROM driver Revision: 3.20
>         Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
>
>  <snip>
>
>         Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type
>  5
>         Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0,  type
>  0
>         Attached scsi generic sg2 at scsi2, channel 0, id 0, lun 0,  type
>  0
>         Attached scsi generic sg3 at scsi2, channel 0, id 1, lun 0,  type
>  0
>
>
>
>  I've tried to  modify the oscarimage.master script (which is symlinked to
>  h1.sh) to specify /dev/sdb instead of /dev/sda, but it has no effect.
>  Dev/sda is still being referenced.  I think if I don't use the UYOK kernel
>  it will use my modified master install script, but then the SAS hard
>  drives aren't accessible.
>
>  So, to summarize, I want to either get SIS to use my edited version of the
>  installation script and reference /dev/sdb instead of /dev/sda, OR change
>  the boot image to properly detect the hard drives as /dev/sda instead of
>  /dev/sdb.
>
>  Please help.
>
>  ~Dale
>
>  --
>  Dale Schuster
>  Systems Administrator
>  Sierra Nevada Corporation
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>  Don't miss this year's exciting event. There's still time to save $100.
>  Use priority code J8TL2D2.
>  
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>  _______________________________________________
>  Oscar-users mailing list
>  Oscar-users@lists.sourceforge.net
>  https://lists.sourceforge.net/lists/listinfo/oscar-users
>

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Oscar-users mailing list
Oscar-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-users

Reply via email to