Skip to main content

raid - Use of 2.5" Laptop Drives in a Server?

itemprop="text">

We're acquiring several 1U servers
with (8) 2.5" drive slots. Although we can use either SATA or SAS, there is a large
price variance as soon as you order 16 or 24 of these drives, so we are looking at the
2.5" SATA interfaced drives.



I know that Seagate
and WD both make "Enterprise" 2.5" drives, which are fast (10k and 15k RPM), but are
also fairly expensive.



What issues would we run
into using 7200RPM 2.5" non-Enterprise drives? By the way, these will be hooked up to a
RAID controller (though, they may just be configured as JBOD). These drives are almost
$100 lower in price, per drive.


class="post-text" itemprop="text">
class="normal">Answer



In
addition to the problems above, you may have additional issue running these drives in
RAID configuration due to the lack of TLER. (If you are considering a model without.)
This quote references desktops and the RAID Edition drives but I imagine the same to be
true in the 2.5" line if you substitute in "notebook" and "enterprise" or "SAS" where
applicable.






Western Digital manufactures desktop edition hard drives and RAID Edition hard
drives. Each type of hard drive is designed to work specifically in either a desktop
computer environment or a demanding enterprise environment.




If you install and use a desktop edition hard drive connected to a
RAID controller, the drive may not work correctly unless jointly qualified by an
enterprise OEM. This is caused by the normal error recovery procedure that a desktop
edition hard drive uses.



When an error is
found on a desktop edition hard drive, the drive will enter into a deep recovery cycle
to attempt to repair the error, recover the data from the problematic area, and then
reallocate a dedicated area to replace the problematic area. This process can take up to
2 minutes depending on the severity of the issue. Most RAID controllers allow a very
short amount of time for a hard drive to recover from an error. If a hard drive takes
too long to complete this process, the drive will be dropped from the RAID array. Most
RAID controllers allow from 7 to 15 seconds for error recovery before dropping a hard
drive from an array. Western Digital does not recommend installing desktop edition hard
drives in an enterprise environment (on a RAID controller).




Western Digital RAID edition hard drives have a feature called TLER
(Time Limited Error Recovery) which stops the hard drive from entering into a deep
recovery cycle. The hard drive will only spend 7 seconds to attempt to recover. This
means that the hard drive will not be dropped from a RAID array. Though TLER is designed
for RAID environments, it is fully compatible and will not be detrimental when used in
non-RAID environments.





Comments

Popular posts from this blog

iLO 3 Firmware Update (HP Proliant DL380 G7)

The iLO web interface allows me to upload a .bin file ( Obtain the firmware image (.bin) file from the Online ROM Flash Component for HP Integrated Lights-Out. ) The iLO web interface redirects me to a page in the HP support website ( http://www.hp.com/go/iLO ) where I am supposed to find this .bin firmware, but no luck for me. The support website is a mess and very slow, badly categorized and generally unusable. Where can I find this .bin file? The only related link I am able to find asks me about my server operating system (what does this have to do with the iLO?!) and lets me download an .iso with no .bin file And also a related question: what is the latest iLO 3 version? (for Proliant DL380 G7, not sure if the iLO is tied to the server model)

linux - Awstats - outputting stats for merged Access_logs only producing stats for one server's log

I've been attempting this for two weeks and I've accessed countless number of sites on this issue and it seems there is something I'm not getting here and I'm at a lost. I manged to figure out how to merge logs from two servers together. (Taking care to only merge the matching domains together) The logs from the first server span from 15 Dec 2012 to 8 April 2014 The logs from the second server span from 2 Mar 2014 to 9 April 2014 I was able to successfully merge them using the logresolvemerge.pl script simply enermerating each log and > out_putting_it_to_file Looking at the two logs from each server the format seems exactly the same. The problem I'm having is producing the stats page for the logs. The command I've boiled it down to is /usr/share/awstats/tools/awstats_buildstaticpages.pl -configdir=/home/User/Documents/conf/ -config=example.com awstatsprog=/usr/share/awstats/wwwroot/cgi-bin/awstats.pl dir=/home/User/Documents/parced -month=all -year=all...

linux - How can I get my mediawiki to stop thinking I have cookies disabled?

I've searched half a day for how to resolve this issue, and can't figure it out. Shortly after I made my wiki a simple private wiki according to the instructions at Mediawiki's website, it started giving me this weird login error message: Wiki uses cookies to log in users. You have cookies disabled. Please enable them and try again. If I remove those private wiki settings, the error disappears, even if I try logging in. But I need it to be a private wiki for only my team. So what do I do? Here's what I've done so far. Just to be safe, after ever change, I try rebooting Apache using: sudo /etc/init.d/apache2 restart In my php.ini file, I have the following set: session.save_path = "/var/lib/php5" session.cookie_secure = secure session.cookie_path = /tmp session.cookie_domain = my server's internal URL (should I even set this? this field was blank before, but not commented out) session.referer_check = Off I ran the following to ensure that the fold...