[Solved]: Looking for help: iRiver H140 with Toshiba MK2431GAH

[iRiverer]

Thx for looking.

After your post, I downloaded gparted, and checked for myself that my drive also has sector size 512. But I could remember that I set somewhere size 4096. So I startet fat32 formatter to look, and I recognized I used a complete different program called Windows Disk Management before. D'oh, how stupid of me!
I checked with a very small file in the rockbox folder, it has size 300 bytes, but on the drive it reserves 32kb. Very strange, perhaps you are right and this has something to do with the slow copying and the not correct settings.
The broken joystick navigation on the other seems really to be a hardware malfunction, cause I checked with the original firmware, there I have the same problems

At the moment, I'm reformating with fat32 formatter. Then I have to restore the old backup and copy the missing files.
It will consume some hours again, but if then I can use my iRiver again (even with a malfunctioning joystick) I'm satisfied.

[iRiverer]

Well, after a very long weekend with formating, restoring and recopying for hours and hours, I think I have my iRiver in a status where the settings actually take effect, but as I assumed, the joystick doesn't work correctly.

I think I will keep it this way for now. Perhaps after a little time I will buy an old H140 or H120 from ebay and install my drive to that one to get a device with a working joystick.

[DTSyX]

I have some new information that others, that modded their H1X0 the same way I did, might find interesting.

First regarding the problem that iRiverer was experiencing regarding transfer speed (or shall I say slowness). Even though I haven't experienced that slow transfer speed as iRiverer did, I also have the feeling that the transfer speed of the H140-MK2431GAH combination is lower that with the original setup. I've found some information about the probable cause. But I haven't solved the problem yet because I have no experience in doing such operations, don't even know if I would have all the necessary tools and - most of all - don't really understand yet, what parts they are really talking about, because I find two of the members talking of different parts for the solution. I have to asked them first before I can even think of trying to fiddle around with that problem.
But here are the links:

The general rockbox wiki regarding that problem:

http://www.rockbox.org/wiki/UDMAonUSB


The thread regarding the probable solution:

http://forums.rockbox.org/index.php?topic=20402.0





The second information I wanted to share involving the H140-MK2431GAH combination is as follows.

I updated to the latest rockbox version (3.10, from 3.9.1) using rockbox utility. As I got used to the process was slow but - seemingly - sucessful. When done and pulling the usb cable the system told me to restart/reboot as the system had been updated. I pressed the respective buttom (I think it was the joystick) and the system rebooted (though I think it was not a complete booting process all the from the "normal" beginning), no problems here.
But when I shut the player down later and started it again, I got an error message telling me that the checksum of the "firmware" was not correct and the player booted the original iriver os.

See attached pictures. Also note that the model name is cryptic.
I found a thread where someone describes a similar problem with his ipod:

http://forums.rockbox.org/index.php?topic=29689.0


I tried several things, including renaming the '.iriver' folder and "installing" rockbox (3.9.1 and 3.10, respectively) anew. When booting the error message now was 'file not found' (I guess rockbox.iriver was meant). Anyway, the player was 'broken'. When changing to the original hdd of the player, the player started whithout any problem. So it was purely a problem of the hdd (file system, file table, whatever).

I ran chkdsk /r /f. No errors found, nothing changed.

So I pulled out the bazooka: I copied all needed files to another hdd and formatted the 240GB-hdd using fat32formatter completely, meaning not using the quick format option. That obviously took some time, but after reinstalling rockbox 3.10 the player started as usually.

So, when it comes to the H140-MK2431GAH combination, it works but it apparently has it flaws one has to live with, at least using the setup decribed in this thread above.

Other than that I had no problems in the daily use of this H140 mod - using .flac and .ogg, respectively.


[Edit]:
Though rockbox 3.10 generally worked with my iriver mod, it didn't want to play a larger .ogg file and froze every time when I tried to play it. So I switched back to rockbox 3.9.1 which instantly played this file.

So, as an information for all users with the same or a similar iriver mod, you might want to save yourself some time and stay with 3.9.1 in the first place.

I want to remind you that the problems I decribe most probably originate from the bootloader 7 pre 4 that is essential to be able to run a big hdd like Toshiba MK2431GAH on the iriver H140. So, no rockbox 3.10 bashing here. I acutally like(d) the new sleep timer implementation and features in 3.10 better...
 
 
 
