| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 81267 | 2007-07-22 09:54:00 | HDD CLONK NOISE | notechyet (4479) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 571505 | 2007-07-23 13:01:00 | But how to copy stuff when windows can't see it and knoppix can't access it? | Agent_24 (57) | ||
| 571506 | 2007-07-23 22:15:00 | But how to copy stuff when windows can't see it and knoppix can't access it?That's why he put it back in the freezer. If he still can't get it running after the freezer, then the only avenue he has left is a professional recovery service - it's long past the stage where any of the above tools would be useful. | Erayd (23) | ||
| 571507 | 2007-07-24 00:58:00 | Wouldn't it be possible that in the course of the hardware failure, the data was corrupted so it cannot be read? Even if freezing brings the hardware back in working condition again, it should still not be able to read said data, thus it doesn't show up. :confused: |
Agent_24 (57) | ||
| 571508 | 2007-07-24 01:20:00 | That is, indeed, a strong possibility. If that is the case, then he will not be able to do anything to recover the data himself, and will need to pay to get it professionaly done. | Erayd (23) | ||
| 571509 | 2007-07-24 01:38:00 | Hello to you all Now this problem is(I think) solved.:o The HDD is dead! :( I tried with freezing and it did rum smother for about 1/2 hr. During that time I tried all sorts of ways too get on to the data: like over the windows explorer, tried to see it in partition magic, even loaded Knoppix live and could see the hhd there, it said the HDD is not accessible. and shortly after that it started to clonk again, so that leaves me with...?? NT |
notechyet (4479) | ||
| 571510 | 2007-07-24 02:58:00 | Apart from the mechanical problem the data will still be on the disk . The file system is gone . That means that OSs can't access the data through the file system . The clonking might mean that the servo surface is flakey . Any Unix/Linux will get any readable data without the file system . There's a magic programme called dd which can do that . The big problem is knowing where the data are without the file system . Half an hour isn't long enough to search for things; though you might manage to copy a fair amount to a good disk in that time . That would create one big file, which could then be searched for data . |
Graham L (2) | ||
| 571511 | 2007-07-24 03:10:00 | That's kinda what I was trying to say with the ghost an image of it idea, though you're right, even ghost probably wouldn't be able to do it, but I have heard of dd, which may indeed turn up something useful If you're lucky you might be able to start copying with dd, then when the drive dies again, if it's possible to know where it stopped copying at, freeze the drive again and then start from where it stopped, hopefully you can freeze it enough times to get most data off it mind you I have never use that program |
Agent_24 (57) | ||
| 571512 | 2007-07-24 03:30:00 | If you're lucky you might be able to start copying with dd, then when the drive dies again, if it's possible to know where it stopped copying at, freeze the drive again and then start from where it stopped, hopefully you can freeze it enough times to get most data off it mind you I have never use that programThat is a brilliant idea, and yes - it's quite possible. Just look at the size of the dd dumpfile when it fails, and resume from the next byte once (if) you get the drive running again. Once you have all the pieces, just 'cat' them back together. The smaller the drive is, the faster this process will be. |
Erayd (23) | ||
| 571513 | 2007-07-24 03:33:00 | I gather that Ghost is intended to make a copy of a disk; but an unreadable copy of an unreadable disk isn't all that useful. (I suppose a matched pair might sometimes be better than one :D ). dd is intended for recovering data off unreadable devices. It can use a device hardware address as an "input file", and write to a file in a working file system e.g. dd if=/dev/hda of=diskdata.dat bs=512 skip=100 count=1000 would copy 1000 blocks, after skipping 100, from the first IDE disk drive to a file. It would ignore any partitioning ... it gets blocks off a physical device. (The "bs=" is necessary for, e.g., MS disks because Unix blocks are 1024). There are lots of options. ;) It's a very useful tool. Or vice versa. dd if=memorytest.img of=/dev/fda bs=512 would write a bootable floppy from an image file. |
Graham L (2) | ||
| 571514 | 2007-07-24 06:15:00 | Hi Graham Would it be an option to load one of the linux on VMware and try to access the HDD from there. The only thing is that after the second freeze the clonking went for about 5 times and then it shut itself down(did not spin anymore). Should I freeze it once more and have a go? Any other suggestions? Thanks NT |
notechyet (4479) | ||
| 1 2 3 4 | |||||