RAIDXpert2 Help: RAID 1 is "CRITICAL"

[Jonny_Quick]

C: Primary Boot HD: WD_BLACK SN770 2TB (2Tbyte NVME)
D: RAID1 (data only) SATA HDs:
- #1 *WDC WD4000FYYZ-05UL1B0 (4 Tbyte)* <--- ***BAD HD***
- #2 ST4000NM0035-1V4107 (4 Tbyte)

Not Assigned a Drive Letter: TEAM TM8FP6128G (Used to dual-boot into Linux Mint)

I built this PC 2 years ago, and set-up two 4-Gbyte HDs as a RAID 1, and now the software says the RAID is "Critical".
The research I've done says I need to replace the defective HD with a good one, BUT

In BIOS I turned off the RAID and selected AHCI, and then ran Victoria on both HDs. Victoria finds 16 uncorrectable blocks on the WDC 4 Tbyte HD,
but I want to know that it's 100% certain that the HD cannot be repaired and put back into use, before replacing it.

Also, I've never replaced a bad HD in a RAID1, and am afraid I'll do something and destroy the data that is on the good HD, so before doing
anything else, I'm here to find out what I should do.

I wonder if the common-sense 1st step is to simply indicate that the "bad" HD is a "spare" (whatever the RAIDXpert2 language is), and just let the
RAID software try to rebuild the array. Maybe the 16 uncorrectable blocks can be remapped? And again, I'm worried about doing something that
gets the data on the good HD overwritten.

Thanks in advance.

[WebClaw]

and then ran Victoria on both HDs.

Why did you run a high intensive I/O program on data you define as critical?

If the data is truly critical, treat it as such.

Create a 1:1 image / clone of the healthy (Seagate) 4TB drive using a program like OpenSuperClone. Then rebuild the array to a new drive by assigning the drive you replaced (WD) as a hot spare in the BIOS.

[Jonny_Quick]

and then ran Victoria on both HDs.

Why did you run a high intensive I/O program on data you define as critical?

If the data is truly critical, treat it as such.

Create a 1:1 image / clone of the healthy (Seagate) 4TB drive using a program like OpenSuperClone. Then rebuild the array to a new drive by assigning the drive you replaced (WD) as a hot spare in the BIOS.

I didn't define it as "critical", RAIDXpert2 said it was. I have no idea what that means. I'm trying to avoid buying a 3rd 4Tbyte HD. I want to know if the "bad one" is actually bad, and if it can be repaired, and the RAID rebuilt, and I want to know how to do it. I ran Victoria because it looked like "chkdsk" on steroids. Thought perhaps it would somehow fix things. Also the data isn't critical, but there is a lot of it, and I'd rather not lose it.

[WebClaw]

My bad - I incorrectly interpreted CRITICAL as your data, not the status of the array. Most controllers will simply say "Degraded" - though "Critical" sounds way cooler.

The actions you are performing will not silence the SMART warnings - so the output from your array will remain the same (in your case "critical"). The bad one is actually bad. That said, your next step is to perform a full SMART on the drive - so we can see all values; not just those which Victoria produced. This will likely provide proof of the claim.

[Jonny_Quick]

The actions you are performing will not silence the SMART warnings - so the output from your array will remain the same (in your case "critical"). The bad one is actually bad. That said, your next step is to perform a full SMART on the drive - so we can see all values; not just those which Victoria produced. This will likely provide proof of the claim.

How do I perform a "full SMART" on the drive? Special software?

How can you be certain the drive is 100% bad? In the past, I've run chkdsk and it does some kind of "repair", and things are fine after that.
I can't run chkdsk, or any other software that operates on a single drive, while it's configured as RAID, so I'm outside of my standard routine.
Isn't there any kind of whiz-bang software that can be run?
I'm actually prepared for purchasing a replacement HD, have it picked out on NewEgg, and if/when this WD HD gets reliably condemned, I intend to check here to see if the replacement HD is a good choice.

What I was mostly hoping for (here) was to find out how to indicate the good HD as the "original" and have the AMD RAID software (RAIDXpert2) just try to rebuild the array, but the main concern here was that I'd get it backwards and overwrite the good data on the good HD with whatever is on the bad HD. I get the idea that this software isn't very popular, as there isn't much documentation, and other people have let me know that software RAIDs are not good (for reasons I don't understand) and that if a person is determined to run a RAID 1, a dedicated hardware card is the way to go, so I have my eye on that idea as well.

