Welcome, Guest. Please login or register.
Did you miss your activation email?
November 24, 2017, 06:06:45 PM
Home Help Search Login Register
News:

+  DIY DataRecovery.nl Support forum
|-+  Recent Posts
Pages: [1] 2 3 ... 10

 1 
 on: September 19, 2017, 02:20:19 PM 
Started by egalli - Last post by egalli
We had one drive fail hard. Dead.
The second failed, but after a reseat of the drive it spun back up.
It had a predictive failure, but it spun up.

We replaced the dead drive and imported it in but the data was kyboshed.
The file system was readable but many files, including a critical hyper-V AVHDX
file was corrupt.

I'm guessing that the array got punctured.

Regardless critical files were not readable.
So we removed the drives and are trying to read them
in a separate machine.

I ran the version you recommended and it did not crash.
It was able to recover some fragments that are of use to us so
the product has helped quite a bit.




 2 
 on: September 18, 2017, 12:18:38 PM 
Started by egalli - Last post by Joep
Hello,

Oh bummer, two drives failing what a nightmare. Let's hope RAID parameters can be determined. As iRecover keeps testing different solutions, it uses more and more memory. The version I linked to can use more memory on a 64 bit Windows version.

At the same time, iRecover not finding valid array parameters isn't a good sign.

How were those 2 drives 'resurrected'? In some cases it is better to run with the two disks you're most certain about.

 3 
 on: September 17, 2017, 01:35:43 AM 
Started by egalli - Last post by egalli
Sorry for the delay.
We had a 3 drive RAID 5 volume that had a dual drive failure.
We were able to resurrect both drives, but the raid had become broken at that point.
We are looking for data fragments from a MySQL DB that was on the volume.

I'm going to try the version you recommend and see what happens.

Thanks

 4 
 on: September 13, 2017, 06:47:25 PM 
Started by egalli - Last post by Joep
Hello,

Again, better use the version I linked to. Best ran on a 64 bit Windows so memory will not be an issue.

What kind of RAID anyway with all the different sized disks? And what happened to it?

 5 
 on: September 13, 2017, 01:38:05 PM 
Started by egalli - Last post by egalli
Thanks for responding.
We're running it on a Win2k12R2 server.
The version we installed is the latest that was available for download when we purchased it.

irecover.exe is dated 9/6/2012 9:13AM - 4.87MB

 6 
 on: September 12, 2017, 02:05:00 AM 
Started by egalli - Last post by Joep
Hello,

What OS? Most likely it's running out of memory. If you're not using this version: http://www.diydatarecovery.nl/download_irecoverzip_delay_copy.htm then try with that on a 64 bit version of Windows.

 7 
 on: September 11, 2017, 04:08:04 PM 
Started by egalli - Last post by egalli
Hi
We're seeing iRecover apparently crash after running for over 24 hours.

We start it up and select  the members of the RAID and start the scan.
Everything looks great. It scans for many hours (over 24), however when we check it the
following day the app is no longer running. No crash or application error on the screen.
Nothing in the event log either. We restart it and again it never completes, and randomly
crashes/shuts down after over 24 hours.

We're at a loss figuring out why this happens.
Below is the last few lines from the iRecover logfile.

Can anyone point us in the right direction here?

Thanks in advance,
Ed