[Edit 08.12.2012]

As I found out today, the problem with updating Rockbox on a modified H140 (at least the kind I have) - meaning no successful update unless one formats the whole disc and starts anew (otherwise 'bad checksum error' when trying to boot) - only occurs when trying to update from 3.9.1 (maybe also "and before") to 3.10 and higher. Updating (or downgrading) from 3.10 (and higher) to any version from 3.10 on works as usual by simply extracting the .zip file or using Rockbix Utiliy, meaing just overriding the files. So, no hassles with switching Rockbox versions from 3.10 on.
I haven't noticed that before because I always started with 3.9.1 when trying to update to 3.10, 3.11.2 and 3.12.
 
[Edit 17.01.2013]
 
Regarding the problem mentioned just above. It seems to be a problem of either the bootloader 7 pre 4 or the 240GB hdd drive. I can up- and downgrade between the different Rockbox versions as I please as long as I haven't filled the drive with all my music. If the hdd is filled up (with my H140 there a 5GB free) the mentioned bad checksum error occurs and can only be "healed" by formatting the drive and start anew.
I even checked, if after a version upgrade on a filled hdd there would be some heavy fragmenting going on that prevents some important rockbox files from beeing loaded during the boot process. But it looked ok, no fragmentation within the rockbox files.
Strange bug...

[Uwe Z]

Hi all,
just wanted to express my sincere thanks for the incredible help this thread provided in upgrading my H140 to a 240gb Toshiba MK2431!!
For years I dreamt of getting all my music on my H140 and now I finally succeded!!!
- Flash the bootloader with the 7pre4,  make a copy of the files on the old hard drive, take the old hd out, put in the new one connect via USB to laptop, create a fat32 partition  with free MiniTool Partition Wizard, copy the whole directory of the old hd on the formatted drive, DONE!
Slam dunk!
For the next years or decades I got enough storage space (I hope  )
Kudos to those who tried and tried and who were bold enough to take the risk of briking their H140.

[Uwe Z]

Hi All,
thought everythings perfect but after I copied all my music files on the new HD I observe some problems. Upfront before I go into details:
- folders structure "A-Z" and as subdirectories "Artist" and subdirectory "Albums"
- total: 151GB in 27000 files and 2600 folders
2 problems 
A)After I copied the files and intialized the database about 16000 files were imported into the data base which took very long but ok I can wait.
But it stopped which results in an ncomplete database!In the "developers section" under "System" "View database info" I can see the 100% progress are reached after the letter L which equaly to the 16k files.
B) If i browse through the "Files" there are no files ("Artists" and Albums" and no "songs" displayed after the letter "L"
I checked all settings but the only one which I think may have an influence is the directory cache: enabled and the max number of files per directory set to max = 10000 files.
If I connect the H140 to the laptop via USB all of the Artists, Albums and Songs are there! I can even play them on the laptop using for example VLC player.
Questions:
- has anybody experienced this before and if yes how to solve
- is there a wrong setting on my H140?
- or is there a general Rockbox restriction which doesnt allow to load more than 16k files?
- do I need to change the file structure for example just put all "Artist" folders in the top level?
I am not sure if this post is in the right forum section but it is certainly related to the H140 and the use of the 240gb HD.
Thanks for your HELP!

[gevaerts]

Hi All,
thought everythings perfect but after I copied all my music files on the new HD I observe some problems. Upfront before I go into details:
- folders structure "A-Z" and as subdirectories "Artist" and subdirectory "Albums"
- total: 151GB in 27000 files and 2600 folders
2 problems 
A)After I copied the files and intialized the database about 16000 files were imported into the data base which took very long but ok I can wait.
But it stopped which results in an ncomplete database!In the "developers section" under "System" "View database info" I can see the 100% progress are reached after the letter L which equaly to the 16k files.
B) If i browse through the "Files" there are no files ("Artists" and Albums" and no "songs" displayed after the letter "L"
I checked all settings but the only one which I think may have an influence is the directory cache: enabled and the max number of files per directory set to max = 10000 files.
If I connect the H140 to the laptop via USB all of the Artists, Albums and Songs are there! I can even play them on the laptop using for example VLC player.

I'm going to concentrate on this one. If you can't get at the files from the file browser, the database won't get at them either.

Questions:
- has anybody experienced this before and if yes how to solve
- is there a wrong setting on my H140?

I don't think so, but maybe you're hitting a bug. Can you try disabling the directory cache (in Settings->System->Disk) to see what happens? I wouldn't be surprised if that helps (although it comes at a price, file browsing will feel slower, the directory cache is there for a reason...). If that makes a difference, we can investigate more.

- or is there a general Rockbox restriction which doesnt allow to load more than 16k files?

No. In fact, 27000 files isn't *that* many. People who enjoy chiptunes routinely have twice as many.

There is a (configurable) limits for the maximum number of files per directory (as you noted), but from your description of your directory structure that can't be it.

- do I need to change the file structure for example just put all "Artist" folders in the top level?

No. Your setup sounds entirely reasonable to me.

[Uwe Z]

Gevaerts, thanks for your quick response.
I agree it sounds logic to me that if the files are not accesible the database wont find either.
Yesterday evening after my post I did delete Rockbox and installed again and until I started to initialize the data base all files were there! Then I did run the database over night but when I started agin this morning there was an error on the database and the files are gone again. Today I tried with dir cache on and off ....no difference. What I saw today as well was for the first time when I start a short message is displayed: "filetype array full".
Deinstalled/installed  Rockbox again but no luck , files are not there.... and even worse now the ones which are there dont play if I open them. A quick message flashes saying "codec failed".
 FYi rockbox version r23925-091211.
I am lost. No clue what to do. I am getting desperate.

[Uwe Z]

Additional info: just installed developers version a2ab22e-130121 and to my surprise the files are there!!! Did not dare to start database...But once I turn off and restart r23925-091211 is back on  . and the files do not show again!
I was not able to install the a.... version again using Rockbox Utility or by extracting after deleting the rockbox folder.
Strange....

[Uwe Z]

I found a solution!
With bootloader 7pre4 and starting from disc image (NOT from RAM or ROM image!!) i can run the last development build a2ab22e and with this system ALL files show and also the database builds up without causing any trouble!
But as soonas I start from ROM or RAM image suddenly stable build r.... = 3.12 is mounted aagain and this build does not take more files thn 16k.
This version is even on when I delete the rockbox folder!
Why this is the case is a mystery to me but I dont really care because I got it fixed! However I would still like to understand ....

[bluebrother]

But as soonas I start from ROM or RAM image suddenly stable build r.... = 3.12 is mounted aagain and this build does not take more files thn 16k.
This version is even on when I delete the rockbox folder!

Sure, since it is in flash memory, not on disk. Have you actually updated the flashed Rockbox after updating?

Also, a flashed Rockbox still loads some files from disk (like the codecs). If you update the build on the disk to a development version but don't update the flashed Rockbox you will get a mismatch, resulting in "codec error"s and the like.

[Uwe Z]

Thanks Bluebrother,
Not sure about the flashing procedure. I flashed it with 7pre4 and I think you are right I still had the stable build 3.12 on the disc. That makes sense.
So that means I should flash again with 7pre4??
(I will go through the procedure again but I am not sure as right now EVERYTHING works perfect. Database did build up, files are all there, themes are set ..... Nothing to complain about. Just happy. But if I do a reset I have to avoid starting from ROM or RAM image.)
Any risk involved with flashing 7pre4 and having the development build on the disc?


 

[Uwe Z]

Questions answered!
I just did it: flashed rombox.river and rockbox.iriver using iriver_flash plugin  .....SUCCESS! .
Restarted from ROM image ....done!
This made my day . Now I am set for future travel.....see picture!
Thanks to the Rockbox team!

[DTSyX]

Just as FYI and future reference:

I stepped away from using FAT32formatter because I think it might had something to do with my ssd having died off after about 2,5 years (= several Rockbox updates = several ssd reformats).

I think it's the bootloader (7pre4) that forces me to format and reinstall the whole disk every time I want to do an Rockbox update - even if I go back to the version that was on the disk before I get an checksum error at boot time.


[edit August 21st 2017]

Seems like others experience the same problem (see comment section of the linked site). Also, it might be that this problem affects only certain rockbox (main) releases:

https://www.rockbox.org/tracker/task/12769?string=h140&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=

[/edit]


And as the FAT32formatter seems to work "with brute force" (initialising disk) or maybe it's the sector size of 512 bytes it's using one sometimes has to tried a few times until the disk is finally formatted correctly.

Since I found out about the new main release of Rockbox (3.14) I did this procedure all over again and the ssd was reaction slowly afterward I got the feeling the FAT32formatter "did it again".

I also "updated" my 240GB hdd (as backup). But with that one I used the FAT32format (guiformat) tool (http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm). That proposes 32768 which work fine, too (the H140 boots).
I just found out that that's not 32768 bytes per sector but 512 bytes per sector * 64 sectors per cluster - so it's bytes per cluster. The program says allocation unit size. I thought that was bytes per sector because one can also choose 512 - my bad.
Anyway - I feel more comfortable using the FAT32format (guiformat) than the FAT32Formatter for now.

And thinking about that having to reformat every time I update Rockbox I came across https://www.rockbox.org/wiki/IriverFlashing (and http://www.rockbox.org/twiki/bin/view/Main/RoLo). I think I visited that page a few years back and fiddled with my H140. So, I thought maybe I flashed my H140 but never updated the flash version after updating the files on the disk. But as it turns out I never did it right, so I never actually flashed my H140.

So, this time I actually flashed my H140. But if you do so, please do NOT forget to do a backup = ROM dump first! I somehow missed it and would have been screwed (kind of) if I didn't have a backup H140 with which I could do a dump that also worked on my first H140. So I could reverse everything and start from scratch.

But now I'm booting from ROM. That's not only faster but I think I can bypass the having to re-format etc. with every update. Because now I just update the flash and ROM immediately after (as in before reboot) the Rockbox update and should be fine with subsequent reboots - no more checksum errors as I don't boot from disk anymore.
At least that's what I'm thinking and hoping. :-)

