Re: HCPGIR450W and HCPGIR453W after editing user direct

Fri, 05 Nov 2010 18:41:30 -0700 

Hi Koray,

Lets try a step by step approach. Start by verifing that you are running with 
the correct directory. And second, try to find out what the correct IPL 
processes are for the guests.

I would expect that your zVM guy has handed the correct instructions and that 
you indeed have to edit DIRECT USER. However, some sites use DIRMAINT and some 
do not. It doesn't matter what you use but it is vital for you to know for sure 
who owns the directory and what file the actual (correct) directory is. 
Especially in this case where you get unexpected results just after you have 
put a directory online. If DIRMAINT is the owner and you use MAINT you can get 
an (very) old directory online. The same can be true if you have editted the 
wrong file or by accident have put the wrong directoryfile online. Perhaps you 
have used a directory where minidiskentries have been swapped.

So logon to user MAINT again. Issue a "FILEL DIRECT USER * ". Is there only one 
on C or do you have more than one? If there is one on A or B then that's your 
problem. And just for fun, issue "FILEL USER DIRECT * ". Found any that could 
be a directory and if so, any differences in the minidiskstatements for the 
guests?

As for DIRMAINT, issue "VMLINK DIRMAINT 1DB (FILEL" and see if there is a USER 
BACKUP. And if so, is it a recent one?

Once you know for sure that you are looking at the correct directory, take a 
look at the IPL statement in the directoryentry for this linux guest. Is it IPL 
100 (or IPL 102)? In case of IPL <vdev> the environment is set in the directory 
and the guest will IPL from the minidisk in the IPL statement. Then you need to 
determine if the minidisks have swapped for some reason and why.

Or is it IPL CMS? Then take a look at the statement for the 191 device. Is it a 
LINK or a MDISK statement? Are they perhaps linked to the TCPMAINT 191? That 
would explain your comments on the TCPMAINT userid.

Next take a look at the linux guest 191 disk. "VMLINK <guest> 191 (FILEL". In 
there you will find the PROFILE EXEC. It will execute some commands, IPL is one 
of them. What IPL command is executed, IPL 100 or IPL 102?

Your comments on IPL from 100 and/or 102 would suggest to me that at some point 
the (default) configuration has been changed. And perhaps also the location of 
the 191 minidisk. It looks like it has been decided to change the default IPL 
100 to IPL 102 (or the other way around). Should you have put an obsolete 
directory online it could be that in the old directory the 100 and 102 are 
swapped compaired to the new directory. Or that the 191 minidisk has been 
changed to have a different profile exec for some of the guests.

Regards, Berry.

-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Koray 
Kusat
Sent: zaterdag 6 november 2010 0:01
To: [email protected]
Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct

Hi Berry,

