Support and General Use > User Interface and Voice

Description of icons?

<< < (3/3)

saratoga:

--- Quote from: Fraoch on November 27, 2011, 04:39:29 PM ---Is there a utility that checks Rockbox's file system for errors then? 

--- End quote ---

Built into your PC's operating system, yes. 

Fraoch:
Ah.  I checked it using Ubuntu's "Disk Utility" program - it indicated the file system was clean.

There were two partitions - a 99 MB partition and a 4.0 GB partition.  I could only check the 4.0 GB partition as the 99 MB partition does not have a recognized format.  The 4.0 GB partition is formatted as FAT32 (as expected) and it can be checked.

fsck (Linux's command-line file checking utility) reported a tiny error, but again was not able to check the 99 MB file system - the 99 MB partition was /dev/sdd1 and the 4.0 GB partition was /dev/sdd2:


--- Code: ---fsck from util-linux 2.19.1
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdd1

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

mark@Sauron:~$ sudo fsck /dev/sdd2
fsck from util-linux 2.19.1
dosfsck 3.0.9, 31 Jan 2010, FAT32, LFN
/Playlists
 Start does point to root directory. Deleting dir.
/metadata.log
  File size is 336 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
Reclaimed 10 unused clusters (40960 bytes).
Free cluster summary wrong (0 vs. really 10)
1) Correct
2) Don't correct
? 1
Leaving file system unchanged.
/dev/sdd2: 1429 files, 965220/965230 clusters
--- End code ---

I did try to correct the small error - it didn't seem to have an effect because fsck reported "Leaving file system unchanged" despite my request to correct.

Oh...looking at fsck, I think I see why the metadata log file is corrupted.  I filled up the 4.0 GB completely, there's no empty space to write the log file.  Oops.

I'll delete a track, rescan the database and try to write the log file again.  For that matter, I'm thinking it's unwise to leave the device with 0 B of free space...

Again, thanks!

saratoga:
Theres no point in trying to generate a log file from a corrupt file system.  Its just going to contain nonsense. 

Fraoch:

--- Quote from: Fraoch on November 27, 2011, 05:27:42 PM ---For that matter, I'm thinking it's unwise to leave the device with 0 B of free space...
--- End quote ---

Well that was the key.  I deleted a small track, initialized the database and Rockbox took off like a rocket, finding ~4000 files in about 30 seconds.  Then it slowed down and took a second or so to find each file.  I think it was using some sort of temp space or filling up the log file and it ran out of file space again.

I deleted a much longer track, leaving about 7 MB of space free.  This time it found something like 13 000 files in about a minute and advised a reboot to enable (never seen that before!)  I rebooted and got a "Commiting database X/9" popup and got into Rockbox after X got to 9 (took a minute).

The database works perfectly now!

Thanks for all the help.  I apologize for the noobishness.

Note to others...leaving ~0 bytes of storage space free is a bad idea. :-[

Navigation

[0] Message Index

[*] Previous page