We have two MD1000 SAS storage arrays hooked up to a Dell R710 server. During a large file transfer (40+ GB) to one of the MD1000 arrays it will slow way down to a crawl. It looks as if it is slowing down at the same spot every time we attempt to transfer a file. The other MD1000 that is hooked to the server has no problem with file transfers. This only happens when we copy to the MD1000. Copying from the MD1000 works as it should. Smaller file transfer copy fine. The Dell Sever Manager shows no errors with any of the hardware. PERC card batteries do not show low or bad. Any suggestions appreciated!
↧
MD1000 slows way down on large file transfers
↧
Need Win 7 Driver for PERC 9 h330 Mini
I need to install Win 7 64 on a Precision Rack 7910 workstation. The installation disk for SP1 doesn't have a driver for the RAID controller. The download from the 7910 support page is an exe file that isn't recognized and won't let me extract the driver to copy it. I haven't been able to find one that I can put on a thumb drive and that the Windows installation routine will recognize as a valid driver.
I've tried searching the Dell site and Googling for it, also tried to find it on another 7910 running Win 10.
Can you help me to find it or suggest a work-around?
↧
↧
Degraded Hard drive
Hi,
We have poweredge R910 that is configured with 4 drive in RAID 5 and 2 drives in RAID 1 and othere 2 Drives Also in RAID 1.
Now when I check the Manament server I can see that one of the disk of one of the RAID 1 is showing Degraded and I can see that one of the disks has red X so we have to replace this drive.
if I understand it correctly we must replace the drive with exact the same drive.
Question:
the current drive has order numer of 400-22925 we can not find with the same order numer any drive so I did search the Dell website and find the same drive but has the order numer 400-22931
can we use this drive to replace the defect one? also I think the only thing we must do is without shuting down the server just remove the defect drive and replace it with new one is this also correct?
defect drive:
Physical Disks
ID | 0:0:6 |
Status | Critical |
Name | Physical Disk 0:0:6 |
State | Failed |
Bus Protocol | SAS |
Media | HDD |
Revision | DE09 |
T10 PI Capable | No |
Certified | Yes |
Capacity | 837.75GB |
Used RAID Disk Space | 837.75GB |
Available RAID Disk Space | 0.00GB |
Hot Spare | No |
Vendor ID | DELL(tm) |
Product ID | AL13SEB900 |
Serial No. | 54U0A0RHFRD2 |
Part Number | PH0RC34W7557145V8F73A03 |
Negotiated Speed | 6.00 Gbps |
Capable Speed | 6.00 Gbps |
Sector Size | 512B |
Manufacture Day | 07 |
Manufacture Week | 22 |
Manufacture Year | 2014 |
SAS Address | 500003958840DE4A |
↧
H310 Mini MessageID: STOR0210, Message: SCSI sense data (Sense key: B Sense code: 4B Sense qualifier: 3) - problem moves around
R720xd with Perc H310 Mini.18 Drives
16 of the drives are unraided.
2 drives are Raid1 (they are the last two drives on the bus bays 16 and 17)
O/S is Red Hat 6.7
OMSA has started populating the messages file with these
Server_Administrator: 4530 2095 - Storage Service Severity: Informational, Category: Storage, MessageID: STOR0210, Message: SCSI sense data (Sense key: B Sense code: 4B Sense qualifier: 3) received from Physical Disk 0:1:12 on Controller 0 at Connector 0.
Which disk reports the error changes.
On a totally idle system I wrote a loop to exersise the drives.
Against each drive on the system it executes:
drives=$( lvmdiskscan | grep sd | awk '{printf "%s ",$1}' )
for dx in $drives
do
echo Exercising $dx | tee -a /var/log/messages
lsscsi 2>&1 | grep $( echo $dx | cut -b1-8 ) | tee -a /var/log/messages
dd if=$dx of=/dev/null ***=1024 count=1000000
echo
done
echo Exercising done | tee -a /var/log/messages
Synopsis: It reads from disks, logs which disk its working on to /var/log/messages. In parallel the OMSA software is logging any storage events to /var/log/messages.
Output looks like this:
Exercising /dev/sda1
[0:0:0:0] disk SEAGATE ST91000640SS AS0B /dev/sda
Feb 5 13:11:13 Server_Administrator: 4530 2095 - Storage Service Severity: Informational, Category: Storage, MessageID: STOR0210, Message: SCSI sense data (Sense key: B Sense code: 4B Sense qualifier: 3) received from Physical Disk 0:1:0 on Controller 0 at Connector 0.
Exercising /dev/sdq1
[0:2:0:0] disk DELL PERC H310 2.12 /dev/sdq
Exercising /dev/sdq2
[0:2:0:0] disk DELL PERC H310 2.12 /dev/sdq
Exercising /dev/sdb1
[0:0:1:0] disk SEAGATE ST91000640SS AS0B /dev/sdb
Exercising /dev/sdc1
[0:0:2:0] disk SEAGATE ST91000640SS AS0B /dev/sdc
Exercising /dev/sdd1
[0:0:3:0] disk SEAGATE ST91000640SS AS0B /dev/sdd
Exercising /dev/sde1
[0:0:4:0] disk SEAGATE ST91000640SS AS0B /dev/sde
Exercising /dev/sdf1
[0:0:5:0] disk SEAGATE ST91000640SS AS0B /dev/sdf
Exercising /dev/sdg1
[0:0:6:0] disk SEAGATE ST91000640SS AS0B /dev/sdg
Exercising /dev/sdh1
[0:0:7:0] disk SEAGATE ST91000640SS AS0B /dev/sdh
Feb 5 13:12:17 Server_Administrator: 4530 2095 - Storage Service Severity: Informational, Category: Storage, MessageID: STOR0210, Message: SCSI sense data (Sense key: B Sense code: 4B Sense qualifier: 3) received from Physical Disk 0:1:7 on Controller 0 at Connector 0.
Feb 5 13:12:21 Server_Administrator: 4530 2095 - Storage Service Severity: Informational, Category: Storage, MessageID: STOR0210, Message: SCSI sense data (Sense key: B Sense code: 4B Sense qualifier: 3) received from Physical Disk 0:1:7 on Controller 0 at Connector 0.
Exercising /dev/sdi1
[0:0:8:0] disk SEAGATE ST91000640SS AS0B /dev/sdi
Feb 5 13:12:31 Server_Administrator: 4530 2095 - Storage Service Severity: Informational, Category: Storage, MessageID: STOR0210, Message: SCSI sense data (Sense key: B Sense code: 4B Sense qualifier: 3) received from Physical Disk 0:1:8 on Controller 0 at Connector 0.
Exercising /dev/sdj1
[0:0:9:0] disk SEAGATE ST91000640SS AS0B /dev/sdj
Exercising /dev/sdk1
[0:0:10:0] disk SEAGATE ST91000640SS AS0B /dev/sdk
Exercising /dev/sdl1
[0:0:11:0] disk SEAGATE ST91000640SS AS0B /dev/sdl
Exercising /dev/sdm1
[0:0:12:0] disk SEAGATE ST91000640SS AS0B /dev/sdm
Exercising /dev/sdn1
[0:0:13:0] disk SEAGATE ST91000640SS AS0B /dev/sdn
Exercising /dev/sdo1
[0:0:14:0] disk SEAGATE ST91000640SS AS0B /dev/sdo
Exercising /dev/sdp1
[0:0:15:0] disk SEAGATE ST91000640SS AS0B /dev/sdp
In this particular run the drive in bays 0,7 and 8 complained. On other runs it may be other drives. It may also be a varying number of drives that flag the issue.
I've updated all the firmware available via the lifecycle controller by pointing it at ftp.dell.com
All the drives are dell certified.
OMSA is at 8.2
Tried downgrading to OMSA 7.4 - but still received same messages.
Sometimes the key qualifier value is 2 other times it is 3.
In the month of January over 17,000 messages were generated to /var/log/messages.
Mixed in with these are also 83 messages in the format:
Storage Service Controller event log: Unexpected sense: Encl PD 20 Path 5e4ae0208df0bb00, CDB: 1c 01 a0 00 04 00, Sense: 5/24/00: Controller 0 (PERC H310 Mini)
The 5/24/0 messages do not occur often and are deemed (per googling) to be informational in nature and not of realy concern. I'm more concerned about the msgs shown above. I have reports when the end users are allowed to use the box that it lags behind all other boxes doing the same work. The other boxes have identical configs and do not generates these messages.
Any thoughts/advice would be much appreciated.
↧
Dell SC 2020 - Failed to re-balance ports
Hi ALL
I have some problem
but
I can not find the cause of the problem!!
zoning set
↧
↧
NX4 Error
Hi All,
following to power problems, our servers do not have access to the most NX4 storage.
Checking by SSH (on Control Station), by running the command nas_checkup i get this results:
[root@control-station bin]# nas_checkup
Check Version: 5.6.45.5
Check Command: /nas/bin/nas_checkup
Check Log : /nas/log/checkup-run.160216-093544.log
-------------------------------------Checks-------------------------------------
Control Station: Checking if NBS clients are started....................... Fail
Control Station: Checking if NBS configuration exists...................... Pass
Control Station: Checking if NBS devices are accessible.................... Fail
Control Station: Checking if NBS service is started........................ Fail
Control Station: Checking if NAS partitions are mounted.................... Pass
Data Movers : Checking status........................................... Pass
--------------------------------------------------------------------------------
One or more error-level checks have failed. Follow the instructions
below to correct the problem and try again.
-------------------------------------Errors-------------------------------------
Control Station: Check if NBS clients are started
Symptom: NBS clients (nd-clnt 5 6) are not started
Action : Contact EMC Customer Service and refer to EMC Knowledgebase
emc146016. Include this log with your support request.
Control Station: Check if NBS devices are accessible
Symptom: Failed NBS (nd-clnt processes) devices access check
NOTE: Several checks depend on NBS device access to run. These checks
were not run.
Action :
1. This may occur if NBS is not configured correctly or if the NBS
service is not started. Look in the "Checks" section to see if the
following checks passed:
* Control Station: Check if NBS configuration exists
* Control Station: Check if NBS service is started
* Control Station: Check if NBS clients are started
If either of those checks did not pass, follow the instructions for
that check to correct the problem, then rerun "nas_checkup" to verify
that the NBS devices can now be accessed.
2. This may also occur if Data Movers are powered down or pulled out.
If you are on the primary Control Station, look in the "Checks"
section to see if the following check passed:
* Data Movers: Check status
If this check failed, follow its instructions to correct the
problem, then rerun "nas_checkup" to verify that the NBS devices can
now be accessed.
3. If the problem persists, escalate this issue through your support
organization. Provide this output and any errors or output that
occurred running the commands in this procedure in the escalation.
Control Station: Check if NBS service is started
Symptom: NBS (nd-clnt processes) service is not (or not fully) started
Action : Use the command "/sbin/service nbs start" to restart the NBS
service or reboot the Control Station.
Please can you help us?
I wish i could talk to the customer also paid.
Best Regards
Renato
↧
Raid Tiering?
Dear All,
how does RAID Tiering work, especially in SC 2000 series? Is data moved between different RAID levels? Is it really physically moved or is there any abstraction layer? Is there any other name for this technique?
Somewhere I found a powerpoint presentation that suggests that data was held simultaneously in RAID level 10 for write and level 5 or 6 for read access. Is this possible? Is there any caching technique? When is determined what "hot" data is?
Is tiering reasonable when there are SAS disks only, no SSDs (or SATA as lower level)?
Thank you in advance.
- Chris
↧
Add Disk Array to R620 with MD1200
I have a R620 server running Redhat Enterprise 6.4 connecting a MD1200 disk array with a H800 card
the disk usage on the MD1200 disk array will be full soon.
Can we add another MD1200 disk array to expand the disk storage ?
We may need further 30TB. It seems the MD1200 could not provide enough disk space. What other module of disk array can we add ?
Thank you
Macus
↧
EMC CX4-120, failed disk
Hi,
I would replace a failed disk on my EMC Storage CX4-120
It's out of warrenty, service tag <ADMIN NOTE: Service tag removed per privacy policy>
How can we proceed?
Thanks
Claudio
↧
↧
MD3000i Degraded wide port becomes failed
Hi,
We have an out of warranty MD3000i that has been running fine for years, but has recently begun throwing event code 1707, 1706 and 4011 errors every few months, and leaving us with Virtual Disk Not On Preferred Path showing in the MDM client. Previously we checked all cabling, redistributed the disks back to the preferred path and the error goes away for several weeks. Are we looking at a failing controller or could this be a network component issue?
↧
PowerVault Logs report failed RAID Module - but all appears well.
Recieved an e-mail from our PowerVault MD3220i yesterday showing the following message:
Host ID: Out-of-Band
Event Error Code: 1710
Event occurred: Mar 15, 2016 2:54:45 PM
Event Message: RAID Controller Module wide port has gone to failed state Event Priority: Critical Component Type: RAID Controller Module Component Location: Enclosure 0, Slot 1
However, looking at the management console it shows everything is running and clear states: 'Storage Array Status is optimal'
No loss of service was reported during this event, everything working ok and the two servers that make up the cluster using this SAN as shared storage are all running as they should.
The event log shows one error related to this e-mail, followed by a number of informational events concerning things like Physical Disk Timed Out, Initiators failed to register, etc but I also recieved an e-mail saying 'Needs attention condition resolved' (although the order was a bit odd).
It would appear all is ok, the RAID controller had a bit of a 'wobbly' but seems to have resolved itself however I am concerned this has happed.
I've taken a Support Data Package in preperation to send to Dell, but I'm not in the office until next week and I can't do a support call via e-mail for this according to the website but have to call.
Any thoughts? Should I be worried? Appreciate if a Dell Support Rep could contact me.
Pete
↧
Manual for eLatitude e6410 with ssd drive
Hello all. I found a manual that I needed a couple month ago. I lost the url or the download that I did. Now I am wondering if anyone knows where I can download this manual again. It had pictures showing how to install the ssd drive plus it show how to take the computer to get down where the ssd drive was. Hope someone can help me *** this. Cateddy (Chuck)
PS the computer is a latitude e6410 laptop
↧
Win 10 not recognizing 3 tb hard drive on OptiPlex 7010 intel rapid storage utility does ??
Win 10 not recognizing 3 tb hard drive on OptiPlex 7010 intel rapid storage utility does ??
↧
↧
Installing Windows 7 64Bit on new SSD
Hey Guys,
i'm just getting a headdache. Windows installation doesn't find the installed ssd. I created a new VD in the PERC H310 menu and everything looks fine but windows setup doesn't see the device. Also not, when i choose the driver folder from the CD. I than downloaded some drivers from the dell homepage and choosed the windows setup to look on the usb device but... nothing works, windows doesn't "see" the ssd.
Changed vom ATA to AHCI, tested, back to ATA, tested ... how can i solve this problem?
↧
Re-install MDSM for MD300
I have an MD3000 connected to a PE2950 running Unix, and the PC that had the MDSM was removed from the network and disposed of (without my knowledge...). Can I install the MDSM on a new PC (windows XP VM or 7 pro VM) and access the working MD3000 without changing the configuration? I know one drive has failed and need to replace and configure.
Thanks,
↧
NX3230 Storage mirror
HI Everyone,
First of all well done, what a great forum.
I currently have a system with 2 x PowerEdge R630 and 2 x NX3230 NAS servers, running windows server 2012 R2 and windows storage server respectively.
I am planning to have the two power edge servers on a failover cluster and use iSCSI to map drives on the NX3230's .
However I need my NX3230's to be mirrored. Can you kindly indicate if this is possible? Will I need 3rd party software for this? What is the best way to go here?
Thanks,
Warren Gauci
↧
Storage on the C2665dnf printer
I want to dispose of my C2665dnf printer and need to know if it has storage on it that I need to worry about.
↧
↧
Re: Unable to back up on Drive E
O/S MS Windows 7
C Drive 250 GB
E Drive 1 TB
F Drive 75 GB
Hi Guys
I was wondering if you could help me before I head down to the local Dell service centre I use a 17 inch Alien all has been going well up to now , Since April for some reason it will no longer makes a back up from C drive to E Drive . All I was getting was E drive was full but from looking at Drive E there was 763 GB Free so it made no sense any way I delete all the old back ups plus I ran CC cleaning plus I checked E Drive for any problems but nothing found after scanning the whole drive .
I did delete all backups from last years plus I ran CC clean to remove all the old temp files and left on Drive E 763 GB so there is tons of space however it still wont let me back up But there is 763.GB available so it makes no sense ? All I get when I attempt to back up the C drive is error code 0x81000019 .
I did delete all backups from last years plus I ran CC clean to remove all the old temp files and left on Drive E 763 GB so there is tons of space however it still wont let me back up But there is 763.GB available so it makes no sense ? All I get when I attempt to back up the C drive is error code 0x81000019 .
I suppose some program has changed something in the registry so that it is no longer possible to use the M/S software to backup, whether maliciously or other, one never knows.
↧
DR4100 set up SNMP
Greetings community,
Please could someone point me in the right direction in terms of setting up SNMP on a DR4100. I downloaded the Administrators Guide and searched for SNMP in the doc, and it didnt give me what I wanted.
Is there another doc I must get this from? I checked the forums and came across an earlier post where the Dell admin had posted a link, but this was removed from the original post.
I understand that SNMP queries need to be done via port 199, and when I nmap my DR4100 it shows this port is not open.
Thanks
↧
md3000i Degraded Physical Disk Channel
Hi,
I have an md3000i with attached md1000. We had a HDD fail which the hot spare took over with no down time or issues.
Now I replaced the failed drive and it was put back into the array. Once that completed now I'm showing Degraded Physical Disk Channel on channel 0,1 (I'm assuming that's the LUN number since LUNs 0 and 1 are part of the RAID group with the failed disk).
Also it seems to have created a Virtual Disk Not On Preferred Path issue. This md3000i has dual controllers and the ESX hosts are all multipathed but not sure why all of this is coming around after replacing a failed disk.
Thanks,
Josh.
↧