Re: Recover array after I panicked

["Patrik Dahlström" <risca@powerlamerz.org>]

On 04/24/2017 11:04 PM, Phil Turmel wrote:
> On 04/23/2017 08:15 AM, Patrik Dahlström wrote:
>>
>>
>> On 04/23/2017 02:11 PM, Wols Lists wrote:
>>> On 23/04/17 12:58, Roman Mamedov wrote:
>>>> On Sun, 23 Apr 2017 12:36:24 +0100
>>>> Wols Lists <antlists@youngman.org.uk> wrote:
>>>>
>>>>> And, as the raid wiki tells you, download lspci and run that
>>>>
>>>> Maybe you meant lsdrv. https://github.com/pturmel/lsdrv
>>>>
>>> Sorry, yes I did ... (too many ls_xxx commands :-)
>> Ok, I had to patch lsdrv a bit to make it run. Diff:
> 
> Thanks for the patch.  Could you elaborate a bit on the errors you
> received so I can reproduce and document this fully?
Sure. It started out with this error:
$ ./lsdrv
Traceback (most recent call last):
  File "./lsdrv", line 413, in <module>
    probe_block('/sys/block/'+x)
  File "./lsdrv", line 389, in probe_block
    blk.FS = "MD %s (%s/%s)%s %s" % (blk.array.md.LEVEL, blk.slave.slot,
blk.array.md.raid_disks, peers, blk.slave.state)
AttributeError: 'NoneType' object has no attribute 'LEVEL'

So I added an if statement for blk.array.md.
Next, I got this error:
$ ./lsdrv
Traceback (most recent call last):
  File "./lsdrv", line 414, in <module>
    probe_block('/sys/block/'+x)
  File "./lsdrv", line 406, in probe_block
    blk.FS += " '%s'" % blk.ID_FS_LABEL
TypeError: unsupported operand type(s) for +=: 'NoneType' and 'str'

That's what the other 2 if statements are for. I don't claim to know the
root cause of the errors, I've simply worked around them.

> 
> Also, do you have some large files (media files, perhaps) that you know
> are in your array but you have a copy in hand?  If so, you could use the
> findHash script in my github account to map how that file is laid out on
> your array's devices.  Since large media files tend to be contiguous,
> such a map would definitively show your chunk size and device order.
I'll take a look. I definitely have some large continuous files on this
array.
> 
> It would also show if your data offsets are consistent among the member
> drives (but not the absolute value of the offset).
> 
> Phil
> 
>