| 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
| ||||
| ||||
Hi, p550 (9133-55A, 8x300GB, RAID enablement) I created a RAID5 Array of 7 hdisks (each 300GB), which results in 1 disk of ~1.65TB. Now the installation of the VIO Server using the shipped CD fails, because it's booting a 32BitKernel and thus not support disks of this size. When I redefine the array and start with only 3 hdisks (which is minimum), installation of the VIO (mksysb) is fine. But there's no re-striping and no parity when adding the remaining disks in a second step. What am I doing wrong here ? Can I somehow use a 64Bit Kernel for restoring the mksysb from the VIO cd ? Obviously the SW doesnt fit to the HW .Thansks for hints !! Lars |
|
#2
| ||||
| ||||
mmh ... Installing the VIO on a small hdisk and adding the remaining hdisks to the array is not good, too. Since there's no pvresize command available in the vio server restricted shell, the system dont recognize the new (larger) size of the disk .... Any ideas on how to get the new disk size ??? Lars |
|
#3
| ||||
| ||||
Hmmm Nice question. IBM should be excomunited for this. hehe. What about if you actually install VIOS on a smaller disk and once installed you can change the kernel by applying the same procedure used for AIX systems. Then take a backup and restore on tape, destroy and create your 1.6 GB RAID, and install from this backup. I know is not a very elegant solution, but it can work. Hope this helps
__________________ cd3lgad0p |
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| how to add a virtual disk to a lpar? | Melih | IBM PowerVM Editions | 6 | May 24th, 2007 09:16 |
| Vio Client san disk allocation | datamax | IBM PowerVM Editions | 2 | February 21st, 2007 03:43 |
| VIO Disk Performance | gbarth | IBM PowerVM Editions | 7 | January 8th, 2007 16:42 |
| Lost SAN connection/0514-038 Error loading kernel extension | paulmann | pSeries - System p | 3 | December 14th, 2006 18:54 |