NO CONSOLE MSGS when IPLing an OFFLINDR-restored system - resolved
Thanks to Paul, Vic & Mark!! Using the MP3000 SE, I configured all unnecessary CHPIDs offline to the Linux LPAR... and I started getting IPL msgs!! Thanks much!!! Lesson learned...I will modify my IODF !! Dave In a message dated 10/15/2002 8:11:45 AM Mountain Daylight Time, [EMAIL PROTECTED] writes: > Dave, > > I had one Linux LPAR (9672T26 LPAR mode) that used to give me fits. I > saw similar symptoms: IPL load complete, SAD activity, but no console > messages. Once I went to lunch and came back to find there were > messages after nearly an hour of 'blank console'. This was pre IFL and > the LPAR had small weight values, but still!! I trimmed down the 'GEN' > to eliminate all of the unnecessary channels and devices and retained > only the absolute essentials and that made all the difference in the > world. Messages started coming back to the console in seconds. > (Alternately, you could just "CONFIG OFF" the unnecessary stuff via > HCM). YMMV. > > Good luck, > Paul >
Re: NO CONSOLE MSGS when IPLing an OFFLINDR-restored system
>> I am making the (possibly incorrect) assumption that you have ensured that >> the >> LPAR has only necessary devices online, and in particular no 3174s or like >> (as >> per previous posts). >> >> Good luck, >> Vic Cross >> >hmmm..yes I do have other devices accessible to this lpar (like 3174s), but >that's always been >the case in the past and did not interfere with linux ipls?? >Dave Dave, I had one Linux LPAR (9672T26 LPAR mode) that used to give me fits. I saw similar symptoms: IPL load complete, SAD activity, but no console messages. Once I went to lunch and came back to find there were messages after nearly an hour of 'blank console'. This was pre IFL and the LPAR had small weight values, but still!! I trimmed down the 'GEN' to eliminate all of the unnecessary channels and devices and retained only the absolute essentials and that made all the difference in the world. Messages started coming back to the console in seconds. (Alternately, you could just "CONFIG OFF" the unnecessary stuff via HCM). YMMV. Good luck, Paul
Re: NO CONSOLE MSGS when IPLing an OFFLINDR-restored system
In a message dated 10/15/2002 12:23:51 AM Mountain Daylight Time, [EMAIL PROTECTED] writes: > I am making the (possibly incorrect) assumption that you have ensured that > the > LPAR has only necessary devices online, and in particular no 3174s or like > (as > per previous posts). > > Good luck, > Vic Cross > hmmm..yes I do have other devices accessible to this lpar (like 3174s), but that's always been the case in the past and did not interfere with linux ipls?? Dave
Re: Fwd: NO CONSOLE MSGS when IPLing an OFFLINDR-restored system
Dave, I suspect that your bootloader is not handling the copy process well. In your original message you said that you reran zipl, but I have had problems (even on PCs) with bootloaders getting confused about devices moving about underneath them. From my experience, bootloader builders work best and most predictably when all of the disks are in the final configuration. I suggest IPLing your installation system and using that as a rescue system. I think this process has been described previously, but here's a snapshot: 1) IPL installation system, break out of installation script 2) Load DASD driver to access your DASD with the *same* dasd= line as your system will use 3) mount the filesystems (at least your boot device and the /, /sbin and /boot directories must be accessible) 4) chroot to the root directory of your mounted system (this is not technically necessary, but it does eliminate the need to change your zipl command line or configuration file) 5) run zipl 6) unmount filesystems, cross fingers, re-IPL I'm not sure why a RAMDISK system does not IPL (but then I'm not sure exactly what you mean by RAMDISK system...). I am making the (possibly incorrect) assumption that you have ensured that the LPAR has only necessary devices online, and in particular no 3174s or like (as per previous posts). Good luck, Vic Cross On 15.10.2002 at 06:06:10, Dave Myers <[EMAIL PROTECTED]> wrote: > Well as a second test, I OFFLINDR-copied by RAMDISK system > to the MP3000-H70 and it does not IPL either. > NO CONSOLE MSGS. > > Anyone have any ideas why this would not work. > Thanks, > Dave Myers >
Fwd: NO CONSOLE MSGS when IPLing an OFFLINDR-restored system
Well as a second test, I OFFLINDR-copied by RAMDISK system to the MP3000-H70 and it does not IPL either. NO CONSOLE MSGS. Anyone have any ideas why this would not work. Thanks, Dave Myers I attempted to copy(backup/restore) a RH 7.2 system today using OFFLINDR. (I've done this in the past successfully). The system is being moved from an older mp3000-a20 to an mp3000 h70. The source system was made up of 4 3390 volumes. 1. dasda1 - / 2. dasdb1 - /usr 3. dasdc1 - swap1 4. dasdd1 - swap2 This is what i did: On MP3000-A20 system: 1. updated parmfile to point to my new device address on the target system. 2. ran zipl 3. updated the ipaddr in ifcfg-eth0 4. updated /etc/fstab to remove swap filesystems (because I did not copy those 2 3390s to the tgt system) 5. Issued command swapoff -a 6. updated /etc/chandev to change the lcs0 addrs 7. shutdown the system 8. backed up the system using offlindr ** see note below 1. On mp3000 h70 OFFLINDR restored the 2 3390 volumes 2. IPL'd new target 3. Received NO CONSOLE MSGS, BUT NOTICED THAT THE SYSTEM DID "IPL COMPLETE" and the CPU showed activity. ** NOTE: The source RH 7.2 system had two SWAP FILESYSTEMs on two other 3390s...and I did NOT copy those to the target system. Instead I updated fstab to not mount the swap filesystems. ANY IDEAS??? TIA Dave
NO CONSOLE MSGS when IPLing an OFFLINDR-restored system
I attempted to copy(backup/restore) a RH 7.2 system today using OFFLINDR. (I've done this in the past successfully). The system is being moved from an older mp3000-a20 to an mp3000 h70. The source system was made up of 4 3390 volumes. 1. dasda1 - / 2. dasdb1 - /usr 3. dasdc1 - swap1 4. dasdd1 - swap2 This is what i did: On MP3000-A20 system: 1. updated parmfile to point to my new device address on the target system. 2. ran zipl 3. updated the ipaddr in ifcfg-eth0 4. updated /etc/fstab to remove swap filesystems (because I did not copy those 2 3390s to the tgt system) 5. Issued command swapoff -a 6. updated /etc/chandev to change the lcs0 addrs 7. shutdown the system 8. backed up the system using offlindr ** see note below 1. On mp3000 h70 OFFLINDR restored the 2 3390 volumes 2. IPL'd new target 3. Received NO CONSOLE MSGS, BUT NOTICED THAT THE SYSTEM DID "IPL COMPLETE" and the CPU showed activity. ** NOTE: The source RH 7.2 system had two SWAP FILESYSTEMs on two other 3390s...and I did NOT copy those to the target system. Instead I updated fstab to not mount the swap filesystems. ANY IDEAS??? TIA Dave