[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Issue on resizing domU root partition
Hello everybody, I need to resize a domU root partition, running EXT3, but I'm facing some issue with pygrub, I supose. My domU root disk is on a LV device. Before resizing, it looks like this: [root@master]# fdisk -lu /dev/vgVMs/lvDbserver Disk /dev/vgVMs/lvDbserver: 7516 MB, 7516192768 bytes 255 heads, 63 sectors/track, 913 cylinders, total 14680064 sectors Units = setores of 1 * 512 = 512 bytes Dispositivo Boot Start End Blocks Id System /dev/vgVMs/lvDbserver1 128 4016249 2008061 82 Linux swap / Solaris /dev/vgVMs/lvDbserver2 * 4016256 14667344 5325544+ 83 Linux (Note that partitions start blocks are not default because of RAID alignment requisites.) Ok, from the dom0 (and with domU turned off, off course) I extend the LV, delete the second partition and recreate it with the same starting block but bigger than before, matching the new LV size. After this, it will look like this: [root@master Agent]# fdisk -lu /dev/vgVMs/lvDbserver Disk /dev/vgVMs/lvDbserver: 16.1 GB, 16106127360 bytes 255 heads, 63 sectors/track, 1958 cylinders, total 31457280 sectors Units = setores of 1 * 512 = 512 bytes Dispositivo Boot Start End Blocks Id System /dev/vgVMs/lvDbserver1 128 4016249 2008061 82 Linux swap / Solaris /dev/vgVMs/lvDbserver2 4016256 31455269 13719507 83 Linux Ok, still from domU, I resize the second partition with resize2fs (adding devices with kpartx -a before, and after removing mappings with kpartx -d). Resizing suceeds ok, but when I try to start the domU, it fails with that following message: Traceback (most recent call last): File "/usr/bin/pygrub", line 658, in ? fs = fsimage.open(file, get_fs_offset(file)) File "/usr/bin/pygrub", line 117, in get_fs_offset offset += get_solaris_slice(file, offset) File "/usr/bin/pygrub", line 80, in get_solaris_slice raise RuntimeError, "Invalid disklabel magic" RuntimeError: Invalid disklabel magic No handlers could be found for logger "xend" Error: Boot loader didn't return any data! (I know that filesystem has not been corrupted, because I can even mount it sucesfull on dom0, if I try.) What could be wrong? Would be that a pygrub bug, or am I missing something? I'm using Red Hat Enterprise here, with Xen hypervisor 3.1.2, and kernel 2.6.18. I would be very thankful if anybody could help me. Thank you. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |