Control: tag -1 moreinfo

On Tue, 2013-01-08 at 16:04 +0100, varacanero wrote:
> Package: installation-reports
> Severity: important
> Tags: d-i
> 
> 
> 
> -- Package-specific info:
> 
> Boot method: network
> Image version:
> http://ftp.us.debian.org/debian/dists/squeeze/main/installer-amd64/
> Date: Mon, 07 Jan 2013 19:50:00 -0800
> 
> Machine: X9SCL/X9SCM mb, 16GB mem, Intel(R) Xeon(R) CPU E3-1265L V2 @
> 2.50GHz, amd64 system, kvm-qemu guest installation
> 
> Partitions: see below
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:           [O]
> Detect network card:    [O]
> Configure network:      [O]
> Detect CD:              [ ]
> Load installer modules: [O]
> Detect hard drives:     [O]
> Partition hard drives:  [E]
> Install base system:    [O]
> Clock/timezone setup:   [O]
> User/password setup:    [O]
> Install tasks:          [O]
> Install boot loader:    [O]
> Overall install:        [O]
> 
> Comments/Problems:
> 
> On the kvm host, i installed a guest system with virt-install (0.500.3-2):
> 
> lvcreate -L 1.2G -n debian_squeeze_baseimage vg_toad0
> 
> virt-install --name debian-squeeze-baseimage --ram 512 --os-type linux
> --os-variant debiansqueeze --virt-type kvm --disk
> path=/dev/vg_toad0/debian_squeeze_baseimage
> --location=http://ftp.us.debian.org/debian/dists/squeeze/main/installer-amd64/
> --nographics -x"DEBIAN_FRONTEND=text console=ttyS0"
> 
> I need a guest with just one (root) partition, no swap, because i want
> to easily grow the partition after later cloning. So i chose manual
> partitioning, created one partition for /, and went on.
> Installation succeeded, guest did boot well in kvm, however, the
> partition looks broken with sfdisk:
>
> sfdisk -l /dev/mapper/vg_toad0-debian_squeeze_baseimage
> 
> Disk /dev/mapper/vg_toad0-debian_squeeze_baseimage: 157 cylinders, 255
> heads, 63 sectors/track
> Warning: The partition table looks like it was made
>   for C/H/S=*/238/17 (instead of 157/255/63).
> For this listing I'll assume that geometry.
>
> Units = cylinders of 2071552 bytes, blocks of 1024 bytes, counting from 0
> 
>    Device Boot Start     End   #cyls    #blocks   Id  System
> /dev/mapper/vg_toad0-debian_squeeze_baseimage1          0+    623-
> 623-   1259520   83  Linux
>                 start: (c,h,s) expected (0,120,9) found (0,32,33)
>                 end: (c,h,s) expected (623,25,5) found (156,237,17)
[...]

We try to use 1 MiB alignment for partitions, not cylinder alignment.
This is important for performance on 4K-sectored hard disks, RAID arrays
and flash drives.  Using the geometry that sfdisk reported but decided
to ignore (157/255/63), the start is at 32 * 63 + 33 - 1 = 2048 sectors
= 1 MiB exactly and the end is at (156 * 255 + 237) * 63 + 17 = 2521088
sectors = 1231 MiB exactly.  So this all looks good.

The various programs you've used to inspect the image probably should be
trusting the claimed geometry and should not be confused by 1 MiB
alignment.

A raw dump of the partition table:
    dd if=/dev/mapper/vg_toad0-debian_squeeze_baseimage bs=512 count=1 | od 
-tx1 -Ax
would help to confirm where the error lies.

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to