Re: IPL Centos s390x dvd in RESCUE mode?
On Mon, Mar 31, 2008 at 4:33 AM, Ian S. Worthington [EMAIL PROTECTED] wrote: According to Redhat's documentation it should be possible to ipl the install dvd in RESCUE mode. However when I try it seems to go into install mode, asking me for my ctc addresses: From what I recall you can run the installer to configure your network and DASD and then decide to to into a rescue mode. The distributors have chosen to use a single solution for LPAR and Linux on z/VM. In a virtual machine they could do a bit more guessing, but that's where you need it less. In LPAR you certainly do not want that. We've seen the trouble with Linux trying to probe shared MVS packs. I believe the entire rescue approach is a desktop thing. Being able to bring up a rescue system on the IP address of your production server would scare the hell out of me. I would expect people running Linux servers to bring their own life boats. With Linux on z/VM you have a lot of material to build such a (remotely operated) life boat. Rob -- Rob van der Heij Velocity Software GmbH http://velocitysoftware.com/ -- 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
Re: Problems with rexec
Hello again, I have read carefully your mail and i have made some changes to my configuration and now it works :) And now as you stated RXAGENT1 works with anonymous logons. The other guest (vpajsz) is authorized to issue command (when I block anoymous login). Thanks again for help in resolving my problem. I have only added: :NICK.VPAJSZ :TYPE.SERVER :CLASS.REXEC_AGENT to SYSTEM DTCPARMS file. Jakub Szefler Administrator MainFrame Pion Operacji IT Grupy TP/Departament Infrastruktury Wydział Infrastruktury Informatycznej Dział Mainframe ul. Goplańska 25, 91-463 Łódź tel.0 42 655 32 29 fax.0 42 655 42 22 www.tp.pl __ Treść tej wiadomości zawiera informacje przeznaczone tylko dla adresata. Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę, prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Wednesday, March 26, 2008 4:02 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Problems with rexec On Wednesday, 03/26/2008 at 09:31 EDT, Szefler Jakub [EMAIL PROTECTED] wrote: Hello, I'm confused,too. I have checked my configurations on z/VM version 5.2 and 5.3 with or without changes in system dtcparms. IBM DTCPARMS according to redbook never changes. Sorry, but Redbooks are not the authority on IBM DTCPARMS. I am. :-) IBM DTCPARMS *can* change due to service or SPEs (between-release enhancements). That's how I designed it, that's why SYSTEM DTCPARMS exists, and that's why IBM DTCPARMS lives on the 591 disk (with other things you don't change). And i still receive two answers: monika:/# rexec -l RXAGENT1 -p RXAGENT1 126.177.54.30 q time TIME IS 14:16:17 EST WEDNESDAY 03/26/08 CONNECT= 00:00:00 VIRTCPU= 000:00.00 TOTCPU= 000:00.00 TIME IS 14:16:17 EST WEDNESDAY 03/26/08 CONNECT= 00:00:00 VIRTCPU= 000:00.00 TOTCPU= 000:00.00 I wrote the notice to our support to resolve this problem. For the 3rd and final time: Do NOT use RXAGENT1 as the target of an REXEC command. It doesn't have a traditional PROFILE EXEC like other users do. My fix for this is to change the password of RXAGENT1 to AUTOONLY. In fact, I plan to make that change in our next release. (I've been asked by others to make ALL of the servers AUTOONLY so that sysprogs can avoid having to manage their passwords.) Alan Altmark z/VM Development IBM Endicott -- 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 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
Re: DASD error on zlinux ipl
At first blush, it appears that you added volumes to VolGroup00, but failed to run mkinitrd and zipl afterward. This is my favorite (or at least most common) error. If it comes up far enough, log into root and check /proc/dasd/devices to see if you have what you expected to have. You may need to re-activate them and run mkinitrd and zipl to get them permanently into the fold, then boot once more. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 3/30/08 7:08 PM, Ian S. Worthington [EMAIL PROTECTED] wrote: Restarting my zlinux system today I got the following which seems to suggest some problem on 120. I'm assuming this is a red herring as it also appears in my last good console (underneath)? VolGroup00 should contain 122 as well I suspect, as it was extended to use this volume, though there's nothing on it as the fs is ext2 and couldn't be extended online and I have no other way of booting. Could it be this its not finding, or has got corrupted? Any help/advice on how to disentangle this most welcome. Ian .. 18:39:00 Loading dasd_mod.ko module 18:39:01 Loading dasd_eckd_mod.ko module 18:39:01 HHCCP048I 0120:CCW=2742 0FBDFFB8=1D00 0800 18:39:01 HHCCP075I 0120:Stat=0E40 Count=0040 18:39:01 HHCCP076I 0120:Sense=8000 000B0804 18:39:01 HHCCP077I 0120:Sense=CMDREJ 18:39:01 dasd_erp(3990): 0.0.0120: EXAMINE 24: Command Reject detected - fatal error 18:39:01 dasd(eckd): I/O status report for device 0.0.0120: 18:39:01 dasd(eckd): in req: 0fbdfee0 CS: 0x40 DS: 0x0E 18:39:01 dasd(eckd): device 0.0.0120: Failing CCW: 0fbdffb8 18:39:01 dasd(eckd): Sense(hex) 0- 7: 80 00 00 00 00 0b 08 04 18:39:01 dasd(eckd): Sense(hex) 8-15: 00 00 00 00 00 00 00 00 18:39:01 dasd(eckd): Sense(hex) 16-23: 00 00 00 00 00 00 00 00 18:39:01 dasd(eckd): Sense(hex) 24-31: 00 00 00 80 00 00 0b 08 18:39:01 dasd(eckd): 24 Byte: 0 MSG 4, no MSGb to SYSOP 18:39:01 dasd(eckd): Related CP in req: 0fbdfee0 18:39:01 dasd(eckd): CCW 0fbdffb0: 2742 0FBDFFB8 DAT: 1d00 0800 000 18:39:01 0 18:39:01 dasd(eckd): 0.0.0120: PSF-SSC on storage subsystem HRC.ZZ0001.0120 retur 18:39:01 ned rc=-5 18:39:01 dasd(eckd): 0.0.0120: 3390/0A(CU:3990/01) Cyl:3339 Head:15 Sec:224 18:39:01 Using cfq io scheduler 18:39:01 dasd(eckd): 0.0.0120: (4kB blks): 2404080kB at 48kB/trk compatible disk layout 18:39:01 dasda:VOL1/ 0X0120: dasda1 dasda2 18:39:01 dasd(eckd): 0.0.0121: 3390/0A(CU:3990/01) Cyl:3339 Head:15 Sec:224 18:39:01 dasd(eckd): 0.0.0121: (4kB blks): 2404080kB at 48kB/trk compatible disk layout 18:39:01 dasdb:VOL1/ 0X0121: dasdb1 18:39:02 Loading dasd_fba_mod.ko module 18:39:02 Loading dm-mirror.ko module 18:39:02 Loading dm-zero.ko module 18:39:02 Loading dm-snapshot.ko module 18:39:04 Making device-mapper control node 18:39:04 Scanning logical volumes 18:39:04 Reading all physical volumes. This may take a while... 18:39:05 Couldn't find device with uuid 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'. 18:39:05 Couldn't find all physical volumes for volume group VolGroup00. 18:39:05 Couldn't find device with uuid 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'. 18:39:05 Couldn't find all physical volumes for volume group VolGroup00. 18:39:05 Couldn't find device with uuid 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'. 18:39:05 Couldn't find all physical volumes for volume group VolGroup00. 18:39:05 Couldn't find device with uuid 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'. 18:39:05 Couldn't find all physical volumes for volume group VolGroup00. 18:39:05 Volume group VolGroup00 not found 18:39:05 ERROR: /bin/lvm exited abnormally (pid 188) 18:39:05 Activating logical volumes 18:39:07 Couldn't find device with uuid 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'. 18:39:07 Couldn't find all physical volumes for volume group VolGroup00. 18:39:07 Couldn't find device with uuid 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'. 18:39:07 Couldn't find all physical volumes for volume group VolGroup00. 18:39:07 Couldn't find device with uuid 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'. 18:39:07 Couldn't find all physical volumes for volume group VolGroup00. 18:39:08 Kernel panic - not syncing: Attempted to kill init 18:39:08 CPU: SIGP Stop (05) CPU0001, PARM : CC 0 18:39:08 CPU: SIGP Store status (0E) CPU0001, PARM 00D0C000: CC 2 18:39:08 CPU: SIGP Store status (0E) CPU0001, PARM 00D0C000: CC 0 18:39:08 HHCCP011I CPU: Disabled wait state 18:39:08 PSW=00020001 8000
Re: IPL Centos s390x dvd in RESCUE mode?
On Mon, 2008-03-31 at 11:18 +0800, John Summerfield wrote: Ian S. Worthington wrote: According to Redhat's documentation it should be possible to ipl the install dvd in RESCUE mode. However when I try it seems to go into install mode, asking me for my ctc addresses: Why do you think that is a problem? Yep, you have to answer the initial networking questions (because there's no CONF to reference). Afterwards, instead of launching the installer, rescue mode will start. Note that you can do this through z/VM by just adding 'rescue' to the PARM file. 22:12:53 Starting the zSeries initrd to configure networking. Version is 1.1 22:12:55 Which kind of network device do you intend to use 22:12:55 (e.g. ctc, iucv, qeth, lcs). 22:12:55 Enter 'qeth' for OSA-Express Fast Ethernet, Gigabit Ethernet 22:12:55 (including 1000Base-T), High Speed Token Ring, and ATM 22:12:55 (running Ethernet LAN emulation) features in QDIO mode. 22:12:55 Enter 'lcs' for OSA 2 Ethernet/Token Ring, OSA-Express Fast Ethernet in 22:12:55 non-QDIO mode, OSA-Express High Speed Token Ring in non-QDIO mode and 22:12:55 Gigabit Ethernet in non-QDIO mode. It has confirmed: 22:10:47 Kernel command line: root=/dev/ram0 ro ip=off ramdisk_size=4 rescue So I'm assuming that its happy with my ins file: * minimal lpar ins file g:/images/kernel.img 0x g:/images/initrd.img 0x0080 D:/zcentos/rescue/rescue.prm 0x00010480 and prm: root=/dev/ram0 ro ip=off ramdisk_size=4 rescue (If its relevant I have detached my disks as I don't want them to be accidentally written to.) Anyone know how to boot this in RESCUE mode? ian ... Ian S. Worthington, MBCS. -- 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 -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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 -- Brad Hinson [EMAIL PROTECTED] Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 -- 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
Re: IPL Centos s390x dvd in RESCUE mode?
Thanks guys, that's given me some reassurance. When I answer my DASD range, I assume I should response with the addresses of all volumes I have on the system to be rescued? ian ... -- 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
Re: IPL Centos s390x dvd in RESCUE mode?
On Mon, 2008-03-31 at 16:30 +0100, Ian S. Worthington wrote: Thanks guys, that's given me some reassurance. When I answer my DASD range, I assume I should response with the addresses of all volumes I have on the system to be rescued? ian ... Yes, this corresponds to any and all DASD you want online during the rescue session. -Brad -- 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 -- Brad Hinson [EMAIL PROTECTED] Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 -- 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
Re: IPL Centos s390x dvd in RESCUE mode?
Thanks Brad. Seems to be up now. Now to see what I can do about my lvm problem... Many thanks. ian -- Original Message -- Received: Mon, 31 Mar 2008 05:04:29 PM BST From: Brad Hinson [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Subject: Re: IPL Centos s390x dvd in RESCUE mode? On Mon, 2008-03-31 at 16:30 +0100, Ian S. Worthington wrote: Thanks guys, that's given me some reassurance. When I answer my DASD range, I assume I should response with the addresses of all volumes I have on the system to be rescued? ian ... Yes, this corresponds to any and all DASD you want online during the rescue session. -Brad -- 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
Re: DASD error on zlinux ipl
Hi Robert --
Hmm. I certainly didn't do a zipl and pretty sure I didn't do a mkinitrd
either. They don't seem to be mentioned in the instructions I was following.
I can't boot my system normally, but thanks to some help on this list, have
now got it up in rescue mode.
cat devices seems to show all volumes at least present:
0.0.0120(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096,
601020 blocks, 2347 MB
0.0.0121(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096,
601020 blocks, 2347 MB
0.0.0122(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096,
1803060 blocks, 7043 MB
0.0.0123(ECKD) at ( 94:12) is dasdd : active at blocksize: 4096,
1803060 blocks, 7043 MB
-/bin/sh-3.00#
Is it possible to run mkinitrd and zipl in rescue mode?
Your help is much appreciated.
Thanks.
i
-- Original Message --
Received: Mon, 31 Mar 2008 01:35:49 PM BST
From: RPN01 [EMAIL PROTECTED]
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DASD error on zlinux ipl
At first blush, it appears that you added volumes to VolGroup00, but failed
to run mkinitrd and zipl afterward. This is my favorite (or at least most
common) error.
If it comes up far enough, log into root and check /proc/dasd/devices to
see
if you have what you expected to have. You may need to re-activate them and
run mkinitrd and zipl to get them permanently into the fold, then boot once
more.
--
Robert P. Nix Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844 Rochester, MN 55905 /( )\
-^^-^^
In theory, theory and practice are the same, but
in practice, theory and practice are different.
On 3/30/08 7:08 PM, Ian S. Worthington [EMAIL PROTECTED] wrote:
Restarting my zlinux system today I got the following which seems to
suggest some problem on 120. I'm assuming this is a red herring as it
also appears in my last good console (underneath)?
VolGroup00 should contain 122 as well I suspect, as it was extended to
use
this volume, though there's nothing on it as the fs is ext2 and couldn't
be
extended
online and I have no other way of booting. Could it be this its not
finding, or has got corrupted?
Any help/advice on how to disentangle this most welcome.
Ian
..
18:39:00 Loading dasd_mod.ko module
18:39:01 Loading dasd_eckd_mod.ko module
18:39:01 HHCCP048I 0120:CCW=2742 0FBDFFB8=1D00 0800
18:39:01 HHCCP075I 0120:Stat=0E40 Count=0040
18:39:01 HHCCP076I 0120:Sense=8000 000B0804
18:39:01 HHCCP077I 0120:Sense=CMDREJ
18:39:01 dasd_erp(3990): 0.0.0120: EXAMINE 24: Command Reject detected
- fatal error
18:39:01 dasd(eckd): I/O status report for device 0.0.0120:
18:39:01 dasd(eckd): in req: 0fbdfee0 CS: 0x40 DS: 0x0E
18:39:01 dasd(eckd): device 0.0.0120: Failing CCW: 0fbdffb8
18:39:01 dasd(eckd): Sense(hex) 0- 7: 80 00 00 00 00 0b 08 04
18:39:01 dasd(eckd): Sense(hex) 8-15: 00 00 00 00 00 00 00 00
18:39:01 dasd(eckd): Sense(hex) 16-23: 00 00 00 00 00 00 00 00
18:39:01 dasd(eckd): Sense(hex) 24-31: 00 00 00 80 00 00 0b 08
18:39:01 dasd(eckd): 24 Byte: 0 MSG 4, no MSGb to SYSOP
18:39:01 dasd(eckd): Related CP in req: 0fbdfee0
18:39:01 dasd(eckd): CCW 0fbdffb0: 2742 0FBDFFB8 DAT:
1d00 0800 000
18:39:01 0
18:39:01 dasd(eckd): 0.0.0120: PSF-SSC on storage subsystem
HRC.ZZ0001.0120 retur
18:39:01 ned rc=-5
18:39:01 dasd(eckd): 0.0.0120: 3390/0A(CU:3990/01) Cyl:3339 Head:15
Sec:224
18:39:01 Using cfq io scheduler
18:39:01 dasd(eckd): 0.0.0120: (4kB blks): 2404080kB at 48kB/trk
compatible disk layout
18:39:01 dasda:VOL1/ 0X0120: dasda1 dasda2
18:39:01 dasd(eckd): 0.0.0121: 3390/0A(CU:3990/01) Cyl:3339 Head:15
Sec:224
18:39:01 dasd(eckd): 0.0.0121: (4kB blks): 2404080kB at 48kB/trk
compatible disk layout
18:39:01 dasdb:VOL1/ 0X0121: dasdb1
18:39:02 Loading dasd_fba_mod.ko module
18:39:02 Loading dm-mirror.ko module
18:39:02 Loading dm-zero.ko module
18:39:02 Loading dm-snapshot.ko module
18:39:04 Making device-mapper control node
18:39:04 Scanning logical volumes
18:39:04 Reading all physical volumes. This may take a while...
18:39:05 Couldn't find device with uuid
'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'.
18:39:05 Couldn't find all physical volumes for volume group
VolGroup00.
18:39:05 Couldn't find device with uuid
'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'.
18:39:05 Couldn't find all physical volumes for volume group
VolGroup00.
18:39:05 Couldn't find device with uuid
'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'.
18:39:05 Couldn't find all physical volumes for volume group
VolGroup00.
18:39:05 Couldn't find device with uuid
sles10 on hercules.
Hi, I am trying to install sles10 on Hercules. Managed to finish the installation and ran into a problem, when rebooting from a disk. It starts and then issues: cio: Was not able to determine available CHSCs. Error starting thread in diagnose 0x308: Success And stops. Anybody was able to boot sles10 on Hercules? Regards, Mike -- 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
Re: sles10 on hercules.
Michael Prahin wrote: cio: Was not able to determine available CHSCs. Error starting thread in diagnose 0x308: Success And stops. Anybody was able to boot sles10 on Hercules? It's a known hercules problem. It's fixed in development and will be fixed in next release. You can either pick the development version, compile it and use it, or use one of the various snapshots floating around. PS : It's not a SLES 10 problem. The problem started with some version of the stock 2.6 kernel when they decided to use DIAG 308 - which was improperly implemented in hercules (implemented enough to make the kernel think it had DIAG 308, not implemented enough to actually be usable). The cio: xxx message is not a real issue (it just means some dynamic I/O reconfiguration won't be available). So any new enough kernel based system will also fail. --Ivan -- 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
Re: DASD error on zlinux ipl
The easiest way to do this is:
1. Bring the LVM online:
vgscan
vgchange -a y
2. Mount the logical volume(s):
mkdir /mnt/sysimage
mount /dev/volgroupname/logvolname /mnt/sysimage/
mount /dev/dasda1 /mnt/sysimage/boot
mount /dev/volgroupname/logvolname /mnt/sysimage/usr
mount /dev/volgroupname/logvolname /mnt/sysimage/var
[etc.]
3. chroot into the mounted system:
chroot /mnt/sysimage
4. Rerun zipl/mkinitrd:
zipl -V; mkinitrd -v -f /boot/initrd-`uname -r`.img `uname -r`
-Brad
On Mon, 2008-03-31 at 17:54 +0100, Ian S. Worthington wrote:
Hi Robert --
Hmm. I certainly didn't do a zipl and pretty sure I didn't do a mkinitrd
either. They don't seem to be mentioned in the instructions I was following.
I can't boot my system normally, but thanks to some help on this list, have
now got it up in rescue mode.
cat devices seems to show all volumes at least present:
0.0.0120(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096,
601020 blocks, 2347 MB
0.0.0121(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096,
601020 blocks, 2347 MB
0.0.0122(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096,
1803060 blocks, 7043 MB
0.0.0123(ECKD) at ( 94:12) is dasdd : active at blocksize: 4096,
1803060 blocks, 7043 MB
-/bin/sh-3.00#
Is it possible to run mkinitrd and zipl in rescue mode?
Your help is much appreciated.
Thanks.
i
-- Original Message --
Received: Mon, 31 Mar 2008 01:35:49 PM BST
From: RPN01 [EMAIL PROTECTED]
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DASD error on zlinux ipl
At first blush, it appears that you added volumes to VolGroup00, but failed
to run mkinitrd and zipl afterward. This is my favorite (or at least most
common) error.
If it comes up far enough, log into root and check /proc/dasd/devices to
see
if you have what you expected to have. You may need to re-activate them and
run mkinitrd and zipl to get them permanently into the fold, then boot once
more.
--
Robert P. Nix Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844 Rochester, MN 55905 /( )\
-^^-^^
In theory, theory and practice are the same, but
in practice, theory and practice are different.
On 3/30/08 7:08 PM, Ian S. Worthington [EMAIL PROTECTED] wrote:
Restarting my zlinux system today I got the following which seems to
suggest some problem on 120. I'm assuming this is a red herring as it
also appears in my last good console (underneath)?
VolGroup00 should contain 122 as well I suspect, as it was extended to
use
this volume, though there's nothing on it as the fs is ext2 and couldn't
be
extended
online and I have no other way of booting. Could it be this its not
finding, or has got corrupted?
Any help/advice on how to disentangle this most welcome.
Ian
..
18:39:00 Loading dasd_mod.ko module
18:39:01 Loading dasd_eckd_mod.ko module
18:39:01 HHCCP048I 0120:CCW=2742 0FBDFFB8=1D00 0800
18:39:01 HHCCP075I 0120:Stat=0E40 Count=0040
18:39:01 HHCCP076I 0120:Sense=8000 000B0804
18:39:01 HHCCP077I 0120:Sense=CMDREJ
18:39:01 dasd_erp(3990): 0.0.0120: EXAMINE 24: Command Reject detected
- fatal error
18:39:01 dasd(eckd): I/O status report for device 0.0.0120:
18:39:01 dasd(eckd): in req: 0fbdfee0 CS: 0x40 DS: 0x0E
18:39:01 dasd(eckd): device 0.0.0120: Failing CCW: 0fbdffb8
18:39:01 dasd(eckd): Sense(hex) 0- 7: 80 00 00 00 00 0b 08 04
18:39:01 dasd(eckd): Sense(hex) 8-15: 00 00 00 00 00 00 00 00
18:39:01 dasd(eckd): Sense(hex) 16-23: 00 00 00 00 00 00 00 00
18:39:01 dasd(eckd): Sense(hex) 24-31: 00 00 00 80 00 00 0b 08
18:39:01 dasd(eckd): 24 Byte: 0 MSG 4, no MSGb to SYSOP
18:39:01 dasd(eckd): Related CP in req: 0fbdfee0
18:39:01 dasd(eckd): CCW 0fbdffb0: 2742 0FBDFFB8 DAT:
1d00 0800 000
18:39:01 0
18:39:01 dasd(eckd): 0.0.0120: PSF-SSC on storage subsystem
HRC.ZZ0001.0120 retur
18:39:01 ned rc=-5
18:39:01 dasd(eckd): 0.0.0120: 3390/0A(CU:3990/01) Cyl:3339 Head:15
Sec:224
18:39:01 Using cfq io scheduler
18:39:01 dasd(eckd): 0.0.0120: (4kB blks): 2404080kB at 48kB/trk
compatible disk layout
18:39:01 dasda:VOL1/ 0X0120: dasda1 dasda2
18:39:01 dasd(eckd): 0.0.0121: 3390/0A(CU:3990/01) Cyl:3339 Head:15
Sec:224
18:39:01 dasd(eckd): 0.0.0121: (4kB blks): 2404080kB at 48kB/trk
compatible disk layout
18:39:01 dasdb:VOL1/ 0X0121: dasdb1
18:39:02 Loading dasd_fba_mod.ko module
18:39:02 Loading dm-mirror.ko module
18:39:02 Loading dm-zero.ko module
18:39:02 Loading dm-snapshot.ko module
18:39:04 Making device-mapper control node
18:39:04 Scanning logical volumes
Re: Problems with rexec
On Monday, 03/31/2008 at 06:32 EDT, Szefler Jakub [EMAIL PROTECTED] wrote: I have read carefully your mail and i have made some changes to my configuration and now it works :) And now as you stated RXAGENT1 works with anonymous logons. The other guest (vpajsz) is authorized to issue command (when I block anoymous login). Thanks again for help in resolving my problem. I have only added: :NICK.VPAJSZ :TYPE.SERVER :CLASS.REXEC_AGENT to SYSTEM DTCPARMS file. You don't want to do that. Only users who are specifically defined to handle REXEC anonymous requests should be listed as REXEC_AGENTs. Do not create a DTCPARMS entry for VPAJSZ. The only requirements for PROFILE EXEC are that it must - access TCPMAINT 592 - not SET AUTOREAD OFF - exit when complete - avoid doing anything that would interfere with the *MSG system service after the PROFILE has ended. Alan Altmark z/VM Development IBM Endicott -- 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
SP4 version of mksles9root.sh
An updated version of the mksles9root.sh script that supports SLES9 SP4 has been added to the Patches page on the web site. http://linuxvm.org/Patches/index.html#mksles9root Mark Post -- 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
Re: DASD error on zlinux ipl
Thanks Brad. Seem to having some problems with this: -/bin/sh-3.00# chroot /mnt/sysimage2 chroot: cannot execute /sbin/loader: No such file or directory I'm using mnt/sysimage2 for this as sysimage exists: isn't that were the rescue system mounts the installation it found? I did: vgscan vgchange -a y mkdir /mnt/sysimage mount /dev/VolGroup00/LogGroup00 /mnt/sysimage2 mount /dev/dasda1 /mnt/sysimage2/boot chroot /mnt/sysimage2 I've attached the results from pvdisplay and lvdisplay. There's only one other VolGroup and that doesn't contain any boot data so I'm not worrying about mounting that just at the moment. Any thoughts? # pvdisplay --- Physical volume --- PV Name /dev/dasdd1 VG Name VGztpf PV Size 6.88 GB / not usable 3.11 MB Allocatable yes (but full) PE Size (KByte) 4096 Total PE 1760 Free PE 0 Allocated PE 1760 PV UUID 27fl0g-kjxZ-VTij-eVvc-kfSM-MngN-0zrYNF --- Physical volume --- PV Name /dev/dasdb1 VG Name VolGroup00 PV Size 2.29 GB / not usable 11.64 MB Allocatable yes (but full) PE Size (KByte) 32768 Total PE 73 Free PE 0 Allocated PE 73 PV UUID CYsk0I-XLWq-Kv9d-WtiJ-FEgu-b2IA-nY3aKi --- Physical volume --- PV Name /dev/dasda2 VG Name VolGroup00 PV Size 2.19 GB / not usable 7.66 MB Allocatable yes (but full) PE Size (KByte) 32768 Total PE 70 Free PE 0 Allocated PE 70 PV UUID hVAnW9-UZWp-gCqC-Sphe-I70J-MZSm-GKjOXN --- Physical volume --- PV Name /dev/dasdc1 VG Name VolGroup00 PV Size 6.88 GB / not usable 3.11 MB Allocatable yes (but full) PE Size (KByte) 32768 Total PE 220 Free PE 0 Allocated PE 220 PV UUID Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd # lvdisplay --- Logical volume --- LV Name/dev/VGztpf/LVztpf VG NameVGztpf LV UUIDeENhVR-eSRV-pFi6-GU2K-Gph8-h1es-tI2MyN LV Write Accessread/write LV Status available # open 0 LV Size6.88 GB Current LE 1760 Segments 1 Allocation inherit Read ahead sectors 0 Block device 253:0 --- Logical volume --- LV Name/dev/VolGroup00/LogVol00 VG NameVolGroup00 LV UUID9u3PP2-LwdK-XA58-rQPO-3kLs-K73H-NSIEDj LV Write Accessread/write LV Status available # open 1 LV Size10.84 GB Current LE 347 Segments 4 Allocation inherit Read ahead sectors 0 Block device 253:1 --- Logical volume --- LV Name/dev/VolGroup00/LogVol01 VG NameVolGroup00 LV UUIDWDKLbG-Ysln-It39-0eaH-cqw9-ISrf-y6Esd9 LV Write Accessread/write LV Status available # open 1 LV Size512.00 MB Current LE 16 Segments 1 Allocation inherit Read ahead sectors 0 Block device 253:2 # pvs PV VG Fmt Attr PSize PFree /dev/dasda2 VolGroup00 lvm2 a- 2.19G0 /dev/dasdb1 VolGroup00 lvm2 a- 2.28G0 /dev/dasdc1 VolGroup00 lvm2 a- 6.88G0 /dev/dasdd1 VGztpf lvm2 a- 6.88G0 -- Original Message -- Received: Mon, 31 Mar 2008 08:59:54 PM BST From: Brad Hinson [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Subject: Re: DASD error on zlinux ipl The easiest way to do this is: 1. Bring the LVM online: vgscan vgchange -a y 2. Mount the logical volume(s): mkdir /mnt/sysimage mount /dev/volgroupname/logvolname /mnt/sysimage/ mount /dev/dasda1 /mnt/sysimage/boot mount /dev/volgroupname/logvolname /mnt/sysimage/usr mount /dev/volgroupname/logvolname /mnt/sysimage/var [etc.] 3. chroot into the mounted system: chroot /mnt/sysimage 4. Rerun zipl/mkinitrd: zipl -V; mkinitrd -v -f /boot/initrd-`uname -r`.img `uname -r` -Brad On Mon, 2008-03-31 at 17:54 +0100, Ian S. Worthington wrote: Hi Robert -- Hmm. I certainly didn't do a zipl and pretty sure I didn't do a mkinitrd either. They don't seem to be mentioned in the instructions I was following. I can't boot my system normally, but thanks to some help on this list, have now got it up in rescue mode. cat devices seems to show all volumes at least present: 0.0.0120(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 601020 blocks, 2347 MB 0.0.0121(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096,
64-bit Slack/390
Hello, Does anybody know what's going on with 64-bit Slack realase? -- 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
Re: 64-bit Slack/390
On Mon, Mar 31, 2008 at 6:04 PM, in message [EMAIL PROTECTED], Przemyslaw Kupisz [EMAIL PROTECTED] wrote: Hello, Does anybody know what's going on with 64-bit Slack realase? Yes. :) I got about 75% done with it, then it's been too low on my priority list for a while. Is there a real need for it? I could try to spend some more time on it. Mark Post -- 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
Re: DASD error on zlinux ipl
On Mon, Mar 31, 2008 at 5:48 PM, in message [EMAIL PROTECTED], Ian S. Worthington [EMAIL PROTECTED] wrote: Thanks Brad. Seem to having some problems with this: -/bin/sh-3.00# chroot /mnt/sysimage2 chroot: cannot execute /sbin/loader: No such file or directory I'm using mnt/sysimage2 for this as sysimage exists: isn't that were the rescue system mounts the installation it found? I did: vgscan vgchange -a y mkdir /mnt/sysimage mount /dev/VolGroup00/LogGroup00 /mnt/sysimage2 mount /dev/dasda1 /mnt/sysimage2/boot chroot /mnt/sysimage2 I've attached the results from pvdisplay and lvdisplay. There's only one other VolGroup and that doesn't contain any boot data so I'm not worrying about mounting that just at the moment. Any thoughts? Most likely you need to mount the /usr file system as well, as Brad suggested. I would imagine /sbin/loader has shared libraries it needs to access on /usr. Mark Post -- 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
Re: sles10 on hercules.
Michael Prahin wrote: Hi, I am trying to install sles10 on Hercules. Managed to finish the installation and ran into a problem, when rebooting from a disk. It starts and then issues: cio: Was not able to determine available CHSCs. Error starting thread in diagnose 0x308: Success That error message itself is issued badly. It results from detecting an error (a function sets errno and returns -1), and then using another function that alters errno and using the new value to report the error. Since the later function worked in this case, the error message is Success instead of something else such as Operation Canceled. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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
Re: IPL Centos s390x dvd in RESCUE mode?
Brad Hinson wrote: On Mon, 2008-03-31 at 11:18 +0800, John Summerfield wrote: Ian S. Worthington wrote: According to Redhat's documentation it should be possible to ipl the install dvd in RESCUE mode. However when I try it seems to go into install mode, asking me for my ctc addresses: Why do you think that is a problem? Yep, you have to answer the initial networking questions (because there's no CONF to reference). Afterwards, instead of launching the installer, rescue mode will start. I was trying to find Ian's concerns, _not_ your guesses. I can guess too, but I'm not willing to assume I can read his mind. Note that you can do this through z/VM by just adding 'rescue' to the PARM file. 22:12:53 Starting the zSeries initrd to configure networking. Version is 1.1 22:12:55 Which kind of network device do you intend to use 22:12:55 (e.g. ctc, iucv, qeth, lcs). 22:12:55 Enter 'qeth' for OSA-Express Fast Ethernet, Gigabit Ethernet 22:12:55 (including 1000Base-T), High Speed Token Ring, and ATM 22:12:55 (running Ethernet LAN emulation) features in QDIO mode. 22:12:55 Enter 'lcs' for OSA 2 Ethernet/Token Ring, OSA-Express Fast Ethernet in 22:12:55 non-QDIO mode, OSA-Express High Speed Token Ring in non-QDIO mode and 22:12:55 Gigabit Ethernet in non-QDIO mode. It has confirmed: 22:10:47 Kernel command line: root=/dev/ram0 ro ip=off ramdisk_size=4 rescue So I'm assuming that its happy with my ins file: * minimal lpar ins file g:/images/kernel.img 0x g:/images/initrd.img 0x0080 D:/zcentos/rescue/rescue.prm 0x00010480 and prm: root=/dev/ram0 ro ip=off ramdisk_size=4 rescue (If its relevant I have detached my disks as I don't want them to be accidentally written to.) Anyone know how to boot this in RESCUE mode? ian ... Ian S. Worthington, MBCS. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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
Re: DASD error on zlinux ipl
Thanks Mark. I'm not sure there is anything to mount at /usr. LGztpf mounts at /ztpf. There's a LogVol01, but I'm not sure where that's meant to mount. Certainly its not happy being mounted at /usr, which in any case already contains a whole bunch of its own stuff. In fact where ever I try to mount LogVol01 it gives the same error. -/bin/sh-3.00# mount /dev/VolGroup00/LogVol00 /mnt/sysimage2 -/bin/sh-3.00# mount /dev/VGztpf/LVztpf /mnt/sysimage2/ztpf -/bin/sh-3.00# mount /dev/VolGroup00/LogVol01 /mnt/sysimage2/usr mount: Mounting /dev/VolGroup00/LogVol01 on /mnt/sysimage2/usr failed: Device or resource busy -/bin/sh-3.00# ls /mnt/sysimage/usr X11R6 etc include lib libexec sbin src bin games kerberos lib64 local share tmp -/bin/sh-3.00# chroot /mnt/sysimage2 chroot: cannot execute /sbin/loader: No such file or directory -/bin/sh-3.00# ian ... -- Original Message -- Received: Tue, 01 Apr 2008 12:08:58 AM BST From: Mark Post [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Subject: Re: DASD error on zlinux ipl On Mon, Mar 31, 2008 at 5:48 PM, in message [EMAIL PROTECTED], Ian S. Worthington [EMAIL PROTECTED] wrote: Thanks Brad. Seem to having some problems with this: -/bin/sh-3.00# chroot /mnt/sysimage2 chroot: cannot execute /sbin/loader: No such file or directory I'm using mnt/sysimage2 for this as sysimage exists: isn't that were the rescue system mounts the installation it found? I did: vgscan vgchange -a y mkdir /mnt/sysimage mount /dev/VolGroup00/LogGroup00 /mnt/sysimage2 mount /dev/dasda1 /mnt/sysimage2/boot chroot /mnt/sysimage2 I've attached the results from pvdisplay and lvdisplay. There's only one other VolGroup and that doesn't contain any boot data so I'm not worrying about mounting that just at the moment. Any thoughts? Most likely you need to mount the /usr file system as well, as Brad suggested. I would imagine /sbin/loader has shared libraries it needs to access on /usr. Mark Post -- 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 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
Re: IPL Centos s390x dvd in RESCUE mode?
Thanks John, but it transpires I was just being overcautious. I wanted to make sure I wasn't going to end up overwriting the dasd I'm trying to save by mistake. My mind's pretty simple to read in any case: my wife's always telling me that so it must be true! i -- Original Message -- Received: Tue, 01 Apr 2008 12:24:01 AM BST From: John Summerfield [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Subject: Re: IPL Centos s390x dvd in RESCUE mode? Brad Hinson wrote: On Mon, 2008-03-31 at 11:18 +0800, John Summerfield wrote: Ian S. Worthington wrote: According to Redhat's documentation it should be possible to ipl the install dvd in RESCUE mode. However when I try it seems to go into install mode, asking me for my ctc addresses: Why do you think that is a problem? Yep, you have to answer the initial networking questions (because there's no CONF to reference). Afterwards, instead of launching the installer, rescue mode will start. I was trying to find Ian's concerns, _not_ your guesses. I can guess too, but I'm not willing to assume I can read his mind. Note that you can do this through z/VM by just adding 'rescue' to the PARM file. 22:12:53 Starting the zSeries initrd to configure networking. Version is 1.1 22:12:55 Which kind of network device do you intend to use 22:12:55 (e.g. ctc, iucv, qeth, lcs). 22:12:55 Enter 'qeth' for OSA-Express Fast Ethernet, Gigabit Ethernet 22:12:55 (including 1000Base-T), High Speed Token Ring, and ATM 22:12:55 (running Ethernet LAN emulation) features in QDIO mode. 22:12:55 Enter 'lcs' for OSA 2 Ethernet/Token Ring, OSA-Express Fast Ethernet in 22:12:55 non-QDIO mode, OSA-Express High Speed Token Ring in non-QDIO mode and 22:12:55 Gigabit Ethernet in non-QDIO mode. It has confirmed: 22:10:47 Kernel command line: root=/dev/ram0 ro ip=off ramdisk_size=4 rescue So I'm assuming that its happy with my ins file: * minimal lpar ins file g:/images/kernel.img 0x g:/images/initrd.img 0x0080 D:/zcentos/rescue/rescue.prm 0x00010480 and prm: root=/dev/ram0 ro ip=off ramdisk_size=4 rescue (If its relevant I have detached my disks as I don't want them to be accidentally written to.) Anyone know how to boot this in RESCUE mode? ian ... Ian S. Worthington, MBCS. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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 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
Re: DASD error on zlinux ipl
chroot is designed to run a single command with a ch'd root. You can chroot a shell, which is the default, and probably what Brad was expecting to happen when he wrote his instructions. I wonder if your $SHELL is set to /sbin/loader, which would explain the error. I have no idea what /sbin/loader is, perhaps it's an initrd utility. It's not on any of my root filesystems. It's almost certainly not what you want with chroot. Something else that frequently gets missed is that chroot runs the command you specify, AFTER ch'ing the root. So, for example, if you execute chroot /mnt /sbin/zipl, what actually gets run is what WAS, before the chroot, /mnt/sbin/zipl. You probably shouldn't have been given the instructions as they were, as these become potential gotchas. I would recommend amending step 3 in Brad's instructions to chroot /mnt /sbin/sh, and then running step 4 as written. ok r. -Original Message- From: Ian S. Worthington [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2008 4:43 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: DASD error on zlinux ipl Thanks Mark. I'm not sure there is anything to mount at /usr. LGztpf mounts at /ztpf. There's a LogVol01, but I'm not sure where that's meant to mount. Certainly its not happy being mounted at /usr, which in any case already contains a whole bunch of its own stuff. In fact where ever I try to mount LogVol01 it gives the same error. -/bin/sh-3.00# mount /dev/VolGroup00/LogVol00 /mnt/sysimage2 -/bin/sh-3.00# mount /dev/VGztpf/LVztpf /mnt/sysimage2/ztpf -/bin/sh-3.00# mount /dev/VolGroup00/LogVol01 /mnt/sysimage2/usr mount: Mounting /dev/VolGroup00/LogVol01 on /mnt/sysimage2/usr failed: Device or resource busy -/bin/sh-3.00# ls /mnt/sysimage/usr X11R6 etc include lib libexec sbin src bin games kerberos lib64 local share tmp -/bin/sh-3.00# chroot /mnt/sysimage2 chroot: cannot execute /sbin/loader: No such file or directory -/bin/sh-3.00# ian ... -- Original Message -- Received: Tue, 01 Apr 2008 12:08:58 AM BST From: Mark Post [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Subject: Re: DASD error on zlinux ipl On Mon, Mar 31, 2008 at 5:48 PM, in message [EMAIL PROTECTED], Ian S. Worthington [EMAIL PROTECTED] wrote: Thanks Brad. Seem to having some problems with this: -/bin/sh-3.00# chroot /mnt/sysimage2 chroot: cannot execute /sbin/loader: No such file or directory I'm using mnt/sysimage2 for this as sysimage exists: isn't that were the rescue system mounts the installation it found? I did: vgscan vgchange -a y mkdir /mnt/sysimage mount /dev/VolGroup00/LogGroup00 /mnt/sysimage2 mount /dev/dasda1 /mnt/sysimage2/boot chroot /mnt/sysimage2 I've attached the results from pvdisplay and lvdisplay. There's only one other VolGroup and that doesn't contain any boot data so I'm not worrying about mounting that just at the moment. Any thoughts? Most likely you need to mount the /usr file system as well, as Brad suggested. I would imagine /sbin/loader has shared libraries it needs to access on /usr. Mark Post -- 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 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 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
Re: DASD error on zlinux ipl
Thanks Raymond. I think you've correctly diagnosed the problem: -/bin/sh-3.00# echo $SHELL /sbin/loader Clearly there's no sign of that on my system either... I've tried your alternative for chroot -- several different variants in fact -- all without success. It refuses to find sh, even though it clearly there this time. Any thoughts? Here's the console: Mount volumes (apart from swap): -/bin/sh-3.00# vgscan Reading all physical volumes. This may take a while... Found volume group VGztpf using metadata type lvm2t Found volume group VolGroup00 using metadata type lvm2 -/bin/sh-3.00# vgchange -a y 1 logical volume(s) in volume group VGztpf now active 2 logical volume(s) in volume group VolGroup00 now active -/bin/sh-3.00# mkdir /mnt/sysimage2 -/bin/sh-3.00# mount /dev/VolGroup00/LogVol00 /mnt/sysimage2 -/bin/sh-3.00# mount /dev/dasda1 /mnt/sysimage2/boot -/bin/sh-3.00# mount /dev/VGztpf/LVztpf /mnt/sysimage2/ztpf Check presence: -/bin/sh-3.00# ls -l /sbin/sh lrwxrwxrwx1 root 0 4 May 17 2007 /sbin/sh - bash chroot: -/bin/sh-3.00# chroot /mnt/sysimage2 /sbin/sh chroot: cannot execute /sbin/sh: No such file or directory -/bin/sh-3.00# chroot /mnt/sysimage2 /mnt/sysimage/sbin/sh chroot: cannot execute /mnt/sysimage/sbin/sh: No such file or directory -/bin/sh-3.00# chroot /mnt/sysimage2 /mnt/sysimage/sbin/bash chroot: cannot execute /mnt/sysimage/sbin/bash: No such file or directory -/bin/sh-3.00# chroot /mnt/sysimage2 /sbin/bash chroot: cannot execute /sbin/bash: No such file or directory -- Original Message -- Received: Tue, 01 Apr 2008 12:58:43 AM BST From: Stricklin, Raymond J [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Subject: Re: DASD error on zlinux ipl chroot is designed to run a single command with a ch'd root. You can chroot a shell, which is the default, and probably what Brad was expecting to happen when he wrote his instructions. I wonder if your $SHELL is set to /sbin/loader, which would explain the error. I have no idea what /sbin/loader is, perhaps it's an initrd utility. It's not on any of my root filesystems. It's almost certainly not what you want with chroot. Something else that frequently gets missed is that chroot runs the command you specify, AFTER ch'ing the root. So, for example, if you execute chroot /mnt /sbin/zipl, what actually gets run is what WAS, before the chroot, /mnt/sbin/zipl. You probably shouldn't have been given the instructions as they were, as these become potential gotchas. I would recommend amending step 3 in Brad's instructions to chroot /mnt /sbin/sh, and then running step 4 as written. ok r. -Original Message- From: Ian S. Worthington [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2008 4:43 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: DASD error on zlinux ipl Thanks Mark. I'm not sure there is anything to mount at /usr. LGztpf mounts at /ztpf. There's a LogVol01, but I'm not sure where that's meant to mount. Certainly its not happy being mounted at /usr, which in any case already contains a whole bunch of its own stuff. In fact where ever I try to mount LogVol01 it gives the same error. -/bin/sh-3.00# mount /dev/VolGroup00/LogVol00 /mnt/sysimage2 -/bin/sh-3.00# mount /dev/VGztpf/LVztpf /mnt/sysimage2/ztpf -/bin/sh-3.00# mount /dev/VolGroup00/LogVol01 /mnt/sysimage2/usr mount: Mounting /dev/VolGroup00/LogVol01 on /mnt/sysimage2/usr failed: Device or resource busy -/bin/sh-3.00# ls /mnt/sysimage/usr X11R6 etc include lib libexec sbin src bin games kerberos lib64 local share tmp -/bin/sh-3.00# chroot /mnt/sysimage2 chroot: cannot execute /sbin/loader: No such file or directory -/bin/sh-3.00# ian ... -- Original Message -- Received: Tue, 01 Apr 2008 12:08:58 AM BST From: Mark Post [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Subject: Re: DASD error on zlinux ipl On Mon, Mar 31, 2008 at 5:48 PM, in message [EMAIL PROTECTED], Ian S. Worthington [EMAIL PROTECTED] wrote: Thanks Brad. Seem to having some problems with this: -/bin/sh-3.00# chroot /mnt/sysimage2 chroot: cannot execute /sbin/loader: No such file or directory I'm using mnt/sysimage2 for this as sysimage exists: isn't that were the rescue system mounts the installation it found? I did: vgscan vgchange -a y mkdir /mnt/sysimage mount /dev/VolGroup00/LogGroup00 /mnt/sysimage2 mount /dev/dasda1 /mnt/sysimage2/boot chroot /mnt/sysimage2 I've attached the results from pvdisplay and lvdisplay. There's only one other VolGroup and that doesn't contain any boot data so I'm not worrying about mounting that just at the moment. Any thoughts? Most likely you need to mount the /usr file system as well, as Brad suggested. I would imagine
Re: IPL Centos s390x dvd in RESCUE mode?
Ian S. Worthington wrote: Thanks John, but it transpires I was just being overcautious. I wanted to make sure I wasn't going to end up overwriting the dasd I'm trying to save by mistake. I thought you were, especially since it was the network configuration you were balking at. I'm happy to boot and run almost any installer up to the point it starts asking about how to partition drives! The latest rawhide (Fedora I describe as a rolling beta, Rawhide is it's riskier sibling) is perfectly safe on one of my systems, it can't find the drives. My mind's pretty simple to read in any case: my wife's always telling me that so it must be true! She's probably reading your face:-) i -- Original Message -- Received: Tue, 01 Apr 2008 12:24:01 AM BST From: John Summerfield [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Subject: Re: IPL Centos s390x dvd in RESCUE mode? Brad Hinson wrote: On Mon, 2008-03-31 at 11:18 +0800, John Summerfield wrote: Ian S. Worthington wrote: According to Redhat's documentation it should be possible to ipl the install dvd in RESCUE mode. However when I try it seems to go into install mode, asking me for my ctc addresses: Why do you think that is a problem? Yep, you have to answer the initial networking questions (because there's no CONF to reference). Afterwards, instead of launching the installer, rescue mode will start. I was trying to find Ian's concerns, _not_ your guesses. I can guess too, but I'm not willing to assume I can read his mind. Note that you can do this through z/VM by just adding 'rescue' to the PARM file. 22:12:53 Starting the zSeries initrd to configure networking. Version is 1.1 22:12:55 Which kind of network device do you intend to use 22:12:55 (e.g. ctc, iucv, qeth, lcs). 22:12:55 Enter 'qeth' for OSA-Express Fast Ethernet, Gigabit Ethernet 22:12:55 (including 1000Base-T), High Speed Token Ring, and ATM 22:12:55 (running Ethernet LAN emulation) features in QDIO mode. 22:12:55 Enter 'lcs' for OSA 2 Ethernet/Token Ring, OSA-Express Fast Ethernet in 22:12:55 non-QDIO mode, OSA-Express High Speed Token Ring in non-QDIO mode and 22:12:55 Gigabit Ethernet in non-QDIO mode. It has confirmed: 22:10:47 Kernel command line: root=/dev/ram0 ro ip=off ramdisk_size=4 rescue So I'm assuming that its happy with my ins file: * minimal lpar ins file g:/images/kernel.img 0x g:/images/initrd.img 0x0080 D:/zcentos/rescue/rescue.prm 0x00010480 and prm: root=/dev/ram0 ro ip=off ramdisk_size=4 rescue (If its relevant I have detached my disks as I don't want them to be accidentally written to.) Anyone know how to boot this in RESCUE mode? ian ... Ian S. Worthington, MBCS. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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 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 -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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
(Apr 2 Webcast) Problem Determination with Linux on System z
Cross-posted for the readers of IBMVM, Linux-390 and IBMMAIN. The next Linux on System z Live Virtual Class (LVC) is planned for Wednesday, April 2nd 11:00 AM EDT. There is no charge to participate in this technical education session. Title: Problem Determination with Linux on System z Most frequently-seen customer problems and what to do, if yours is not among them Speakers: Steffen Thoss, IBM Boeblingen and Holger Smolinski, IBM Boeblingen Abstract: This presentation is about problem resolution in Linux on System z running with or without z/VM. A selection of frequent customer problems and their solution is shown. We demonstrate usage of debugging tools to collect important system data and analyze real life problems. In addition we explain, how you can check the health state of your system using these documents before or after a problem occurs. Date: Wed - April 2, 2008 Time: 11:00 AM Eastern Daylight Time (New York), 10:00 AM Central Daylight Time London 4:00 PM, Frankfurt 5:00 PM, Moscow 7:00PM Duration: 75 minutes REPLAY INFORMATION: The replay will be available on the web approximately 3 hours after the event. Attend the Replay. How to attend (For Customers): Connect/Listen to the replay to the Live Virtual Class (LVC) session using the following URL: https://asp22.centra.com:443/GA/main/0194ba1701188cd08703c166 OR Connect/Download the Presentation/Listen to the replay from the z/VM Website at: http://www.vm.ibm.com/education/lvc You can connect to the LVC session up to 10 minutes prior to the start of the session. If you are unable to connect to the Live Virtual Class session, you can listen to the audio portion of the session via telephone using the following: Teleconference Information Toll free : 1-888-240-4148 International:1-719-234-0214 Access Code: 355253 Note: use of the telephone connection does not provide capability for you to ask questions during the session. Replays: As a reminder, the 2007/2008 sessions are available for replay from the z/VM website at: http://www.vm.ibm.com/education/lvc Please direct any questions to Julie Liesenfelt at [EMAIL PROTECTED] Again...Please direct any questions to Julie Liesenfelt at [EMAIL PROTECTED] Thanks! Regards, Pam Christina (IBM z/VM in Endicott NY) -- 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
Re: DASD error on zlinux ipl
On Mar 31, 2008, at 6:14 PM, Ian S. Worthington wrote: Check presence: -/bin/sh-3.00# ls -l /sbin/sh lrwxrwxrwx1 root 0 4 May 17 2007 /sbin/sh - bash What you would actually want to check the presence of, here, is: /mnt/sysimage2/sbin/bash as that is what will be executed with chroot when you correctly type: chroot /mnt/sysimage2 /sbin/bash Brad's instructions could equally well have been amended thus: chroot /mnt/sysimage2 /sbin/zipl -V chroot /mnt/sysimage2 /sbin/mkinitrd -v -f /boot/initrd-`uname -r`.img `uname -r` Which would then run the zipl and mkinitrd _on your mounted /mnt/ sysimage2 dasd_. Now that I type that out, you're going to have another very big problem and a still unbootable system, as the mkinitrd must come _before_ zipl! Here are my suggestions for alternate steps 3 4 from Brad's process, assuming I've correctly inferred that VolGroup00/LogVol00 is your normal root filesystem (/) and that dasda1 is /boot: 3. Create the initrd: # mkinitrd -b /mnt/sysimage2/boot -d /dev/VolGroup00/LogVol00 # cp -p /boot/initrd* /mnt/sysimage2/boot (if somebody can tell me why this writes the initrd to /boot instead of /mnt/sysimage2/boot and thus requires the manual 'cp' step, I would be grateful) 4. Run zipl # chroot /mnt/sysimage2 /sbin/zipl ok bear -- 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
