Hal Pomeranz on Nostr: Here's a wacky Linux factoid-- If you look at the RAID UUID in the superblock on disk ...

Here's a wacky Linux factoid--

If you look at the RAID UUID in the superblock on disk it's in little-endian byte order:

Linux Software RAID version 1.2 (1) UUID=cccdcc9b:f86a0b98:98df7949:8f2f7bb8 name=localhost:boot level=1 disks=2

But if you look at the metadata for active volumes in the /run/mdadm/map file, the UUIDs are in big-endian (network byte order) format:

md126 1.2 9bcccdcc:980b6af8:4979df98:b87b2f8f /dev/md/localhost:boot

I spent some time today being confused by why the UUIDs weren't matching before I realized what was going on.

#Linux #RAID #DFIR