Welcome, Guest. Please login or register.
Did you miss your activation email?
September 26, 2017, 10:04:19 AM
Home Help Search Login Register
News:

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  iRecover (Moderators: Tom, Joep)
| | |-+  iRecover Crashing?
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: iRecover Crashing?  (Read 201 times)
egalli
member

Posts: 7


« on: September 11, 2017, 04:08:04 PM »

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
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1457


WWW
« Reply #1 on: September 12, 2017, 02:05:00 AM »

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.
Logged

--
Kind regards,
Joep
egalli
member

Posts: 7


« Reply #2 on: September 13, 2017, 01:38:05 PM »

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
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1457


WWW
« Reply #3 on: September 13, 2017, 06:47:25 PM »

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?
Logged

--
Kind regards,
Joep
egalli
member

Posts: 7


« Reply #4 on: September 17, 2017, 01:35:43 AM »

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
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1457


WWW
« Reply #5 on: September 18, 2017, 12:18:38 PM »

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.
Logged

--
Kind regards,
Joep
egalli
member

Posts: 7


« Reply #6 on: September 19, 2017, 02:20:19 PM »

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.



Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  


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!