Due to an unscheduled powercycle on my linux server, I got a very troubling page from mdadm, the multi-disk administrator, saying it had marked one of the disks as failed.
This, presumably, was due to a flaky SATA controller that didn’t make /dev/sda available by the time the kernel was mounting /dev/md0, so software raid turned it off.
It was easy enough to get the drive back into play:
sudo mdadm /dev/md0 --add /dev/sda1
And easy enough to monitor progress:
mrm@gronk:~$ cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md0 : active raid5 sda1[3] dm-2[1] dm-1[0] 580074880 blocks level 5, 64k chunk, algorithm 2 [3/2] [UU_] [====>................] recovery = 22.0% (63875072/290037440) finish=178.1min speed=21154K/sec
Related posts:
- Run a RAID6 on Amazon EBS For Fun and Profit
With all this badmouthing Amazon’s Elastic Block Store, I wanted to share how we’ve set up our MySQL server for AdGrok. Step 1: Create a bajillion tiny EBS volumes We’ve...... - HOWTO: Mount your USB hard drives at boot time on Ubuntu
I’ve got a number of external USB hard drives connected to my ubuntu server that need to mount to a predictable directory. When you log into Gnome, the desktop environment...... - +1 for Apple
Night before last, I found bad blocks on my MacBook Pro. I dropped off the laptop at the Burlingame Apple Store (after making an “Apple Concierge” appointment, so no lines),...... - Installing Ubuntu from a USB Drive
I just bought a new green server (25-30 watts at full load!) and wanted a brand-new Jaunty experience. The MSI Wind Nettop doesn’t come with an optical disk drive, nor......