SATA drives and Acer T135

More on the SATA / Acer T135 saga.

Having got the PC to “see” the drive in the BIOS, it should be a simple matter of restoring the system volume onto this drive (or cloning it from the old drive), making it a primary, active partition (so it’s bootable into Windows), and off we go, yes?

So I created 1 large partition for the system and restored onto it. Did this work? No. Not in these Acer machines.

According to boot.ini (which the wonderful StorageCraft ShadowProtect software can read easily), partition 2 was set as the boot volume. And I only had 1 partition – so better change it.
So I edited it to be partition 1, and tried again. No luck.

I recall that the machine was supplied with the drive having two partitions –

  • Partition 1, around 2.8 Gbytes, for automatic ‘recovery’ of the machine
  • Parition 2, the usual Windows system volume.

The recovery process is an Acer thing. Basically on boot, you hold down a key (Alt+F10) and the machine goes into auto-recovery mode. This basically re-initialises the system partition (2) from a factory-created archive held on partition 1. That’s what the 2.8 Gbytes is used for. It provides a degree of safety for uses who trash up their machines so they won’t boot, and I suppose it’s cheaper than supplying Windows installation media.

I’m not a great fan of this kind of auto-recovery (after all, it will trash all your programs and data, for sake of getting Windows re-installed). I prefer to use StorageCraft ShadowProtect with an external USB drive, as then I can get the machine back exactly to “how it was” the last time backed up.

Out of a mix of desperation and curiosity, I tried holding down Alt+F10 as the machine booted (off the new disk, which did not have any recovery software on it, only a clean system image). Voila! it booted into Windows, off my new partition 1. So this told me two things:

  1. I could restore the machine, somehow.
  2. The Acer BIOS somehow seems to be ignoring boot.ini, and doing its own thing, based on this Alt+F10 key (or lack of it).
  3. The Alt+F10 key forces a boot from partition 1. It works, but it’s a bit inconvenient for everyday use.

Another attempt

Now knowing this about the Acer machine, I tried again, but this time

  • Small initial partition (around 2.8 GB), which I put a copy of the Acer restore stuff onto from the original disk
  • Large system partition (the rest of the disk) for Windows etc.

The first was copied from the original Acer-supplied hard disk. The second came from my ShadowProtect backup.

Still no luck. It would not boot into Windows. But with Alt+F10 held down, it would boot into the Acer Recovery software on Partition 1.

Yet Another Attempt
Finally, in desperation – I thought – why not run this Acer recovery software, and at least see if it can make the machine (normally) bootable, off a freshly restored partition 2. So I let it restore, effectively over-writing partition 2 with its virgin install of Windows + the Acer utilities etc. that came with the machine. (No CD-ROMs are supplied as standard).

This resulted in a machine that actually boots up (although missing a lot of stuff, obviously). So – here’s the trick – that Acer Restore feature is actually necessary for a machine rebuild – in a totally non-obvious way. boot.ini looked just the same, before and after the restore.

I wonder what the Acer Restore does to the disk. It does some magic that is not obvious.

So … having proved that was possible, I then restored the ShadowProtect image back over partition 2. And that finally worked! I had a machine that booted normally, and had everything back where we wanted it.

I still don’t know why the machine is so fickle with its boot-up, and why it ignores Windows’ own boot.ini.

Conclusions

  • If you have an Acer T135, that 2.8G of “stuff” on the Restore partition is essential to the continued use of the machine, if you replace hard disks. Don’t just think that having valid Windows install media and a valid key will be enough to get you out of trouble.
  • Acer T135 has its own boot control which ignores Windows.
  • Don’t forget to jumper new SATA drives down to the older standard, if they can be detected.

and finally

  • Don’t buy machines with proprietary motherboards and BIOSs if you can help it! Sooner or later they will drive you mad.

