Can't transfer my recordings via USB to the Mac

[nslhrn]

For some reason, when I record, I can't move the recordings from the iRiver to the Mac. I used to be able to do it with no porblem but now, on files larger than 30 or 40MB, the iRiver hangs and I get some kind of I/O error.

If I double click on the file in the broswer and play it in Quicktime, I can jump to any section but if I try any method of getting the file of the iriver, I'm stuck.

Anybody have this issue? How do I solve it? Makes it really difficult to do what I want to do. The REP is the reason I have Rockbox on the iRiver-to monitor recordings and be able to edit the files on my computer. I would think the transferring would be simple. Any ideas.

Oh, I've been having the problem for 1 year, I almost stopped using my iRiver because of this. I've had the iRiver for about 4 years, ihp 120-the first one. battery life is getting significantly lower.

THANKS!

[petur]

this sounds like harddisk corruption.

When connecting via USB, rockbox is not involved, everything is done in hardware. So if rockbox does something wrong, it has to be during the creation of the file.

Things to try:
- chkdsk/scandisk the player
- try the same with just dummy files (copy to player and back)
- backup, format the disk and restore the files and try again

[nslhrn]

OK. When I try to back up the disc, I can't because of the same stoppage. I'm on a mac. The disk utilities for MAC don't complete. I''l try my wifes windows PC.

 My only work around is to open the individual files with quicktime, copy them(which puts the file  in RAM, export them as a .wav or .mp3 file. Of course, with the number recordings I make each week, this is expensive to my time and schedule.


This also happens with files I drag and drop to the unit. So, if I've riped a CD and plaed it on the iRiver, sometimes I can't those to transport back to my computer.  Portions will transfer but there will be a hang. Some FOlders, no problem. I'd say 3 of every 5 folders I try to export to the computer hangs up. Most of my recorxings hang up.

I wonder if this has to do with disc speed type issues.  As if, the computer is requesting information to quickly or something and the slow iRiver drive can't keep up. (Can't you tell I nkow nothign about computers)

[gnu]

No, it's not the disk speed.
I'd guess that your disk is corrupted - run a chkdsk!

[nslhrn]

OK. I'll run the scndsk BUT I don't know how. I use a mac 99% of my life.
I'm here with  Windows all fired up and the drive attached. Now what?

Thanks again.

[petur]

2 options:
1) right-click the drive in explorer, select Properties, then the Tools tab
2) open a commandline box (Start->run program and type cmd) and type chkdsk : /f  (example chkdsk F: /f)

The latter will give more info as the first is a gui just hiding the interesting stuff...

feel free to post the resulting output here

[nslhrn]

OK did that the only option that seems related to the scndsk is error check, the other options are defrag and backup. So, I selected the error check. It's been running for about an hour in Phase II.

At least the iRiver is continuing to function during that long of a spin.

oooooohhh kaayyy. It ran for three hours then stopped " Erro check complete." Nothing more.
Transferring a 305 4 mb files is extremely slow for me and stopped about hald way throuhg.

Can/should the iRiver be defragged?

[gnu]

Why not?

[petur]

I wonder why you didn't go the dosbox route.
Did you tick the 'repair errors' checkbox?

Anyway, if your disk is corrupted and you start a defrag, you might as well do a format on it, it will have the same effect....

Another thing to check: h1x0 series sometimes suffer from a broken connection between motherboard and HDD. The normal symptoms are that the disk is not accessible at all, but it is still a thing to check. You would have to look for broken solderings on the daughterboard.

[nslhrn]

I don't know windows well enough to do that.  What is the dosbox.

[petur]

2) open a commandline box (Start->run program and type cmd) and type chkdsk : /f  (example chkdsk F: /f)

The latter will give more info as the first is a gui just hiding the interesting stuff...

feel free to post the resulting output here