Also was fĂĽr eine CPU die hat, ist meines Erachtens erstmal egal.
Im Bezug auf mdadm sagt die man-page (auszugsweise):
--metadata=
Declare the style of RAID metadata (superblock) to be used. The default is 1.2 for --create, and to guess for other operations. The default can be overridden by setting the metadata value for the CREATE keyword in mdadm.conf.
Options are:
0, 0.90
Use the original 0.90 format superblock. This format limits arrays to 28 component devices and limits component devices of levels 1 and greater to 2 terabytes. It is also possible for there to be confusion about whether the superblock applies to a whole device or just the last partition, if that partition starts on a 64K boundary.
1, 1.0, 1.1, 1.2 default
Use the new version-1 format superblock. This has fewer restrictions. It can easily be moved between hosts with different endian-ness, and a recovery operation can be checkpointed and restarted. The different sub-versions store the superblock at different locations on the device, either at the end (for 1.0), at the start (for 1.1) or 4K from the start (for 1.2). "1" is equivalent to "1.0". "default" is equivalent to "1.2".
und:
-U, --update=
Update the superblock on each device while assembling the array. The argument given to this flag can be one of sparc2.2, summaries, uuid, name, homehost, resync, byteorder, devicesize, no-bitmap, or super-minor.
[...]
The byteorder option allows arrays to be moved between machines with different byte-order. When assembling such an array for the first time after a move, giving --update=byteorder will cause mdadm to expect superblocks to have their byteorder reversed, and will correct that order before assembling the array. This is only valid with original (Version 0.90) superblocks.
Also, wenn es nur um endian-awareness geht, sollte das auch so gehen, ebenso mit der byte-order. Allerdings scheinen sich die Optionen gegenseitig auszuschließen. Einen Versuch wäre es aber wert, bevor die Krämpfe in einer VM anfangen.
Das Problem zwischen QUEMU und VBox wurde ĂĽbrigens neulich
hier aufgedeckt. Es scheint sich besonders dann drastisch zu manifestieren, wenn man QUEMU wieder deinstalliert.