Thursday, October 17, 2013

HELP! - Rescue my Intel RAID


Just had to post this one, after a narrow escape:

LESSON: ALWAYS BACK UP YOUR DATA BEFORE UPDATING BIOS FIRMWARE!

While diagnosing some sleep/wake issues on an ASUS P8H77-I motherboard, I was forced to update the BIOS. While this is pretty easy on the Asus boards, Be aware that sometimes a BIOS update can wipe the Intel RAID controller configuration!

Looking at the RAID management screen in the BIOS it was obvious that two of the 4 RAID-5 disks had somehow been marked as 'non-RAID' and therefore were not members of the set anymore.

All may not be lost however, if you encounter this, and you know your RAID disks are good - in other words they were ok before the update, then you could try this:

http://www.overclock.net/t/478557/howto-recover-intel-raid-non-member-disk-error

Essentially:
- Boot into the RAID config (CTRL-I on my board)
- DELETE the RAID configuration [just wipes the RAID sig on the disks]
- CREATE a NEW RAID configuration of EXACTLY THE SAME SETTINGS as before
- Reboot
Windows will still not recognise the partition I discovered but you can recover this using TESTDISK:
http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step

- Download TestDisk
- Start it up, and let it scan for partitions
- you should see your missing volume within seconds.
- Stop the scan (unless you have more AWOL volumes)
- Write the partition signature
- Reboot again.

Data was restored 8-)

More details here:
http://forums.anandtech.com/archive/index.php/t-2226542.html

Remember:
ALWAYS BACK UP YOUR DATA BEFORE UPDATING BIOS FIRMWARE!

[Your experience may vary from the above, but I felt it was worth posting that this worked flawlessly for me]

Tuesday, January 01, 2013

Controlling your Crashplan Backup

Happy New Year by the way!



Here's a quick hack I use to control Crashplan on my Windows Home Server.  If you've not tried Crashplan, you're missing out - It's a cloud based and peer-to-peer backup solution that 'just works', complete with the ability to avoid that huge initial backup to your friend's PC by taking the 'seed' backup to them on a USB drive, then sync the changes over the net. There even a smartphone app to get your files on the go.

You can configure it to backup 'all the time', and you can also configure it to run between certain times of day. This was great until I calculated that it would take 4 months to pump my backup up to the Crashplan Cloud running 11pm-8am using all my upstream bandwidth !!

One of the problems of a DSL internet connection is that authough you might have a tasty 20mbit connection for downloads, you only get a 1mbit connection for uploads (or backups) - this is fine until you try to use that connection while the backup is running, things are extremely slow as a result of all the data you're sending 'up' your DSL connection.

Cue a nasty hack to help us out a bit! - this simple script adds a little intelligence to when the backup actually runs. I should point out that Crashplan is configurable in terms of the bandwidth it uses when you're at your PC, or away from it - though with a headless Windows Home Server, I'm always away, so have less control of this, coupled with more than one PC in the house, this is a little limited , but if you have just one PC or laptop it will work fine for you.

I use this simple script to do the following:
  • Run the backup at night time (22:00-08:00) - no-one is using the net at that time 8-)
  • During the day run the backup, unless one of our PC's is being used, in which case stop it.
This works quite crudely by starting and stopping the Windows Service that actually drives CrashPlan. But it means that whenever we're 'not' using the internet connection at home, the backup can have as much as it wants.

Hopefully I wont have to wait 4 months now!