Couldn't certify a disk - Functionality Issues

RE: Couldn't certify a disk

SoftRAID Support — Mon, 23 Jun 2025 18:00:52 +0000

I cannot find what the fix was of the earlier user, I don't know who gave the advice.
So lets start fresh:

Run the Windows Diagnostic program with the drives connected. You can download it here: https://download.owc.com/diagnostics/windows

This should generate a .ZIP file - When you get a response, reply with the zip file and any other descriptive information that can help them (copy/paste this post).

send it to support @ softraid.com

RE: Couldn't certify a disk

SoftRAID Support — Tue, 17 Jun 2025 18:36:23 +0000

@dimsimlim

I am still researching what happened. I think this was fixed "over the phone", so I am not sure what the fix was.

RE: Couldn't certify a disk

dimsimlim — Fri, 13 Jun 2025 23:49:56 +0000

@doc52 Hey mate could you please explain the solution you ended up with? im having the same error codes with 2 out of 4 seagate barracudas 4tb. 2938

thanks for your help

RE: Couldn't certify a disk

Doc52 — Sat, 03 May 2025 15:01:58 +0000

The guys got back to me and fixed the issue, thank you.
Sincere apologies for not posting this earlier, have been away with medical issues, did not mean to be rude.

RE: Couldn't certify a disk

Doc52 — Sat, 15 Apr 2023 11:05:53 +0000

All done - awaiting your results.
Thank you.

RE: Couldn't certify a disk

SoftRAID Support — Mon, 03 Apr 2023 16:08:10 +0000

@doc52

Go to Softraid.com/support and create a support case.
then wait for a response.

Run the Windows Diagnostic program with the drives connected. You can download it here: https://download.owc.com/diagnostics/windows

This should generate a .ZIP file - When you get a response from tech support, reply with the zip file and any other descriptive information that can help them (copy/paste this post).

This could be related to hardware and is outside my abilities.

RE: Couldn't certify a disk

Doc52 — Mon, 03 Apr 2023 06:15:36 +0000

@softraid-support Hi.

Details:
4 brand new 18Tb Iron Wolf Pro's.
One Brand new OWC Thunderbay 8
And a newbie to this particular system ... hey what could go wrong ? 😀
I've been building systems and networks for over 25 years, as well as running over VPN backups off site through PfSense boxes etc, with the likes of Unison, Command line and batch backups.
So I have a bit of tech ability, (Enough to be self dangerous I guess 😉 ) however SoftRAID and the OWC environment is all new to me and I'm keen to learn.

Following the instructions I added the drives to the first 4 bays A-D
The initial issue was in Bay A It failed to see a drive and would not even allow a verify of the disk.
It showed as Disk bay A - 0 bytes, 0 bytes free but would not allow any actions at all.

I then swapped the drive to Bay D and had the same issue.
So I assumed the disk was faulty and have since returned it for a new one.

At which point I had the D drive in bay A and decided to run a certify on it, and away it went.
I then decided to do the same on B and C bays.
That is when I had the issues :

1.
Couldn't certify Disk 9: ST18000NE000-2YY101
The system cannot find message text for message number 0x in the message file for.(Exception from HRESULT:0x8007013D)

2.
Couldn't certify Disk 8: ST18000NE000-2YY101
Exception from HRESULT:0xFDC50020

Really weird, as I could not find any information on these errors..

I am awaiting the new drive at which point I will attempt to certify all 4 at the same time.

Any suggestions are more than welcome.

Cheers.

Doc

RE: Couldn't certify a disk

SoftRAID Support — Fri, 31 Mar 2023 15:28:53 +0000

@Doc52

this is why certify is good. I am checking with the windows engineer on these errors, I am not familiar with them.
one thing to check, are all the drives that failed on one side of the enclosure? A Thunderbay has 4 independent PCI buses, or lanes. If this were an enclosure issue the issues would stay in a set of 2 together, often. So if the drives are failing in random locations, that helps point to the drives.
I assume the failing disks do not show "predictive failure"? (reallocated sectors or SMART failure)

Couldn't certify a disk

Doc52 — Fri, 31 Mar 2023 03:57:34 +0000

Hi Guys, Doc in Canberra Australia and a Newbie.

I've just bought the OWC Thunderbay 8 and added 4 18TB Iron Wolf Pro's to the first 4 bays.
Had to send 1 drive back as it simply didnt show on the Softraid Start-up at all and the other 3 did.
One of the 3 is doing a 7 day certify and the other two have done the verification test and come out as AOK.
This is where it gets a bit strange.
.

The two that have completed verification will not do the Certification, and yes I tried the Certify first, figured as it did not work I would do the Verify and then try the certify test.
Nope these two brand new have the following errors:

1.
Couldn't certify Disk 9: ST18000NE000-2YY101
The system cannot find message text for message number 0x in the message file for.(Exception from HRESULT:0x8007013D)

2.
Couldn't certify Disk 8: ST18000NE000-2YY101
Exception from HRESULT:0xFDC50020

Both written as you see them above.

Have I got two more bad brand new disks or am I getting a softraid, software issue?
Both disks verified as AOK and both show as healthy, but neither will certify.
They are both Iron Wolf Pro disks.

I am, as I write, certifying 3 disks and they are all happily churning away.
Two 3TB Seagate's and 1x18 TB Iron Wolf Pro.

Any advice / help appreciated.

Regards.
Doc