Author Topic: Toshiba MK30186A 30GB  (Read 16615 times)

0 Members and 1 Guest are viewing this topic.

Offline typeoserv

  • Newbie
  • Posts: 8
Toshiba MK30186A 30GB
« on: April 12, 2006, 01:46:19 am »
after trying every hint on the board (i think)
the *.sys corrupted, the dd hack, reflashing 10 times,
i still have not gotten the drive to work
i do remeber seeing someone else not being able to get this drive to work,

my reason for posting is to find anyone else who has tryed this drive, successful or not
thanks :'(

Offline markbowen

  • Global Moderator
  • Veteran.
  • *****
  • Posts: 438
Re: Toshiba MK30186A 30GB
« Reply #1 on: April 12, 2006, 01:22:51 pm »
If you want help, you should post more info.  What model box are you trying to patch?  I think with few exceptions, the patch CD eventually works for most models.

BTW, it's not any *.sys file you need to corrupt.  The file you might need to corrupt is ramdisk.sig.

Also, I didn't find any posts of anyone not being able to get a 30gb Toshiba drive working.

Kenwood DNX7200/Kenwood KHD-C710 Keg/320GB DMS

Offline typeoserv

  • Newbie
  • Posts: 8
Re: Toshiba MK30186A 30GB
« Reply #2 on: April 12, 2006, 07:05:02 pm »
Post i was refrencing --->
 >>3          DMS Hacking / DMS Hacks / Re: One more try, please help.
 >>on: 03/29/06 at 4:07pm
 >>Started by CtrlAltDel | Post by TommydCat
 >>I seem to be in the same boat here...
 >>The logs from the original DMS show that the patching went successful and the verification checked out ok as well.
 >>
 >>I put in the new DMS and it sits there for a bit (solid red light, steady blinking green light) then it powers off and I get EJECT on   >>the head unit.  Log looks the same as above as well.
 >>
 >>The old DMS drive is a 10gig Toshiba and the new one is a 30gig Toshiba (taken from a working laptop).  Both drives appear fine  >>when in the cradle.
 >>
 >>Could there be something specific about the 30gig Toshiba it doesn't like?  Where to look?>>

Its a Kenwood Keg 710, i tryed both the ramdisk.sig & the aadec.sig

Let me know what info you need / i should post for someone to be able to help

Thanks
Erik
« Last Edit: April 12, 2006, 07:07:33 pm by typeoserv »

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Toshiba MK30186A 30GB
« Reply #3 on: April 13, 2006, 02:32:53 am »
if it says it verified ALL the patches you should be OK, make sure the jumpers are set to primary not secondary

Offline TommydCat

  • Newbie
  • Posts: 9
Re: Toshiba MK30186A 30GB
« Reply #4 on: April 13, 2006, 11:04:04 pm »
I'll grab my drive after I get back home and compare the model numbers, as I don't know the model number of mine off-hand...  It seems the keg just plain refuses to boot my new drive (no jumpers, looks exactly the same as the original 10 gig Toshiba that came in the DMS).

Perhaps I'll jumper it to master and see what happens.

Otherwise perhaps this drive just isn't compatible for some reason?  :(

Offline TommydCat

  • Newbie
  • Posts: 9
Re: Toshiba MK30186A 30GB
« Reply #5 on: April 14, 2006, 02:20:15 am »
Mine is a Toshiba MK3021GAS.  (Even jumpered for master, the phatbox simply will not boot it...  Recognized in both the hack ISO and in windows just fine in USB 1.1 dock)

ATA-5, 100MB/sec bus
Data Storage Physical: Per drive, formatted* 30.0058GB
Data Heads 2 Number of Disks 1
Logical Configuration:
Heads 16
Cylinders 16,383
User Sectors/Track at zone 0 63
Logical Blocks (LBA) 58,605,120

I can't find the MK30186A anywhere on Toshiba's site or Google... Are you sure that's the correct model?

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Toshiba MK30186A 30GB
« Reply #6 on: April 14, 2006, 01:00:15 pm »
please post the output of "fdisk -l /dev/sda" while the device is connected and you're in the DMS repair or hack CD's console

The keg doesn't care about volume labels but it must be partition #1 and 5

Also, it MUST be formatted as FAT32

Offline typeoserv

  • Newbie
  • Posts: 8
Re: Toshiba MK30186A 30GB
« Reply #7 on: April 15, 2006, 01:13:32 am »
sorry, its a MK3018GAP

will post output as soon as i reinstall vmware

Offline TommydCat

  • Newbie
  • Posts: 9
Re: Toshiba MK30186A 30GB
« Reply #8 on: April 17, 2006, 03:37:16 pm »
Quote
please post the output of "fdisk -l /dev/sda" while the device is connected and you're in the DMS repair or hack CD's console

The keg doesn't care about volume labels but it must be partition #1 and 5

Also, it MUST be formatted as FAT32

The original 10gig Toshiba that came in the DMS:
[size=12]
# ./sfdisk -l /dev/sda
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0


