View Single Post
Posts: 65 | Thanked: 113 times | Joined on Mar 2011 @ Austria
#297
Originally Posted by maacruz View Post
You simply have a damaged filesystem for whatever reason (sure you haven't a full filesystem?). DT has that shutdown issue which causes the filesystem not to be umounted when it happens, and ext2 doesn't act kindly if it is not unmounted, having a tendency to accumulate errors.
At my firsts attemps at boot from mmc, much before DT, I also ran into troubles with ext2 quite often.
The best sollution is to move to ext3, as the journal protects you from the usual problems that arise if the ext2 filesystem is not properly umounted.
To solve your problem now, boot into flash and "fsck -p -f" the ext2 partition. Then I suggest you to convert it to ext3 (Diablo incorrectly mounts ext3 as ext2 but DT fixes that)
Thanks. In the meantime, I successfully converted the partition into ext3 using your steps and also added an additional layer of work as described here. The inode errors, however, are still coming back.

I also discovered the reason for the "short read in buffer_copy" errors: the deb file, which I was trying to install with dpkg, was not download fully. After i wget the file again, the "short read" error disappeared.

However, I still could not install the new kernel. A downgrade to kernel 1 worked. An upgrade not:

dpkg -i kernel kernel-dt-sd_2.6.21-3_all.deb
Reading database...
Preparing to replace kernel-dt-sd 2.6.21-1 (using kernel-dt-sd_2.6.21-3_all.deb)...
Unpacking replacement...
Setting up kernel kernel-dt-sd (2.6.21-1)
Installing new kernel modules in initfs...
Flashing new kernel image...
Image(s) successfully flashed
Kernel image flashed
Please reboot

Any hints?