2011/8/4 Paul Menzel <pm.debian@xxxxxxxxxxxxxx>:
[…]
> After having grown `/dev/sda2` using `fdisk /dev/sda2` with mdadm not
> running I forgot to grow the RAID1 and probably overwrote the md
> metadata (0.90) or made it unavaible because it was not at the end of
> the partition anymore after growing the physical and logical LVM
> volumes and filesystems.
>
> # blkid
> /dev/sda1: UUID="fb7f3dc5-d183-cab6-1212-31201a2207b9"
> TYPE="linux_raid_member"
> /dev/sda2: UUID="cb6681b4-4dda-4548-8c59-3d9838de9c22"
> TYPE="crypto_LUKS" # In `fdisk` I had set it to »Linux raid
> autodetect« (0xfd) though.
It looks like `fdisk` did a bad/incomplete job. `sfdisk` shows a warning(?).
--- 8< --- sfdisk output --- >8 ---
% sudo sfdisk -l /dev/sda
Disk /dev/sda: 243201 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 61 62- 497983+ fd Linux raid autodetect
/dev/sda2 62 243200 243139 1953014017+ fd Linux raid autodetect
end: (c,h,s) expected (1023,254,63) found (512,254,63)
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
% sudo sfdisk -V /dev/sda
partition 2: end: (c,h,s) expected (1023,254,63) found (512,254,63)
/dev/sda: OK
--- 8< --- sfdisk output --- >8 ---
Could that be related? Tomorrow I will look into this.
[…]
Thanks,
Paul
> [1] http://www.saout.de/pipermail/dm-crypt/2011-August/001857.html
> [2] http://www.hermann-uwe.de/blog/resizing-a-dm-crypt-lvm-ext3-partition
> [3] http://grml.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
