Md3000 Error
Contents |
Enclosure Troubleshooting a Damaged Enclosure Troubleshooting Power Supplies Troubleshooting Enclosure Cooling Problems Troubleshooting SAS Physical Disks Troubleshooting Enclosure Connections Hard Controller Failures and Lockdown smcli commands dell Conditions Safety First—For You and Your Enclosure To perform certain
Md3000i Manual
procedures in this document, you must work inside the enclosure. While working inside the enclosure,
Dell Powervault Modular Disk Storage Manager User Guide
do not attempt to perform service except as explained in this guide and elsewhere in your documentation. CAUTION: Only trained service technicians are authorized to remove
Md Storage Manager
the enclosure cover and access any of the components inside the enclosure. Before performing any procedure, see your Product Information Guide for complete information about safety precautions, working inside the enclosure and protecting against electrostatic discharge. Start-Up Routine Look and listen during the enclosure's start-up routine for the indications described in dell support Table5-1. For a description of the front- and back-panel indicators, see "About Your System". Table 5-1. Start-Up Routine Indications Look/listen for: Action Alert messages. See your storage management documentation. An unfamiliar constant scraping or grinding sound when you access a physical disk. See "Getting Help". NOTE: At least two physical disks must be installed in the enclosure. Troubleshooting External Connections Loose or improperly connected cables and bent pins are the most likely source of problems. Ensure that all external cables are securely attached to the external connectors on your system and that none of the connectors are damaged. See "Back-Panel Indicators and Features" for the back-panel connectors on your enclosure. Troubleshooting a Wet Enclosure ProblemLiquid spilled on the enclosure.Excessive humidity. Action CAUTION: Only trained service technicians are authorized to remove the enclosure cover and access any of the components inside the enclosure. Before performing any procedure, see your Product Information Gu
Dell Join the Community! Creating your account only takes a few minutes. Join Now After replacing the battery backup units the array went back to optimal until I realized that I had lost all the iSCSI volumes in disk manager. I know that couldn't be right so after further inspection I realized that it looks like the iSCSI network configuration was messed up. From Dell Modular Disk Storage Manager under the iSCSI tab i select to 'Configure iSCSI Host Ports" and get this error. "Unable to obtain current iSCSI network settings for RAID controller module 1 port 1 and module 1 port 0." Since everything was working fine, http://ftp.respmech.com/pub/MD3000/en/MD3000_Owners_Manual/trouble.htm with the exception of "Failed battery" error in MDSM. Anyone point me in a direction, will gladly postmore info if I knew what would help. Event logs show "Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data." This is what leads me to believe it perhaps just a setting lost in replacing the battery unit. Thanks for reading this far, Wes Reply https://community.spiceworks.com/topic/391862-error-after-replacing-raid-controller-battery-backup-units-in-md3000i Subscribe RELATED TOPICS: CalDigit HDPro RAID - Enter battery backup mode Raid controller battery raid mirror and a battery backup unit 18 Replies Thai Pepper OP Galen in Laguna Oct 7, 2013 at 11:45 UTC If you changed the battery with the power being off, then you probably lost the configuration the battery was keeping. 0 Habanero OP Paul Mek Oct 7, 2013 at 11:51 UTC Galen in Laguna wrote: If you changed the battery with the power being off, then you probably lost the configuration the battery was keeping. Ive changed the battery with the unit powered off before and its just fine. 0 Habanero OP Paul Mek Oct 7, 2013 at 11:53 UTC Did you plug the nics back in to the same cables on the host? 0 Poblano OP Wes Spruell Oct 8, 2013 at 12:01 UTC The battery had already failed prior to replacing it. I followed the steps - open Modular Disk Storage Manager (MDSM) - click on the Support tab - select Manage Raid Controller Modules - click on Redistribute Virtual Disks - move preferred paths for all on "0" over to "1" - place the RAID controller module offline - remove the RAID controller module - remove the screws holding the battery cov
Case and Cooling Fetish CPU & Motherboard Technologia Mobile Computing Outpost Networking Matrix Other Hardware Agora Classifieds Ars DIY Forum (Name TBD!) Operating Systems & Software Battlefront Microsoft OS & http://arstechnica.com/civis/viewtopic.php?t=60962 Software Colloquium Linux Kung Fu Windows Technical Mojo Distributed Computing Arcana Macintoshian Achaia Programmer's Symposium The Server Room Ars Lykaion Gaming, Extra Strength Caplets The Lounge The Soap Box The Boardroom The Observatory Ars Help & Feedback Ars Subscription Member Areas Image Galleries MD3000i complaining about VDisk not in prefered path 8 posts Fulgan Ars Tribunus Angusticlavius et Subscriptor Tribus: Swiss iguanas storage manager Registered: Jun 28, 2000Posts: 7508 Posted: Tue Jul 21, 2009 3:25 am Hello folks,I'm a bit puzzeled about this one: We have 3 dell 1950 servers running vSphere 4 connected to a Dell MD3000i iSCSI SAN. We have full redundant path (2 independent switches dedicated to the SAN, 2 controllers in the fabric, each with two NIC and each server has two NIC). That setup worked for more than a year now.Yesterday, around noon, the ESX smcli commands dell stopped seeing the second controller completely: all path that where active on it fell back to the other controller and that's when the SAN started complaining about the VDisk not being on the preferred path.No error is reported on the SAN except that path problem. The ESX servers now only see only 2 of the 4 possible targets (the ones on the first controller). From the ESX servers, I can ping all the interfaces on both SAN controller.To me, symptoms indicates a dead controller: if the issue was on the switches, I'd still see both controllers, just one NIC on each. I doubt the same failure would affect the 3 EXS machines all by themselves. Trouble is: the SAN itself insists the controller itself is perfect working order.Recently, we made the following changes (a couple of weeks ago):- Moved to vSphere 4 (from ESX 3.5).- Enabled jumbo frames on the SAN network (i.e. In ESX, on the switches and on the SAN NICs).I've opened a trouble ticket by Dell and they should come back to me during the afternoon, but I'd love to hear what the hive mind has to say about that issue.Thanks Cool Modine Ars Tribunus Angusticlavius Tribus: A ratio of jump to vertical leaping ability Registered: Dec 24, 1999Posts: 7396 Posted: Tue Jul 21, 2009 5:51 am quote:To me, symptoms in