Skip to main content

raid - What will happen if encountered a URE?



About hdd URE, I knew these points:





  1. For some reasons, when harddisk reading a sector that the FEC(Foward Error Correction data) could not correct the errors on that sector, we encontered an URE.

  2. The rating we encountered an URE is very low, but still exists.

  3. When reconstructing a RAID 5 array, sometimes it will happened and the reconstruction progress will stop.



But I still have some questions:




  1. If there is a single disk, what will happened? Hardware/file system report an error and we lost a file? Or we got the file with wrong data?


  2. Will rewrite some data to that URE sector could turn the sector become normal? Or must we use some utilities provieded by HDD manufactory and remap another reserve sector?

  3. If it happened when we mirror/re-mirror a RAID 1/10 array, what will the RAID controller do? Stop the mirror progress? Or just copy the uncorrect data to another disk?






Thanks for the answer, question 1&2 is solved.



But the 3rd question I mean if encountered URE when converting a single HDD to RAID 1 array by add another new disk, or replacing a failure disk in a RAID 1/10 array, there's no redundancy to correct the error. Will it complete the mirror/re-mirror progress with error data? OR stop the progress like RAID 5 recontruction?


Answer





  1. With a single disk, an unrecoverable error is just that - it can't be done and it is reported to the filesystem and subsequently to the application trying to read a file. Generally, it is preferred to get an explicit error instead of unreliable data.

  2. Writing to an unreadable sector will either fix the physical sector (for a soft error when e.g. writing was interrupted by power loss) or the drive will map the logical sector to one of its spare pool. This happens at the discretion of the drive and isn't usually user/driver selectable.

  3. The RAID controller will most likely repair the sector - either from the mirror or by rebuilding the data from the redundancy set. When during a mirror or rebuild a(nother) read error prevents this repair, the error sticks and the array is bad. Some RAID sets can repair multiple errors (RAID 6 or some nested RAIDs) but once errors pile up you're out of luck.



It's important to make sure errors don't pile up on rarely used sectors - they can become uncorrectable errors when sectors are left unread for months or even years. So, make sure you enable data scrubbing, media patrol, patrol read or whatever it's called on your hardware to check all data on a regular basis. That way, you ensure a rebuild works when you need it.



Some people report that during a rebuild, additional drives start to fail because of the stress but I've found this to be a myth. The drives just stumble on stale, accumulated errors. You can stress even very old drives for days without any problems.


Comments

Popular posts from this blog

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...

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)

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits, ...