Re: EXT2 directory corrupted
> >Unconnected directory inode 11 (???)
>
> The problem probably is, that on most of my ext2 filesystems
> lost+found *is inode 11*. That means that e2fsck is probably trying
> to move lost+found to itself.
>
> However I have also ext2 filesystems with lost+found being other
> inode numbers. So maybe the solution is to say NO to the above
> question from fsck, then manually removing lost+found, creating a new
> one, and fscking again. Of course I don't take responsibility for
> this.
mklost+found is used to create lost+found (in case it wasn't obvious).
Michael
Reply to: