160Gb Samsung only 4.77Gb possible on PHTDTA partition

[toophat]

Hello everybody, a few days ago I bought a Samsung HM160HC 160Gb drive on wich I put the system files with the PhatHack DMS Tools v2.12. Strangely I cannot put more than 4.77 Gb on the PHTDTA partition wich is formatted as FAT32 with 4097 bytes per cluster.
I ran already CHKDSK /f s: to repair it if that maybe was nessecerry on that S partition (PHTDTA) but it gives no solution. I have Windows XP Prof. SP2 on my PC wich is a Pentium 4 2.4Ghz.

Somebody have an idea??

[sbingner]

You need to use the DMS tools to format it -- windows won't format FAT32 properly

[toophat]

It's automatic formatted inside the PhatHack DMS Tools v2.12 which I used when I prepared the new Samsung. So I assume it must have done this OK.
Other suggestions?

[VorTechS]

Does the partition show correctly in windows 'Disk Management'.

The tools uses a 3rd party application to format the drive (mkdosfs), and assuming the partition size is showing up correct, I wonder if there is a bad block that the formatting tools cannot get past during formatting.  It is a complete disk check, and perhaps there's an option not being correctly specified in the formatting to bypass/mark bad blocks.

Sbingner: perhaps the above is something you might have come across before with this tool?

[toophat]

I Prepared the Samsung with the DMS Tools v2.10,  but again on the PHTDTA partitition I get the "Disk is Full" error. This is now after copying 634KB, very strange...
The DMS Tools v2.12 did not want partition the drive and the DMS Tools v2.12 program stops, that's the reason I used v2.10 but now with the 634KB barrier.
Here are the log files of mkdosfs.exe;
=================================
mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>
\\.\L: has 255 heads and 63 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 312450735 sectors;
file system has 2 32-bit FATs and 8 sectors per cluster.
FAT size is 304533 sectors, and provides 38980204 clusters.
Volume ID is 4a92833c, volume label PHTDTA     .

mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>
\\.\L: has 255 heads and 63 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 312450735 sectors;
file system has 2 32-bit FATs and 8 sectors per cluster.
FAT size is 304533 sectors, and provides 38980204 clusters.
Volume ID is 4a951063, volume label PHTDTA     .

mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>

mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>

mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>

mkdosfs.exe 2.8 (28 Feb 2001)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>

========================================
And this one is from the PHTSYS partition;

mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>
\\.\K: has 255 heads and 63 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 131072 sectors;
file system has 2 32-bit FATs and 1 sector per cluster.
FAT size is 1009 sectors, and provides 129022 clusters.
Volume ID is 4a928339, volume label PHTSYS     .

mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>
\\.\K: has 255 heads and 63 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 131072 sectors;
file system has 2 32-bit FATs and 1 sector per cluster.
FAT size is 1009 sectors, and provides 129022 clusters.
Volume ID is 4a95105f, volume label PHTSYS     .

mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>

mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>

mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>

mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>
\\.\L: has 255 heads and 63 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 131072 sectors;
file system has 2 32-bit FATs and 1 sector per cluster.
FAT size is 1009 sectors, and provides 129022 clusters.
Volume ID is 4a9f9b15, volume label PHTSYS     .

mkdosfs.exe 2.8 (28 Feb 2001)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>
=======================================

As you can see mkdosfs 2.8 accepted the formatting instead of v2.11 but now there is a limit of 634 Kb. How is that possible???
Nevertheless, windows 'Disk Management' reported both partitions as OK (PHTDTA 148.99GB and PHTSYS 64MB)

[toophat]

I wrote that I can only copy 634Kb to PHTDTA but that must be 634Mb...

[VorTechS]

I would definately use version 2.12 of the tools as previous versions will loose you a lot of space because of incorrect partition parameters (not as much as you are reporting though!)

You are already aware of the Logs directory, the DMS Tools uses the same as PhatHack Media Manager.  Clear out the logs directory and run version 2.12 of the tools. 

