Rhel 5.4 install problems
In the redhat.conf file I think you need to use lower case letters for the device number triple. Try SUBCHANNELS=0.0.e017,0.0.e018,0.0.e019 Cliff Laking IBM United Kingdom -- Date:Tue, 19 Jan 2010 18:00:08 -0500 From:Sue Sivets ssiv...@fdrinnovation.com Subject: Rhel 5.4 install problems I'm trying to install Rhel 5.4 under VM, and it's not doing what I think it should be doing as far as the redhat.conf file is concerned. I installed Rhel 5.3 a couple of months ago (using the redhat parm conf files), so I copied both the parm and conf files from that system to the 191 disk for the new machine, and updated the conf file with the correct information. Then I copied the kernal initrd files from the Rhel 5.4 dvd. I think everything is setup correctly, and I'm not getting any messages that look like error messages, but after I punch the files to the reader and ipl it, I'm getting prompted for the dasd and network information, as if the software either doesn't see the cmsconffile info in the parm file, or as if it doesn't even know the conf file exists. On the 5.3 install, the system prompted me for the password that I wanted to use for root, the 5.4 system is not doing that, but it does tell me when I can log in to the new system as user root, using SSH. Of course when I try to do that, I get prompted for roots password. If there is a default, I don't know what it is, and so far everything I've tried in both upper and lower case has not worked. The redhat.parm file is: root=/dev/ram0 ro ip=off ramdisk_size=4 CMSDASD=191 CMSCONFFILE=redhat.conf The redhat.conf file is: HOSTNAME=red54.idp.com DASD=0500-8f27 NETTYPE=qeth IPADDR=192.168.250.245 SUBCHANNELS=0.0.E017,0.0.E018,0.0.E019 NETWORK=192.168.250.0 NETMASK=255.255.255.0 BROADCAST=192.168.250.255 SEARCHDNS=idp.com GATEWAY=192.168.250.161 DNS=192.168.150.156 MTU=1500 LAYER2=0 VSWITCH=1 PORTNAME= PORTNO=0 Does anyone have any idea of how to make this install work? I don't really mind having to enter the information manually, but the password part of the problem has stopped me cold, and I don't see any way of going any further without fixing whatever is causing the password promt to not happen. If anyone knows what the default password is, I would appreciate knowing what it is, so I can at least get logged on and hopefully get the system installed. I can always change the root password later on. Thank you to anyone who's got any ideas. Sue Sivets -- Suzanne Sivets Systems Programmer Innovation Data Processing 275 Paterson Ave Little Falls, NJ 07424-1658 973-890-7300 Fax 973-890-7147 ssiv...@fdrinnovation.com -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Rhel 5.4 install problems
Mark Ver wrote: Try defining a second cpu DEF CPU 02 Or try doing a define stor of 2G or greater. If I recall correctly, there was an issue found with parameter file handling on RHEL 5.4 installer image that required such restrictions. I think this will be documented in an updated release notes if not done so already. But whenever I've seen that problem, I've been able to log on after specifying the network info manually. So it sounds like there is another problem involved here. Also as far as I know, the prompt into the Red Hat installer shouldn't be asking for a password ... is the session just hanging? Or is actually coming back with an access denied message? Another thing to check is the protocol your ssh client (for example PuTTY) is using. It should be ssh protocol 2, not 1. Here are a few things that might be a good place to start debug: 1) see if you can log in as debug instead of root (should also not require a password) 2) if using a Windows ssh client, try logging in from another Linux system with X forwarding explicitly disabled (small x flag) in case X forwarding is causing some sort of disruption in getting the display from the loader program. ssh -x r...@mysystem.net 3) press enter twice on the z/VM console for the guest, this should get it to display a console prompt, ex: sh-3.2# You can then use it to do stuff like: ifconfig tail /tmp/anaconda.log cat /tmp/netinfo cat /etc/passwd ps | grep sshd - Mark Ver -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- Brad Hinson bhin...@redhat.com Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 www.redhat.com/z -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Dirmaint doesn't work.
Thanks for your reply. That's right. As you mention above, I used the clean option in configaa datadvh. Also, this auto reply error messages was related with 'MAXIMUM_UNASSIGNED_WORKUNITS=' option which default value was 10. So, I change the default value to 100 and delete the LINK parameter under DATAMOVE directory file and delete file 'PURGES PENDING'. After update above configuration, I issue the PURGE command with noclean option. then all error message was disappeared. However, we still have problem when I used the purge command by maint, it was not purged clearly that i think. Because, after purged the guest, it information was still exist in directory file that was appeared by 'DIRM USER NOPASS'. 1. How can I purge the guest in perfectly by purge command? 2. That was related problem 'CLEAN' or 'NOCLEAN' option? If this problem was related 'CLEAN' option in CONFIGAA DATADVH configuration file, we have to another way to remove the guest. Always, we have to shared the one storage by two z/VM. So, when we make the guest in first, we define the directory and racf on both systems. thanks in advance. best regards. If DIRMAINT didn't respond to your initial request, then there was something wrong with it at that point. When you logged on and issued the DVHBEGIN command, you restarted DIRMAINT. That is why your commands started to be processed. What you need to find out is the status of DIRMAINT before you logged in. Do you keep the console logs archived anywhere? If you do, check the one from just before 16:23:45 and see what state DIRMAINT was in at that point. When you purge a guest, but default DIRMAINT tries to clean up any minidisks defined to that guest. It does this by transferring them to the DATAMOVE virtual machine, which then does a format on the disks before giving them back to the system. So, that is what the messages involving DATAMOVE are about. If this guest had a lot of minidisks, or they were very large ones, this process can take quite awhile. So, that may have been part of the delay you were seeing (can't really tell without seeing the full console log). You can avoid the cleanup process if it isn't important to your situation. To avoid it, use the NOCLEAN option on the PURGE command, for example: dirm for xlnx2 purge noclean Then, DIRMAINT deletes the guest from the directory but does not format the disks. Martha McConaghy Marist College -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
