Tag Info

Hot answers tagged

15

Your system I assume is still up, so the best thing to do is make an immediate backup, dump the disks/array, rebuild, and restore from the backup. Bad blocks don't always mean your backups are also bad. If you haven't experienced any performance problems or damaged files, then your backups should still be complete enough to finish a restore. To test, take ...


11

Just recently I read an article by one of Godaddy's engineers about this very topic: Learning to Deal with Learning On their hardware (Dell PERC cards) battery learning cycle happens every 90 days, but no way to know when exactly it'll happen, ie during peak or off-peak hours. They talked about different solutions: Outright disable Battery Learning. ...


9

S.M.A.R.T. is not the final word in disk or storage monitoring!! It's a component, but modern RAID controllers use it along with other methods to determine drive and array health. I'm assuming this is a PERC controller in a Dell PowerEdge server. The normal Linux-friendly approach to health monitoring of Dell hardware is to install the Dell OMSA agents for ...


8

Right this instant, do the following: Stop rotating backups or deleting old ones for this system. You want to keep all of the backups you currently have. Take a full backup of the server. Hopefully the disks are still good enough that your data is intact, and you won't encounter any problems running the new full backup. Then scrap those disks, and ...


8

It does not look like it does... From HDD Support for 2.5TB, 3TB Drives and Beyond (Article is recent - Mar 31 2011, 5:21 PM EDT): IMPORTANT NOTE! Only the Dell H700 and H800 currently support the 3TB drives (H200 will add support later this year) - NO earlier controllers, such as the PERC4/5/6, SAS5/6 (or ANY other Dell controller not mentioned) have ...


8

You have one drive in a RAID that is misbehaving, and producing occasional errors? Sounds like a hardware problem, and one that is likely to get worse. You should consider replacing the drive. Yes, it's expensive, but how much is your time worth, and how bad would it be if the entire drive went south at an inopportune moment?


7

The short answer is yes, that's the level of performance you should expect to see from the H200. The long answer: The H200 is the old SAS 6iR with SATA 6Gb/s support. It doesn't have the usual features you'd see on a RAID card (battery backup unit, onboard caching, RAID5/6 support). The cache determines how fast your RAID array is (along w/ the # of ...


7

The Dell PERC H310 controller does not have the ability to use write cache. H310 — Entry hardware RAID controller. Provides entry-level performance with no cache. RAID5 functionality with modest performance. Your write performance will suffer as a result of this. This is a very bad controller for ESXi or virtualization using local disks.


7

You should acquire new hardware and install a modern operating system like Windows Server 2012 R2 and then migrate your applications and data to it. Windows Server 2003 is quickly approaching end of support and you should be focusing your effort on getting off of it, not on rigging it to keep on running.


6

The Dell PowerEdge R320 is a lower-end 1U rackmount server. Your storage options within that chassis are either 8 x 2.5" small-form-factor disks or 4 x 3.5" large-form-factor drives. Due to the price point of this server, it's commonly spec'd with in the 4 x 3.5" disk combination... Sidenote: one of the things that's happened in server storage recently is ...


6

This: Fault Tolerant Shared PERC 8 Card Configuration — [...] The default cache policy for virtual disks created in this configuration is write-through. In this mode, write completion information is returned to the host after the data is written to the disk. is the ultimate performance killer. Change the cache policy to write-back if it is ...


6

Since you are using a Dell PERC controller, you should also use the appropriate tool for managing it - Dell provides the OpenManage Server Administrator Storage Management for exactly this purpose. It will help you identify and replace the failed disk of your array.


6

PERCs have generally been fairly good about this for me. I don't have a PERC 4e/Di handy, but the general procedure has always been (for me): Remove all disks from the recipient server and reset all controller configurations to factory default (no virtual disks defined). Insert the donor disks to the recipient server. If at all possible, insert the donor ...


6

You want to grab a Dell Server Install CD from somewhere like here, easier than fooling around with F6 and floppy disks. Just boot from the CD and it will walk you through the process, load drivers (including drivers for other hardware like your NIC, etc) and give you a functional machine at the end of it.


