Partition Analysis takes forever...

[edbrandt]

Hi

I'm working on a NAS that failed, 7 drives (2 TB each) where 4 drives seems to be the ones in use, and 3 drives appears to be spare (or deleted from the Raid, time will tell)..

Anyway; all drives were cloned sucessfully and probably raid setup found. But partition information was wrong, and I'm now running Partition analysis which takes forever...

The partition analysis has been running for 6 days now, and still in progress. It's currentrly on step 2/5 (step 1 was finish this morning), and from the log I can see new file names appear every 2 second, so not the speed of light.

My computer has Intel i7-9700K CPU (3.6 GHz), and 32 GM RAM. CPU is running at 18-20%, approx. 29% of RAM is in use.


Which leads me to my questions: Is this normal behaviour? Is there any obvious way to speed up this process?


Thanks!

[DataMedics]

Just mount the task and use third-party software like UFSExplorer, DMDE, R-Studio, etc.

[d_d_recovery]

Source of the post Hi

I'm working on a NAS that failed, 7 drives (2 TB each) where 4 drives seems to be the ones in use, and 3 drives appears to be spare (or deleted from the Raid, time will tell)..

Anyway; all drives were cloned sucessfully and probably raid setup found. But partition information was wrong, and I'm now running Partition analysis which takes forever...

The partition analysis has been running for 6 days now, and still in progress. It's currentrly on step 2/5 (step 1 was finish this morning), and from the log I can see new file names appear every 2 second, so not the speed of light.

My computer has Intel i7-9700K CPU (3.6 GHz), and 32 GM RAM. CPU is running at 18-20%, approx. 29% of RAM is in use.

Which leads me to my questions: Is this normal behaviour? Is there any obvious way to speed up this process?


Thanks!

Can you give us more information about why the NAS failed?
It is very unusual for a NAS to have 3 unused drives (though not impossible).
Are you sure you have the mix right?

[edbrandt]

Source of the post Just mount the task and use third-party software like UFSExplorer, DMDE, R-Studio, etc.

I'll give that a try. Thanks.

[edbrandt]

Source of the post Can you give us more information about why the NAS failed?
It is very unusual for a NAS to have 3 unused drives (though not impossible).
Are you sure you have the mix right?

- NAS Problem: Customer lost access to control panel (the person who set up the NAS 5 years ago couldn't remember), and they performed a factory reset, They got access, but could only find the data originally copied to the NAS 5 years ago. Not any newer data.
- Unused drives.. Yes, but they are not empty. When I imaged the drives, the first four drives had approc 2 TB data, the latter 3 drives had 300 GB
- Correct mix.. The drives are numbered, and I used same order when adding drives to raid in PC-3000. Autodetect discovers two possible configurations. See image:

[Nick_TS]

Hello,

What's file system on the raid? What are PC-3000 and DE versions?

[lcoughey]

After getting all the drives cloned, I would take 5 minutes to look at the mdadm details on each drive to determine the RAID config and order of failure. Once determined, then I'd take another minute or two to load the RAID with UFS Explorer and it should be smooth sailing after that. Of course, if there is some odd file system, LUNs or encryption, things will be slowed down while figuring them out.