EVERY hdd data LOST

    Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    • EVERY hdd data LOST

      Hi,
      I've just lost every hdd data withouth any explainable reason.
      I am using unstable repo and I have updated just today as usual but it seems the results are my hdd /movies and /music (and other customized) folders data are totally lost 8o
      Please tell me there's a way to understand/retireve lost data because I didn't really expect this loss.....
    • check if the hdd is really mounted (telnet --> mount). if data is really lost you can try to recover it (e.g. with nucleus kernel linux).
      Gruss
      Dre

      Boxen: diverse
      Developer Project Merlin
    • The "ln" stuff just creates a linked directory "hdd" into the /media/hdd folder, don't know how it can be useful :)
      But, hey, seems I'm not 100% lost...I didn't ever notice nor thing to check if hdd was mounted because I was still seeing the HDD folder there with things into it and shared with my network too, but it is NOT mounted.
      I double checked fstab and there are still my two lines:
      /dev/sda1 /media/usb auto defaults 0 0
      /dev/sdb1 /media/hdd auto defaults 0 0
      where sda1 is the usb key (it IS mounted) and sdb1 the hdd.
      I tried launching mount /dev/sdb1 /media/hdd but after thinking some time it told me:
      mount: mounting /dev/sdb1 on /media/hdd failed: Invalid argument
      and now it doesn't even think anymore and says that at the fly ?(
      What does it mean? Ideas?

      ---edit---
      other data:
      root@dm8000:/media/hdd# blkid /dev/sdb1
      /dev/sdb1: UUID="bc69eeb8-48a5-43af-ac10-c07d4406d8e3" TYPE="ext2"
      ---edit1---
      root@dm8000:/sbin# fsck.ext2 -p /dev/sdb1
      /dev/sdb1: Note: if several inode or block bitmap blocks or part
      of the inode table require relocation, you may wish to try
      running e2fsck with the '-b 32768' option first. The problem
      may lie only with the primary block group descriptors, and
      the backup block group descriptors may be OK.

      /dev/sdb1: Block bitmap for group 2688 is not in group. (block 2296941567)


      /dev/sdb1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
      (i.e., without -a or -p options)


      So I've done it...

      root@dm8000:/sbin# fsck.ext2 /dev/sdb1
      e2fsck 1.41.9 (22-Aug-2009)
      fsck.ext2: Group descriptors look bad... trying backup blocks...
      /dev/sdb1 was not cleanly unmounted, check forced.
      Resize inode not valid. Recreate<y>? yes

      Pass 1: Checking inodes, blocks, and sizes
      Error allocating block bitmap (4): Memory allocation failed
      e2fsck: aborted

      So I tried to check bad blocks...

      root@dm8000:/sbin# fsck.ext2 -c /dev/sdb1
      e2fsck 1.41.9 (22-Aug-2009)
      fsck.ext2: Group descriptors look bad... trying backup blocks...
      Resize inode not valid. Recreate<y>? yes

      sh: badblocks: not found
      /dev/sdb1: Updating bad block inode.
      Pass 1: Checking inodes, blocks, and sizes
      Error allocating block bitmap (1): Memory allocation failed
      e2fsck: aborted


      ...that's a quite big headache. Are we sure by blkid the hdd is ext2? I thought not! I'm out of ideas anyway and I'd like not to do damages....

      ---edit2---
      I am downloading & installing Ubuntu on my pc machine to check the disk.
      Any hints on how to go on? fsck.ext2 -p ?
      Thanks :]

      Dieser Beitrag wurde bereits 4 mal editiert, zuletzt von cmatte ()

    • Sorry, didn't see answers because hdd was working ok after having done that work with Ubuntu :)
      I tried the command and it says me:

      root@dm8000:~# smartctl -a /dev/sdb
      smartctl version 5.38 [mipsel-oe-linux-gnu] Copyright (C) 2002-8 Bruce Allen
      Home page is smartmontools.sourceforge.net/

      Device: WD Ext HDD 1021 Version: 2002
      Segmentation fault

      ...quite scaring...
      Do you think I should pass to ext3? I though it was ext3. In fact Ubuntu's fsck found many "ext3" properties and deleted them because file system was ext2 for it ?(
      Is there a way to to ext2>ext3 right now that ext2 or whatever it is now is working as it should?
      Thanks :)
    • It's seen by the image as an hdd, not usb device as the usb dmm key.
      But it's usb, yes, I though to have said sorry.
      It's a 1tb external usb disk. I had formatted it with another image in the past and continued working as it should with newnigma2, till this.

      Dieser Beitrag wurde bereits 3 mal editiert, zuletzt von cmatte ()