LSI foreign import failed "Unknown Error"

sannyasi

Prominent
Jul 12, 2017
2
0
510
I've got an old LSI sas raid10 system from someone else I'm attempting to online.
All drive LED's are green
Foreign config is found
All drives within the config are online
Yet import fails with "unknown error".

As seen in the image below the config shows a raid 10 with 10pd's (dell powerVault MD has 14 drives in total... I'm assuming these 4 extra were for HS volumes, they show up as "ready")

I'm not sure why "Span 0 (Missing)" is there since if there are only 10 drives used, they are present from ID 3-12?

Any ideas what could be done to regain access to this data?
Thanks

raidSetup.jpg
 
Solution
I think it may be showing you 10 PDs just because that's how many it sees right now, not because that's how many it thinks are in the array. Its picking up that Disk Group 0 should have a span 0, and its not seeing either disk from that span. Whether this is a firmware bug, or someone played around with the disks t-shooting before you got it, who knows.

At the end of the day, if the controller isn't seeing the foreign config on all the disks, it can't import the array.

sannyasi

Prominent
Jul 12, 2017
2
0
510


I honestly have no idea how many drives were being used.
I thought 12 could have been possible since it has the missing span0, however the foreign config states PD count as 10.
So is it culling 2 drives from the config and incorrectly reporting 10 drives in the config???? IDK.

If it is the drives are there (+2 more since there are 14 drives total), however they are marked as "Ready" and not part of the foreign config.
I don't know how to force them to rejoin the config, without importing it first, and as stated I can't import the config.
 

marko55

Honorable
Nov 29, 2015
800
0
11,660
I think it may be showing you 10 PDs just because that's how many it sees right now, not because that's how many it thinks are in the array. Its picking up that Disk Group 0 should have a span 0, and its not seeing either disk from that span. Whether this is a firmware bug, or someone played around with the disks t-shooting before you got it, who knows.

At the end of the day, if the controller isn't seeing the foreign config on all the disks, it can't import the array.
 
Solution