October 14, 2009

Procyon upgrades

I finally got around to doing something today which I've been putting off. I took Procyon to see the computer doctor.

It's been running really hot for a long time, and I've been coping with it by putting it up on spacers to allow it to breath better, and by using the system power control to throttle back the CPU clock rate, and by being careful about using it heavily on hot days. All of which I shouldn't have to be doing.

Today I got off my butt and took it out to the computer place that's on my way to the grocery/variety store where I do most of my shopping. I left Procyon there to be cleaned out, while I went on to Fred's. I wanted to buy a coat (the one I have is 20 years old and getting kind of ragged). So I did that, and then stopped back at the computer store on the way home. Had to wait maybe ten minutes (no big deal) and it cost me $15. And now Procyon is running more than 10 degrees cooler at full clock rate than it used to with the clock rate throttled to 70%.

Reason I was finally willing to do that was because of the backups that Deneb has been making every night. And it occurred to me today that this might make it easy for me to put a larger HD inside Procyon. It's a 200G drive, divided into two partitions. And I'm pretty sure that Deneb's backups are file-oriented, not block-oriented. In fact, I'm certain of it.

Deneb came with a boot CD for purposes of restoring a crashed computer from the backups. The idea is that if your HD is totally dead, you boot off that CD, and it makes contact with Windows Server on your LAN and restores the whole thing. What I'm wondering is how that process would work if the HD was suddenly magically bigger?

In other words, if I replaced my 200G drive with a 320G drive, would the backup CD work? Would the restoration work? Would my apps work afterwards?

I might get a new drive and give it a try. After all, if it fails I can just put the old drive back in. And it sure would be nice to have more space on this thing. Even if I had to make the new space a third partition.

Which might not be necessary. NTFS partitions can be made larger; it's a feature of the file system. If it initially created a 111G C partition and a 66.7G D partition, which is how it is now, and didn't use any of the rest of the space on the larger drive, I could later add all the rest of the drive space to D. That would be fine.

Another possibility is to copy all the stuff that's currently on D onto the server and delete it all, and then delete that partition as well. Then run another backup, just before swapping drives. That way it only restores one partition.

OK, all you Windows Home Server gurus out there. (Quentin?) Think this would work? Or have a reasonable chance of working?

UPDATE: Hitachi has a 7200 RPM 320G SATA drive for just $80. There are other drives which are cheaper, but I like Hitachi as a brand. And $80 is amazingly cheap.

Posted by: Steven Den Beste in Computers at 04:27 PM | Comments (13) | Add Comment
Post contains 567 words, total size 3 kb.

1 Fry's had 640GB Hitachi SATA drives available ~1 month ago.  <$100 IIRC.  I got 2 of them.  (/proc/scsi/sci reports the model as  "Hitachi HDT72106")

Wow.  Even less now.  http://www.frys.com/product/5947264?site=sr:SEARCH:MAIN_RSLT_PG

Posted by: Mark A. Flacy at October 14, 2009 07:45 PM (Lbkvv)

2 That's the wrong form factor. It won't fit into a notebook computer like Procyon.

Posted by: Steven Den Beste at October 14, 2009 08:00 PM (+rSRq)

3 So what was it that was causing Procyon's overheating?  Was it, as you expected, just dusty?

Posted by: Wonderduck at October 14, 2009 08:41 PM (/O6qY)

4 Yeah. He said that a lot of dust came out of it.

Posted by: Steven Den Beste at October 14, 2009 08:50 PM (+rSRq)

5

Yes, you can install a bigger HD and restore to the bigger drive.  My father dropped his laptop and borked the hd.  Luckily I had backed up his system on my WHS.  I installed a much larger drive and 45 minutes later the restore had completed without issue.  If I recall correctly, I believe the restore cd program gives you a slider indicating how big you want to size the restored partition.  You can get a good idea of the process by inserting the restore cd and stepping through the dialogue windows (not surprisingly, the limits are the size of your data and the size of the drive).  No data is affected and no changes are made until the last confirmation which has clear warnings.

The backups work at the cluster level  (from wikipedia.) This technology uses Volume Shadow Services (VSS) technology on the client computer to take an image based backup of a running computer. Because the backup operates on data at the cluster level, single instancing can be performed to minimize the amount of data that travels over the network and that will ultimately be stored on the home server. This single instancing gives the server the ability to store only one instance of data, no matter if the data originated from another computer, another file, or even data within the same file.

