On Wed, May 03 2017, Alfred Matthews wrote: > Sorry to disappear for a bit. > > Of necessity I've migrated to another working system and I'm in Arch. > Utility here is fsck.hfs as opposed to hpfsck. I'd like to post that > output. I wonder if they are the same thing, or completely different. > > mdadm --build /dev/md0 --level=0 -n2 --chunk=8K /dev/sdb2 /dev/sdc2 > > works, then, > > fsck.hfs -v /dev/md0 > *** Checking volume MDB > drSigWord = 0xffffffff > drCrDate = Mon Feb 6 06:28:15 2040 > drLsMod = Mon Feb 6 06:28:15 2040 > drAtrb = BUSY | HLOCKED | UMOUNTED | BBSPARED | BVINCONSIS | > COPYPROT | SLOCKED > drNmFls = 65535 > drVBMSt = 65535 > drAllocPtr = 65535 > drNmAlBlks = 65535 > drAlBlkSiz = 4294967295 > drClpSiz = 4294967295 > drAlBlSt = 65535 > drNxtCNID = 4294967295 > drFreeBks = 65535 > drVN = "" > drVolBkUp = Mon Feb 6 06:28:15 2040 > drVSeqNum = 4294967295 > drWrCnt = 4294967295 > drXTClpSiz = 4294967295 > drCTClpSiz = 4294967295 > drNmRtDirs = 65535 > drFilCnt = 4294967295 > drDirCnt = 4294967295 > drEmbedSigWord = 0xffff > drEmbedExtent = 65535[65535..131069] > drXTFlSize = 4294967295 > drXTExtRec = > 65535[65535..131069]+65535[65535..131069]+65535[65535..131069] > drCTFlSize = 4294967295 > drCTExtRec = > 65535[65535..131069]+65535[65535..131069]+65535[65535..131069] > Bad volume signature (0xffffffff); should be 0x4244. Fix? y > Volume creation date is in the future (Mon Feb 6 06:28:15 2040). Fix? y > Volume last modify date is in the future (Mon Feb 6 06:28:15 2040). Fix? y > Volume bitmap starts at unusual location (1), not 3. Fix? y > *** Checking volume structure > *** Checking extents overflow B*-tree > > It's possible that I was unwise in accepting the changes from fsck. Definitely possible. Given how many of the numbers listed above are 0xffff or 0xffffffff, it is unlikely that the tool found anything useful. > >>> >>> How is your C coding? You could >>> apt-get source hfsplus >>> and hack the code and try to build it yourself.... >>> > > Still fine. By now not clear if this is what's needed. I don't think I can be of further help, sorry. NeilBrown > > Al > -- > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html