-------------------------------------
Volume information for ID 00000302
Origin             : Reconstructed RAID
Partition type     : Unknown
Capacity           : 408 GB
Number of sectors  : 856424448
RAID type          : RAID5 (Checkerboard)
Stripe size        : 128
Rotation parameters: 0 / 0
Member 00          : 285474816 sectors at LBA 0 on device 0101
Member 01          : 1169686528 sectors at LBA 0 on device 0102
Member 02          : 1952448512 sectors at LBA 0 on device 0103
Member 03          : 2930277168 sectors at LBA 0 on device 0104
The device Disk 1 - DELL PERC H310, ID 0101 is not S.M.A.R.T.-capable
The device Disk 2 - DELL PERC H310, ID 0102 is not S.M.A.R.T.-capable
The device Disk 3 - DELL PERC H310, ID 0103 is not S.M.A.R.T.-capable
The device Disk 4 - JMicron, ID 0104 is not S.M.A.R.T.-capable
Loading RAID ID transform
Done loading RAID ID transform
Sector size 512
Open physical drive 00000100 success, 279 GB : Disk 0 - SEAGATE ST3300657SS; maxLBA=585937500
Sector size 512
Open physical drive 00000101 success, 136 GB : Disk 1 - DELL PERC H310; maxLBA=285474816
Sector size 512
Open physical drive 00000102 success, 557 GB : Disk 2 - DELL PERC H310; maxLBA=1169686528
Sector size 512
Open physical drive 00000103 success, 931 GB : Disk 3 - DELL PERC H310; maxLBA=1952448512
Sector size 512
Open physical drive 00000104 success, 1397 GB : Disk 4 - JMicron; maxLBA=2930277168
Sector size 512
Open physical drive 00000100 success, 279 GB : Disk 0 - SEAGATE ST3300657SS; maxLBA=585937500
Sector size 512
Open physical drive 00000101 success, 136 GB : Disk 1 - DELL PERC H310; maxLBA=285474816
Sector size 512
Open physical drive 00000102 success, 557 GB : Disk 2 - DELL PERC H310; maxLBA=1169686528
Sector size 512
Open physical drive 00000103 success, 931 GB : Disk 3 - DELL PERC H310; maxLBA=1952448512
Sector size 512
Open physical drive 00000104 success, 1397 GB : Disk 4 - JMicron; maxLBA=2930277168
TS: Stop validation
TS: Stopped validation
Logging - shut down

 8 
 on: September 09, 2017, 04:27:37 PM 
Started by 3cabbage - Last post by Joep
Hi,

Well no, unfortunately I do not have additional suggestions. We're more on the software / logical damage side of things.


 9 
 on: August 26, 2017, 12:58:37 PM 
Started by 3cabbage - Last post by 3cabbage
Hi Joep,

I found out that my controller card was a Cat 2 so I needed a replacement where I could unsolder the BIOS and replace it with my own. I found a few suppliers in Hong Kong, so I used one of them.

It has been a while since I last wrote because the first controller card PCB that I was sent wasn't the one I ordered (then they actually had the cheek to try and charge me to rectify their mistake), so I had to order another (from a different supplier).  Each took almost three weeks to arrive, but the second one was the right serial number.

Before connecting to my HDD I first tried tried using the Hyperterminal tests to see if I could get a response from the card, but I didn't so I was still unsure if it is the card causing a problem or not.

I decided to press ahead with changing the BIOS by first removing the one in the new donor card, my reasoning being if there was a problem it wouldn't damage my working BIOS.  I had seen a youtube video where they made a square of copper wire to melt the solder on all four legs of the BIOS simultaneously, so I made one using the copper out of some cast off twin and earth power cable.  It worked very well and I took the BIOS off the PCB quickly and easily, then cleaned off the excess solder from the chip socket. 

Before removing the BIOS on my own card, I realised that it was difficult to see the notch and I didn't want to replace it back to front, so I put a touch of snowpake at the end nearest the board edge.  I then proceded to remove my BIOS and all was going well until the solder was molten. I removed the soldering iron and copper and started to remove the BIOS.  Seven of the legs came out straight away, but the solder hardened on the eigth leg and it snapped off virtually flush with the encapsulation.  "Oh dear!" (or words to that effect) said I.  Luckily I had some small gauge wire and I soldered on a new leg before putting the BIOS in the new donor board and soldering it in.

After checking everything looked OK, I then screwed the board back onto the HDD, connected up and switched on.  Unfortunately, I am still getting the same original symptoms in that my PC thinks I have a USB Mass Storeage disk with four generic USB devices. 

One thing I have learnt, I am reasonably good at soldering having many years of professional practice, but with larger standard soldering equipment on the small BIOS chips that have such short non-flexible legs, if I have to do it again I will seriously consider paying the extra for someone else to swap out the BIOS.  Doing it myself cost me around 6 (8 USD$) using a donor board from Hong Kong, whereas getting someone else to do it with specialist equipment would cost around 40 (52 USD$ - and the company I saw was in USA) and probably worth the extra cost to reduce the stress.

It looks like I may not be able to get my data off at all, but I'll go away and scratch my head some more in the hope I can think of something else to try.

Thanks for all your help.

Alan

 10 
 on: August 18, 2017, 10:01:51 AM 
Started by pz49 - Last post by Joep
Hello,

Best way to approach NAS recovery is not using RAID recovery. Try again following this:
http://www.diydatarecovery.nl/irecoverhelp/NAS_recovery.htm

With the version that's linked to from that page, so http://www.diydatarecovery.nl/download_irecoverzip_delay_copy.htm

Pages: [1] 2 3 ... 10


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.20 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!