[NBLUG/talk] Oh, goodness, what have I done?

[Robert Hayes]

OK. Upon more investigation, I found reference to the losetup command.

I ran 
# losetup /dev/loop0 /dev/hdd

and then ran e2fsck on /dev/loop0

The result was:

/dev/loop0: ***** FILE SYSTEM WAS MODIFIED *****

     487 inodes used (0%)
     144 non-contiguous inodes (29.6%)
         # of inodes with ind/dind/tind blocks: 12895/12857/12701
   41187 blocks used (1%)
       0 bad blocks
       0 large files

     279 regular files
      70 directories
       0 character device files
       2 block device files
       0 fifos
     -69 links
     127 symbolic links (127 fast symbolic links)
       0 sockets
--------
       1 file

And now I can mount /dev/loop0 and see lots of directories and files inside 
lost+found on that partition. The files and directories all have names like 
#123456, but that's OK.

However when I try to mount /dev/hdd1 or run e2fsck on hdd1 it still comes 
back faulty. Isn't /dev/loop0 just a link or image version of /dev/hdd1?

How can a transfer that corrected information to /dev/hdd1?

Thanks!

Bob



On Friday 11 February 2005 11:14 am, Robert Hayes wrote:
> I was having difficulty with a secondary hdd, nothing TERRIBLY critical in
> terms of data, but would prefer not to lose it.
>
> I unmounted the drive, and ran
> e2fsck -fvy /dev/hdd1
>
> I went crazy with invalid block numbers, dtime errors, magic block, etc.
>
> Here's the stupid part. I stopped e2fsck: <ctrl>-c.
>
> Now this is what I get.
>
> Is it terminal? Should I be tasered?
>
> Please be gently.
>
> Thanks.
>
>
> #:  e2fsck -b 8193 /dev/hdd
> e2fsck 1.34-WIP (21-May-2003)
> e2fsck: Bad magic number in super-block while trying to open /dev/hdd
>
> 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>
>
> As you can see, this is a loop.
>
>
>
> _______________________________________________
> talk mailing list
> talk at nblug.org
> http://nblug.org/cgi-bin/mailman/listinfo/talk