| Blogs | Classifieds | Downloads | FlashChat | Gallery | Googlemap | Invite Friends | Links | Projects | Reviews | Wiki |
| |||||||||
Welcome to the pSeries Tech Forums,
our free peer-based support site for administrators, engineers and architects working with IBM pSeries servers and software. You are currently viewing our site as a guest which gives you limited access to view most discussions, articles, tutorials and access our other free features. By joining our community you will be able to collaborate with administrators, engineers and architects charged with designing, delivering or maintaining IBM pSeries server environments. Founded by a recognized IBM pSeries consultant and IBM Redbook author, pSeries Tech Forums was developed with the single mission of bringing IBM pSeries professionals together into a single self-help community. Registration is fast, simple and absolutely free to all IT professionals with responsibility for or interest in IBM pSeries servers. We invite you to join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
| Our Sponsors | |
| | |
| Want to advertise? | |
![]() |
| | LinkBack | Thread Tools |
|
#1
| ||||
| ||||
| I have a server at AIX 5.3.5 SP3 currently running on POWER3 hardware. I will be rehosting to an LPAR on a p570. The LPAR on the p570 will use virtual SCSI disks. I took a mksysb backup and was able to restore it successfully to the p570 LPAR. When the server rebooted after the installation, it was unable to boot from the disks I had just restored the OS image on. I booted to SMS mode and they cannot be seen. I booted to maintenance mode with no problem. To me it sounds like I'm missing some virtual SCSI filesets. Does anyone have any suggestions? |
|
#2
| ||||
| ||||
Did you restore the mksysb with a NIM server? If so restore that mksysb and also have an lpp_source for 5.3 TL5 SP3 (or higher) so that any necessary device drivers can be loaded. If not then you need to load ALL the device drivers onto the existing LPAR and then take the mksysb. People need to remember that an mksysb is intended to be restored or the original or identical hardware to where the mksysb was originally installed. As such rehosting this way is not necessarily the best way to do things. Often a fresh install of the OS and configuring it is a better solution. Of course you've documented everything that is configured on the original box - and yoiu want to keep those settings the same on the rehosted one, don't you ;-).
__________________ Ross Mather, IBM AIX IT Specialist. That said anything I say here is my own opinion and not anything that you can ever hold against IBM. Ohhh and don't forget that I make mistakes too.... |
|
#3
| ||||
| ||||
Yes I did restore using a NIM server and had the LPPSource. That's probably why the install portion went fine. I was looking at my plan B which is rebuilding a clean system. I do document all of the system specific items via a shellscript. My "clean" mksysb installs and boots with no problem on this server. |
|
#4
| ||||
| ||||
Hi When restoring images from servers on older HW remember that on Power3 there's no LPAR, no CPU sharing and no Virtualization, so there's no driver in the mksysb to manage such things. What i do is to modify my LPAR with dedicated CPU and in your specific case i would install first on a physical disks, then apply all virtualization stuff to the LPAR (Apply the full TL) and then take another mksysb and then install in the LPAR based on VIOS SCSI server adapter. Hope this helps
__________________ cd3lgad0p |
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| |