Disk /dev/sda: 9590 cylinders, 64 heads, 32 sectors/track
Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start    End   #cyls    #blocks   Id  System
/dev/sda1          1    260     260     266240    b  Win95 FAT32
/dev/sda2        261   9589    9329    9552896    5  Extended
/dev/sda3          0      -       0          0    0  Empty
/dev/sda4          0      -       0          0    0  Empty
/dev/sda5        261+  9589    9329-   9552895+   b  Win95 FAT32
#
[/size]

The new 30gig Toshiba:
[size=12]
# ./sfdisk -l /dev/sda
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0


Disk /dev/sda: 28615 cylinders, 64 heads, 32 sectors/track
Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start    End   #cyls    #blocks   Id  System
/dev/sda1   *      1     64      64      65536    b  Win95 FAT32
                start: (c,h,s) expected (1,0,1) found (0,32,33)
                end: (c,h,s) expected (64,63,32) found (8,73,1)
/dev/sda2         65  28614   28550   29235200    5  Extended
/dev/sda3          0      -       0          0    0  Empty
/dev/sda4          0      -       0          0    0  Empty
/dev/sda5         65+ 28614   28550-  29235199+   b  Win95 FAT32
#
[/size]
(Note: boot flag I added in act of desperation after repeated failures)
« Last Edit: April 17, 2006, 03:38:32 pm by TommydCat »

Offline TommydCat

  • Newbie
  • Posts: 9
Re: Toshiba MK30186A 30GB
« Reply #9 on: April 17, 2006, 10:11:52 pm »
Putting the 30 gig in the Keg results in the flashing green light of doom...  I counted 5 flashes, but I don't see a corresponding entry for this (the FAQ starts a 6 flashes for drive reset/id).

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Toshiba MK30186A 30GB
« Reply #10 on: April 18, 2006, 03:30:01 am »
I didn't get all the flashes mapped out, it's a pain.... when I get home in 2 weeks I can look it up in the ROM...  Ihould however keep updating it when I look one up ;)

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Toshiba MK30186A 30GB
« Reply #11 on: April 18, 2006, 03:32:34 am »
BTW: the drive looks fine, I'd cleaning off the PHTSYS partition (quick-format in windows is fine as long as you keep label) and reloading firmware on it from PMM

Otherwise, it could be that your hack isn't actually applied properly... but your log looked good... if you're in the NC area, I'm out here on businesss and could help you out ;)

Offline TommydCat

  • Newbie
  • Posts: 9
Re: Toshiba MK30186A 30GB
« Reply #12 on: April 18, 2006, 04:23:10 am »
I'll try that (removing the force* files from the root directory).  I might not get a lot of time to play with it for the next few days, though.

I'm basically more at the point of curiosity of why it's not working rather than caring that it doesn't work - I'll just buy a new proven drive to use instead of this one if I really get serious ;)

I'm in the Seattle area, so not even close, but I do appreciate your help and ongoing work for the project!

(Note, I hijacked this thread, but haven't heard back from the OP  ;D)
« Last Edit: April 18, 2006, 04:25:27 am by TommydCat »

Offline TommydCat

  • Newbie
  • Posts: 9
Re: Toshiba MK30186A 30GB
« Reply #13 on: April 20, 2006, 05:05:21 am »
Quote
BTW: the drive looks fine, I'd cleaning off the PHTSYS partition (quick-format in windows is fine as long as you keep label) and reloading firmware on it from PMM

Booyah!  Apparently the keg didn't like the file system.  Quick format and reload and it's working! :)
How does the utility ISO make the filesystem?  Just dd'ing the partition or something?  (Wondering if the geometry threw it off or something).

Thanks for the help, greatly appreciated.  I'll be looking to make a contribution in a few paychecks  8-)

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Toshiba MK30186A 30GB
« Reply #14 on: April 20, 2006, 12:54:52 pm »
I suspect it wasn't so much the FS as some file somewhere on the FS being corrupted

It makes the FS with mkdosfs, then copies over all the files from the old DMS.   It shouldn't have problems like you had ;)

Offline typeoserv

  • Newbie
  • Posts: 8
Re: Toshiba MK30186A 30GB
« Reply #15 on: April 26, 2006, 12:10:51 am »
my 30GB looks like this

 Disk /dev/sda: 28615 cylinders, 64 heads, 32 sectors/track
Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from 0
 
   Device       Boot       Start      End      #cyls      #blocks      Id  System
/dev/sda1         1     64      64      65536    b              Win95 FAT32
/dev/sda2         65      28614   28550   29235200 5            Extended
/dev/sda3          0      -       0          0     0            Empty
/dev/sda4          0      -       0          0          0            Empty
/dev/sda5         65+      28614   28550-  29235199+ b              Win95 FAT32

the the box is goota be hacked by now, ive left the origional DMS with the hack on it in the box for the past 2 weeks, getting the hacked message everytime

