Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1962419.1
Update Date:2017-02-01
Keywords:

Solution Type  Technical Instruction Sure

Solution  1962419.1 :   Procedure for Copying the USB Image to a USB Flash Drive, When DVD drive is not Responsive  


Related Items
  • Oracle Communications Performance Intelligence Center (PIC) Software
  •  
  • Oracle Communications EAGLE (Software)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec Eagle 5
  •  




In this Document
Goal
Solution


Created from <SR 3-10117397581>

Applies to:

Oracle Communications EAGLE (Software) - Version EPAP 14.0 and later
Oracle Communications Performance Intelligence Center (PIC) Software - Version 10.2.0 to 10.2.0 [Release 10.0]
Information in this document applies to any platform.

Goal

Copying the USB Image to a USB Flash Drive, When DVD drive is not Responsive.

During an activity on an EPAP, TPD media validation, the DVD was not getting detected for both EPAPS. The issue has been observed for a long time back.

Additional Observations: While checking BIOS for A server first boot device was "Intel(R)RMM2 VDrive 1"; in CDROM order menu also i could see only 4 (instead of 5) options that to of Intel(R)RMM2 VDrive 1.

Powered off and removed the CD drive from the EPAP and Inserted it back, still the problem did not resolve.

Solution

DVD drive was not responsive. An alternate procedure was used. Copying the USB image to a USB Flash drive. Pocedure shared below is successful.

Copying the USB image to a USB flash drive to achieve a Bootable Image:

For Tekelec Platform Distribution (TPD) and TVOE where bootable USB media is required for system installation, the following instructions are provided to Copy the USB image for TPD and /or TVOE identified in the table above to a USB Flash Drive in a manner that yields a bootable image for use on the system. For all other software images where a USB is preferred media for loading the system (example: blade servers), software images can be transferred to USB using a standard “drag and drop” methodology after downloading to your site.

  1. Run fdisk to determine what devices exist PRIOR to plugging in the USB device:
    # fdisk -l | grep "Disk /dev"
    Disk /dev/sda: 300.0 GB, 299966445568 bytes
    Disk /dev/sdb: 1499.8 GB, 1499830990848 bytes
    Disk /dev/mapper/vgroot-plat_root: 1073 MB, 1073741824 bytes
    Disk /dev/mapper/vgbuild-home: 1499.8 GB, 1499828584448 bytes
    Disk /dev/mapper/vgroot-plat_var: 1073 MB, 1073741824 bytes
    Disk /dev/mapper/vgroot-plat_usr: 4294 MB, 4294967296 bytes
    Disk /dev/mapper/vgroot-plat_tmp: 1073 MB, 1073741824 bytes
    Disk /dev/mapper/vgroot-plat_var_tklc: 4294 MB, 4294967296 bytes
    Disk /dev/mapper/vgroot-scratchpad: 287.9 GB, 287863472128 bytes
  2. Insert USB drive
  3. Run fdisk again to determine how the USB device was enumerated (/dev/sdc in this example)
    # fdisk -l | grep "Disk /dev"
    Disk /dev/sda: 300.0 GB, 299966445568 bytes
    Disk /dev/sdb: 1499.8 GB, 1499830990848 bytes
    Disk /dev/mapper/vgroot-plat_root: 1073 MB, 1073741824 bytes
    Disk /dev/mapper/vgbuild-home: 1499.8 GB, 1499828584448 bytes
    Disk /dev/mapper/vgroot-plat_var: 1073 MB, 1073741824 bytes
    Disk /dev/mapper/vgroot-plat_usr: 4294 MB, 4294967296 bytes
    Disk /dev/mapper/vgroot-plat_tmp: 1073 MB, 1073741824 bytes
    Disk /dev/mapper/vgroot-plat_var_tklc: 4294 MB, 4294967296 bytes
    Disk /dev/mapper/vgroot-scratchpad: 287.9 GB, 287863472128 bytes
    Disk /dev/sdc: 2044 MB, 2044723200 bytes
  4. Run dmesg to confirm how the USB device was enumerated
    # dmesg | tail -20
    usb 1-5: Manufacturer: Generic
    usb 1-5: SerialNumber: F8F3A1CA
    usb 1-5: configuration #1 chosen from 1 choice
    Initializing USB Mass Storage driver...
    scsi3 : SCSI emulation for USB Mass Storage devices
    usb-storage: device found at 2
    usb-storage: waiting for device to settle before scanning
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    usb-storage: device scan complete
    scsi 3:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 2
    sd 3:0:0:0: Attached scsi generic sg4 type 0
    sd 3:0:0:0: [sdc] 3993600 512-byte logical blocks: (2.04 GB/1.90 GiB)
    sd 3:0:0:0: [sdc] Write Protect is off
    sd 3:0:0:0: [sdc] Mode Sense: 03 00 00 00
    sd 3:0:0:0: [sdc] Assuming drive cache: write through
    sd 3:0:0:0: [sdc] Assuming drive cache: write through
     sdc: sdc1
    sd 3:0:0:0: [sdc] Assuming drive cache: write through
    sd 3:0:0:0: [sdc] Attached SCSI removable disk
  5. Run fdisk command on the newly enumerated device name to determine the partition name (sdc1 in this example)
    # fdisk -l /dev/sdc
    Disk /dev/sdc: 2044 MB, 2044723200 bytes
    31 heads, 30 sectors/track, 4294 cylinders
    Units = cylinders of 930 * 512 = 476160 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x3fb6f5c2

    Device Boot Start End Blocks Id System
    /dev/sdc1 2 4295 1996040 6 FAT16
  6. Use the dd command to copy the image to the USB device (to the device and not the partition)
    # dd if=TPD.install-6.5.1_82.28.5-CentOS6.4-x86_64.usb of=/dev/sdc
    2306305+0 records in
    2306305+0 records out
    1180828160 bytes (1.2 GB) copied, 504.454 s, 2.3 MB/s
  7. Remove USB drive and reinsert it. Run dmesg again to determine name.
    # dmesg | tail -20
    usb 1-5: Product: Mass Storage
    usb 1-5: Manufacturer: Generic
    usb 1-5: SerialNumber: F8F3A1CA
    usb 1-5: configuration #1 chosen from 1 choice
    scsi4 : SCSI emulation for USB Mass Storage devices
    usb-storage: device found at 3
    usb-storage: waiting for device to settle before scanning
    usb-storage: device scan complete
    scsi 4:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 2
    sd 4:0:0:0: Attached scsi generic sg4 type 0
    sd 4:0:0:0: [sdc] 3993600 512-byte logical blocks: (2.04 GB/1.90 GiB)
    sd 4:0:0:0: [sdc] Write Protect is off
    sd 4:0:0:0: [sdc] Mode Sense: 03 00 00 00
    sd 4:0:0:0: [sdc] Assuming drive cache: write through
    sd 4:0:0:0: [sdc] Assuming drive cache: write through
     sdc: unknown partition table
    sd 4:0:0:0: [sdc] Assuming drive cache: write through
    sd 4:0:0:0: [sdc] Attached SCSI removable disk
    ISO 9660 Extensions: Microsoft Joliet Level 3
    ISO 9660 Extensions: RRIP_1991A
  8. Mount the partition on the USB device to the /media mount point (use partition name and not device): # mount /dev/sdc1 /media
  9. Verify the USB contents look as expected (example below is from TPD)
    # lsf /media
    total 835588
    drwxr-xr-x 5 root root 4096 Dec 31 1969 ./
    dr-xr-xr-x. 29 root root 4096 Jan 11 17:10 ../
    drwxr-xr-x 3 root root 4096 Jan 11 14:22 images/
    -r-xr-xr-x 1 root root 32768 Jan 11 13:22 ldlinux.sys*
    drwxr-xr-x 2 root root 4096 Jan 11 14:22 syslinux/
    -rwxr-xr-x 1 root root 855554048 Jan 11 14:22 TPD.install-6.5.1_82.28.5-CentOS6.4-x86_64.iso*
    -rwxr-xr-x 1 root root 32229 Jan 11 14:22 TPD.ks*
    drwxr-xr-x 4 root root 4096 Jan 11 14:22 umvt/
  10. Mount the ISO image (may be different for non-TPD USB images) from the USB image to another mount point: mount -o loop /media/TPD.install-6.5.1_82.28.5-CentOS6.4-x86_64.iso /mnt/upgrade
  11. Run command to validate the ISO image: # /mnt/upgrade/upgrade/.validate/validate_cd
    Validating cdrom:
    UMVT Validate Utility v2.2.2, (c)Tekelec, June 2012
    Validating /media/TPD.install-6.5.1_82.28.5-CentOS6.4-x86_64.iso
    Date&Time: 2014-01-14 17:53:31
    Volume ID: tklc_000-0000-000_Rev_A_82.28.5
    Part Number: 000-0000-000_Rev_A
    Version: 82.28.5
    Disc Label: TPD
    Disc description: TPD
    The media validation is complete, the result is: PASS

    CDROM is Valid
  12. Unmount the ISO image:
    # umount /mnt/upgrade
  13. Unmount the USB device:
    # umount /media

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback