Sponsored Content
Full Discussion: LPAR cannot added disk
Operating Systems AIX LPAR cannot added disk Post 302986863 by lckdanny on Wednesday 30th of November 2016 11:12:12 PM
Old 12-01-2016
Quote:
Originally Posted by bakunin
You create it on the VIOS, not the IVM. You need to create a so-called "vhost". Here is a link where, as far as i saw in overviewing it, everything necessary is described: Virtual SCSI.

I hope this helps.

bakunin
Thanks Bankunin,

Thanks for you help.

But I have another question needs your advices.

We have a LPAR, it crash last month, some delete file under /etc, so the AIX system cannot bootup correctly, so I did a restore on /etc, but there have an error during bootup.

Code:
Successfully updated the Kernal Authorization Table.
Successfully updated the Kernal Role Table.
Successfully updated the Kernal Command Table.
Successfully updated the Kernal Device Table.
Successfully updated the Kernal Object Domain Table.
Successfully updated the Kernal Domains Table.
OPERATIONAL MODE Security Flags
ROOT                :   DISABLED
TRACEAUTH       :   DISABLED
System runtime mode is now OPERATIONAL MODE.
Starting LPAR boottime name check...
0526-001 alog: /etc/.lpar-boottime is not an alog file.
Checking...
Checking...
Checking...
Checking...FAILED

ERROR::Current LPAR name, [db1a], is not equal to saved LPAR name: []!

ERROR:: Halting the node to prevent improper bootup!
Sending nohup output to nobup.out.

I found there a file /etc/.lpar-boottime control on this, how can I re-create this file under maintenance mode to make the server bootup or any command bypass this checking?

Thanks.
 

10 More Discussions You Might Find Interesting

1. AIX

LPAR and vio disk mapping

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)
Discussion started by: daveisme
4 Replies

2. 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

3. AIX

VIO Backing Disk LPAR how to find which one ?

hello Folks, my vio: $ lsmap -all SVSA Physloc Client Partition ID --------------- -------------------------------------------- ------------------ vhost0 U9117.MMA.6534BE4-V2-C11 0x00000003 VTD ... (0 Replies)
Discussion started by: filosophizer
0 Replies

4. AIX

p595 LPAR no longer sees SAN boot disk

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)
Discussion started by: rwesterik
2 Replies

5. Red Hat

Partitioning newly added disk to Redhat

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)
Discussion started by: bobby320
2 Replies

6. AIX

VIO and LPAR disk/fcs communications

: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)
Discussion started by: Dallasguy7
3 Replies

7. 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

8. Solaris

Cannot remove disk added to zpool

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)
Discussion started by: LittleLebowski
14 Replies

9. AIX

Adding disk to my lpar

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)
Discussion started by: vax
4 Replies

10. AIX

AIX lpar bad disk I/O performance - 4k per IO limitation ?

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
TIME_SECOND(9)						   BSD Kernel Developer's Manual					    TIME_SECOND(9)

NAME
time_second, time_uptime, boottime -- system time variables SYNOPSIS
#include <sys/time.h> extern time_t time_second; extern time_t time_uptime; #include <sys/kernel.h> extern struct timeval boottime; DESCRIPTION
The time_second variable is the system's ``wall time'' clock. It is set at boot by inittodr(9), and is updated periodically via timecounter(9) framework, and also updated by the settimeofday(2) system call. The time_uptime variable is a monotonically increasing system clock. It is set at boot, and is updated periodically. (It is not updated by settimeofday(2).) The boottime variable holds the system boot time. It is set at system boot, and is updated when the system time is adjusted with settimeofday(2). The variable may be read and written without special precautions. All of these variables contain times expressed in seconds and microseconds since midnight (0 hour), January 1, 1970. The bintime(9), getbintime(9), microtime(9), getmicrotime(9), nanotime(9), and getnanotime(9) functions can be used to get the current time more accurately and in an atomic manner. Similarly, the binuptime(9), getbinuptime(9), microuptime(9), getmicrouptime(9), nanouptime(9), and getnanouptime(9) functions can be used to get the time elapsed since boot more accurately and in an atomic manner. SEE ALSO
clock_settime(2), ntp_adjtime(2), timeval(3), hardclock(9), hz(9) BSD
March 13, 2008 BSD
All times are GMT -4. The time now is 06:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy