Skip to main content

enRAIDing by remote control

Facing an interesting challenge. I updated a few machines in... remote places, & in so doing had to run the installer sans RAID (it complained about different machines in different ways) in a hurry, & now I address the challenge of enRAIDing a system by remote control.

I’ve grabbed a disk image of one of the remote machines, & plugged it into a local machine as a test-bed. This has revealed an immediate issue: the SATA controller in this machine is different to either of the others, so it won’t boot the disk image.

At the moment, I’ve booted a rescue image, borrowed part of the prospective RAID partner-drive & am bzip2’ing images of each partition into the borrowed partition, to implement a simple worst-case restore scenario.

When that’s secure, I’ll get into making the confused SATA drivers happy, then use the resulting bootable hard disk to walk through the process of making a small chroot-ish area on a transient partition, then walking the machine through switching opensshd into that, then...

Copying the live partitions into one-partition RAID versions of themselves, then unmounting & “reformatting” each live partition into a RAID component, joining that to (updating it from) the freshly-copied RAIDed version of itself on the secondary disk, remounting it again, then refrain for each. The exciting part is going to be booting from the transient partition into a system with working LAN & opensshd so I can reRAID the root partitions.

By remote control. Watching someone try this via ’doze would be... entertaining. For the onlookers.

Stay tuned for an (eventual) outcome.

Labels:

Comments

Leon RJ Brooks said…
Compression wonderment: bzip2 squashed a basically-blank 8.5GB partition down to a 32MB compressed image file.

It’s a pity that this won’t apply to all of the partitions, else I could fit the entire hard disk into a 1GB Flash stick fairly easily. At the moment, it’s compressed 4 of 8 partitions & used just over a GB to store 10.6GB raw.
15 February, 2008 10:50
Leon RJ Brooks said…
I’ve given myself an unfair advantage: I’d left a brace of unused partitions on each drive, which I’ll be able to press into service as transient boot partitions.

This means that I can basically cp -a enough file trees onto a t-b-p to reboot onto that with working LAN & sshd, then rework the other partitions, then reboot back onto the reworked system. Sounds fairly simple... except for the gap of over 4000km between keyboard & workings. About a fifth of the way around the world. (-:
18 February, 2008 12:56
Leon RJ Brooks said…
So far, on the model system, I’ve been able to “cheat” successfully.

I set up the second drive as a set of RAID partitions (with mods to /etc/raidtab & /etc/mdadm.conf), added a new boot option to /boot/grub/menu.lst which treats the RAID as root (etc) & has an initrd containing modules like raid1, then booted into the RAIDed partitions (still retaining, up to now, the ability to boot old-style in case some part doesn’t work as well as it should).

Then merged the old partitions into the RAID & deleted the old-style boot option.
21 February, 2008 22:52
Post a Comment

Popular posts from this blog

An Open and Shut response to Darl McBride

Hi, Darl. I see you’re being dishonest again . It’d be really nice if you could shoot straight for a change, but I think Kerry’s Dad will be selling snowplows in Hell first. Three years ago, when I first joined The SCO Group, we focused the company on the area that was most profitable and provided the most benefit to customers, investors, resellers, developers and employees: UNIX No, you focused the company on suing people, which was most profitable to lawyers and provided some golden parachutes for your buddies. People thought we were crazy. They were right. But since SCO owns the UNIX operating system The SCO Group does not own UNIX® in any sense of the word. The Open Group owns the UNIX trademark, definition and other rights , The SCO Group does not. The SCO Group doesn’t even own the UnixWare® or OpenServer® code, the rights to those are held by Novell and TSG use them only by permission and under certain conditions — which they have violate...
5 comments
Read more

5x7 text dot-matrix in five minutes...

This is a fairly primitive toy I threw together today for a specific purpose, published in case it’s any use to others... feed it a list of words as command arguments, which it will then display as a 5x7 ASCII dotmatrix with ‘#’ as a dot & ‘_’ as a blank. /* * display text using a 5x7 bitmap font in ASCII letters */ static unsigned char font [] [5] = { { 0x00,0x00,0x00,0x00,0x00 }, // 0x20 32 { 0x00,0x00,0x6f,0x00,0x00 }, // ! 0x21 33 { 0x00,0x07,0x00,0x07,0x00 }, // " 0x22 34 { 0x14,0x7f,0x14,0x7f,0x14 }, // # 0x23 35 { 0x00,0x07,0x04,0x1e,0x00 }, // $ 0x24 36 { 0x23,0x13,0x08,0x64,0x62 }, // % 0x25 37 { 0x36,0x49,0x56,0x20,0x50 }, // & 0x26 38 { 0x00,0x00,0x07,0x00,0x00 }, // ' 0x27 39 { 0x00,0x1c,0x22,0x41,0x00 }, // ( 0x28 40 { 0x00,0x41,0x22,0x1c,0x00 }, // ) 0x29 41 { 0x14,0x08,0x3e,0x08,0x14 }, // * 0x2a 42 { 0x08,0x08,0x3e,0x08,0x08 }, ...
5 comments
Read more

Citizens Augmenting Government Waste

So here we have Microsoft-funded “ Citizens Against Government Waste ” (CAGW) heavily criticising Massachusetts’s switch to an internationally accepted and open document standard (not open source, open standard — but I seem to remember a large monopolist who frequently confuses the two when it suits them). I remember CAGW, they were the organisation who had dead people writing in to support Microsoft in court a few years ago — thanks to sbergman27 for the link — is this “the dead hand of CAGW” at work again? Let’s follow the money and find out. Who stands to lose the most money and control if Massachusetts switches to an unencumbered document format? Big surprise, it’s CAGW sponsor Microsoft, through their dominant MS-Office suite. Why did CAGW list Microsoft’s suite last, after two other much-less-dominant examples which are waning anyway? If you’re inclined to wallow in additional irony, consider that at leas...
Post a Comment
Read more