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
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT OSX
mount_udf
MOUNT_UDF(8) BSD System Manager's Manual MOUNT_UDF(8)
NAME
mount_udf -- mount a UDF filesystem
SYNOPSIS
mount_udf [-o options] [-s sessionStart] [-n lastRecordedLBA] [-b blockSize] [-p packetSizeInBlocks] [-v verificationPolicy] [-w] devicePath
mountPath
DESCRIPTION
The mount_udf command attaches the UDF filesystem residing on the device devicePath to the global filesystem namespace at the location indi-
cated by mountPath. This command is normally executed by mount(8) at boot time.
The options are as follows:
-o options
Options are specified with a -o flag followed by a comma separated string of options. See the mount(8) man page for possible options
and their meanings.
-v verificationPolicy
This is an advanced option not useful for regular use. It controlls the verification policy when writing to RW type optical media.
Its value can be "meta", "all", or "none". Policy "meta" means only the metadata are verified after they are written. This is the
default policy. Policy "all" means to verify data written, which could be several times slower than policy "meta". Policy "none"
does not verify any data. It is only slightly faster than "meta" in normal cases, but may result a corrupted UDF disc if the write
of metadata fails.
-s sessionStart
This is an advanced option not useful for regular use. When manually mounting a UDF volume with Virtual Partition, it specifies the
start Logical Block Address of the last session where UDF data structures (VRS and AVDP) resides. This value overrides the value
obtained from the device.
-n lastRecordedLBA
This is an advanced option not useful for regular use. When manually mounting a UDF volume with Virtual Partition, it specifies the
last recorded Logical Block Address where the UDF VAT ICB will be searched. This value overrides the value obtained from the device.
-b blockSize
This is an advanced option not useful for regular use. It specifies the block size in bytes used when mounting the UDF volume. This
value overrides the value obtained from the device.
-p packetSizeInBlocks
This is an advanced option not useful for regular use. It specifies the packet size in blocks when manually mounting the UDF volume.
This value overrides the value obtained from the device.
-w This is an advanced option not useful for regular use. It forces to enable the experimental packet writing function on optical media
that has not been fully supported, such as CD-R, CD-RW, DVD-R, DVD+R, HD DVD-R, and BD-R. Writing to these media does not work on
some drives and may cause data corruption or data loss on some other drives. Therefore, this flag should be used only by file system
developers when debugging the experimental write functions.
The -s, -n, -b, and -p flags are not useful in normal use. They are mainly used for debugging and data recovery. Since the -s, -n, and -p
flags are all specified in units of block size, when any of these flags are specified, it is strongly recommended that the -b flag is also
specified.
SEE ALSO
mount(2), unmount(2), fstab(5), mount(8)
BUGS
Reading of all UDF revisions (1.02 - 2.60) on both block device (e.g., hard drives and USB drives) and most optical media is supported.
Writing to block devices, DVD-RW and DVD+RW is supported with the following exceptions: (1) Cannot write Finder Info, Resource Fork, or other
extended attributes in UDF volumes of revision 1.02 and 1.50; (2) Cannot write to mirrored metadata partition.
HISTORY
The mount_udf utility first appeared in Mac OS X.
4th Berkeley Distribution December 6, 2006 4th Berkeley Distribution