Am Mittwoch, 28. Juni 2017, 13:55:09 schrieb Adam Thompson: > If you search the archives, I had a very similar problem a few months ago. > There is already an option to mdadm to update a v1 superblock in the wrong > byte order. It just wasn't obvious when looking at the mdadm man page. > Going from memory, search for "byte order" instead of "endian" to find the > option. -Adam If you refer to --update=byteorder, the documentation says it is only for v0.90 metadata. Also it's only the super_offset field so far, other fields like magic are correct. Greetings, Eike
Attachment:
signature.asc
Description: This is a digitally signed message part.
