CFW 3.11 hard drive disappears

MontysEvilTwin said:
Regarding the new version, since the 'inline_data' feature is EXT4 only, shouldn't e2fsck simply refuse to set it on EXT3 filesystems? Also, if you have to answer 'no' then 'yes' to get the correct outcome, using the -y switch with e2fsck directly, or fixdisk on the HDR-FOX, would lead to the 'inline_data' feature being set on the filesystem making the drive inaccessible to the Humax unit?
Click to expand...
Yes and yes. Daft, isn't it?

(should work on an HD, yes - gives you the newer utilities for manual intervention at least)

I suspect that your inode still has the flag set but the older e2fsck doesn't recognise it (nor care).
The scaninline tool should tell you though, and then you could remove it with debugfs.
 
Black Hole said:
If I have understood this correctly, there don't need to be any changes in the file system as the old tools ignore this flag.
Click to expand...
Right, as long as you can remove the feature from the filesystem superblock, which requires the newer version of the tools.
 
af123 said:
Right, as long as you can remove the feature from the filesystem superblock, which requires the newer version of the tools.
Click to expand...
I'll run the new tool later. You are right, once the 'inline_data' feature is set on a filesystem an older version of e2fsck cannot remove it.
 
af123 said:
MontysEvilTwin - install the new e2recover package and that will give you the 1.43 versions of some utilities to make this easier.
They'll be on the disk but you can copy to /tmp to run while it is unmounted.

Code: 
humax# opkg files e2recover
Package e2recover (1.43.4) is installed on root and has the following files:
/mod/sbin/43.dumpe2fs
/mod/sbin/43.debugfs
/mod/sbin/43.tune2fs
/mod/sbin/scaninline
/mod/sbin/43.e2fsck
Click to expand...
I installed the e2recover package and first ran 'scaninline' to check for affected inodes. There were lots so I am just posting a portion of them:
Code: 
HDFox# chmod u+x scaninline               
HDFox# ./scaninline /dev/sda1             
Opened /dev/sda1 'Red Drive'             
  -> 16927/30523392 inodes in use.       
Scanning inodes...                       
Found bad inode 16516 = 0x1536c58b.       
Found bad inode 16545 = 0xdf364c80.       
Found bad inode 16563 = 0x7ea740c4.       
Found bad inode 16659 = 0xd3238d48.       
Found bad inode 16660 = 0x7581cc4b.       
Found bad inode 16911 = 0x37048d49.       
Found bad inode 16982 = 0xf58180c9.       
Found bad inode 17253 = 0x74910000.       
Found bad inode 17319 = 0x9710408c.       
Found bad inode 17356 = 0x5311898c.       
Found bad inode 17394 = 0xfd22cdc7.       
Found bad inode 17442 = 0x52114949.       
Found bad inode 17448 = 0xb714894c.       
Found bad inode 17498 = 0x72324c0c.       
Found bad inode 17571 = 0x31064dc0.       
Found bad inode 17591 = 0xd90789cc.       
Found bad inode 17651 = 0x9135c04d.       
Found bad inode 17685 = 0xd92300ca.
Found bad inode 17686 = 0x5312414d.     
Found bad inode 17763 = 0x789184c1.     
Found bad inode 17989 = 0x1f840c80.     
Found bad inode 18223 = 0x73a781cf.     
Found bad inode 18227 = 0x1a94c0c8.     
Found bad inode 18306 = 0x758544c1.     
Found bad inode 18320 = 0x5d83c8c1.     
Found bad inode 18321 = 0xf0b5808e.     
Found bad inode 18350 = 0x9c824840.     
Found bad inode 18374 = 0xf9968c8e.     
Found bad inode 18404 = 0x98a5c84d.     
Found bad inode 18457 = 0x5905ccc0.     
Found bad inode 18521 = 0x9da2894f.     
Found bad inode 18612 = 0xfcb5cd00.     
Found bad inode 18774 = 0x7f1100c5.     
Found bad inode 18844 = 0x5f168d08.     
Found bad inode 18946 = 0xdcb00d45.     
Found bad inode 19035 = 0x7232c58f.     
Found bad inode 19087 = 0xb51188c2.     
Found bad inode 19238 = 0xfda7c9c4.     
Found bad inode 19249 = 0x18a40508.     
Found bad inode 19421 = 0x5e824047.     
Found bad inode 19435 = 0xf827080f.     
Found bad inode 19534 = 0xbe344449.
I then ran the latest version of e2fsck, manually inputting 'n' and 'y' answers as described in post #16. FYI there was a third type of output from e2fsck related to the 'inline_data' flag, e.g:
Code: 
Inode 1032192 has INLINE_DATA_FL flag but extended attribute not found.  Truncate<y>?
Anwering 'y' is the correct response. Eventually I ended up with a clean filesystem, with no errors detected by the latest version of e2fsck, and 'inline_data' was not set in the filesystem.
 
MontysEvilTwin said:
Found bad inode 16516 = 0x1536c58b.
Click to expand...
Ok, these are just random (corrupt) as far as I can see.
This one, for example, has the 'I am an EXT4 snapshot in the process of being deleted' flags set too.
Glad you have knocked it into shape - I was thinking of adding a -fix flag to scaninline, which would save the n/y typing but it's probably better to have let e2fsck do it's thing.

I've now tried scaninline on all of my boxes without it finding any dodgy inodes.
 
You must log in or register to reply here.
Back
Top