OK, but please: open a separate thread for every separate problem you have. We try to handle (as far as is possible) one problem per thread so that searching for an already given solution later will not be convoluted. Thank you.
Quote:
Originally Posted by lckdanny
I haven't bothered with the other probable problems you encountered while booting (one problem at a time) but you could have found a solution for this by simply entering "0526-001 AIX" into Google. The second hit shown is: Porblem with errorlog (sic!).
We have a frame the uses 2 vios that assign disk storage to LPAR's. We have a LPAr with multiple disk and I want to know how do I tell which vio is serving the disk. For example the LPAr has hdisk 0, 1, 2, 3 all the same size. I want to know which vio is serving hdisk0, 1. (4 Replies)
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)
Hello, we have a wierd and urgent problem, with a few of our p595 LPARs running AIX 5.3. The LPARs ran AIX 5.3 TL 7 and booted off EMC SAN disks, using EMC Powerpath. Every boot we run "pprootdev on" and "pprootdev fix". We can issue "bosboot -a" and we can reboot the machines.
Now, on two... (2 Replies)
Hi Everyone,
I have added new Virtual disk to OS. The main point is I need to bring this whole Disk into LVM control, is it necessary to partition the disk using fdisk command and assign partition type as '8e', or can I directly add that disk into LVM, by running pvcreate command with out... (2 Replies)
:wall::wall::wall:
1. I have created an LPAR in the HMC.
2. I have allocated the storage from an Hitachi AMS2500 and assigned it to the host group.
3. I have zoned the LPAR and Storage on a Brocade 5100. (The zone sees the AMS)
Next I activated the LPAR in the HMC, SMS mode for the mksysb... (3 Replies)
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)
I added a disk to a zpool using "zpool add diskname"
My intention was mirror a zpool disk that no mirror; that is a zpool with only one disk. I did not issue the right command. Now, the disk has been added successfully but I cannot remove nor detach it as Solaris 11 thinks it has data on it... (14 Replies)
hi all i have entered Aix environment 4 months had experienced in linux
what i am facing is i am unable to do sort of RnD with aix like
installation on my own, creating vgs managing networks, the VIOS, storage,lpars,
So we have a setup here almost all are in live production environment
with... (4 Replies)
Hi Guys,
I have fresh new installed VIO 2.2.3.70 on a p710, 3 physical SAS disks, rootvg on hdisk0
and 3 VIO clients through vscsi, AIX7.1tl4 AIX6.1tl9 RHEL6.5ppc, each lpar has its rootvg installed on a LV on datavg (hdisk2) mapped to vhost0,1,2
There is no vg on hdisk1, I use it for my... (1 Reply)
Discussion started by: frenchy59
1 Replies
LEARN ABOUT MINIX
partitio
PARTITION(8) System Manager's Manual PARTITION(8)NAME
partition - make a partition table
SYNOPSIS
partition [-mf] device [type:]size[+*] ...
DESCRIPTION
Partition makes a partition table on device using the types and sizes given. It may be used in combination with repartition(8) for auto-
matic installation of Minix.
You may give up to four type:size[+*] specifications for the partitions. You may also specify holes before, between, and after the parti-
tions. A hole differs from a partition specification by not having a type.
The first hole is by default 1 sector to make space for the primary bootstrap and the partition table. The other holes are 0.
The type field is the type of the partitition in hexadecimal. The size field is the partition's size in sectors. The + or * may option-
ally be added to indicate that the partition must be expanded to contain any leftover space on the device or to mark the partition active.
Partitions are padded out to cylinder boundaries, except for the first one, it starts on track 1. Some operating systems care about this.
Minix and MS-DOS do not.
OPTIONS -m Minix only, no need to pad partitions. This is the default for subpartition tables.
-f Force making a partition table even if the device is too small.
EXAMPLE
partition /dev/hd0 01:16384 81:40000 81:2880* 06:20000+
Partitions disk 0 into an 8 Mb DOS partition, 20 Mb Minix /usr, 1.44 Mb Minix / (active), and a DOS partition of at least 10 Mb at the end
of the disk. (06:0+ would have been ok too, it's just a sanity check.)
SEE ALSO hd(4), part(8), repartition(8).
AUTHOR
Kees J. Bot (kjb@cs.vu.nl)
PARTITION(8)