[Q] Boot problem LOST.FOUND

6 posts
Thanks Meter: 0
By Montaxx, Junior Member on 31st July 2014, 11:42 AM
Post Reply Subscribe to Thread Email Thread
Hey Guys,

I have a Android/WinCE Car Radio.
So I got Android on a SD Card and it booted well, but one day it stopped booting.
If I mount the SD from the internal Android on the device, there is a LOST.FOUND directory on the boot partition where boot.scr and so on is.
If I delete the directory and restart, the system boots from the SD again. But if I do a restart, the system won't boot again. I need to delete the LOST.FOUND directory every time...
I'll Attach the boot partition, maybe you can give me a solution to this.
Attached Files
File Type: rar boot.rar - [Click for QR Code] (3.99 MB, 11 views)
Last edited by Montaxx; 31st July 2014 at 11:52 AM.
1st August 2014, 08:31 AM |#2  
OP Junior Member
Thanks Meter: 0
1st August 2014, 10:02 AM |#3  
Junior Member
Thanks Meter: 0

If you run fsck, the filesystem check and repair command, it might find data fragments that are not referenced anywhere in the filesystem. In particular, fsck might find data that looks like a complete file but doesn't have a name on the system — an inode with no corresponding file name. This data is still using up space, but it isn't accessible by any normal means.

If you tell fsck to repair the filesystem, it will turn these almost-deleted files back into files. The thing is, the file had a name and location once, but that information is no longer available. So fsck deposits the file in a specific directory, called lost+found (after lost and found property).

Files that appear in lost+found are typically files that were already unlinked (i.e. their name had been erased) but still opened by some process (so the data wasn't erased yet) when the system halted suddenly (kernel panic or power failure). If that's all that happened, these files were slated for deletion anyway, you don't need to care about them.

Files can also appear in lost+found because the filesystem was in an inconsistent state due to a software or hardware bug. If that's the case, it's a way for you to find files that were lost but that the system repair managed to salvage. The files may or may not contain useful data, and even if they do they may be incomplete or out of date; it all depends how bad the filesystem damage was.

Make sure your boot files in the root of the partition are ok.
Make a backup of the files, copy the files in the lost.found directory over the existing files or use the original one (firmware download from device supplier?)
And make sure you unmount the SDcard safe.

Good luck..
Last edited by Elkan1985; 1st August 2014 at 10:14 AM. Reason: double rules.
1st August 2014, 11:36 AM |#4  
OP Junior Member
Thanks Meter: 0
THere are no files at the LOST.FOUND directory.

If I take a other SD and put the stock image on it, it's the same problem.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes