Question Windows 10 with SDD as C, RAID 1 with a Smart Event starting it very slow

[caliskier]

Hi,

I have a windows 10 PC with a MSI motherboard that I set up two 2TB HDD in RAID 1 (Mirror) using the MSI onboard RAID controller, not a s Software RAID.

One of the disks says "Smart Event" in yellow on startup with the total raid "bootable" and in "rebuild" mode. I was able to get all my data backed up onto other drives.
Windows starts very very slowly even after Windows 10 refresh.

Question one, are the two issues related? Smart Event and slow windows 10 start?
Question two, its not very clear which disk is in "smart event" mode. How is that determined?

For Question 2, here is what I know:
Cant determine anything in the device manager, it just says you have a RAID 1 working fine.
In BIOS I cant tell anything.
On startup I see the raid volume is in rebuild status, and both disks and their model (models are identical) and serial numbers, and I can tell by serial number which has the smart event (maybe that serial number is printed on the drive and I can figure it out that way)
I also see an ID number which are 4 and 5, while drive numbers are 5 and 6.

Also as a 3rd piece of information. Before I wiped the machine it was freezing often, like every hour or if I tried to wake it up with the mouse it would wake up and I can see the screen, but no mouse movement, frozen, no control alt delete. When I went to pull the drives to protect them for the windows refresh I did not remember were the wires went (woops,) and plugged them back in wrong and crossed the raid drive with another 3TB drive I use for TV recording. I turned it on with them plugged in wrong and it said the status was degraded, I fixed this and now it says Smart Event on one of the drives as described above.
Note 1: All this happened BEFORE I wipped the C SSD for Windows 10 reinstall.
Note 2: Its possible and likely that I was having a "smart event" before I screwed up the wires on the HDDs. I saw yellow text when I would start the computer but did not pay attn. I would have expected it to be much more clear like "Hey dude! your RAID is Failing!!!" I know what to look for now.

Can anyone give me some guidance?

 

[caliskier]

Yep, that WD External would work just fine.
Pricewise, 2TB is rather slim these days. A few months ago, I bought an 8TB for $140.
Currently, $131.
https://www.amazon.com/gp/product/B07CQJBSQL

I would NOT use the WD (or Seagate) software to do this.
Instead, the Macrium schedule that you're already going to use.
Keep the backups under one sphere of functionality.

So I am reading up on the Marcium Reflect SW this morning and I read this here:Differential Image

Disadvantages of differential images:

• As the time since the last full image was taken increases, the size of the differential grows as does the time it takes to create the differential image.
• In order to reduce this time, it is necessary to perform a full image occasionally to reduce the size of the subsequent differential images.

I don't understand. If I am daily or weekly doing a differential image, i am expecting it, when done, to look exactly like my main installed data drive. Why would it be different such that I need to "perform a full image" occasionally? What I am hoping it does is replace the image in an emergency regardless of how many times i have deferentially updated, is that not how it works? (note, I am assuming in an emergency when I am refreshing the data to a new drive, its copy paste)

 

[USAFRet]

OK.

Differential
There is a Full Image, and then a series of Differential.
The Differential contains ALL the changes since the last Full Image.
You need both files to fully recreate the contents.

So, in case of need, you simply select the Differential you want. (usually the very last one) and it will find its previous Full and recreate all of that on the target drive.

Downside is that each Diff gets larger than the previous, and takes longer to save.
Eventually, you have a HUGE Differential from the original Full Image.

So, create a new Full, and then then next and subsequent Diffs will be smaller.
Delete the older Full and Diffs.


Incremental
There is a Full, and then a series of Incrementals.
Each Incremental contains only the changes since the last Incremental.

This has the advantage of much smaller files sizes and faster saving of each.
However, to reconstruct...you need ALL of the intervening Incrementals and the original Full Image.


Both concepts work. I've used both.

 

[USAFRet]

(note, I am assuming in an emergency when I am refreshing the data to a new drive, its copy paste)

No, it is NOT copy/paste.

You go through the Macrium client and tell it which Image to reconstitute.
If Differentials, just select last nights Diff, and it will figure it out.

Writing that whole Diff and Full out to the new replacement drive.
Data, OS, boot partition...everything that was included.

And if you're rebuilding the C drive, you'll need a RescueCD or USB.
Boot from that, and point it at the relevant Image(s) to recover.
I've done this as well.
I have a bootable Macrium RescueUSB sitting in the bottom of my case. If I need it...I need to open the case anyway to swap a drive.
It won't get lost in there.

 

[caliskier]

No, it is NOT copy/paste.

You go through the Macrium client and tell it which Image to reconstitute.
If Differentials, just select last nights Diff, and it will figure it out.

Writing that whole Diff and Full out to the new replacement drive.
Data, OS, boot partition...everything that was included.

And if you're rebuilding the C drive, you'll need a RescueCD or USB.
Boot from that, and point it at the relevant Image(s) to recover.
I've done this as well.
I have a bootable Macrium RescueUSB sitting in the bottom of my case. If I need it...I need to open the case anyway to swap a drive.
It won't get lost in there.

Ok, Marcium stiches it together for me, the diff and full. I get it, just need to play with it. Thanks again. I should never have a Cdrive issue or at least I am not worrying about it. Maybe I should be? Other than OS and apps thats all that is on it and I am using a SSD for it.

 

[USAFRet]

Drive issues happen.

As related earlier, one of my SSD's died suddenly.
Zero warning...just dead.

Being proactive with backups is how you belay that.
Drives can be replaced. Software and your personal files can't.

 

[caliskier]

Ok, update, so I let it run through the process, did not restart for 3 days. Status has changed.

This does not mean I am not going to do the Marcium reflect, you have sold me on that. I am wondering what this means however...

On startup it says the status of my RAID1 is Normal. Under the Divises for that RAID it lists the same disk as having the SMART event and the other disk has Member Disk.

what does this mean?

Also Windows is still taking like 5 min to start once i get past the BIOS screen