Hi List, I'm suffering SD Card corruption. It seems like there is/was a kernel who nuked the first 1024 Bytes, but this error is on the second partition of a 2 GB SD Card.
Both Freerunner (Running 20080813 and latest kernel) and Laptop (Ubuntu x86) print the same errors, here is the dmesg of my laptop: [50615.571305] EXT2-fs error (device mmcblk0p2): ext2_check_page: bad entry in directory #46466: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 [50625.249136] EXT2-fs error (device mmcblk0p2): ext2_check_page: bad entry in directory #185: unaligned directory entry - offset=1024, inode=4291814232, rec_len=6911, name_len=20 [50625.377935] EXT2-fs error (device mmcblk0p2): ext2_check_page: bad entry in directory #185: unaligned directory entry - offset=8192, inode=1647255843, rec_len=28265, name_len=47 [50625.526097] EXT2-fs error (device mmcblk0p2): ext2_check_page: bad entry in directory #186: rec_len is smaller than minimal - offset=0, inode=94109696, rec_len=0, name_len=0 [50625.566072] EXT2-fs error (device mmcblk0p2): ext2_check_page: bad entry in directory #194: unaligned directory entry - offset=0, inode=169760, rec_len=49430, name_len=0 [50627.824648] EXT2-fs error (device mmcblk0p2): ext2_check_page: bad entry in directory #195: directory entry across blocks - offset=0, inode=3854366540, rec_len=50688, name_len=143 [50630.197467] EXT2-fs error (device mmcblk0p2): ext2_check_page: bad entry in directory #188: unaligned directory entry - offset=0, inode=4280215741, rec_len=57647, name_len=132 [50630.286887] EXT2-fs error (device mmcblk0p2): ext2_check_page: bad entry in directory #73052: directory entry across blocks - offset=0, inode=1953068832, rec_len=8296, name_len=116 [50630.477691] EXT2-fs error (device mmcblk0p2): ext2_check_page: bad entry in directory #73052: unaligned directory entry - offset=4096, inode=1869898098, rec_len=15730, name_len=60 [50630.852545] EXT2-fs error (device mmcblk0p2): ext2_check_page: bad entry in directory #54443: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 On deleting a about 500Mb files it prints (just a snip): [49358.837078] EXT2-fs error (device mmcblk0p2): ext2_free_blocks: Freeing blocks not in datazone - block = 64178, count = 1 [49358.838624] EXT2-fs error (device mmcblk0p2): ext2_free_inode: bit already cleared for inode 8152 [49358.840352] EXT2-fs error (device mmcblk0p2): ext2_free_blocks: Freeing blocks not in datazone - block = 64179, count = 7 [49358.842862] EXT2-fs error (device mmcblk0p2): ext2_free_inode: bit already cleared for inode 8153 [49358.845819] EXT2-fs error (device mmcblk0p2): ext2_free_blocks: Freeing blocks not in datazone - block = 64186, count = 1 [49358.847559] EXT2-fs error (device mmcblk0p2): ext2_free_inode: bit already cleared for inode 8154 [49358.849493] EXT2-fs error (device mmcblk0p2): ext2_free_blocks: Freeing blocks not in datazone - block = 64173, count = 1 [49358.852115] EXT2-fs error (device mmcblk0p2): ext2_free_inode: bit already cleared for inode 8148 [49358.854825] EXT2-fs error (device mmcblk0p2): ext2_free_blocks: Freeing blocks not in datazone - block = 64188, count = 2 Very interesting is this (also during deleting files): [49357.883262] attempt to access beyond end of device [49357.883269] mmcblk0p2: rw=0, want=9751408856, limit=3954368 This whole stuff started during installation of Debian (using the script at [1]), so it's either caused by too much transfers onto the card or the script messed up the partition table (which, while thinking about it, is very probable, esp. because of the access beyond end of device error). Anyone any ideas? [1] http://wiki.debian.org/DebianOnFreeRunner -- Sebastian M. Student of Computer Science at the University of Kaiserslautern. _______________________________________________ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support