Jump to content

joyvalle

Member
  • Posts

    8
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Belgium

Everything posted by joyvalle

  1. Hi Jaclaz, @dencorso About the name, ofc, it is not precise enough .... but when I posted to the forum, I didn't know the issue with the hard drive but It seemed to be related to the "seagate 7200.11 malediction" (You can find traces of this malediction in ancient written documents ... ) @Jaclaz Do I have to start crying the loss of my data ? Press Ctrl-C to interrupt Initial status (read from logfile) rescued: 3715 MB, errsize: 0 B, errors: 0 Current status rescued: 3827 MB, errsize: 996 GB, current rate: 0 B/s ipos: 1 TB, errors: 18, average rate: 548 B/s opos: 1 TB, time from last successful read: 2.3 d Finished 2 days and 7 hours for 3 Gb on 1 Tb :'(. If this is not a malediction, I don't know what it is ... Is there anything else I can try? Does Seagate or an other company has a chance to recover the data? Thks Sad KiD
  2. hello Jaclaz, I tried to backup the drive but the process did not succeed. Here is the error: LBA 6 304 023 (try2): WinError 1117 impossible to satisfy the demand because of an error on the "peripherique E/S" (I guess in english this is I/O) Do you have any idea what is it? NB: I tried to explore the data with dmde to see the block but as you can guess, when I arrive to the block 6304023, the same error arises. KiD
  3. Hello Jaclaz, Both files (LBA 6291519 and LBA 976760063) are identical. So I'll do the backup and try the "CHKDSK" procedure. KiD
  4. hey, I'm back. (sorry for the late answer) A little question: Do you know why there is an error message written in the MBR? "Invalid partition table... Error Loading Operating System ... Missing Operating System" So the block 63 (VBR) is in attachment. I watched the content and there is something more than weird... It contains a message in french (here in english): "Error reading disk .... BOOTMGR absent ....BOOTMGR compress .... CTRL+ALT+DEL to restart .... restart" Ctrl alt del to restart ??? It looks like the message was written in sdb instead of stdout (I am not an expert. This is just a guess from a C programmer ). Actually, the block 6291519 starts with FILE0 and there is a $MFT further in the block.... I'll try DMDE. Thanks again for the support!! KiD vbr_block6291519.zip
  5. Yes it is a NTFS partition. I tried to backup the disk in an image with Clonezilla but it failed.... For future reader, the command on linux to read the MBR is: sudo dd if=/dev/sdc of=/tmp/backup-sdc.mbr bs=512 count=1 For the vbr, I used this command: sudo dd if=/dev/sdc of=/tmp/back-sdc.vbr bs=512 count=1 skip=62 but I am not sure if it is correct. (As I used cloneZilla with a external disk to backup, the external disk was recognized as sdb and the mounted disk was sdc. Then, even if I removed the external disk, the disk is no more sdb but sdc ... weird) The log for the "Quick Search" is in the .zip file attached. thks, KiD mbr_vbr_log.zip
  6. Hello Jaclaz, I'm more familiar with linux command than windows. I use linux for work while windows is more for gaming... So here is the result of fdisk -l : Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xcbce2081 Device Boot Start End Blocks Id System /dev/sdb1 63 1953520064 976760001 7 HPFS/NTFS/exFAT (To be complete, there is a sda but I didn't paste the result) This means that the partition is seen. I knew that because in the linux file explorer (thunar), the partition name is correct. Here is the log from testdisk Fri Jan 24 14:03:11 2014 Command line: TestDisk TestDisk 6.14, Data Recovery Utility, July 2013 Christophe GRENIER <grenier@cgsecurity.org> http://www.cgsecurity.org OS: Linux, kernel 3.2.0-40-generic (#64-Ubuntu SMP Mon Mar 25 21:22:10 UTC 2013) x86_64 Compiler: GCC 4.4 Compilation date: 2013-07-30T14:13:28 ext2fs lib: 1.41.12, ntfs lib: libntfs-3g, reiserfs lib: 0.3.1-rc8, ewf lib: 20120504 /dev/sda: LBA, HPA, LBA48, DCO support /dev/sda: size 976773168 sectors /dev/sda: user_max 976773168 sectors /dev/sda: native_max 976773168 sectors /dev/sdb: LBA, HPA, LBA48, DCO support /dev/sdb: size 1953525168 sectors /dev/sdb: user_max 1953525168 sectors /dev/sdb: native_max 1953525168 sectors Warning: can't get size for Disk /dev/mapper/control - 0 B - 1 sectors, sector size=512 Hard disk list Disk /dev/sda - 500 GB / 465 GiB - CHS 60801 255 63, sector size=512 - WDC WD5000AAKX-08ERMA0, S/N:WD-WCC2EV882038, FW:19.01H19 Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - ST31000333AS, S/N:9TE1Y4G0, FW:CC4H TestDisk exited normally. I'll do the copy of the drive asap. KiD
  7. Hello guys, I have a seagate HDD 1To (ST31000333AS). I have no more access to the disk. This means that I can see the disk in an file explorer but when I click on it, I can't get into the drive and see the files. Under Linux, the drive has the right name while under windows, I just see a drive but in both, the data are not accessible. No wired sound comes from the drive which makes me think that it is not a hardware problem. When I boot in the Bios, the drive is seen with the correct serial number and the right size. So it seems that it is neither a BSY nor a 0 LBA error... Using SeaTools, I did the short test but It failed while the SMART test succeeded. The report of the test says that I should use Seagate for DOS but I don't know what to do.... So if any of you can help me, it would be fantastic! KiD NB: ofc, I do this to retrieve the data. The possible solution that allows me to use the drive again but with the loss of my data does not interess me ...
  8. Hello guys, I have a HDD seagate 7200.11 that is bricked but no wired sound is coming from the drive. I can't manage to find what is the error, i.e if it is a BSY or 0 LBA or anything else. My drive appears in the BIOS but I don't see the type of error. The drive is listed with the right size but I can't access it neither in windows nor in linux. Seatools sees the drive but the short test doesn't succeed but the SMART yes. Do you know a way to identify clearly the error? Thks
×
×
  • Create New...