recover raid 0 after bios update

How to use TestDisk to recover lost partition
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Locked
Message
Author
kingikra
Posts: 4
Joined: 15 May 2020, 16:34

recover raid 0 after bios update

#1 Post by kingikra »

Hi,

So I did the mistake of updating my bios without making sure that all my data on a raid 0 controller was fully backup (most of it had backup).
I went over the following instructions: https://blog.quindorian.org/2013/07/rep ... rted.html/

It almost worked perfectly except the phase where testdisk should find the lost partition in seconds. When I started the analyze, it jumped immediately to 25% and from there started to crawl.
It read 2 sectors in 1 second which will eventually complete in 4-5 days :-(

During the analyze, I currently have the following:
Image

The log looks like this:


Thu May 14 21:02:14 2020
Command line: TestDisk

TestDisk 7.2-WIP, Data Recovery Utility, May 2020
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Windows 7 (7601) SP1
Compiler: GCC 9.3, Cygwin32 3001.4
ext2fs lib: 1.45.3, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: 20140608, curses lib: ncurses 6.1
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sda)=8001585938432
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=120034123776
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdc)=4000787030016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdd)=4000752599040
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sde)=15631122432
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=8001585938432
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=120034123776
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive2)=4000787030016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive3)=4000752599040
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive4)=15631122432
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=119926685696
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=4000650887168
filewin32_getfilesize(\\.\F:) GetFileSize err Incorrect function.

filewin32_setfilepointer(\\.\F:) SetFilePointer err Incorrect function.

Warning: can't get size for \\.\F:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\G:)=4000751550464
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\H:)=15630073856
Hard disk list
Disk /dev/sda - 8001 GB / 7452 GiB - CHS 972804 255 63, sector size=512 - Intel Raid 0 Volume, S/N:Data, FW:1.0.
Disk /dev/sdb - 120 GB / 111 GiB - CHS 14593 255 63, sector size=512 - Samsung SSD 840 Seri, S/N:1SH9ENDA355556 X, FW:DXT0
Disk /dev/sdc - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - WDC WD4004FZWX-00GBGB0, S/N:344b4b4b4e564c31202020202020202020202020, FW:81.H0A81
Disk /dev/sdd - 4000 GB / 3725 GiB - CHS 60799 255 63, sector size=4096 - WD Elements 107C, S/N:WCC4ENAF9XC9, FW:1065
Disk /dev/sde - 15 GB / 14 GiB - CHS 1900 255 63, sector size=512 - SanDisk Cruzer Blade, S/N:20052242711AE8725050, FW:1.27
Disk \\.\PhysicalDrive3 - 4000 GB / 3725 GiB - CHS 60799 255 63, sector size=4096 - WD Elements 107C, S/N:WCC4ENAF9XC9, FW:1065
Drive G: - 4000 GB / 3725 GiB - CHS 60799 255 63, sector size=4096 - WD Elements 107C, S/N:WCC4ENAF9XC9, FW:1065

Partition table type (auto): EFI GPT
Disk /dev/sda - 8001 GB / 7452 GiB - Intel Raid 0 Volume
Partition table type: EFI GPT

Analyse Disk /dev/sda - 8001 GB / 7452 GiB - CHS 972804 255 63
hdr_size=92
hdr_lba_self=1
hdr_lba_alt=3907029167 (expected 15628097535)
hdr_lba_start=34
hdr_lba_end=3907029134
hdr_lba_table=2
hdr_entries=128
hdr_entsz=128
check_part_gpt failed for partition
1 P MS Reserved 34 262177 262144 [Microsoft reserved partition]
Current partition structure:
No FAT, NTFS, ext2, JFS, Reiser, cramfs or XFS marker
1 P MS Reserved 34 262177 262144 [Microsoft reserved partition]
1 P MS Reserved 34 262177 262144 [Microsoft reserved partition]
2 P MS Data 264192 15628095487 15627831296 [Basic data partition] [Data]


I also run photorec in parallel. Is it bad to run it in parallel? Photorec also works very slowly but recovers files:
Image


Is there a chance I'll be able to recover the raid? My raid is an Intel one. 4 HDDs os 2TB each. Total of 8TB.

Please let me know if you need any other information.


Thanks
Gil
User avatar
cgrenier
Site Admin
Posts: 5441
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: recover raid 0 after bios update

#2 Post by cgrenier »

The current partition table looks OK:
1 P MS Reserved 34 262177 262144 [Microsoft reserved partition]
2 P MS Data 264192 15628095487 15627831296 [Basic data partition] [Data]

What problem do you have when you try to access the partition Data ?
kingikra
Posts: 4
Joined: 15 May 2020, 16:34

Re: recover raid 0 after bios update

#3 Post by kingikra »

In the disk management it looks like this:
Image

I can't access the partition
kingikra
Posts: 4
Joined: 15 May 2020, 16:34

Re: recover raid 0 after bios update

#4 Post by kingikra »

BTW, do I have to let it complete the scan or can I stop it now? Will it let me restore the MS Data partition table?

Thanks
kingikra
Posts: 4
Joined: 15 May 2020, 16:34

Re: recover raid 0 after bios update

#5 Post by kingikra »

Just a last update. The testdisk completed his analyze and reported that the partition table is corrupted and can't be restored :-(
Fortunatly, it let me see and backup all the files and folders on the RAID.
Unlike photorec, that restores the files in different names and dates as the original files and without the folders (it creates folders in the format of recup_dir.1, recup_dir.2, etc'), testdisk restores the files in the same folders, names and dates as the original ones.

For me that was enough as, anyhow, I'm moving the disks into a new PC which will, anyway, need to reformat them and recreate the RAID from scratch

Thanks anyway!
recuperation
Posts: 3026
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: recover raid 0 after bios update

#6 Post by recuperation »

kingikra wrote: 20 May 2020, 18:18 For me that was enough as, anyhow, I'm moving the disks into a new PC which will, anyway, need to reformat them and recreate the RAID from scratch
See you soon! Creating a RAID 0 with 4 drives increases your chances of data loss by a factor of 4.
Locked