Posted by: kderosa at October 15, 2009 04:50 AM (/qyKz)

6 That's good to know. I think I'll give it a try.

Posted by: Steven Den Beste at October 15, 2009 07:47 AM (+rSRq)

7

I just tried a dry run using the restore CD, and it didn't load network drivers. Looks like I need to buy a USB flash drive to put the drivers onto. (I saw the instructions for how to get the drivers; seems straightforward once you have a USB flash drive.)

I'll buy one next time I go to the store, and then try it again. It's probably a good thing I'm going through this now, in any case, rather than waiting until after a real crash some time.

Posted by: Steven Den Beste at October 15, 2009 11:02 AM (+rSRq)

8

Are you using the restore disk that came with the server or have you burned a cd of the new Restore PC program that came with the first service pack?

goto \\denedb\software\Home PC Restore CD and find the restorecd.iso file.  Use that (once you've burned it to a cd) instead of the original disk.  It has better driver support.

I had the same network driver issue that you're having with the original disk, but the new program ran without issue.

 

Posted by: kderosa at October 16, 2009 03:55 AM (/qyKz)

9

The only thing in that directory was a readme. I looked at it and it had a URL at Microsoft to download from.

That gave me a file with extension MSI, which turns out to be a self-unpacking archive which contained the ISO.

The ISO was dated July 2008 and when I booted from it it seemed to be exactly the same as the other one. It didn't know about my networking hardware. (Which is peculiar; I bought this computer November 2007.)

I need to go to the store today anyway and I'll get a USB flash drive.

The restore program is strange. First thing it does is ask you if you have more or less than 512 MB of RAM. Can't it tell? Why doesn't it ask the BIOS?

Posted by: Steven Den Beste at October 16, 2009 11:41 AM (+rSRq)

10

Flash drive purchased, and when I reached that point in the restore process, it read the flash drive and did install the network drivers.

But it couldn't locate the server. I'm sure it's exactly the same problem I had when I restored the server software: the IP is in a different block. I'm currently using the 192.168.*.* black hole and I fear I'm going to have to move everyone over to that other one on a permanent basis. Bleah.

Posted by: Steven Den Beste at October 16, 2009 04:04 PM (+rSRq)

11

The iso in  my directory is dated 7/12/2008.  And has a link to this download:  http://www.microsoft.com/downloads/details.aspx?FamilyID=26881305-91cc-4f37-b1fc-3813c423df2c&displaylang=en

The primary reason for the upgrade was to include native vista x64 client support.  I have no idea why the restore program can't auto detect the amount of RAM, but I do know that the >512MB version of the connector is an optimized version.

Sounds like your server shipped with the updated restore program but that your network hardware drivers still weren't included.

Posted by: kderosa at October 16, 2009 04:53 PM (/qyKz)

12 As a minor note, an address on the 169.254.*.* subnet usually indicates that the computer is using a DHCP client, and cannot find a DHCP server to talk to that will give it an IP address on the local subnet. One solution is to run a DHCP server on your network that gives out addresses on the 192.168.1.* subnet.

The usual place to run a DHCP server is on your gateway (most consumer routers have them), but if all you need it for is to assign a local IP when you run the recovery disk, Deneb might have a DHCP server that can be enabled and configured easily.

Posted by: benzeen at October 16, 2009 09:00 PM (SQ64B)

13

Well, surprise of all surprises, I found a freeware DHCP server on a Microsoft WHS forum. It's been there for two years, so presumably if there was something wrong with it a moderator would have removed the post long since. So I downloaded it and installed it, and it looks like it's working.

Tomorrow I'll try the restore CD again, but it's too late tonight.

Posted by: Steven Den Beste at October 16, 2009 09:23 PM (+rSRq)

Hide Comments | Add Comment

Enclose all spoilers in spoiler tags:
      [spoiler]your spoiler here[/spoiler]
Spoilers which are not properly tagged will be ruthlessly deleted on sight.
Also, I hate unsolicited suggestions and advice. (Even when you think you're being funny.)

At Chizumatic, we take pride in being incomplete, incorrect, inconsistent, and unfair. We do all of them deliberately.

How to put links in your comment

Comments are disabled. Post is locked.
16kb generated in CPU 0.0129, elapsed 0.0319 seconds.
20 queries taking 0.0225 seconds, 30 records returned.
Powered by Minx 1.1.6c-pink.