What is the drive model. what happened, what was the operating sistem.
exteral ethernet NAS?
no it is not.
Never mind, if translator on hdd it self is bad you can get same errors , tell us model number and manufacturer.
and one more thing how do you connect it, to yoour pc over ethernat cable?
Again if anyone has any sensible replies, the file system is XFS. Anyone aware of tools for file recovery of an XFS file system?
Andy
Andy,
Do you know the filename? You could try and locate the inode table entry for the file. Failing that search for remnants of a Master File Table. Sounds to me that it may have been a NTFS partition at one time. Either one would tell you the starting and continuing extents for the file you are looking for.
Again if anyone has any sensible replies, the file system is XFS. Anyone aware of tools for file recovery of an XFS file system?
Andy
OK this is not really nice thing to say, first off all you need to know is the didk ok or not.If it has Badsectorst that can mean that something with firmware is wrong.
second if you didnt take it out from the box i need do know how do you connect it to your pc, Is it over crossover or not,
3. What is the model off hdd inside the box so i can help you with common firmware problems, but you do not need help as I can see.
Nikola
r-studio, stellar….
Tried them already, also tried xfs_repair in Linux (as it appears the superblock is corrupt). All negative so far. The disk is a Maxtor 120GB diamond Max Plus 9 (model - 6y120L0). Firmware YAR41BW0.
I'll leave it for now, many thanks.
Andy
there is a whole world in data recovery thaty is not run bu west , i is run by east.
Leave on the side what you have been stuiding for now and realise that you need to have a working drive in order to extract data.
So repair the hard drive and you will have your data.
CAn you do sequentil check of every sector on the hdd, can u read them
If you can than u have logcal probelm, but if not then….
Can scan whole drive, and how is it conneted to your pc
Andy,
Have you tried using a secondary superblock? Provided you are using an image, try fsck'ing the disk, then run xfs_repair