On 17/01/11 14:56, Jim Cheetham wrote:
> On Mon, Jan 17, 2011 at 2:44 PM, Roger Searle<ro...@stepahead.org.nz> wrote:
>> Thanks Jim and Craig for the suggestion to do fsck and possibly write
>> off the partition, as noted it is a backup drive and 1 of 2 that are
>> regularly rotated because you never know when something might go wrong!
> Well, if you are writing it off, how about trying the unlink/fsck
> trick and see if that helps? I'd be keen to hear from someone using it
> in practice ...
>
> -jim
>
OK - but I got kind of stuck, and time pressures took me right to "write
it off". The drive must be mounted in TrueCrypt to be able to write to
it, and while it is I got:
roger@mercury:/usr/share/man$ fsck /media/truecrypt1/
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
fsck.ext2: Is a directory while trying to open /media/truecrypt1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
So first question: Does fsck correctly know it's a corrupt superblock
given it's encrypted?
If I then unmount the drive in TrueCrypt, it does not show in the
results of the mount command. This being the point at which I decided
to move on! I've not yet done a mkfs.
How would I then run fsck without a TrueCrypt mount? Or is the unlink
suggestion done via other means?
Cheers,
Roger
_______________________________________________
Linux-users mailing list
Linux-users@lists.canterbury.ac.nz
http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
