Thanks Andreas - replies below.
On 11/16/2016 11:14 AM, Andreas Klauer wrote:
On Wed, Nov 16, 2016 at 09:04:29AM +0000, Alexander Shenkin wrote:
I'm getting a 'No space left on device error'. Any thoughts?
It's smaller by 4096 bytes, that's probably not a problem.
ddrescue seems to have failed to copy 128K of data,
but that's probably not a big problem either.
Regarding the failed copy, where do you see the 128k? I see that there
was an errsize of 65536 bytes, but I'm not sure how to tell if that was
ever able to be read by ddrescue... i suspect ddrescue ran out of disk
space before it was able to retry those unreadable bytes...
Won't both issues be problematic (i.e. unread data + out of space)? I
believe the last drive partition is the one that participates in the
array that gets mounted as "/"... so, can't really just throw that one
away...
https://i.imgur.com/SMdCo12.png
Your problem is something else:
Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Sector size (logical/physical): 512 bytes / 512 bytes
Disklabel type: gpt
Disk /dev/sdc: 2.7 TiB, 3000592977920 bytes, 732566645 sectors
Sector size (logical/physical): 4096 bytes / 4096 bytes
Disklabel type: dos
The physical sector size is different.
Unfortunately GPT partition scheme still depends on sector size and is
inherently incompatible when dd(rescue)'d to a drive with different size.
In theory it would be possible to ignore this, i.e. interpret GPT
correctly on a 4K sector drive even if it was created for a 512b drive,
or vice versa, but Linux is quite strict about standards in this case.
(If Linux was smarter it would work in Linux but fail for Windows...)
Anyway, you'll have to fixer-upper your GPT partition tables to 4K.
gdisk has an expert -> recovery section that might be able to do so
automagically, or you could just manually recreate with the correct
_byte_ offsets (sector offset will be different).
So, just trying to understand the issue here... The original (failed)
drive had 512 byte sectors... Does that mean that ddrescue has copied
the 512 partition tables to my 4k drive, and hence I just need to fix
the partition table on the new 4k drive?
Your partitions are all MiB aligned so there are no alignment issues.
Once the partition table is fixed you should be able to proceed normally.
Regards
Andreas Klauer
--
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
