I've added some instrumentation and made my printf a log entry. dmraid -rd now shows:
DEBUG: not isw at 1000204884992 DEBUG: isw metadata found at 1000203803136 from probe at 1000203803136 DEBUG: not isw at 1000204884992 DEBUG: isw metadata found at 1000203803136 from probe at 1000203803136 Is the output. Concretely, isw formats appear to be meant to have a signature 1K back (2 sectors) from end of drive. This can have an extended data block which can point to other areas etc etc. However, for my drive the signature is simply not found (DEBUG: not isw at 1000204884992), which means it doesn't move onto doing extended block processing or whatever. I've also updated the patch to be (somewhat) less hardcoded - it now jumps 2115 sectors back so may work for other people with 'no RAID Drives found'. My changes add no compile warnings. ** Attachment added: "patch to detect on my hardware" http://launchpadlibrarian.net/26492397/17_fix_isw_raid_detection_1TB.patch ** Attachment removed: "first version, just hard codes my sector in, but demonstrates the shape of the patch." http://launchpadlibrarian.net/26351050/current.patch -- intel isw raid metadata at odd offset https://bugs.launchpad.net/bugs/372170 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
