letting battenberg rebuild

| | Comments (0)
Personalities : [raid1] [raid10]
md1 : active raid10 sda2[0] sdh2[7] sdg2[6] sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1]
      7772118016 blocks 256K chunks 2 near-copies [8/8] [UUUUUUUU]
      [===>.................]  resync = 18.9% (1469509312/7772118016) finish=245.7min speed=427408K/sec

Why am I not rebuilding online?  because fear.  two disks failed out of the raid at once on the old system. 

Edit: 

Yeah, so the rebuild is almost done, and just like last time I rebuilt offline, I think I may have made a mistake.   The thing was?  the first time I rebooted battenburg, things came back up, only for two disks to fall out of the raid during rebuild, causing another reboot.  

If the problem was load-related, my reaction would have been rational.  However, I don't believe the problem was load-related, so I probably should have verified that the system was up and running on the new system, rebooted, and let the thing rebuild online.


here is where we stand now:



(Repair filesystem) 132 # cat /proc/mdstat
Personalities : [raid1] [raid10]
md1 : active raid10 sda2[0] sdh2[7] sdg2[6] sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1]
      7772118016 blocks 256K chunks 2 near-copies [8/8] [UUUUUUUU]
      [===================>.]  resync = 98.8% (7683022720/7772118016) finish=5.4min speed=272570K/sec





Yeah, so the disks from battenberg?  they are now in Jellico.   It's a very similar server, but with a different motherboard/HBA/backplane, so all the components that likely caused the problem are new. 

Leave a comment

About this Entry

This page contains a single entry by luke published on July 4, 2014 4:48 PM.

Nope, looks like battenberg disk subsystem/backplane is completely broken was the previous entry in this blog.

battenberg is back (in jellicoe) is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.