"Write Error" trying recover partitions on Raid 5 Array Topic is solved

[metagraphica]

Trying recover partitions on Raid 5 array that 'lost' two out of four disks during a BIOS update for my motherboard.
I was able to set all 4 drives as "Non-Raid Disks" and then re-create the array in the BIOS. The drives were never disconnected from their SATA ports so I know they are in the correct order.

I was able to successfully run TestDisk -> Analyze -> Quick Scan -> Deeper Scan. The Deeper Scan found all my Partitions and was able to show me the correct files and all the data in them. However when I tried to 'Write' the Partitions I got a "Partition: Write error" - file_pwrite(5,32,buffer,2(0/0/3)) write err Read-only file system

This is a Win7 pc and the partitions were created in Win7. The Raid array is NOT encrypted. I only have MS Security Essentials currently running for AV. Currently the entire Raid array shows up as "Disk 1 Unknown 4191.79GB Not Initialized" in Disk Management.

Any help figuring out how to 'Write' the partitions would be GREATLY appreciated.

I have attached my TestDisk log
Here is a snippet from the end of the TestDisk Log:

interface_write()
1 P MS Data 264192 419694584 419430393 [Programs]
2 P MS Data 419694592 839124991 419430400 [Data]
3 P MS Data 839124992 1258555391 419430400 [Data II]
4 P MS Data 1258555392 5452859391 4194304000 [Photos]
5 P MS Data 5452859392 6501435384 1048575993 [Artwork]
write!
file_pwrite(5,32,buffer,2(0/0/3)) write err Read-only file system

Partition: Write error

Analyse Disk /dev/sdb - 4500 GB / 4191 GiB - CHS 547203 255 63
hdr_size=92
hdr_lba_self=1
hdr_lba_alt=2930277167 (expected 8790816767)
hdr_lba_start=34
hdr_lba_end=2930277134
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 419694591 419430400 [Basic data partition] [Programs]
3 P MS Data 419694592 839124991 419430400 [Basic data partition] [Data]
4 P MS Data 839124992 1258555391 419430400 [Basic data partition] [Data II]
5 P MS Data 1258555392 5452859391 4194304000 [Basic data partition] [Photos]
6 P MS Data 5452859392 6501435391 1048576000 [Basic data partition] [Artwork]

[Fiona]

Currently the entire Raid array shows up as "Disk 1 Unknown 4191.79GB Not Initialized" in Disk Management.

Since W2k, disk must be initalized in the Windows disk management console, that windows can handle it.
Don't use your RAID-controller to initialize it.
It could overwrite sectors and make recovery impossible.
Some user reported, that Windows creates partitions during converting from basic to GPT.
In case, don't format anything.
TestDisk should find your partition using the boot sector and its backup.
Have a retry to write it to your GUID-partition table.

[metagraphica]

Fiona,

Thanks for the quick reply. I've brought the disk online in Win7 and am running the 'Deeper Search' on it again. It takes about 28 hours for the 'Deeper Search' to run so I'll let you know the results tomorrow.

-meta

[remy]

28 hours passed, but for next time :Edit : 28hours not passed. I have read the date/time of your inscription.

With 6.14, while deepersearch, you may "go to the end of the partition just recovered" with F key. In your case, deepersearch would have taken some seconds.

Something else : You killed your array, thus loosing partition table. But you probably did not erase the secondary GPT table, that is at the end of the disk.

Booting with a linux live-USB in such a case, you should have been able to recover your partitions and reconstruct your primary GPT header with "pdisk" quite easily. Perhaps it would be a good idea to have a look, before loosing the raid happens another time.

[metagraphica]

Fiona, Remy,

Thanks for the extra advice. I'll have to remember it for the next time this happens (hopefully NEVER).
I was only running v6.13 so I couldn't skip but that was OK as it just ran while I was sleeping and at work.

Test disk finished the 'Deep Search' about 15 minutes ago and was able to write the partitions. Everything is fully functional again. No loss of data. Thanks much for everyone's help! Donation on it's way!

-meta

[Fiona]

Thank you for your feedback!
I'll set your topic as solved.