[twobob]

Whoopsie.

EXT4-fs error (device sdb): ext4_lookup:1044: inode #2: comm ls: deleted inode referenced: 15
ls: ./xz504-static-arm.tar.gz: Input/output error

And during boot : )

Spoiler:

NET: Registered protocol family 17
9pnet: Installing 9P2000 support
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 4
sda: unknown partition table
sd 0:0:1:0: [sdb] 4194304 512-byte logical blocks: (2.14 GB/2.00 GiB)
sd 0:0:1:0: [sdb] Write Protect is off
sd 0:0:1:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sdb: unknown partition table
sd 0:0:1:0: [sdb] Attached SCSI disk
rtc-pl031 dev:e8: setting system clock to 2012-08-08 16:57:11 UTC (1344445031)
sd 0:0:0:0: [sda] Attached SCSI disk
VFS: Mounted root (squashfs filesystem) readonly on device 8:0.
Freeing init memory: 100K
8139cp 0000:00:0c.0: eth0: link up, 100Mbps, full-duplex, lpa 0x05E1
EXT4-fs (sdb): mounting ext3 file system using the ext4 subsystem

EXT4-fs (sdb): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (sdb): recovery complete
EXT4-fs (sdb): mounted filesystem with ordered data mode. Opts: (null)
Not using distcc.

Heh, running e2fsck, any ideas, I'm struggling to conceptualise the device.

EDIT: Simply point it at the file...

twobob@dev ~/BLDS/system-image-armv6l $ e2fsck -v hdb.img

Spoiler:

e2fsck 1.42 (29-Nov-2011)
hdb.img: recovering journal
hdb.img contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry 'xz504-static-arm.tar.gz' in / (2) has deleted/unused inode 15. Clear<y>? yes

Pass 3: Checking directory connectivity
Unconnected directory inode 135169 (/???)
Connect to /lost+found<y>? yes

Unconnected directory inode 270337 (/???)
Connect to /lost+found<y>? yes

Unconnected directory inode 409601 (/???)
Connect to /lost+found<y>? yes

Pass 4: Checking reference counts
Inode 2 ref count is 6, should be 9. Fix<y>? yes

Unattached inode 12
Connect to /lost+found<y>? yes

Inode 12 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 16
Connect to /lost+found<y>? yes

Inode 16 ref count is 2, should be 1. Fix<y>? yes

Inode 135169 ref count is 8, should be 7. Fix<y>? yes

Inode 270337 ref count is 3, should be 2. Fix<y>? yes

Inode 409601 ref count is 14, should be 13. Fix<y>? yes

Pass 5: Checking group summary information
yyBlock bitmap differences: -(1703--1706) -(1723--1728) -(2260--2264) -(2287--2288) -(2519--2520) -(6039--6428) +(10225--10230) +(10257--10260) +(10574--10637) +(10769--10771) +(10865--10880) +(10977--11008)yyyy +(11137--11264)
Fix<y>? yes

yyFree blocks count wrong for group #0 (3445, counted=448).
Fix<y>? yes

Free blocks count wrong for group #1 (7254, counted=4920).
Fix<y>? yes

Free blocks count wrong for group #2 (7678, counted=5296).
Fix<y>? yes

Free blocks count wrong for group #3 (7413, counted=5518).
Fix<y>? yes

Free blocks count wrong for group #4 (7678, counted=4299).
Fix<y>? yes

Free blocks count wrong for group #5 (7413, counted=4787).
Fix<y>? yes

Free blocks count wrong for group #6 (7678, counted=6168).
Fix<y>? yes

Free blocks count wrong for group #7 (7413, counted=6689).
Fix<y>? yes

Free blocks count wrong for group #66 (7678, counted=6972).
Fix<y>? yes

Free blocks count wrong (1903025, counted=1884472).
Fix<y>? yes

yInode bitmap differences: -15
Fix<y>? yes

Free inodes count wrong for group #66 (2048, counted=1854).
Fix<y>? yes

Directories count wrong for group #66 (0, counted=14).
Fix<y>? yes

Free inodes count wrong (521820, counted=521626).
Fix<y>? yes


hdb.img: ***** FILE SYSTEM WAS MODIFIED *****

2662 inodes used (0.51%)
233 non-contiguous files (8.8%)
12 non-contiguous directories (0.5%)
# of inodes with ind/dind/tind blocks: 438/21/0
212680 blocks used (10.14%)
0 bad blocks
0 large files

2407 regular files
246 directories
0 character device files
0 block device files
0 fifos
4294967293 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
2648 files

Sorted.