6

You should be using the LifeCycle Controller to install the OS, which will include the appropriate drivers for your RAID controller.


5

Part of me says to check with Dell... Specifically to see what they're selling as an option part for these servers and whether they've validated the use of 6TB disks. I'm assuming you wouldn't be using Dell-sourced drives, though... In terms of compatibility, 2TB was the big issue for many controllers. Since the H700 has confirmed large-drive support ...


5

I wouldn't use consumer SSD drives. While they will work, I think the better approach is to find a cost-effective SAS (not SATA) SSD. The Dell OEM drives are Sandisk Lightning (expensive, perform OK, last forever). A more affordable option is the Sandisk Optimus line (not expensive, perform great, endurance unknown)... See both at: ...


5

You need the 'Generation 2' firmware upgrade - HERE's a link.


5

You didn't mention which "latest release" you used. I just tried this and it seems to work fine now. The Dell H700 is using this chipset: # lspci -v | grep LSI 01:00.0 RAID bus controller: LSI Logic / Symbios Logic LSI MegaSAS 9260 (rev 05) Visit the support section of LSI's site, the 9260 is part of the "MegaRAID Value Line". That took me to MegaRAID ...


5

No. The 4KB sector-size on 3TB drives is not supported by the Perc 6/i.


5

In my experience, it's like putting more than 4 GB or RAM into a 32 bit OS, in that the additional space is simply not usable. There is one major difference though, in that if you have support through Dell, and you use unsupported hardware (like a 3 TB drive), you will be invalidating your support, and may very well be told "no" if you need to call in about ...


5

Yes, I believe either your controller or the raid backplane is bad. But I think the controller is the culprit. Can you look up the firmware version of the RAID controller (not to be confused with the system BIOS, which you should also check) and compare to what is available on Dell's site? You may find the version is quite old and that critical issues have ...


5

It's actually rather common, and the main reason it is frequently advised to buy hard drives from different batches in a single RAID set. Identical batches often have identical flaws or thresholds. Also, failures don't always result from just simple old age of the drive, they can also be triggered by minimal power surges, unexpected load for a few minutes, ...


5

It's not possible to say precisely what the odds of X drives going out in Y amount of time are, but it is safe to say that drive failures are not completely independent, as commonly assumed. Multiple disk failures in the same array within close temporal proximity are actually a fairly common occurrence. Less than a month ago, we had 4 drives fail over ...


4

I don't believe there's space for what you want if you wish to use 3.5" disks - have you considered using 2.5" disks instead? if you did you could easily fit what you want into the machine and generally a 2.5" 10krpm disk will perform roughly on par with a 3.5" 15krpm disk - especially when fronted by a nice bit of SSD cache as you wish. I use this solution ...


4

I have experienced the exact same performance issue with a VRTX with the Dual SPERC8. What I have done to work around this at the moment is, change the dual config to a single config. This way I am able to use write-back, which performs way way better. The exact steps: Remove the second SPERC 8 controller Remove the second expander Re-cable the internal ...


4

The answers provided by Grant and Nathan C are great in regards to how you should proceed in handling backups/restoring, and addressing data integrity. Here's some clearer detail on how to handle the RAID set when it comes time to recreate the virtual disk and restore from backup: Verify that you have a good backup of the data Delete the existing virtual ...


4

You can see the SMART status of the disks with the smartctl command and it's -d argument. For example, to see the first disk in the array: # smartctl -a /dev/sda -d sat+megaraid,00 smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-358.6.2.el6.x86_64] (local build) Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net === START OF ...


4

This error corresponds to the cache module on the controller. At this point, you need to probably replace the RAM or the actual PERC controller. This should be standard warranty work.


4

RAID 1 is a mirror. The fact that when you drill down into the virtual disk, you only see Physical Disk 0:0 means that Disk 0:1 has failed and is showing as removed. You could try removing the faulty disk (should be showing with an orange light) and re-inserting it - this sometimes kicks off a rebuild but even if that works you should probably consider ...



Only top voted, non community-wiki answers of a minimum length are eligible