General
cancel
Showing results for 
Search instead for 
Did you mean: 

vitual machine wont boot after increasing root disk size

 
Highlighted
Trusted Contributor

vitual machine wont boot after increasing root disk size

HP-UX 11iv2 on Itanium Blade
I have a VM client which will not boot after I increased the size of its root disk in SAM on the host.
Is there a special way to increase this? or can it not be done?

Getting the following on startup:

Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 2039 MB 2039 MB 2039 MB
Kernel : 2039 MB 2039 MB 2039 MB
User : 1695 MB 1475 MB 1481 MB
-------------------------------------------------------------------------

Loaded ACPI revision 2.0 tables.
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 7.
NOTICE: mod_fs_reg: Cannot retrieve configured loading phase from KRS for module
: cifs. Setting to load at INIT

Boot device's HP-UX HW path is: 0/0/2/0.1.0
iether0: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/0/0
iether1: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/1/0

System Console is on the Built-In Serial Interface
WARNING: Open failed on device 0x1f001002 (error 0x5).
WARNING: Can not read LVM BOOT information (lvmrec).
WARNING: Open failed on device 0x1f001002 (error 0x5).
WARNING: Can not read LVM BOOT information (lvmrec).
WARNING: Open failed on device 0x1f001002 (error 0x5).
WARNING: Can not read LVM BOOT information (BDRA).
WARNING: SWAP device 0xfffffffe is a non-LVM partition, disallowed on LVM disk.
WARNING: SWAP device 0xfffffffe has been deconfigured (set to 0xffffffff).
WARNING: Logical volume for Dump expected but not found.
Swap device table: (start & size given in 512-byte blocks)
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
mountfs:opend

Calling function e00000000103f700 for Shutdown State 8 type 0x2

Stored message buffer up to panic:
Found adjacent data tr. Growing size. 0x338e000 -> 0x738e000.
Pinned PDK malloc pool: base: 0xe000000100c72000 size=118328K
Loaded ACPI revision 2.0 tables.
MMIO on this platform supports Write Coalescing.

MFS is defined: base= 0xe000000100c72000 size= 1428 KB


Unpinned PDK malloc pool: base: 0xe000000108000000 size=81920K
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 7.
NOTICE: mod_fs_reg: Cannot retrieve configured loading phase from KRS for module
: cifs. Setting to load at INIT

0 cec_gen
0/0 gh2p
0/0/0/0 iether
0/0/1/0 iether
Initializing the Ultra320 SCSI Controller at 0/0/2/0. Controller firmware versio
n is 00.00.00.00
0/0/2/0 mpt
0/0/3/0 legacyio
0/0/3/0/1 asio0
0/1 gh2p
0/2 gh2p
0/3 gh2p
0/4 gh2p
0/5 gh2p
0/6 gh2p
0/7 gh2p
120 processor
250 pdh
250/0 ipmi
250/1 acpi_node
0/0/2/0.1 tgt
0/0/2/0.1.0 sdisk
0/0/2/0.15 tgt
0/0/2/0.15.0 sctl
Boot device's HP-UX HW path is: 0/0/2/0.1.0
iether0: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/0/0
iether1: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/1/0

System Console is on the Built-In Serial Interface
WARNING: Open failed on device 0x1f001002 (error 0x5).
WARNING: Can not read LVM BOOT information (lvmrec).
WARNING: Open failed on device 0x1f001002 (error 0x5).
WARNING: Can not read LVM BOOT information (lvmrec).
WARNING: Open failed on device 0x1f001002 (error 0x5).
WARNING: Can not read LVM BOOT information (BDRA).
WARNING: SWAP device 0xfffffffe is a non-LVM partition, disallowed on LVM disk.
WARNING: SWAP device 0xfffffffe has been deconfigured (set to 0xffffffff).
WARNING: Logical volume for Dump expected but not found.
Swap device table: (start & size given in 512-byte blocks)
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
mountfs:opend

System Panic:

panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
4 REPLIES 4
Highlighted
Outstanding Contributor

Re: vitual machine wont boot after increasing root disk size

What do you mean when you say you increased the root disk size? The physical disk size? The size of the file system (which FS?)? What?


Pete

Pete
Highlighted
Trusted Contributor

Re: vitual machine wont boot after increasing root disk size

Hi Pete,

On the VM host, there is a lvol assigned to the VM in question as its root disk.
I increased the size of this lvol on the vm host. Now the VM will not boot with the errors above.
Highlighted
Outstanding Contributor

Re: vitual machine wont boot after increasing root disk size

Hmmm, must be a peculiarity of Virtual Machines, I guess. I've never used them, myself.

So, the VM gets one single LV assigned to it as it's root disk? How does that LV get partitioned into separate File Systems? I'll go do some reading on VM - because I'm obviously wasting your time with my ignorant questions, Allan.

Good luck.


Pete

Pete
Highlighted
Trusted Contributor

Re: vitual machine wont boot after increasing root disk size

thanks Pete,

I got the following reply from HP Support in case anyone else has the same issue:
.........................................
Extending a Logical Volume Backing Store Corrupts the Guest
On the VM Host, do not extend a logical volume (LVM or VxVM) used as a backing store for a
guest root disk. If you do this, the guest panics on its next reboot with the following error:
System panic: all VFS_MOUNTROOTs failed: Need DRIVERS.
In this case, the guest root device has been corrupted. You must reinstall the guest operating
system.
For a logical volume used as a backing store for a guest data disk, you can extend the volume
after removing it from the guest using the hpvmmodify command. After extending the volume,
use the hpvmmodify command to add the volume to the guest. Do not modify a logical volume
used as a backing store without first removing it from the guest.
After you extend the logical volume, use operating system commands on the guest to extend its
file system.