10/23/2011, 05:28 AM
You need to be prepared to run a few commands, because the advice given will depend on the output of those commands.
Originally Posted by 999faz
Since we are seeing messages like: Error Installing /lib/modules/2.6.35...
Then it's failing when installing the kernel modules and it's possible that your root filesystem is full or almost full. If that is the problem, it will almost certainly cause you more problems later, so you can't really ignore it.
If you were willing to run some commands, then the next two commands to run would be like I suggested in this thread...
These two commands should tell us something.
Here is the result on mine.
So the / (root) filesystem is about 80% full (which is o.k.)
# df -h /
Filesystem 1K-blocks Used Available Use% Mounted on
559.1M 444.1M 114.9M 79% /
If your one is closer to 100% that's a problem and we need to run the next command.
Next command (and result on mine).
You will note that in mine, the difference between those two results is 444.1MB - 427.7MB = 16.4MB which is about 3% of the total filesystem size. I'm not an expert, but I think that might be a reasonable amount of space for filesystem metadata. Metadata is information about the structure of the filesystem itself and that metadata is not stored in a file (so not seen by the 'du' command).
# du -xsh /
Now if your 'df' is suggesting your 559.1MB filesystem is near 100% full and 'du' is telling you that there is only about 430MB of files, then where did the extra 130MB come from?
Perhaps there might be something cached (but not held in a file), but a reboot should fix that. If the problem continues after a reboot, then I'm guessing your filesystem metadata got screwed up somehow (no, I don't know how), in which case you need to doctor.
How To Recover - WebOS Internals
If on the other hand, you tell me that both of the two commands report more than 500MB used (out of about 560MB total), then we might be able to find the cause... but I still think you might end up having to doctor.