Sponsored Content
Full Discussion: VIOS LPAR Error 0518
Operating Systems AIX VIOS LPAR Error 0518 Post 302746063 by filosophizer on Tuesday 18th of December 2012 05:28:05 PM
Old 12-18-2012
I am trying to boot from the physical optical media -- that is -- i have assigned the optical media CD/DVD to the LPAR Partition and it boots from the CD-ROM expect that it gets stuck at the led 0518 which is something very strange !
 

10 More Discussions You Might Find Interesting

1. AIX

Problem mapping LUN disk from VIOS to the LPAR

Hello guys, It would be so nice of you if someone can provide me with these informations. 1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies

2. AIX

DUAL VIOS & Client LPAR hangs at 25b3

I have a DUAL VIO ( IBM Virtual I/O ) setup on p 570. Two Vio server ( VIOS ) and many LPAR clients. VIO ( latest version + service pack + applied the fix ) and AIX 6.1 ML2 When both VIOs are running, and if I turn on a Client LPAR, the LPAR hangs at LED 25b3 for more than 1 hour then it... (2 Replies)
Discussion started by: filosophizer
2 Replies

3. AIX

VIOS to lpar Mapping

Hello, I have created mapping of 2 virtual adapters for Lpars using following command: mkvdev -vdev ipanalyzerlv1 -vadapter vhost11 mkvdev -vdev ipanalyzerlv -vadapter vhost13 The above two commands were succesfull but when I want to map the third virtual device to the same Lpar than... (3 Replies)
Discussion started by: Vit0_Corleone
3 Replies

4. AIX

LPAR freezes after switching of storage (lpar is mirrored)

Hi all, I have the following configuration 2 ds3524 storage disk systems located over 2 locations 2 P720 server located over 2 locations DS3524 are connected to san switch. Each vio server has 1 fc adapter attached to a san switch. per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies

5. AIX

What's the difference between VIOS and LPAR?

Hi All, Besides the licenses on VIO and LPAR. What's the main difference with the two? I have installed VIO, my manager told me so, because it's like a free hypervisor but I never installed LPAR before. How do you install it? And if you can give more info on the two, that would be great. ... (5 Replies)
Discussion started by: itik
5 Replies

6. AIX

VIOS IP address - separate vlan for vios servers ?

Hello, Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2. What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies

7. AIX

List LPAR from VIOS

Hi guys, does anyone know how to get a list of the LPAR running on VIOS? Thanks! (5 Replies)
Discussion started by: cecco16
5 Replies

8. AIX

Moving VIOS, LPAR's, HMC to different subnet

Hi, Just joined to new company with one Power 720 Express (8202-E4C) server and have no much experience with IBM systems. I am trying to move everything I mentioned to different subnet as required by customer contract (currently sitting on same subnet as company lan). Access to this subnet will... (8 Replies)
Discussion started by: spricer
8 Replies

9. AIX

VIOS: Extend virtual disk assigned to running lpar?

Hello, VIOS 2.2.1.4 using IVM. I'm trying to extend a virtual disk assigned to a running lpar so that I can expand the lpar's datavg and grow some filesystems for the user. Storage admin expanded the lun and new size was reflected in VIO right away. I then needed the storage pool to... (2 Replies)
Discussion started by: j_aix
2 Replies

10. UNIX for Advanced & Expert Users

Unable to install client AIX LPAR to vscsi hdisk provided from VIOS

Hi everybody, I have Power5 server with 4 internal hdisks each of 70Gb. VIOS server was installed via Virtual I/O Server Image Repository on the HMC. HMC release - 7.7.0 VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies
UDISKS(7)							      udisks								 UDISKS(7)

