Gigabeat F20 and SYSTEM ERROR 00000001

[tdrive]

Hi everybody!

I have a big problem with my Gigabeat F20. Perhaps, I made a brick. I have following symptoms:

- just one bar in the original GB progress bar (duration near 30 seconds)
- system error message (SYSTEM ERROR 00000001)
- original GB USB logo appears when player linked with a PC and then player stucks
- computer makes a sound like an USB device is connected but it cannot been seeing in the explorer as a logical drive. But when i go to Safely Remove Hardware properties, the system sees it as Toshiba HDD Audioplayer but no letter is being assigned to it (in MS Windows).

The same story with Mandriva Linux -- it see only a USB device, not a USB drive.

Anyone know what can possibly help me with my GB?

[AlexP]

What did you do to get to this state?  When you installed the rockbox bootloader, did you keep a backup of the files replaced?  What files are in the GBSYSTEM directory?  Details!

Nonetheless, if it is not a physical hard drive problem, you should be able to use the recovery trick to  put the correct files back:

http://www.rockbox.org/twiki/bin/view/Main/GigabeatFXPort#Gigabeat_Recovery_Procedures

[Phalangees]

Sounds like your missing one of the critical files that are checked for in boot up. I'm not sure why it's not letting you connect to USB properly. On the same page that BigBambi posted, if you scroll all the way down you should see a table with a few files in it. You need to get the GBSYSTEM.zip. That's got dummy files but it'll trick the "bios" of the gigabeat into booting. BigBambi is right, if you need to connect to USB, the recovery procedure might be your best bet to be able to check if you have all the files need.

[scharkalvin]

I noticed that I could not see the GB as a drive under Linux when I first got it with the OF UNTIL I went into the OF and set the connection to Gigabeat room.  This probably enabled USB storage mode in the boot flash?

[tdrive]

I use Rockbox on my GB since January 2007. Usually I have only official subversion of Rockbox with the latest bootloader from GigabeatFXPort page. Couple of times my GB freezed (on this words I mean that playback suddenly stops and Power button doesn't work, display light is off but you can see on dark screen WPS and title of track etc). Only On\Off switch helped me in this situations.

But on 21st of November I put EvilG release on GB (evilg-FX-20070914). After few days (2-3) my player stucked again. After On\Off manipulation I saw things that I descripted above. I don't think that EvilG release is guilty of my GB coma, but I don't know what to do... Perhaps, I must to do a surgery...

2scharkalvin: I can't go on OF in this circumstances.

[AlexP]

Hmmm,

Well as you know we don't support unofficial builds, but I can't see any way an unofficial build could do this.  The first thing we need to do is get it to mount so you can check the disk for errors and the presence of the bootloader files.  If you cannot get past the gigabeat boot screen, I think you will have to try the recovery process.

Once you have tried that, try running  fsck.vfat on it.

[tdrive]

2BigBambi: What do you mean "Once you have tried that, try running  fsck.vfat on it"?

[AlexP]

Sorry, my mistake I thought you said you were on linux.  I'll change it for windows!

Once you have done the recovery trick and hopefully managed to get the gigabeat connected to your computer with a drive letter, you should run chkdsk /f /r on it from a command prompt, which will check for disk corruption.  fsck.vfat is the linux version.

[psycho_maniac]

One way to get the thing to show uo on the computer is this MAKRE SURE THE PLAYER IS TURNED OFF

1. take the backplate off
2. disconnect the hd
3. connect the gigabeat to the computer
4. turn the gigabeat on
5. it SHOULD say error 000024(i think) and will go into emergency disk mode
6. now connect the hd and it will come up on the computer as a disk
7. now if you are missing the files in the gbsystem folder replace them
EDIT: this is on the wiki page that BigBambi linked to....sorry

might be a dumb thing but also check to see that the hd is fat32

[tdrive]

 Somehow I start formatting disk. About 30 minutes
HDD-Low-Level-Format-Tool
(http://hddguru.com/content/en/software/2006.04.12-HDD-Low-Level-Format-Tool/)
was not corresponding. Then it shows next message:

 Format Error occured at offset 0 (then 524 288, 1 048 576, 1 572
864...)

 Does it means that disk has physical problem?
 
 Now (after nearly 1.5 hours from the beginning) programm still looks like a frozen...

[christianqc]

Hi tdrive, I have the same problem right now...have you solved it???

[jmsunlinenet]

I have identical problem and would be interested to know if anyone has solved it. Bootsplash bar comes up partially, then disk drive goes "whrr, whrr, whrr..." and that is it.

I tried the recovery process, hot fix etc., but it does not show the disk in Windows Explorer, so that seemed like a dead end as I still cannot reload the firmware or read the hard drive.

I think maybe there is a physical disk problem.

Interestingly I looked at replacement disks. The hard drive is Toshiba MK4006GAH. Same disk drive as i-Pod. However it seems that you can get a refurbished F40 player on e-Bay for only a bit more than the cheapest drive I could find ($100 vs $70 inclusive of shipping).

Would be really interested if someone can crack this problem without replacing the player or drive.

[psycho_maniac]

Maybe somebody on the forums or IRC has an extra hd for the gigabeat

[AlexP]

The hard drive is Toshiba MK4006GAH. Same disk drive as i-Pod.

Be careful - different iPods use different style disks.  Check out the replacement disk page on the wiki.