[SOLVED] RADI 1 - suddenly both drives shows up in Explorer with different content

Schmoranz

Honorable
Aug 19, 2014
2
0
10,510
0
Hi, I have a RAID 1 setup of two 4TB WD Red drives (WD40EFRX). Motherboard is an ASUS X79-DELUXE.

I've been using it since 2014 for storing my finished projects and some other related materials.

Suddenly yesterday, both drives were visible in Explorer.
And the content of the drives differed. Here is an image:

https://ibb.co/6YYcb6N

It seemed that just a folder was missing. So the above property windows are there to see if there are actually difference on individual file level. Well, oviously yes.

In BIOS,my two 4TB disks are setup in RAID 1 as far as I can tell. Sata mode is not set to RAID (set to AHCI) but not all my disks are in RAID. I haven't made any changes to the computer at all since I was messing with WOL in 2018 or so. It just happened suddenly.
Here is a pic from the UEFI menu:

https://ibb.co/Sf9CDMN

I checked the disks with chkdisk too, but no ovious problems.
C:\WINDOWS\system32>chkdsk E:
The type of the file system is NTFS.
Volume label is Archive.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
298496 file records processed.
File verification completed.
Phase duration (File record verification): 4.86 seconds.
97 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.33 milliseconds.

Stage 2: Examining file name linkage ...
26677 reparse records processed.
340496 index entries processed.
Index verification completed.
Phase duration (Index verification): 27.04 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 128.69 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.31 milliseconds.
26677 reparse records processed.
Phase duration (Reparse point and Object ID verification): 73.71 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 20.80 milliseconds.
21001 data files processed.
Phase duration (Data attribute verification): 0.37 milliseconds.
CHKDSK is verifying Usn Journal...
35720328 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 253.49 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

3815293 MB total disk space.
1967517348 KB in 283321 files.
79608 KB in 21002 indexes.
0 KB in bad sectors.
518955 KB in use by the system.
65536 KB occupied by the log file.
1938745144 KB available on disk.

4096 bytes in each allocation unit.
976715263 total allocation units on disk.
484686286 allocation units available on disk.
Total duration: 32.39 seconds (32390 ms).

C:\WINDOWS\system32>chkdsk G:
The type of the file system is NTFS.
Volume label is Archive.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
247296 file records processed.
File verification completed.
Phase duration (File record verification): 4.12 seconds.
91 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.33 milliseconds.

Stage 2: Examining file name linkage ...
26919 reparse records processed.
278104 index entries processed.
Index verification completed.
Phase duration (Index verification): 23.88 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 89.03 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.39 milliseconds.
26919 reparse records processed.
Phase duration (Reparse point and Object ID verification): 71.21 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 36.98 milliseconds.
15405 data files processed.
Phase duration (Data attribute verification): 0.36 milliseconds.
CHKDSK is verifying Usn Journal...
36905832 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 309.08 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

3815293 MB total disk space.
1965683904 KB in 238530 files.
68812 KB in 15406 indexes.
0 KB in bad sectors.
468647 KB in use by the system.
65536 KB occupied by the log file.
1940639692 KB available on disk.

4096 bytes in each allocation unit.
976715263 total allocation units on disk.
485159923 allocation units available on disk.
Total duration: 28.51 seconds (28517 ms).

To be honest, I'm not really sure exactly what my question is, but something like "can I fix it easilly without backing up and reconfiguring the drives?" or even "think a drive could be bad? should I buy new ones?".

What I'm a bit worried about is files not syncing between drives and not being backed up.

Greatful for any help and sorry if there is information missing here.
 

USAFRet

Titan
Moderator
Mar 16, 2013
144,648
8,672
175,340
22,567
Backing up the data to some other drive and reconfiguring the RAID IS the way to do this.
Any other method carries risk of losing everything.

But...that backing up should have been going on anyway. RAID, of any type, is not a backup.
 

USAFRet

Titan
Moderator
Mar 16, 2013
144,648
8,672
175,340
22,567
Backing up the data to some other drive and reconfiguring the RAID IS the way to do this.
Any other method carries risk of losing everything.

But...that backing up should have been going on anyway. RAID, of any type, is not a backup.
 

ASK THE COMMUNITY