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-GLUE.CONF(5)						udisks-glue Manual					       UDISKS-GLUE.CONF(5)

NAME
udisks-glue.conf - udisks-glue configuration file format SYNOPSIS
~/.udisks-glue.conf $XDG_CONFIG_HOME/udisks-glue/config /etc/udisks-glue.conf $XDG_CONFIG_DIRS/udisks-glue/config DESCRIPTION
udisks-glue is configured by a series of match directives referencing filter directives. Filter directives define parameters that filter the UDisks events. Match directives specify actions to be taken by udisks-glue in case the corresponded filter matches. Filter and match directives can be specified in any order. You should use unique names for filter directives. The rules are evaluated in the order the match directives are specified. A default directive is a special directive used as a fallback in case no other directives match. It does not reference a filter directive. You may choose not to specify a default directive. Due to the way the rules are evaluated, it's recommended that more specific match directives are defined before less specific ones. If a match directive does not specify one of the available actions, another directive may be chosen. The currently available match directives are: automount If set, try to automatically mount the device (unset by default) automount_filesystem Filesystem type to use when automounting the device automount_options List of options to use when automounting the device post_insertion_command Command to run after a device is inserted or after its media has been made available post_mount_command Command to run after a device has been mounted post_unmount_command Command to run after a device has been unmounted post_removal_command Command to run after a device or its media has been removed udisks-glue will substitute some tokens with information about the device in each of the commands listed above: %device_file Path to the device file %mount_point Last known mount point for the device (only replaced in post_mount_command and post_unmount_command) The currently supported filter parameters are: label (string) User-visible label of the detected file system optical (boolean) Set if the device uses optical disc as its media optical_disc_closed (boolean) Set if the optical disc is closed optical_disc_has_audio_tracks (boolean) Set if the optical disc has audio tracks optical_disc_has_audio_tracks_only (boolean) Set if all tracks in the optical disc are audio tracks partition (boolean) Set if the device is a partition of another device partition_table (boolean) Set if the device has a partition table readonly (boolean) Set if the device is a ready-only device removable (boolean) Set if the device is a removable device type (string) Extended information about the device, generally set to the name of the detected file system if the usage property is set to filesystem usage (string) The result of probing for signatures on the block device, generally set to filesystem if a mountable file system was detected uuid (string) UUID of the detected file system Note that the rules are evaluated only at the time the device or its media is inserted. Internal drives are always ignored. EXAMPLE
The following configuration example shows how you can automount USB pendrives and similar devices. Notifications are provided by a custom script that could display on-screen information or provide notifications in some other way: filter disks { optical = false partition_table = false usage = filesystem } match disks { automount = true automount_options = sync post_mount_command = "mount-notify mounted %device_file %mount_point" post_unmount_command = "mount-notify unmounted %device_file %mount_point" } A more complex example shows how the filters can be used to mount optical and non-optical media (USB pendrives and the like) using differ- ent mount options and how a specific program can be launched on non-closed optical discs. # # Filters # filter disks { optical = false partition_table = false usage = filesystem } filter burnable { optical = true optical_disc_closed = false } filter optical { optical = true } # # The default entry (only used if no filters match) # default { post_insertion_command = "insertion-notify %device_file" } # # Additional entries # match disks { automount = true automount_options = { sync, noatime } post_mount_command = "mount-notify mounted %device_file %mount_point" post_unmount_command = "mount-notify unmounted %device_file %mount_point" } match burnable { post_insertion_command = "k3b %device_file" post_mount_command = "mount-notify mounted %device_file %mount_point" post_insertion_command = "udisks --mount %device_file --mount-options ro" } match optical { automount = true automount_options = ro post_mount_command = "mount-notify mounted %device_file %mount_point" post_insertion_command = "udisks --mount %device_file --mount-options ro" } SEE ALSO
udisks(1), udisks-glue(1) udisks(7), udisks-daemon(8) udisks-glue 2011-04-20 UDISKS-GLUE.CONF(5)
All times are GMT -4. The time now is 01:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy