Thank you. I already learned a lot. Your command only shows data for all of the 3 disks. Out of curiosity i used strings /dev/loop42 | grep mp3 and many of my songs showed up - is that a good sign? Just tried the 5 orders like a,b,c a,c,b and so on and receive the same output about mount: wrong fs type, bad option, bad superblock on /dev/md42 and fsck.ext2: Superblock invalid, trying backup blocks.... Then used photorec in all 5 combinations of disks for several minutes without a single file found. Is it possible that i have to keep something else in mind, while assembling the raid? I expected at least some files with photorec when the raid was assembled in the right order. 2016-09-21 21:00 GMT+02:00 Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>: > On Wed, Sep 21, 2016 at 08:31:23PM +0200, Simon Becks wrote: >> Maybe i just assembled it in the wrong order? > > Yes, or maybe the superblock was overwritten by XFS after all. > > You could check what's at offset 1M for each disk. > > losetup --find --show --read-only --offset=$((2048*512)) /the/disk > file -s /dev/loop42 > > If the superblock was still intact it should say ext4 or whatever > your filesystem was for at least one of them. > > You can also try this for the disk you removed 2 month ago. > > If that is not the case and fsck with backup superblock also > is not successful then you'll have to see if you find anything > valid in the raw data. > > 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
