Panic for Clip + 7e3e9b9

[h8uthemost]

I just tried updating to build 7e3e9b9. And like always rockbox asked me if i wanted restart the device so it can update. Once it started though, there was the word Panic and a bunch of text under it. Then the device turned off. And now it won't turn back on.

Any advice?

EDIT: Actually I got the device to turn back on, but it won't get past the panic screen. Here's the text under the word Panic:

Code: [Select]

audio_reset_buffer
noalloc () : EOM (65536 > 0)
bt pc: 0x30036778, sp
A: 0x300367F4
A: 0x3003685C
Anyone know how to get past this, or how to roll back to a previous version?

Thanks.

EDIT AGAIN: Yeah... it definitely won't get passed the Panic screen. And I can't get the device to open up. I think the problem is that I downloaded and tried to do a manual install with an original firmware that wasn't already on my device. It looks like the latest OF is version # 01.02.16 and according to the Sansa thread that holds this firmware it came out in 02-07-2012.

I mean I'm not positive that is where the error is coming from though. It's just a guess. If this is the error though, is there anyway to fix this? Or am I screwed? Because right now it seems like my Clip + is basically bricked...

[saratoga]

Its probably just a corrupt file system crashing the disk cache.  Reboot into the sandisk firmware and then check the disk for errors.

Also, you don't actually have to reinstall the sandisk firmware to update rockbox.  Just copying a new build over will do that fine.

[h8uthemost]

Thanks saratoga. I was just going to post back to say I am able to boot into the OF. I totally forgot about that feature.  I removed the clppa.bin that i was using to update Rockbox, but I still get the Panic screen when I switch the device on.

Sorry for a noobish question, but how exactly to i check for disk errors on linux? I quick search mentioned something about dmesg? So I'm guessing you just cd to the location of the device and run dmesg?

Thanks for the help.

[AlexP]

dmesg prints the kernel message buffer, it can be useful for looking for errors that the kernel reports (i.e. cannot mount filesystem type of thing).

To check the filesystem you want "fsck.vfat"

[h8uthemost]

Ok, thank you Alex. I'll give that a shot.

Right now though all I'm wanting is to get Rockbox off my device so I can start over. I thought it would be as easy as either uninstalling it, or formatting the Clip+. But neither has worked. Everytime I start it I get greeted with the Rockbox screen, and then a File Not Found type of error. Then it goes to a Plug USB Cable screen.

I'll try fsck.vfat and see what that gives me though. Thank you.

EDIT: Ok, here is fsck gave me:

Code: [Select]

fsck /dev/sdb
fsck from util-linux-ng 2.17.2
dosfsck 3.0.9, 31 Jan 2010, FAT32, LFN
FATs differ but appear to be intact. Use which FAT ?
1) Use first FAT
2) Use second FAT
? 2
/SANSA CL.IPP
  Contains a free cluster (2). Assuming EOF.
/SANSA CL.IPP
  File size is 8 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/SYS_CONF.SYS
  Contains a free cluster (3). Assuming EOF.
/SYS_CONF.SYS
  File size is 320 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/##MUSIC#
  Contains a free cluster (4). Assuming EOF.
/##PORT#
  Contains a free cluster (5). Assuming EOF.
/MUSIC
  Contains a free cluster (6). Assuming EOF.
/RECORD
  Contains a free cluster (7). Assuming EOF.
/AUDIBLE
  Contains a free cluster (10). Assuming EOF.
/PODCASTS
  Contains a free cluster (11). Assuming EOF.
/AUDIOBOOKS
  Contains a free cluster (12). Assuming EOF.
/MTABLE.SYS
  Contains a free cluster (5697). Assuming EOF.
/MTABLE.SYS
  File size is 1862468 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/RES_INFO.SYS
  Contains a free cluster (5754). Assuming EOF.
/RES_INFO.SYS
  File size is 51237 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
Leaving file system unchanged.
/dev/sdb: 11 files, 0/59384 clusters
And that's when I pick FAT option number 2 when it asks. When I pick option 1 this is what terminal gives me:

Code: [Select]

fsck /dev/sdb
fsck from util-linux-ng 2.17.2
dosfsck 3.0.9, 31 Jan 2010, FAT32, LFN
FATs differ but appear to be intact. Use which FAT ?
1) Use first FAT
2) Use second FAT
? 1
Leaving file system unchanged.
/dev/sdb: 27 files, 5754/59384 clusters

Post Merge: May 04, 2012, 03:28:26 AMOk. I finally got it working. After I posted the above I reformatted the device once again, then i did another manual install(with a fresh. rockbox folder, not the one I've been using), and everything upgraded just fine.

Now, what do you guys think I should do if I run into this problem again? Within a year of using RB I never encountered this problem so I didn't know what to do. If I go to upgrade again and I get another Panic screen, should I reformat again and then try another manual install?