Recommended tools and parts for this kind of work:

  • Patience
  • Anti-static wrist strap
  • Screws for holding the new drive in
  • SATA cable (usually not supplied with ‘OEM’ drive packages)
  • Jumper (again, usually not supplied)
  • Tweezers for fitting the jumper
  • Partitioning / formatting / backup / restore software, such as Norton Ghost, Acronis TrueImage, Partition Magic. My personal favourite at the moment is Shadowcraft StorageProtect 3.2 which works fast and well in my experience. It comes with a bootable CD-ROM image that means you can work with machines even when the hard disks are unbootable. Review of the software here

Acer T135 with and new SATA drives – a snag

Just came across a nasty little snag with SATA disk drives. I thought I’d write it up, in case you run into something similar.

One of our family computers is an Acer Aspire T135, around 3 years old now. The 80GB hard drive is getting rather full and slow. Time for an upgrade.

Step 1 – check what the existing PC can do.
It has a spare SATA connection on the motherboard, so that seems like the best way to go.
There is plenty of space in the case for a new drive.
There is a spare SATA-compatible power connector (different to the old-style 4-pin Molex’s) dangling in the case.
I’ll need to get a new SATA data cable for the drive.

Step 2 – plan how to use the drive
My initial thought is to use the new drive for the OS and programs, and the old drive as scratch area and – if it makes things run faster – the windows swap file.

Step 3 – choose a drive
A quick look at drive specs etc. suggests a 500GB drive as the best price point at the moment (given that the machine does not have to handle huge amounts of data usually).

A quick check on the Acer website suggests no particular compatibility requirements for second drives (then again, it doesn’t really say a lot about their machines anyway).

Western Digital do a nice looking “Green Power” model which claims to save power. As family PCs get left on all the time, that seems like a good idea.

I got mine from Novatech as they are local (www.novatech.co.uk).

Step 4 – install the drive
Short work with a screwdriver and the new drive was ready to run.
Boot up, check in the BIOS that the drive was recognised … nothing, only the existing drive is found.

I tried various things, including:

  • Swap the existing and new drive data cables
  • Swap the existing and new drive power cables
  • Try with another SATA drive I had available (an older 160GB Maxtor). Ah-ha! That works!

So why does the new drive not work?

Step 5 – fault-finding .. it’s NOT the BIOS …

  • Maybe the BIOS is too old to read 500GB disks. So I flashed the BIOS with a newer version, directly from Gigabyte’s website, rather than from Acer’s website.
  • The motherboard is a K8VM800. But it’s labelled as the K8VM800MAE on the motherboard itself. Gigabyte list two versions – Rev. 1 and Rev. 2 – but nothing about the MAE. According to the chips fitted it’s closest to Rev. 1. (looking at the Ethernet chip type).
  • Incidentally, flashing BIOSs on computers like the Acer T135 that lack a floppy drive is somewhat time-consuming and troublesome. It hasa nice integrated flash card reader though … so … After a bit of Googling, and making a DOS-bootable disk on a Flash SD card, which worked fine on one of my other machines, I gave up, yanked a floppy drive out of another machine, and used that instead …
  • It flashed OK (but with a warning message), and it ran the computer OK, but it kept giving checksum errors on startup. Not such a good idea. Revert back to the original BIOS (which I had kept).

Step 6 – try another 500GB drive

As it happens, I have a 500GB SATA drive (different brand – Samsung) in another machine. So – let’s try that.
It works! So there isn’t a capacity issue. Must be something weird with the drive.

Step 7 – has anyone else hit this before?
After some tricky Googling to avoid the hundreds of old review articles on T135’s, many that have a different spec, I found a forum that suggested that:

  • SATA has different speeds – 150MB/sec and 300 MB/sec
  • While everything is supposed to auto-adjust, it might not

A quick check on the drive manufacturer’s website pulls up a datasheet, and — guess what — there are some jumpers to force the drive down to the slower speed.

http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1679

It’s that OPT1 jumper (pins 5-6 on the drive family I’m using).

Now the BIOS sees the drive. But the original drive seems to be taking ages to boot up in to Windows (despite not being changed at all). More on this tomorrow.