The owner is MAINT i guess, because i'm doing all these editing things with 
MAINT user. I found the file PROFILE EXEC, in TCPMAINT user area (sorry, i dont 
know the big iron's terminology, i found it with "filel
* * *" command with TCPMAINT user) which runs Linux guests automatically during 
IPL. The default setting is Minidisk100, but if i change it to 102, my all 
guests will try to IPL from 102, and this is not what i want.
Because i have 14 guests and 8 of them IPL from 102, 6 of them IPL from 100. I 
need to change this file (or script) somehow, but i dont know how to do it.

Regards

2010/11/5 van Sleeuwen, Berry <[email protected]>
>
> Hi Koray,
>
> Go back to the process of your directory change.
>
> Is MAINT or DIRMAINT the leading directory owner? (take a look at the 
> DIRMAINT 1DB, if there is a recent USER BACKUP chances are DIRMAINT 
> was
> leading)
> Are you sure the correct directory has been put online? Did you have a 
> DIRECT USER on the A or B disk?
> Is DIRECT USER C indeed the directory that you should use? (usually 
> the directory is called USER DIRECT. So either there should be a file 
> with that name or your zVM guy has renamed it to DIRECT USER.)
>
> Regards, Berry.
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:[email protected]] On Behalf Of 
> koray
> Sent: vrijdag 5 november 2010 20:24
> To: [email protected]
> Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct
>
> Hi Eddie,
>
> thanks for the tip!
> yes i did ipl from minidisk 102, and /boot is on Minidisk as well.
> But /dev/dasda1 seems as a part of LVM group. Maybe i remembered wrong.
> Anyway, i dont know why all these changed but now i need to change the 
> default boot minidisk from 100 to 102, my 8 guests have this problem.
> I think its somewhere in ZVM side. How can i do it?
>
> Regards
>
> On 05.11.2010 19:10, Eddie Chen wrote:
> >    Koray,
> >
> >       Did you try to IPL 102 and see if it comes up.
> >       Is the /boot is also on Minidisk 102 as well?
> >       You also should mount "/dev/dasda1 to /mnt " to see if the
> "/boot"
> >       is still on that partition.
> >
> >
> >
> > -----Original Message-----
> > From: Linux on 390 Port [mailto:[email protected]] On Behalf 
> > Of koray
> > Sent: Friday, November 05, 2010 9:24 AM
> > To: [email protected]
> > Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct
> >
> > Hi again to all,
> >
> > after doing lots of research i found the problem is somewhere in 
> > linux, let me explain.
> >
> > - I checked all dasds, there were no offline or unattached.
> > - No overlap in diskmap file.
> > - I compared direct user file with the old backup and i saw there is 
> > no change with disk mappings.
> > - I did all similar checks on Z/VM side, no problems found.
> > - I ipled from SLES11 DVD and choosed boot installed system, it boots!
> > So i thought it's about ZIPL configuration but there was nothing 
> > wrong
>
> > there. I regenerated the bootmap again by running /sbin/zipl, and 
> > tried to reipl from Minidisk100, but no luck.
> >
> > Now lets see what's weird;
> >
> > When i first installed SLES, the disk mapping was:
> > Minidisk100 - dasda - /boot
> > Minidisk101 - dasdb - swap
> > Minidisk102 - dasdc - /
> > Minidisk110 - dasdd - LVM Member
> > ...
> > Minidisk209 - dasdn - LVM Member
> >
> > But when i boot with cd, and activate the DASD's i see
> >
> > Minidisk100 - dasda
> > Minidisk101 - _dasdn_
> > Minidisk102 - dasdb
> > Minidisk110 - dasdc
> > ...
> >
> > It seems the mapping has changed somehow. But when i run the 
> > installed
>
> > system from DVD menu, i see DASD's as they supposed to be:
> >
> > linux101:~ # more /proc/dasd/devices
> > 0.0.0100(ECKD) at ( 94:     0) is dasda
> > 0.0.0101(ECKD) at ( 94:     4) is dasdb
> > 0.0.0102(ECKD) at ( 94:     8) is dasdc
> > 0.0.0110(ECKD) at ( 94:    12) is dasdd
> > 0.0.0200(ECKD) at ( 94:    16) is dasde
> > 0.0.0201(ECKD) at ( 94:    20) is dasdf
> > 0.0.0202(ECKD) at ( 94:    24) is dasdg
> > 0.0.0203(ECKD) at ( 94:    28) is dasdh
> > 0.0.0204(ECKD) at ( 94:    32) is dasdi
> > 0.0.0205(ECKD) at ( 94:    36) is dasdj
> > 0.0.0206(ECKD) at ( 94:    40) is dasdk
> > 0.0.0207(ECKD) at ( 94:    44) is dasdl
> > 0.0.0208(ECKD) at ( 94:    48) is dasdm
> > 0.0.0209(ECKD) at ( 94:    52) is dasdn
> >
> >
> > linux101:~ # more /etc/fstab
> > /dev/disk/by-path/ccw-0.0.0101-part1 swap                 swap
> > /dev/disk/by-path/ccw-0.0.0102-part1 /                    ext3 
> > /dev/system/home     /home /dev/system/opt      /opt /dev/system/tmp      
> > /tmp /dev/system/usr      /usr /dev/system/var      /var proc               
> >   
> > /proc sysfs                /sys debugfs              
> > /sys/kernel/debug devpts               /dev/pts
> >
> >
> > linux101:~ # more /etc/zipl.conf
> > # Modified by YaST2. Last modification on Mon Nov  1 16:46:48 UTC 
> > 2010
>
> > [defaultboot] defaultmenu = menu
> >
> > ###Don't change this comment - YaST2 identifier: Original name:
> > linux### [Linux]
> >       image = /boot/image-2.6.27.19-5-default
> >       target = /boot/zipl
> >       ramdisk = /boot/initrd-2.6.27.19-5-default,0x2000000
> >       parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1
> TERM=dumb"
> >
> > :menu
> >       default = 1
> >       prompt = 1
> >       target = /boot/zipl
> >       timeout = 10
> >       1 = Linux
> >       2 = ipl
> >       3 = Failsafe
> >
> > ###Don't change this comment - YaST2 identifier: Original name: 
> > ipl###
>
> > [ipl]
> >       image = /boot/image
> >       target = /boot/zipl
> >       ramdisk = /boot/initrd,0x2000000
> >       parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1
> TERM=dumb"
> >
> > ###Don't change this comment - YaST2 identifier: Original name:
> > failsafe### [Failsafe]
> >       image = /boot/image
> >       target = /boot/zipl
> >       ramdisk = /boot/initrd,0x2000000
> >       parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1
> > TERM=dumb x11failsafe"
> >
> >
> > As you can see, it seems there is nothing wrong.But when i try to 
> > boot
>
> > from Minidisk100, i see;
> >
> > Mounting root _/dev/disk/by-path/ccw-0.0.0100-part1_
> > Unknown filesystem type 'LVM2_member'
> > Kernel panic - not syncing: Attemted to kill init!
> > HCPGIR450W ...
> >
> > I re-run ZIPL but, no change, it still searches 0.0.0100 for root fs.
> > I think the reason is same with the first DASD activation menu with
> DVD.
> > Linux somehow sees diskmaps different and i cant change the ZIPL
> behaviour.
> >
> > Now, i need to change ZIPL to mount root-fs from Minidisk102.
> > And then research why the Minidisk-Linux Dasd mapping is changing.
> >
> > Sorry for the long mail and thanks for your patient.
> >
> > Regards
> >
> >
> >
> > On 05.11.2010 15:30, martin roby wrote:
> >> I have seen this happen as well; when trying to boot from san disks.
> >> Do you have your root filesystem on a san disk? Can you post your 
> >> user direct entry for a user that fails?
> >>
> >> When you logged all the way out of your Linux guests you reset that 
> >> user. A lot of different things could have happened at that point.
> >>
> >> Do any of your Linux guests still work? When they boot do they go 
> >> straight to the CPU errors? I am assuming you don't get the zipl 
> >> boot
>
> >> menu.
> >>
> >> One thing to look for is an overlaps in your disk map.
> >>
> >> {from maint}
> >> diskmap user {generates a new disk map} x user diskmap {opens the 
> >> new
>
> >> map in the wonderful z/os editor} {then search for overlaps} {I 
> >> usually use "right 10" first so I can see the "gap' messages"}
> >>
> >> /over
> >>
> >> If you have an overlap that would be the issue.
> >> Otherwise either you are not finding your disk at boot or your zipl 
> >> boot was corrupted.
> >>
> >> If you a working system you can move the disk to the new system and 
> >> try to mount it from the working Linux , if it mounts then you can 
> >> try to rewire the zipl boot block.
> >>
> >> Martin
> >>
> >>
> >>
> >> On Thu, Nov 4, 2010 at 3:31 PM, koray<[email protected]>   wrote:
> >>> Hello all,
> >>>
> >>> We have 14 Sles Guests running on Z/VM 5.4. We edited the user 
> >>> direct file and changed the memory settings of Linux guests.For 
> >>> example;
> >>>
> >>> linux001 - 2048M 4096M
> >>> linux002 - 2048M 4096M
> >>> has changed to
> >>> linux001 - 3072M 6144M
> >>> linux002 - 1024M 2048M
> >>>
> >>> Now, i cant ipl my guest's. When i try to ipl from minidisk 100, 
> >>> linux 001 says:
> >>> HCPGIR453W CP Entered, program interrupt loop.
> >>> linux002 says:
> >>> HCPGIR450W CP entered, disabled wait PSW 00020001 80000000 
> >>> 00000000 001536B0
> >>>
> >>> It seems disk mapping are broken but i'm totally sure that i only 
> >>> changed Memory settings, not touched minidisk settings.
> >>>
> >>> Need your help please.
> >>>
> >>> Regards
> >>>
> >>> ------------------------------------------------------------------
> >>> --
> >>> -- For LINUX-390 subscribe / signoff / archive access 
> >>> instructions, send email to [email protected] with the 
> >>> message: INFO LINUX-390 or visit 
> >>> http://www.marist.edu/htbin/wlvindex?LINUX-390
> >>> ------------------------------------------------------------------
> >>> --
> >>> -- For more information on Linux on System z, visit 
> >>> http://wiki.linuxvm.org/
> >>>
> >>
> >> -------------------------------------------------------------------
> >> --
> >> - For LINUX-390 subscribe / signoff / archive access instructions, 
> >> send email to [email protected] with the message: INFO 
> >> LINUX-390
>
> >> or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
> >> -------------------------------------------------------------------
> >> --
> >> - For more information on Linux on System z, visit 
> >> http://wiki.linuxvm.org/
> >>
> >
> > --------------------------------------------------------------------
> > -- For LINUX-390 subscribe / signoff / archive access instructions, 
> > send email to [email protected] with the message: INFO 
> > LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
> > --------------------------------------------------------------------
> > -- For more information on Linux on System z, visit 
> > http://wiki.linuxvm.org/ Please consider the environment before 
> > printing this email.
> >
> > Visit our website at http://www.nyse.com
> >
> > ****************************************************
> >
> > Note:  The information contained in this message and any attachment 
> > to
> it is privileged, confidential and protected from disclosure.  If the 
> reader of this message is not the intended recipient, or an employee 
> or agent responsible for delivering this message to the intended 
> recipient, you are hereby notified that any dissemination, 
> distribution or copying of this communication is strictly prohibited.  
> If you have received this communication in error, please notify the 
> sender immediately by replying to the message, and please delete it 
> from your system.  Thank you.  NYSE Euronext.
> >
> > --------------------------------------------------------------------
> > -- For LINUX-390 subscribe / signoff / archive access instructions, 
> > send email to [email protected] with the message: INFO 
> > LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
> > --------------------------------------------------------------------
> > -- For more information on Linux on System z, visit 
> > http://wiki.linuxvm.org/
> >
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send 
> email to [email protected] with the message: INFO LINUX-390 or 
> visit http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit 
> http://wiki.linuxvm.org/
>
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send 
> email to [email protected] with the message: INFO LINUX-390 or 
> visit http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit 
> http://wiki.linuxvm.org/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO LINUX-390 or visit 
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit http://wiki.linuxvm.org/


----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Reply via email to