This whole effort is, at least in part, a learning endeavor. I figured actually having a working RAID on my PC would be a good way to learn. And so, I have a concern because when I had RAID turned off in BIOS, and AHCI selected, and both HDs were being displayed by Win10's Disk Management as appearing normal, but for some reason I could not navigate either of them. I assume the RAID "did something" rendering the data inaccessible unless it's configured as a RAID, which is the exact opposite of what I thought would happen if one of the drives died.

So, I have @3 Tbytes of data on a "good" drive that I cannot access unless it's configured as a RAID. This is not what I expected, is the point. Next reboot I'll take a screen shot of what I'm looking at, and maybe you can explain what I'm seeing, and why.

[WebClaw]

Individual RAID members cannot be modified outside the RAID. If you run CHKDSK on a single drive which are members of a RAID you could corrupt your volume, I would not do that.

Running SMART (assume you don't R/W mount the drive) is fine. There are many tools that read SMART; given you've already connected the drives directly to Windows individually, I would suggest hddscan.com.

To answer your next Q:

CHKDSK = attempts to fix the file system.
SMART = health of disk internals, not file system / has nothing to do the filesystem.

SMART is telling you the internal functions of the drive are failing. Once this occurs, it cannot be "fixed".

How can you be certain the drive is 100% bad?

I don't have to be certain, your hard drive is telling you its encountering R/W issues. Your interpretation of "good" or "bad" may be different than mine. For me, a good hard drive is one that does not have R/W issues.

Perhaps this will help: https://www.asus.com/ca-en/support/faq/1049870/

[SWM]

Full SMART from the Victoria SMART tab. Special programs are used to read RAID disks under Windows. You cannot write to this disk or run CheckDisk. The data will be corrupted.

[Hardcore Games]

RAID is passe which today is given over JBOD. RAID5 tolerates one failed disk while RAID6 tolerates two failed disks.

[WebClaw]

RAID is passe which today is given over JBOD. RAID5 tolerates one failed disk while RAID6 tolerates two failed disks.

What an amazing resource you are! We're so lucky to have you!

[Jonny_Quick]

Full SMART from the Victoria SMART tab. Special programs are used to read RAID disks under Windows. You cannot write to this disk or run CheckDisk. The data will be corrupted.

I clicked several buttons in Victoria, and all I got was a blank page with rows and columns and no information at all.

However, the RAIDXpert2 software had a "query smart overview" button and it's output is pasted below, and "RAID_LOG.log" is attached.

NOTE: This log file was run while the BIOS was configured for "RAID", and I think Victoria can report SMART information if the BIOS is set for AHCI.

***Create SMART Log file for RAIDXpert2 ***
-------------------------------------------------
Disk 0 ( 0, 0): WDC WD4000FYYZ-05UL1B0
10/06/2026 11:30:35 PM

===============================
SMART ATTRIBUTES: Version 16

===============================
- Attribute ID: 0x01 (Raw Read Error Rate ),
Threshold Value: 000,
Current Value: 200 (Always Passing ),
Raw Value: 175

- Attribute ID: 0x03 (Spinup Time ),
Threshold Value: 000,
Current Value: 232 (Always Passing ),
Raw Value: 7391

- Attribute ID: 0x04 (Spinup Count ),
Threshold Value: 000,
Current Value: 100 (Always Passing ),
Raw Value: 323

- Attribute ID: 0x05 (Reallocation Count ),
Threshold Value: 000,
Current Value: 187 (Always Passing ),
Raw Value: 422

- Attribute ID: 0x07 (Seek Error Rate ),
Threshold Value: 000,
Current Value: 200 (Always Passing ),
Raw Value: 0

- Attribute ID: 0x09 (Poweron Time (Hours) ),
Threshold Value: 000,
Current Value: 075 (Always Passing ),
Raw Value: 18937

- Attribute ID: 0x0a (Spin Retry Count ),
Threshold Value: 000,
Current Value: 100 (Always Passing ),
Raw Value: 0

- Attribute ID: 0x0b (Calibration Retries ),
Threshold Value: 000,
Current Value: 100 (Always Passing ),
Raw Value: 0

- Attribute ID: 0x0c (Power Cycle Count ),
Threshold Value: 000,
Current Value: 100 (Always Passing ),
Raw Value: 259

- Attribute ID: 0xc0 (Emergency Retracts ),
Threshold Value: 000,
Current Value: 200 (Always Passing ),
Raw Value: 252

- Attribute ID: 0xc1 (Load/Unload Cycles ),
Threshold Value: 000,
Current Value: 200 (Always Passing ),
Raw Value: 71

- Attribute ID: 0xc2 (Temperature Celsius ),
Threshold Value: 000,
Current Value: 101 (Always Passing ),
Raw Value: 51

- Attribute ID: 0xc4 (Reallocation Events ),
Threshold Value: 000,
Current Value: 188 (Always Passing ),
Raw Value: 12

- Attribute ID: 0xc5 (Pending Sectors ),
Threshold Value: 000,
Current Value: 200 (Always Passing ),
Raw Value: 271

- Attribute ID: 0xc6 (Uncorrectable Reads ),
Threshold Value: 000,
Current Value: 200 (Always Passing ),
Raw Value: 271

- Attribute ID: 0xc7 (CRC Errors ),
Threshold Value: 000,
Current Value: 200 (Always Passing ),
Raw Value: 0

- Attribute ID: 0xc8 (Write Error Rate ),
Threshold Value: 000,
Current Value: 200 (Always Passing ),
Raw Value: 264


-------------------------------------------------
Disk 1 ( 0, 1): ST4000NM0035-1V4107
10/06/2026 11:30:36 PM

===============================
SMART ATTRIBUTES: Version 10

===============================
- Attribute ID: 0x01 (Raw Read Error Rate ),
Threshold Value: 000,
Current Value: 084 (Always Passing ),
Raw Value: 232241071

- Attribute ID: 0x03 (Spinup Time ),
Threshold Value: 000,
Current Value: 095 (Always Passing ),
Raw Value: 0

- Attribute ID: 0x04 (Spinup Count ),
Threshold Value: 000,
Current Value: 099 (Always Passing ),
Raw Value: 1789

- Attribute ID: 0x05 (Reallocation Count ),
Threshold Value: 000,
Current Value: 100 (Always Passing ),
Raw Value: 0

- Attribute ID: 0x07 (Seek Error Rate ),
Threshold Value: 000,
Current Value: 092 (Always Passing ),
Raw Value: 1635987678

- Attribute ID: 0x09 (Poweron Time (Hours) ),
Threshold Value: 000,
Current Value: 075 (Always Passing ),
Raw Value: 22729

- Attribute ID: 0x0a (Spin Retry Count ),
Threshold Value: 000,
Current Value: 100 (Always Passing ),
Raw Value: 0

- Attribute ID: 0x0c (Power Cycle Count ),
Threshold Value: 000,
Current Value: 100 (Always Passing ),
Raw Value: 276

- Attribute ID: 0xbb (Reported Uncorrect ),
Threshold Value: 000,
Current Value: 070 (Always Passing ),
Raw Value: 30

- Attribute ID: 0xbd (High Fly Writes ),
Threshold Value: 000,
Current Value: 100 (Always Passing ),
Raw Value: 0

- Attribute ID: 0xbe (Airflow Temperature ),
Threshold Value: 000,
Current Value: 051 (Always Passing ),
Raw Value: 825229361

- Attribute ID: 0xc0 (Emergency Retracts ),
Threshold Value: 000,
Current Value: 100 (Always Passing ),
Raw Value: 210

- Attribute ID: 0xc1 (Load/Unload Cycles ),
Threshold Value: 000,
Current Value: 045 (Always Passing ),
Raw Value: 111698

- Attribute ID: 0xc2 (Temperature Celsius ),
Threshold Value: 000,
Current Value: 049 (Always Passing ),
Raw Value: 49 (0 17 0 0)

- Attribute ID: 0xc3 (Recovered ECC Errors ),
Threshold Value: 000,
Current Value: 001 (Always Passing ),
Raw Value: 232241071

- Attribute ID: 0xc5 (Pending Sectors ),
Threshold Value: 000,
Current Value: 100 (Always Passing ),
Raw Value: 0

- Attribute ID: 0xc6 (Uncorrectable Reads ),
Threshold Value: 000,
Current Value: 100 (Always Passing ),
Raw Value: 0

- Attribute ID: 0xc7 (CRC Errors ),
Threshold Value: 000,
Current Value: 200 (Always Passing ),
Raw Value: 0

Attachments

RAID_LOG.log

(5.72 KiB) Downloaded 41 times

[Jonny_Quick]

You cannot write to this disk or run CheckDisk. The data will be corrupted.

Is this true? What if I physically pulled the "bad" HD off the computer, ran some magic "fixy" software on another system, and/or simply wiped and reformatted the HD, then introduced it back into the array as a "hot spare" (or whatever the RAIDXpert2 language is). I'm stuck on the idea that the reason why the HD is "bad" is due to the 16 uncorrectable sectors, but part of me sort of remembers that software like chkdsk can reallocate bad sectors and remap them to good ones. Or something like that. Also please note this is a learning experience, and that I barely know anything.

If I can wipe the HD on another system, and have it used in a rebuilt array, why can't I simply do it where it is?

[SWM]

This is just a warning. I don't mount faulty drives under Windows at all. It starts writing to them as soon as it sees them.

[SWM]

Disk 0 ( 0, 0): WDC WD4000FYYZ-05UL1B0
10/06/2026 11:30:35 PM

===============================
SMART ATTRIBUTES: Version 16

===============================

- Attribute ID: 0x05 (Reallocation Count ),
Threshold Value: 000,
Current Value: 187 (Always Passing - ),
Raw Value: 422

- Attribute ID: 0xc4 (Reallocation Events ),
Threshold Value: 000,
Current Value: 188 (Always Passing ),
Raw Value: 12

- Attribute ID: 0xc5 (Pending Sectors ),
Threshold Value: 000,
Current Value: 200 (Always Passing ),
Raw Value: 271

- Attribute ID: 0xc6 (Uncorrectable Reads ),
Threshold Value: 000,
Current Value: 200 (Always Passing ),
Raw Value: 271

This drive is faulty. 422 reallocated sectors, 271 pending write-reallocation, and an unknown number more unidentified.

The previous message meant that as soon as Windows sees a partition, it begins writing to it at its own discretion.

[SWM]

Bad sectors are detected during disk read/write operations and during idle periods (offline scan). Offline scanning is performed selectively, using the manufacturer's algorithm. There are always sectors that were not included in the current read or scan.
If a sector can be read after n attempts, it is reassigned. If not, the sector is awaiting a write (erase) and is reassigned.
WD HDDs tend to show fewer sectors in SMART (05) than are in the alt list.

[Jonny_Quick]

This drive is faulty. 422 reallocated sectors, 271 pending write-reallocation, and an unknown number more unidentified.

Does "faulty" mean non-repairable? I get the idea that there are 1) a large number of reallocated sectors, 2) a large number pending reallocation and 3) unknown number that are also probably bad, but at this point, does it 100% mean the HD is permanently and forevermore BAD? Is there a limit to the number of sectors that can be reallocated? It's a 4 Tbyte HD, which I imagine is an infinite ocean, and so a few square miles here and there, may not mean anything at the end of the day.

Also, I'm curious to know where and how in the SMART log you were able to see this? I've looked over several SMART logs and it all seems meaningless to me. Is there some kind of software that can translate a SMART log into a report that a layperson/newb can understand?

The previous message meant that as soon as Windows sees a partition, it begins writing to it at its own discretion.

Next reboot I'll post a screen shot of what Computer Management shows when the BIOS is selected to "AHCI" vs. RAID. It looks very odd to me, and if I recall both HDs are inaccessible due to what appears to be a non-standard formatting, maybe? Example the small SSD I use for Linux appears the same way, in that it's reported as being there, but no other information beyond that, so I have the theory that when the two 4 tbyte HDs are being configured as a RAID, they are formatted in something other than NTFS or GPT? And if so, how can Win10 arbitrarily write to them?

Finally, I'm also wondering about what happens to the data if the one good HD can no longer be accessed as part of a RAID array? I get the general impression that none of the data on a HD can be recovered if it is not being run as part of the original RAID it was a part of, meaning that the integrity of the data is 100% dependent on the AMD RAID software and the motherboard, and if (for example) the motherboard died for some reason, the data on the two RAID HDs would be lost forever? I'm curious about the difference between what I used to think was happening, which was a standard "mirror" between two HDs, where the data on both was just as accessible outside the RAID array as if they were inside it, but now I'm getting the idea that this is not true. What kinds of things is the RAID software doing to the HDs that make the data somehow different, compared to just simply copying the data to both HDs at the same time. "Mirror" doesn't convey all the technical truth, and that there is "something else" to think about in order to understand exactly what a RAID 1 is.

