Bad Free Space Map
Chris C. (2322) 174 posts |
Hey guys What causes the bad free space map error? It usually happens when copying files from large SparkFS archives and sometimes by just copying large files around the filecore disk. Usually I can work around by copying the archive to a FAT32 disk opening it and copying the files in the archive to the filecore disk. Could it be from the way I prepared my filecore SD card? I pretty much accepted all defaults on my 64GB card not knowing any better. |
George T. Greenfield (154) 716 posts |
You may find DiscKnight helpful: it’s a filecore-format (and other) disc checker and repairer, and you can get it here https://armclub.org.uk/products/discknight/ I personally find it indispensible (currently using RISC OS on a Pi3). The app is straightforward to use but come back if you have any issues with it. |
Rick Murray (539) 13393 posts |
Try a better power supply, or better quality cable. I used to have numerous problems with SD cards; however after switching to a chunky five port power brick and using the cable that come with my phone (which in day charge mode pulls an amp and a half at 9V), all the problems went away. Don’t rely upon the rainbow square to say the Pi is underpowered. SD cards, in my experience, are a lot more sensitive than the computer itself. Aaaand, not to mention my second big soap box rant (after awful support for non Latin languages) is that the filing system is generally “fragile” and has exactly zero hope of fixing itself (*CheckMap only reports, any other functionality is a lie; you’re SOL if you hit a broken directory; and I’m sure there are numerous fundamental flaws that DiscKnight can spot that the FS itself couldn’t; and don’t even think *Defect does anything useful these days) relying on third party software in order to fix a damaged filesystem… So, check the power. Extracting big files from archives or copying stuff around is what puts the most stress on the SD card (remember, flash devices are not sector based like a harddisc; the underlying flash would likely need to be erased and reprogrammed in blocks and the size of a block is typically between 32K and 128K, maybe more with BIG media) so these are the times when restricted power will bite. |
nemo (145) 2437 posts |
Whatever happened to fsck? I remember that being useful. |
David Pitt (3386) 1248 posts |
Not a lot. Shareware, fiver. 26bit. http://www.filebase.org.uk/software/filer/134 |
Chris C. (2322) 174 posts |
I do own DiscKnight. I use a nice 5V 2A power supply for it. When I run DiscKnight no errors are found. I see it happen on my PandaBoard, Pi and BeagleBoard XM. |