NAME
udisks - Storage Management DESCRIPTION
udisks provides an interface to enumerate storage devices and perform operations on them. Any application can access the org.freedesktop.UDisks service on the system message bus. Some operations (such as formatting disks etc.) is restricted using polkit. DEVICE INFORMATION
On Linux, udisks relies on recent versions of udev(7) and the kernel. Influential device properties in the udev database include: UDISKS_PRESENTATION_HIDE If set to 1 this is a hint to presentation level software that the device should not be shown to the user. UDISKS_PRESENTATION_NOPOLICY If set to 1 this is a hint to presentation level software that the device should not be automounted or autoassembled (for e.g. components of a multi-disk device). UDISKS_DISABLE_POLLING If set to 1 this will disable the polling of drives for media changes, for devices which do not send out media notifications by themselves (this mostly affects CD drives). Some CD drives cause bad effects such as very high CPU usage when being polled. UDISKS_PRESENTATION_NAME The name to user for the device when presenting it to the user. UDISKS_PRESENTATION_ICON_NAME The icon to use when presenting the device to the user. If set, the name must follow the freedesktop.org icon theme specification. The ID_DRIVE_* properties are used to describe what kind of physical media can be used in a device. These are typically set on the main block device (e.g. /dev/sdb) and more than one these properties can be set if the device supports multiple kinds of media. ID_DRIVE_EJECTABLE Whether the media in the drive is physically ejectable. Only set this to 1 (or 0) if the drive truly uses (or doesn't) ejectable media. In particular, it is not necessary to set this for e.g. iPod or Kindle devices where it is necessary to send a command via eject(1) since the desktop user session will offer this option for removable devices regardless of whether they are ejectable. If this property is not set, a heuristic will be used to determine if the media is ejectable (drives using optical, Zip or Jaz media are considered ejectable). ID_DRIVE_DETACHABLE Whether the device is detachable. It is only meaningful to set this to 0 (to avoid marking a device as detachable) since the code for detaching the device is part of udisks itself. If this property is not set, a heuristic will be used to determine if the drive is detachable (currently only devices connected through USB are detachable). ID_DRIVE_CAN_SPINDOWN Whether the device can spin down. It is only meaningful to set this to 0 (to avoid marking a device as being capable of spinning down) since the code for spinning down the device is part of udisks itself. If this property is not set, a heuristic will be used to determine if the drive can spin down (currently only ATA devices, including those USB devices with a SAT layer) can be spun down). ID_DRIVE_FLASH The device is compatible with flash. ID_DRIVE_FLASH_CF The device is compatible with Compact Flash. ID_DRIVE_FLASH_MS The device is compatible with Memory Stick. ID_DRIVE_FLASH_SM The device is compatible with SmartMedia. ID_DRIVE_FLASH_SD The device is compatible with SecureDigital. ID_DRIVE_FLASH_SDHC The device is compatible with High-Capicity SecureDigital. ID_DRIVE_FLASH_MMC The device is compatible with MultiMediaCard. ID_DRIVE_FLOPPY The device is compatible with floppy disk. ID_DRIVE_FLOPPY_ZIP The device is compatible with Zip. ID_DRIVE_FLOPPY_JAZ The device is compatible with Jaz. The ID_DRIVE_MEDIA_* properties describe the current media in a device. As with the ID_DRIVE_* properties, these properties are typically set on the main block device (e.g. /dev/sdb). Typically only one of these properties are set. ID_DRIVE_MEDIA_FLASH The physical media currently inserted into the device is flash. ID_DRIVE_MEDIA_FLASH_CF The physical media currently inserted into the device is Compact Flash. ID_DRIVE_MEDIA_FLASH_MS The physical media currently inserted into the device is Memory Stick. ID_DRIVE_MEDIA_FLASH_SM The physical media currently inserted into the device is SmartMedia. ID_DRIVE_MEDIA_FLASH_SD The physical media currently inserted into the device is SecureDigital. ID_DRIVE_MEDIA_FLASH_SDHC The physical media currently inserted into the device is High-Capicity SecureDigital. ID_DRIVE_MEDIA_FLASH_MMC The physical media currently inserted into the device is MultiMediaCard. ID_DRIVE_MEDIA_FLOPPY The physical media currently inserted into the device is floppy disk. ID_DRIVE_MEDIA_FLOPPY_ZIP The physical media currently inserted into the device is Zip. ID_DRIVE_MEDIA_FLOPPY_JAZ The physical media currently inserted into the device is Jaz. REMOTE CLIENTS
TODO: write me. AUTHOR
Written by David Zeuthen david@fubar.dk with a lot of help from many others. BUGS
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at http://bugs.freedesktop.org/enter_bug.cgi?product=udisks. SEE ALSO
udev(7), polkit(8), udisks-daemon(8), udisks-tcp-bridge(1), udisks(1) udisks March 2008 UDISKS(7)
All times are GMT -4. The time now is 05:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy