On Sat, Jun 20, 2015 at 1:37 PM, Theodore Ts'o <ty...@mit.edu> wrote: > > Or the disk could just be 6+ years old, and it's just too old. If I > were you I would just replace the hard drives and be done with it.
That's probably going to happen in the near future, yes. >> In this case, that would have been cfdisk as of roughly 9 months ago, >> and I *think* the problem was it didn't know what to do with an MD >> device. Notice how the outer partitions start at offset 2048 but the >> inner partitions start at offset 63? > > Or this was just the case where cfdisk didn't want to mess with a > prexisting partition table, and the original partition table as > shipped from the manufacturer was Windows XP compatible. It's the partition table *inside* the MD container that's misaligned, so that can't be it. I'd like to make certain that there isn't an fsck or kernel bug here. Is it possible for you to construct a similarly-misaligned partition within an MD-RAID0 array, unpack the skeleton image I sent you into that partition, and then try to reproduce my original fsck report on that? Do you need more information from me first? zw -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
