Failed upgrade...am I hosed?

[figurefive]

First, thanks for all the hard work you guys have put into this project.

Second, I apologize if the info I'm looking for is elswhere on the forum.  I've read through a lot of the other theads on failed upgrades, but haven't recognized anything that may help me.

Ran cd 1.3 on my 20GB VW PhatBox DMS.  Plugged it into the car and heard the message about the PhatBox being unlocked (this played while a song was playing in the backgound, which concerned me).

Swapped the new 60GB drive into the DMS, completed the script, and loaded firmware.  But I get a solid green light almost immediately on the PhatBox.

Tried putting the 20GB drive back in, but I am now getting flashing green lights.  I think I first get 10 green flashes, a pause, then 5 green flashes, a pause then continuous green flashes.

I've tried rebuilding and reloading the firmware to no avail.  When I looked at the bootload.log it looked corrupted.  All it had was a string of boxes, no readable text.  What would my next step be to try to recover this thing?  Which logs should I be looking at for useful info?


Thanks for any input,

Fig

[judb]

First thing, run a chkdsk on your DMS (the original dms that is) with the repair option (thats found in the properties of the drive letter in explorer.. on the tools tab.)

then try putting the old DMS back in your unit.  See if it boots.  if it does, then try putting in the new DMS.

We've seen lots of issues with the VW DMS not copying properly to the new DMS and not booting.. but the OLD dms should work fine even if the new DMS doesn't.

If the old DMS still doesnt work, try renaming the file ramdisk.sig to ramdisk.bak  then make a copy of phatd.sig as ramdisk.sig ..

Code: [Select]


(from the dos prompt)
g: (where g: is your phtsys drive letter)
move ramdisk.sig ramdisk.bak
copy phatd.sig ramdisk.sig


That should boot if you do that.  Give it a shot.  Good luck!

[figurefive]

Thanks for that!  It worked.  The OEM DMS works once again.

However, the 60GB drive won't boot.  I get 2 green flashes, repeated a couple of times, then 3 green flashes then a fast blinking green light for several minutes.  Then the PB powers cycles and the above repeats.

Here's my patch log.  I'm curious about the end where is says no such file or directory.

: No such file or directory
2048+0 records in
2048+0 records out

hdparm - get/set hard disk parameters - version v3.9

Usage:  hdparm  [options] [device] ..

Options:
-a   get/set fs readahead
-A   set drive read-lookahead flag (0/1)
-c   get/set IDE 32-bit IO setting
-C   check IDE power mode status
-d   get/set using_dma flag
-D   enable/disable drive defect-mgmt
-E   set cd-rom drive speed
-f   flush buffer cache for device on exit
-g   display drive geometry
-h   display terse usage information
-i   display drive identification
-I   read drive identification directly from drive
-k   get/set keep_settings_over_reset flag (0/1)
-K   set drive keep_features_over_reset flag (0/1)
-L   set drive doorlock (0/1) (removable harddisks only)
-m   get/set multiple sector count
-n   get/set ignore-write-errors flag (0/1)
-p   set PIO mode on IDE interface chipset (0,1,2,3,4,...)
-P   set drive prefetch count
-Q   print out the drive id only (60bytes\n)
-q   change next setting quietly
-r   get/set readonly flag (DANGEROUS to set)
-R   register an IDE interface (DANGEROUS)
-S   set standby (spindown) timeout
-t   perform device read timings
-T   perform cache read timings
-u   get/set unmaskirq flag (0/1)
-U   un-register an IDE interface (DANGEROUS)
-v   default; same as -acdgkmnru (-gr for SCSI, -adgr for XT)
-V   display program version and exit immediately
-W   set drive write-caching flag (0/1) (DANGEROUS)
-w   flush os cache and wakeup drive
-X   set IDE xfer mode (DANGEROUS)
-y   put IDE drive in standby mode
-Y   put IDE drive to sleep
-Z   disable Seagate auto-powersaving mode
PhatPatch v0.4 - original code by bushing, additional patches by sbingner
Verifying:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0033 1a00
Unverified!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0026 1a00
Unverified!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0019 1a00
Unverified!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 000c 1a00
Unverified!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13a0    Actual: 0000 13e0
Unverified!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0000 e350    Actual: 0001 e350
Unverified!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0000 03a0    Actual: 0001 03a0
Unverified!
PhatPatch v0.4 - original code by bushing, additional patches by sbingner
Verifying:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13a0    Actual: 0000 13a0
Verified!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0000 e350    Actual: 0000 e350
Verified!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0000 03a0    Actual: 0000 03a0
Verified!
done
: No such file or directory

: No such file or directory
/dos/backup/patch.sh: kup/p: No such file or directory

[todd1010]

One problem I had with booting after putting in the new hard drive was copying over the plugins folder. Ever since I haven't put the plugins folder in the PHTSYS partition my DMS is working/booting fine.

I have a Audi Phatbox which is essentially the same thing as you have. So if your putting the plugins folder in, try deleting it.

Judb recommended trying something with the plugins folder. I'll try it out tonight and post what about.

[figurefive]

That's a good thought, but I never got around to installing any plugins.

I'll keep tinkering with some minor stuff.