Hello, Just want to double check my facts before I do something wrong here. I discovered a computer trying to read past the end of it's disk. attempt to access beyond end of device sdq: rw=0, want=488022554, limit=488017920 fdisk reports: Disk /dev/sdq: 249.8 GB, 249865175040 bytes 255 heads, 63 sectors/track, 30377 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000d7193 Device Boot Start End Blocks Id System /dev/sdq1 1 30 240943+ 83 Linux /dev/sdq2 31 30378 243770310 8e Linux LVM My assumption is that specifying end=30378 is invalid for a disk that only has 30377 cylinders. Have I got this correct? Another identical computer does have end=30377, so I suspect this one got it right. Also wondering why dmesg reports 488017920 blocks but fdisk reports 240943+243770310 block size (and on good system reports 240943+243762277 blocks) - is there a difference in block sizes here? /dev/sdq2 is LVM, and has three partitions for root, swap, and var. --- Physical volume --- PV Name /dev/sdq2 PV Size 232.48 GB / not usable 966.00 KB Allocatable yes PE Size (KByte) 4096 Total PE 59514 Free PE 50403 Allocated PE 9111 PV UUID 58fU6l-MLlo-h5Ar-n9jx-0poC-axdS-VoAmND How do I recover the LVM partition with minimum disruption? Maybe use of pvresize? Before or after fixing the partition size? How can I check if that part of the disk has a LV allocated on it? Thanks -- Brian May <brian@microcomaustralia.com.au>