When the tools fire up, select 'Tools Mode', and then makesure your DMS appears in the drop down list.  If it doesn't. STOP!  Take a look in the logs dir and post a copy of anything here.  I can then take a look and see if the tools is picking up the disk, or if not, look at reasons why.


If your DMS IS in the dropdown, then select your firmware version, and whether or not you want to install the AAC plugin and if your box is not hacked also select the option to install non hacked' firmware.  Once you have selected the firmware version, the second set of toolbar buttons should enable themselves.  (A big mistake people make is not selecting a firmware version and then wondering why the tools won't let them do anything).

If the buttons are enabled, then hit the 'Create New DMS' button, which will wipe the existing partitions, re-create them and then run through the forma.  Version 2.12 of the tools has extensive logging.  So if there's a failure, we can take a look at the logs.  So again, if things don't work please attach the logs and I'll take a look.

As I know you are playing with PhatHack Media Manager, perhaps I can also look at integrating the tools with a view to getting a full resolution to your problem as I'm unable to work at patching up the old version of the tools at the moment.

[toophat]

I installed the Phathack Tools v2.12 and after selecting BMW firmware V9.00 and "Create New DMS" the program halted after a few minutes without partitioning it.
First it's searching for WMI, after that it says "formatting PHTDTA" (with extensive LED flashing on the DMS cradle, USB 2.0) and after one minute or so the message says; "Creating new DMS failed. Check log for more"