[WebClaw]

Does "faulty" mean non-repairable?

Yes.

I've looked over several SMART logs and it all seems meaningless to me.

A time machine would be the same for me. Try: https://en.wikipedia.org/wiki/Self-Moni ... Technology

we care about this:

Code:

Attribute   Raw value
05 Reallocated sectors   422
C4 Reallocation events   12
C5 Pending sectors   271
C6 Uncorrectable sectors   271
C8 Write errors   264


Finally, I'm also wondering about what happens to the data if the one good HD can no longer be accessed as part of a RAID array?

I would strongly suggest you just keep things simple. Turn on RAID, go back to critical and use the previously provided instructions to rebuild the array with a new disk.

motherboard died for some reason, the data on the two RAID HDs would be lost forever?

No. There is likely an offset of sorts at play. The RAID component in the BIOS is likely presenting it to Windows in a different manner due to meta-data needed to configure to RAID.

A RAID 1 is still a mirror, but that does not guarantee each member will appear as a normal standalone Windows disk. RAID metadata, disk offsets, and controller presentation can affect how the individual members are interpreted. The data isn't necessarily dependent on your motherboard surviving. In most cases, a RAID 1 can be reconstructed or accessed using compatible RAID software or hardware. Your WD has 422 reallocated sectors and 271 pending sectors. The drive has already exhausted any reasonable argument for continued production use. You might force those pending sectors to resolve, but that does not make the disk trustworthy again.

