Comment 11 for bug 372170
Revision history for this message
| Robert Collins (lifeless) wrote Re: intel isw raid metadata at odd offset | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
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.