Indicator lights - where to diceipher them?

[figurefive]

Just wondering where I can find out what the flashing green light sequence on my attempted hacked drive means.

It's a 60GB drive going up from 20GB on a VW PhatBox.  I ran the hack and got the verbal confirmation sound.  Then I manually did the copy and format of the new DMS due to the various script issues on the VW version.  Then I reloaded the firmware and removed the forceupdate file from phatsys.

When I attempt to boot the 60GB drive I get a solid green light for a few seconds.  Then a single green flash once.  Then two green flashes repeated four times.  Then three green flashes once.  Then the green light flashes rapidly for several minutes.  After that the Phatbox power cycles and the sequence repeats.

There's no bootload.log file though  

Also...I just noticed something.  After running the hack I still have the flacplay.flac file in the phtsys/music folder, but it is a 0 byte file.  I opened it with notepad, and sure enough it's empty.  Is that normal, or does that mean the script never copied propery and didn't actually run even though I got the confirmation sound?

[STiDriver]

You need to create a dummy one first and it will replace it with useful info.  In the Wiki it was recommended to just copy phatbox.ini to bootload.log

http://wiki.phathack.com/Bootloader_FAQ

[figurefive]

My bad.  I should have looked that up.  Thanks.  Will try that this evening.

[judb]

The flacplay.flac file doesn't have to have any real data, it just has to exist so that we can call the flacplay script that runs the hack.

[A543]

Then I manually did the copy and format of the new DMS

Are you sure you copied the keys and signature properly?

[figurefive]

If the command is
dd if=/dev/sda of=/tmp/image bs=512 count=2048
on the old drive

then
dd if=/tmp/image of=/dev/sda bs=512 count=2048 on the new drive

That's the manual command I did which seemed to process properly.

I copied phatbox.ini to bootload.log in phtsys but I got no results in there.  It's still got the text of the phatbox.ini file.

Did I miss a step for copying the keys and sig?

[A543]

Your command looks fine.  Does the original DMS still work?  And also don't copy any plugins you might have to the new DMS yet. There was at least one person who's box wouldn't boot with the plugins copied over.  It's still being looked into.

[figurefive]

Original DMS still works.  Never installed any plugins.  The PB may just not like the 60GB drive.  It came from a laptop that's a couple of years old.  I wiped it before trying all this, but I may try a brand new drive next.

[judb]

Make sure you don't have any jumpers on the new drive.  Frequently they'll be set to Cable Select which works in the DMS cradle but not in the phatbox.

[figurefive]

Hadn't thought of that.  It doesn't look like there's anything on the pins, but I never really looked.  I suppose it's also possible this drive is CS by default and I need to jumper it to get it to master.

This could be promising as based on the bootloader faq it looks like the PB isn't even identifying the drive - the contents of my bootload.log aren't being overwritten.

[Slack]

figurefive

My problem sounds quite similar to yours.
I checked my drive, and no jumpers = single, master. (Had my hopes up).

Out of curiousity what brand drive do you have?

[figurefive]

Mine's a Toshiba HDD2184 that came out of a Compaq laptop.  Problem is Compaq put their own sticker that pretty much covers all the Toshiba info, so I can't see what it's jumpers do.

According to their website, though, no jumper equals master which is how I have it.