I think it's better to buy a Seagate ST9160821A 160GB next week, maybe it's not possible with this Samsung HM160HC 160Gb :-(
btw, my Phatbox is already hacked and another Seagate Momentus 5400.3 (ST9160821A) 160GB is working fine. The reason for buying the Samsung was that over about a half year or so it's maybe not possible anymore to get IDE drives...

So here are the logs but I think there is no special information in it,
maybe the logs from version 2.10 gives more information.

=======================================
Debug_PhtDta.txt
mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>

Debug_PhtSys.txt
mkdosfs.exe 2.11 (12 Mar 2005)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>

=======================================

[toophat]

I saw that there were two more log files in the My Documents folder!
These are much more interesting I think (the partitions are reported as 000 bytes). I Copied & Paste only the last session in it because they are several 100Kb. Here they are;

===================================
PhatHack_NewDMS_Log.txt


Win32_Drive List
----------------

      Starting device evaluation:
      Determining device signature...
      done.
   Disk ID: 0
   Disk Name: Maxtor 6Y160P0
   PnP Device: IDE\DISKMAXTOR_6Y160P0__________________________YAR41BW0\345938384252454E202020202020202020202020
   Disk Unique ID (not serial!): 56E32FD8

      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #0, Partition #0
      Drive: C:
      Serial #: 249F56BC




      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #0, Partition #1
      Drive: D:
      Serial #: 34BAD49C



      Partition: Disk #0, Partition #1
      Drive: E:
      Serial #: F0E4F92E



      Partition: Disk #0, Partition #1
      Drive: F:
      Serial #: 5C3757CD



      Partition: Disk #0, Partition #1
      Drive: G:
      Serial #: 46FC0DF3



      Partition: Disk #0, Partition #1
      Drive: H:
      Serial #: 8DF81C1A



      Device evaluation complete.
      Next device evaluation:
      Determining device signature...
      done.
   Disk ID: 1
   Disk Name: USB-HS SAMSUNG HM160HC USB Device
   PnP Device: USBSTOR\DISK&VEN_USB-HS&PROD_SAMSUNG_HM160HC&REV_0.01\6&24CC5769&0
   Disk Unique ID (not serial!): 16E32A50

      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      No logical disks available for device partitions.

      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      No logical disks available for device partitions.
      Device evaluation complete.
Checking mounted drives for disk...
...new disk mounts found successfully!
Checking available disk space...
...which is: 000 Bytes.
Checking available disk space...
...which is: 000 Bytes.

Preparing format parameters....
PHTSYS Arguments: -v -n PHTSYS -F 32 L: 0
PHTDTA Arguments: -v -n PHTDTA -F 32 K: 0
Formatting PHTSYS....
completed: Failed!.
Formatting PHTDTA....
completed: Failed!.

The new DMS preparation has failed.
Completion time: 15:11:32

===================================

Startup_Sequence.txt


Win32_Drive List
----------------

      Starting device evaluation:
      Determining device signature...
      done.
   Disk ID: 0
   Disk Name: Maxtor 6Y160P0
   PnP Device: IDE\DISKMAXTOR_6Y160P0__________________________YAR41BW0\345938384252454E202020202020202020202020
   Disk Unique ID (not serial!): 56E32FD8

      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #0, Partition #0
      Drive: C:
      Serial #: 249F56BC




      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #0, Partition #1
      Drive: D:
      Serial #: 34BAD49C



      Partition: Disk #0, Partition #1
      Drive: E:
      Serial #: F0E4F92E



      Partition: Disk #0, Partition #1
      Drive: F:
      Serial #: 5C3757CD



      Partition: Disk #0, Partition #1
      Drive: G:
      Serial #: 46FC0DF3



      Partition: Disk #0, Partition #1
      Drive: H:
      Serial #: 8DF81C1A



      Device evaluation complete.
      Next device evaluation:
      Determining device signature...
      done.
   Disk ID: 1
   Disk Name: USB-HS SAMSUNG HM160HC USB Device
   PnP Device: USBSTOR\DISK&VEN_USB-HS&PROD_SAMSUNG_HM160HC&REV_0.01\6&24CC5769&0
   Disk Unique ID (not serial!): 15002203

      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #1, Partition #0
      Drive: L:
      Serial #: 4A9FAB27




      Partitions List
      ---------------

      (Debugging: About to Query WMI for Logical Disks)

      (Debugging: ..Query Complete)
      Partition: Disk #1, Partition #1
      Drive: K:
      Serial #: 4A9FAB2B



      Device evaluation complete.
   Succeeded....enumerating devices....
      Device
         Checking device name for USB context...
         Not a USB labelled device.
      Device
         Checking device name for USB context...
         Not a USB labelled device.
      Device
         Checking device name for USB context...
         Evaluates to true!
         Also has drive letter!
      Device
         Checking device name for USB context...
         Evaluates to true!
         Also has drive letter!
   Device enumeration complete.

=================================================

[VorTechS]

Okay, don't give up just yet.  Use Computer Management -> Disk Management to wipe the existing partitions from the DMS.
Re-run the DMS tools.  Again, verify that your disk shows up, and try the create new DMS process.

Then, once the process completes/fails - let's see what the logs say.

To me, I think this is showing the Samsung drive has a problem.  If you have another spare 2.5" drive of any size (20, 40, 60GB), it would be interesting also to see if the DMS tools can partition and format these successfully.  If not, you may be looking at cradle issues.

[toophat]

Here I am again (after a week of hard work ;-)
I bought last week a Western Digital Scorpio WD 1200BEVE 120 GB drive and now the DMS Tools v2.12 worked perfect on this drive. Good FAT32 partitions and no strange messages from the logs.

After that I put the songs on it with Phatnoise Music Manager v2.36. It only give troubles with the Loquendo Gabriela voice (20 files the same test phrase, and sometimes a normal TTS fle). After installing another voice no problems at all. Its a total of 95 GB mp3's. So no problem anymore with only 4.77GB possible on the PHTDTA partition or even 634MB...
So after all the problem must be in the Samsung (HM160HC rev.A) or the fact that it's above the 120GB border.

QUESTION; has the DMS Tools v2.12 the lba48 Linux kernel already inside or do I have to copy it over the old kernel when I use a 160GB drive?

But now I'm very happy that it worked again and honestly, PMM v2.36 is not bad at all ;-)

[VorTechS]

The DMS tools detects whether it needs to update the linux kernel based on the disk size.
If you take a look in the logs, you should see a phrase appropriate to this.

But no, you don't need to do anything manually... it's all taken care of!

Glad you are up and running.

I presume the TTS issue occurs in PhatNoise Media Manager as well as PhatHack Media Manager?  If so, as I suggested previously, sounds like a bug / license issue with the Loquendo voices.