2

I have a Dell PowerEdge 2950 with DAS storage attached (MD1000) I rebooted the server to apply window updates (win2008), on restart BIOS detected a VirtualDisk was missing and wanted me to continue or raid Config and import conf .... I continued on.

After startup, there was storage missing... a volume (RAID5). I opened Dell OpenManage and checked the status on the storage. Everything was fine. No failures, nothing degraded. There were no warnings, even no external hdd warning lights on the any drives. The missing virtualdisk is fine and "ready".

All physical disks for the missing raid array are marked as "foreign" EXCEPT for ONE disk. Which was the dedicated hot spare.

EDIT: Possible Answer: So I have more than one disk showing Foreign, I should go to Bios and Import the Foreign Config? There are 2 virtualdisks on that raid controller. If I import the Foreign Config will this effect the second working virtualdisk? Will changing the state from "foreign" to online lose my data?

Windows Event Logs right after the windows update reboot, only warning and errors that I could find...

  1. The current driver version 2.20.00.64 (percsas) is older than the required driver version 2.24.00.64 (percsas) for a controller of model 0x1F0C: Controller 0 (PERC 6/i Integrated)
  2. The current driver version 2.20.00.64 (percsas) is older than the required driver version 2.24.00.64 (percsas) for a controller of model 0x1F01: Controller 1 (PERC 5/E Adapter)
  3. The controller battery needs to be replaced.: Battery 0 Controller 1
  4. Device failed: Battery 0 Controller 1
  5. Controller event log: VDs missing at boot: 00: Controller 1 (PERC 5/E Adapter)
  6. Controller event log: Battery needs replacement - SOH Bad: Controller 1 (PERC 5/E Adapter)
  7. Controller event log: Current capacity of the battery is below threshold: Controller 1 (PERC 5/E Adapter)
  8. Controller event log: BBU disabled; changing WB virtual disks to WT: Controller 1 (PERC 5/E Adapter)

RESULT/ANSWER: I did the "import" and it failed, unknown error. No side effects with the import. VirtualDisk is still "foreign".

Logman
  • 445
  • 2
  • 16
  • 28
  • Import failed, but "no problems"? Meaning all is well and the failure message was erroneous, or do you mean no *new* problems & you're still in the same boat? – JimNim Jan 26 '15 at 07:25
  • I am still in the same boat, VD is still "foreign". I will be trying a "retag". – Logman Jan 26 '15 at 14:50
  • Any luck with that retag? – JimNim Jan 30 '15 at 05:02
  • I ordered a new perc card (perc6) to replace the perc5. I will be replacing it this weekend. It would be the same process with the replacement correct? Just use "import" after replacing the card, and it should pick up all virtualdisks correct? – Logman Jan 30 '15 at 13:15
  • 1
    Yes, I would use the same exact process with a new replacement card. Try importing foreign config - if that doesn't work out, then attempt the "retag" process mentioned, recreating the exact same configuration as before (without initializing the disks). – JimNim Feb 02 '15 at 17:18

2 Answers2

1

Your best best would be to call Dell, I personally don't have enough experience with the Dell perc to confidently tell you "yeah just do that". If the systems out of warranty, they still may help you since its a question and not a HW replacement.

Other than that, me, yes I would import the foriegn config, but I'm probably a little braver than you :)

Eric C. Singer
  • 2,329
  • 16
  • 17
  • I called Dell, it had no warranty and tech person was not an "engineer" so he could not advise me. THough he said if I wanted an hw engineer it would be $299 for the consult. But if it was a software issue then it would be something else... – Logman Jan 22 '15 at 18:28
  • Well... you know if its important, it should be under warranty. IMO, 300 bucks isn't that steep of a price to pay if you're worried about your data. If you have a backup, just try importing the config, you don't have much to lose. If you screw up your system, just restore the data. – Eric C. Singer Jan 22 '15 at 20:27
1

If all drives but 1 for a VD are foreign, you should import. This should NOT affect the config on the remaining drives of the 2nd VD. Still, don't trust the RAID card 100% - make a note of exactly which drives are participating in the 2nd VD in case a "retag" does become necessary.

Recreating the config on the problem drives is possible too if the import fails, though you'll want help from support to be sure that doesn't get done wrong & data overwritten.

Retag = delete the VD, recreate (from the PERC BIOS, not inside the OS), and do NOT initialize. If data isn't seen at that point, consider restoring from backup.

Source: firsthand experience, 3rd tier support for this type of Dell system, specializing in storage.

JimNim
  • 2,776
  • 13
  • 24