[WebClaw]

Just a thing I caught

ST4000NM0035-1V4107 >
Attribute ID: 0xbb (Reported Uncorrect)
Current Value: 070
Raw Value: 30

Your Seagate drive has some concerning issues too (at least in my opinion).

I'd image it as I initially suggested.

[ora]

I'm stuck on the idea that the reason why the HD is "bad" is due to the 16 uncorrectable sectors

No. The "bad" status was determined based on a large number of already reallocated sectors and a slightly smaller number of sectors pending reallocation. Another indicator that most likely wasn't taken into account by the software, but for Western Digital hard drives it is more than significant - write errors. Ideally, this value should be zero or very close to it, certainly not in the hundreds or thousands. This value indicates that the drive is damaged and will soon fail.

Of course, you can ignore all the warnings, but the result will be the hard drive being dropped from the array due to extremely slow performance and data errors - and this will likely go unnoticed, as the status will remain "critical." From now on, the array will only work on the single remaining disk; if it fails, you will lose data.

I don't know how to rebuild the array on this motherboard, so I can't advise you on that, but another thing you should pay attention to is the hard drive temperatures.
Disk 0 ( 0, 0): WDC WD4000FYYZ-05UL1B0
- Attribute ID: 0xc2 (Temperature Celsius ),
Raw Value: 51

Disk 1 ( 0, 1): ST4000NM0035-1V4107
- Attribute ID: 0xc2 (Temperature Celsius ),
Raw Value: 49

Temperatures above 40°C are considered undesirable, and continuous operation at 50–60°C significantly shortens the drives' lifespan - this has been proven in practice. It would be worth considering some form of cooling.

[WebClaw]

I'm stuck on the idea that the reason why the HD is "bad" is due to the 16 uncorrectable sectors

No. The "bad" status was determined based on a large number of already reallocated sectors and a slightly smaller number of sectors pending reallocation. Another indicator that most likely wasn't taken into account by the software, but for Western Digital hard drives it is more than significant - write errors. Ideally, this value should be zero or very close to it, certainly not in the hundreds or thousands. This value indicates that the drive is damaged and will soon fail.

Of course, you can ignore all the warnings, but the result will be the hard drive being dropped from the array due to extremely slow performance and data errors - and this will likely go unnoticed, as the status will remain "critical." From now on, the array will only work on the single remaining disk; if it fails, you will lose data.

I don't know how to rebuild the array on this motherboard, so I can't advise you on that, but another thing you should pay attention to is the hard drive temperatures.
Disk 0 ( 0, 0): WDC WD4000FYYZ-05UL1B0
- Attribute ID: 0xc2 (Temperature Celsius ),
Raw Value: 51

Disk 1 ( 0, 1): ST4000NM0035-1V4107
- Attribute ID: 0xc2 (Temperature Celsius ),
Raw Value: 49

Temperatures above 40°C are considered undesirable, and continuous operation at 50–60°C significantly shortens the drives' lifespan - this has been proven in practice. It would be worth considering some form of cooling.

Good call ora.

[Jonny_Quick]

we care about this:

Code:

Attribute   Raw value
05 Reallocated sectors   422
C4 Reallocation events   12
C5 Pending sectors   271
C6 Uncorrectable sectors   271
C8 Write errors   264


Ok, thanks. I'll get deep into this after I'm done posting here.

I would strongly suggest you just keep things simple. Turn on RAID, go back to critical and use the previously provided instructions to rebuild the array with a new disk.

Right. Well now I have no choice because the thing has gone tits-up, and the WD (BAD) HD can no longer be recognized by the AMD RAID software (it says "SMART ERROR" now), Victoria refuses to even start a scan, Windows Computer Management says it's "not initialized", and ... and ... and ...

So, I give up on trying to fix it, and instead think I should start a new thread asking for help on buying a new HD, so as to not clutter this thread up, because I really appreciate the general educational help here, and have a bunch more questions.

I'm adding "Disks.PNG" and "RAID.PNG" to show what it looks like in Computer Management now, and what it looks like in the AMD RAID software when the BIOS has the two HD's configured as RAID (in case people have never seen what the GUI looks like).

Attachments