Insight Control for Linux
cancel
Showing results for 
Search instead for 
Did you mean: 

Deploy corrupts partioning information for non-OS partition

Holger Zierold
Occasional Contributor

Deploy corrupts partioning information for non-OS partition

Hello,
we have created images using v2.01 and deploy the images back to the same server to fall back to a different state. Partioning information for the non-OS partitions is somehow modified. Details further down.

During deployment the we get the following message regarding the partitions:
com.google.gwt.user.client.rpc.InvocationException: The call failed on the server

The log says:
ERROR [[/]] Exception while dispatching incoming RPC call com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract com.hp.mx.icle.taskchain.partition.client.Storage com.hp.mx.icle.taskchain.partition.client.WizardService.getPartitionSchemeFromRepoId(java.lang.String)' threw an unexpected exception: java.lang.NullPointerException

I've attached the partitioning / image information (xml).

When pressing next ignoring the message we run into a problem with the non-OS partitions:

Disk setup
- 2 disks @ RAID 1 for OS
- 2 disks @ RAID 0 for data
- 1 disk @ RAID 0 unused, no partition is created.

# fdisk -l

Disk /dev/cciss/c0d0: 73.3 GB, 73372631040 bytes
255 heads, 63 sectors/track, 8920 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 13 104391 83 Linux
/dev/cciss/c0d0p2 14 5750 46082452+ 83 Linux
/dev/cciss/c0d0p3 5751 6260 4096575 82 Linux swap / Solaris
/dev/cciss/c0d0p4 6261 8920 21366450 5 Extended
/dev/cciss/c0d0p5 6261 6515 2048256 83 Linux
/dev/cciss/c0d0p6 6516 6646 1052226 83 Linux
/dev/cciss/c0d0p7 6647 8920 18265873+ 83 Linux

Disk /dev/cciss/c0d1: 73.3 GB, 73372631040 bytes
255 heads, 32 sectors/track, 17562 cylinders
Units = cylinders of 8160 * 512 = 4177920 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d1p1 1 17562 71652944 83 Linux

Disk /dev/cciss/c0d2: 73.3 GB, 73372631040 bytes
255 heads, 32 sectors/track, 17562 cylinders
Units = cylinders of 8160 * 512 = 4177920 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d2p1 1 17562 71652944 83 Linux

In details, for c0d1:

# fdisk /dev/cciss/c0d1

The number of cylinders for this disk is set to 17562.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): x

Expert command (m for help): p

Disk /dev/cciss/c0d1: 255 heads, 32 sectors, 17562 cylinders

Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 00 1 1 0 254 32 1023 32 143305888 83
2 00 0 0 0 0 0 0 0 0 00
3 00 0 0 0 0 0 0 0 0 00
4 00 0 0 0 0 0 0 0 0 00

After restoring the ICE image

# fdisk -l

Disk /dev/cciss/c0d0: 73.3 GB, 73372631040 bytes
255 heads, 63 sectors/track, 8920 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 13 104391 83 Linux
/dev/cciss/c0d0p2 14 5751 46085605+ 83 Linux
/dev/cciss/c0d0p3 5751 6261 4096575 82 Linux swap / Solaris
/dev/cciss/c0d0p4 6261 8921 21366357 5 Extended
/dev/cciss/c0d0p5 6261 6516 2048256 83 Linux
/dev/cciss/c0d0p6 6516 6647 1052226 83 Linux
/dev/cciss/c0d0p7 6647 8921 18265873+ 83 Linux

Disk /dev/cciss/c0d1: 73.3 GB, 73372631040 bytes
255 heads, 63 sectors/track, 8920 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d1p1 1 8921 71652928+ 83 Linux

Disk /dev/cciss/c0d2: 73.3 GB, 73372631040 bytes
255 heads, 63 sectors/track, 8920 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d2p1 1 8921 71652928+ 83 Linux

In details, for c0d1:

# fdisk /dev/cciss/c0d1

The number of cylinders for this disk is set to 8920.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): x

Expert command (m for help): p

Disk /dev/cciss/c0d1: 255 heads, 63 sectors, 8920 cylinders

Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 00 1 1 0 254 63 1023 63 143305857 83
2 00 0 0 0 0 0 0 0 0 00
3 00 0 0 0 0 0 0 0 0 00
4 00 0 0 0 0 0 0 0 0 00


==> Additional INFO

-> Disk Setup (1) - details
# hpacucli controller serialnumber= physicaldrive all show

Smart Array P400 in Slot 1

array A

physicaldrive 2I:1:1 (port 2I:box 1:bay 1, SAS, 72 GB, OK)
physicaldrive 2I:1:2 (port 2I:box 1:bay 2, SAS, 72 GB, OK)

array B

physicaldrive 2I:1:3 (port 2I:box 1:bay 3, SAS, 72 GB, OK)

array C

physicaldrive 1I:1:5 (port 1I:box 1:bay 5, SAS, 72 GB, OK)

array D

physicaldrive 2I:1:4 (port 2I:box 1:bay 4, SAS, 72 GB, OK)

-> Disk Setup (2) - details
# hpacucli controller serialnumber=PAFGK0M9SWF5F9 physicaldrive all show

Smart Array P400 in Slot 1

array A

physicaldrive 2I:1:1 (port 2I:box 1:bay 1, SAS, 72 GB, OK)
physicaldrive 2I:1:2 (port 2I:box 1:bay 2, SAS, 72 GB, OK)

array B

physicaldrive 2I:1:3 (port 2I:box 1:bay 3, SAS, 72 GB, OK)
physicaldrive 2I:1:4 (port 2I:box 1:bay 4, SAS, 72 GB, OK)

array C

physicaldrive 1I:1:5 (port 1I:box 1:bay 5, SAS, 72 GB, OK)
2 REPLIES
Steven E. Protter
Exalted Contributor

Re: Deploy corrupts partioning information for non-OS partition

Shalom,

It could be a problem with the actual OS, but I suspect a possible bad sector on the one of the disks, or other hardware problem.

I would boot the server into diagnostic mode and check out all the tests for disks or controller problems.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Rigoberto Corujo
Frequent Advisor

Re: Deploy corrupts partioning information for non-OS partition

Hi Holger,

Can you please open a case for this issue?

Thanks.

Rigoberto