[TheHistorian]

I had attempted to get the 240GB drive working in my H140 five years ago. I ended up with an unusable player, got frustrated, stuck it in a drawer, and mostly ignored music while enjoying other things.

This weekend I was inspired to take a look at it, found your recent post, and after charging, was back up and running in a few minutes! You made my year - thank you!

Just as FYI and future reference:

I stepped away from using FAT32formatter because I think it might had something to do with my ssd having died off after about 2,5 years (= several Rockbox updates = several ssd reformats).

I think it's the bootloader (7pre4) that forces me to format and reinstall the whole disk every time I want to do an Rockbox update - even if I go back to the version that was on the disk before I get an checksum error at boot time.


[edit August 21st 2017]

Seems like others experience the same problem (see comment section of the linked site). Also, it might be that this problem affects only certain rockbox (main) releases:

https://www.rockbox.org/tracker/task/12769?string=h140&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=

[/edit]


And as the FAT32formatter seems to work "with brute force" (initialising disk) or maybe it's the sector size of 512 bytes it's using one sometimes has to tried a few times until the disk is finally formatted correctly.

Since I found out about the new main release of Rockbox (3.14) I did this procedure all over again and the ssd was reaction slowly afterward I got the feeling the FAT32formatter "did it again".

I also "updated" my 240GB hdd (as backup). But with that one I used the FAT32format (guiformat) tool (http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm). That proposes 32768 which work fine, too (the H140 boots).
I just found out that that's not 32768 bytes per sector but 512 bytes per sector * 64 sectors per cluster - so it's bytes per cluster. The program says allocation unit size. I thought that was bytes per sector because one can also choose 512 - my bad.
Anyway - I feel more comfortable using the FAT32format (guiformat) than the FAT32Formatter for now.

And thinking about that having to reformat every time I update Rockbox I came across https://www.rockbox.org/wiki/IriverFlashing (and http://www.rockbox.org/twiki/bin/view/Main/RoLo). I think I visited that page a few years back and fiddled with my H140. So, I thought maybe I flashed my H140 but never updated the flash version after updating the files on the disk. But as it turns out I never did it right, so I never actually flashed my H140.

So, this time I actually flashed my H140. But if you do so, please do NOT forget to do a backup = ROM dump first! I somehow missed it and would have been screwed (kind of) if I didn't have a backup H140 with which I could do a dump that also worked on my first H140. So I could reverse everything and start from scratch.

But now I'm booting from ROM. That's not only faster but I think I can bypass the having to re-format etc. with every update. Because now I just update the flash and ROM immediately after (as in before reboot) the Rockbox update and should be fine with subsequent reboots - no more checksum errors as I don't boot from disk anymore.
At least that's what I'm thinking and hoping. :-)