Offline typeoserv

  • Newbie
  • Posts: 8
Re: Toshiba MK30186A 30GB
« Reply #16 on: April 26, 2006, 12:12:55 am »
tried quick formating the dms agin, still no luck...


Offline typeoserv

  • Newbie
  • Posts: 8
Re: Toshiba MK30186A 30GB
« Reply #17 on: May 31, 2006, 04:12:57 am »
bootload.log:
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: Successful

PatchVerify.log:
Starting Patch Process
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!

patch.log:

: 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: 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

Offline typeoserv

  • Newbie
  • Posts: 8
Re: Toshiba MK30186A 30GB
« Reply #18 on: May 31, 2006, 04:14:33 am »
dmesg.log:

Linux version 2.4.18-rmk3-crypt1 (vince@beach.hq.phatnoise.com) (gcc version 2.95.3 20010315 (release)) #8 Tue Nov 9 11:59:12 PST 2004
Processor: ARM ARM720T revision 2
Architecture: CL-7312 (Phatnoise v1.1)
Machine name is: CL-7312 (Phatnoise v1.1)
Param offset is: 0xC0023000
Tags  offset is: 0xC0023000
fixup_clep7312()
Converting old-style param struct to taglist
edb7211_map_io()
On node 0 totalpages: 4096
zone(0): 4096 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: init=/bin/bash
Relocating machine vectors to 0xffff0000
clps711x_init_irq() begin NR_IRQS = 128
clps711x_init_irq() end
clps711x_setup_timer() SYSCON1 = 0xff000100 adding TC2S and TC2M bits
clps711x_setup_timer() SYSCON1 = 0xff0001c0
clps711x_setup_timer() SYSCON2 = 0xff000100
clps711x_setup_timer() SYSCON3 = 0xff000026
Calibrating delay loop... 36.65 BogoMIPS
initrd_start = 0xC0C00000
Memory: 16MB = 16MB total
Memory: 11952KB available (711K code, 2229K data, 44K init)
Dentry-cache hash table entries: 2048 (order: 2, 16384 bytes)
Inode-cache hash table entries: 1024 (order: 1, 8192 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
ttyAM0 at I/O 0x100 (irq = 12) is a CLPS711x
ttyAM1 at I/O 0x1100 (irq = 28) is a CLPS711x
pty: 256 Unix98 ptys configured
block: 64 slots per queue, batch=16
RAMDISK driver initialized: 16 RAM disks of 1048576K size 1024 blocksize
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
PhatNoise ide_init_default_hwifs()
IO_SYSCON1 = 0x000401C0
IO_SYSCON2 = 0x00040100
IO_SYSCON3 = 0x00040026
IO_MEMCFG1 = 0x00000080
IO_MEMCFG2 = 0xFFFDBD00
hda: PhatNoise DMS 10GB, ATA DISK drive
ide0 at 0xfe100000-0xfe100007,0xfe10000e on irq 6
hda: 19640880 sectors (10056 MB), CHS=19485/16/63
Partition check:
 hda: hda1 hda2 < hda5 >
DAI: Version 1.2
DAI: major 14
DAI: dai_init() initializing stuff
DAI: regs.ARM_ip = 0xff002000
DAI: dai_init() setting fiq handler
FIQ: copying code to 0xFFFF001C
DAI: dai_init() SYSCON1 (0x000401c0)
DAI: dai_init() SYSCON2 (0x00040100)
DAI: dai_init() SYSCON3 (0x00040026)
DAI: dai_init() INTMR1  (0x00040240)
DAI: dai_init() INTMR2  (0x00040000)
DAI: dai_init() INTMR3  (0x00040000)
DAI: dai_init() DAISR   (0x00001505)
DAI: dai_init() DAI64FS (0x00000000)
DAI: dai_init() setting PE.1
DAI: dai_init() setting DAI Control Register
DAI: dai_init() clearing DAI status register bits
DAI: dai_init() setting DAIR_DAIEN
DAI: dai_init() DAISR = 0x00009a00
DAI: dai_init() adding routine to task queue
DAI: dai_init() enabling DAI interrupt
PhatNoise Board v1.1
LED: major 13
DAC Killer: major 0
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Fast Floating Point Emulator V0.9 (c) Peter Teichmann.
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 400 blocks [1 disk] into ram disk... |
/
-
\
|
/
-
\
|
/
-
\
|
/
-
\
|
/
-
\
|
/
-
\
|
done.
Freeing initrd memory: 1024K
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 44K



THose are the logs from the origional DMS...
I've reloaded again and agin, reformated the 30gb in the hack console, re-partitioned.
the 30GB is still not working, no logs show up on that drive.. can someone PLEASE give me a clue????
« Last Edit: May 31, 2006, 04:18:53 am by typeoserv »

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Toshiba MK30186A 30GB
« Reply #19 on: May 31, 2006, 01:40:27 pm »
did you manually create the bootload.log file on the new non working DMS to see if its even recognizing the drive?