F5F Stay Refreshed Hardware Desktop Issue with RAID 1 array experiencing extremely slow startup—boots in 1 to 2 minutes due to significant delays.

Issue with RAID 1 array experiencing extremely slow startup—boots in 1 to 2 minutes due to significant delays.

Issue with RAID 1 array experiencing extremely slow startup—boots in 1 to 2 minutes due to significant delays.

Z
zStarfletcher
Member
Find
69
02-14-2020, 09:13 AM
#1
Hello, I built my own desktop system with a RAID 1 setup. Recently, the BIOS indicated that the RAID array was in a degraded state, which likely means one of the hard drives failed. At the same time, my boot times have become extremely slow—sometimes taking 1 to 2 minutes to start Windows. Since I installed Windows 10 on a fast NVMe SSD, I’m puzzled about why it takes so long to load. My system has a motherboard from Asus, 16 GB of DDR4 RAM, an overclocked i9 CPU, and a powerful RTX 3090 GPU. The power supply is decent, but the storage configuration is causing delays. My main concern is whether a degraded RAID 1 array could really lead to such long boot times.
Reply
Reply
Z
zStarfletcher
02-14-2020, 09:13 AM #1

Hello, I built my own desktop system with a RAID 1 setup. Recently, the BIOS indicated that the RAID array was in a degraded state, which likely means one of the hard drives failed. At the same time, my boot times have become extremely slow—sometimes taking 1 to 2 minutes to start Windows. Since I installed Windows 10 on a fast NVMe SSD, I’m puzzled about why it takes so long to load. My system has a motherboard from Asus, 16 GB of DDR4 RAM, an overclocked i9 CPU, and a powerful RTX 3090 GPU. The power supply is decent, but the storage configuration is causing delays. My main concern is whether a degraded RAID 1 array could really lead to such long boot times.

Reply
Reply
A
Almazik
Member
Find
56
02-16-2020, 06:16 PM
#2
When working with a hardware RAID configuration on your graphics card, the controller might take longer to boot because of a failed drive. This issue was observed on an older Intel system. The RAID interface display would stay active for a longer time after a failure compared to normal operation. While it shouldn't directly impact Windows performance, I haven't confirmed it definitively.
Reply
Reply
A
Almazik
02-16-2020, 06:16 PM #2

When working with a hardware RAID configuration on your graphics card, the controller might take longer to boot because of a failed drive. This issue was observed on an older Intel system. The RAID interface display would stay active for a longer time after a failure compared to normal operation. While it shouldn't directly impact Windows performance, I haven't confirmed it definitively.

Reply
Reply
F
FIZZY258
Member
Find
248
02-16-2020, 07:43 PM
#3
This depends on your configuration. With Intel's RAID, a failing drive might trigger a BIOS response to protect data, but it doesn't always cause a boot delay unless the array is configured for redundancy. Check your specific RAID settings and firmware behavior.
Reply
Reply
F
FIZZY258
02-16-2020, 07:43 PM #3

This depends on your configuration. With Intel's RAID, a failing drive might trigger a BIOS response to protect data, but it doesn't always cause a boot delay unless the array is configured for redundancy. Check your specific RAID settings and firmware behavior.

Reply
Reply
U
UglySlime
Junior Member
Find
8
03-09-2020, 04:02 AM
#4
Your message isn't well formulated. Do you experience a noticeable delay before Windows begins booting, or does it start quickly but run slowly during startup? If the delay is significant, it may indicate a degraded RAID setup.
Reply
Reply
U
UglySlime
03-09-2020, 04:02 AM #4

Your message isn't well formulated. Do you experience a noticeable delay before Windows begins booting, or does it start quickly but run slowly during startup? If the delay is significant, it may indicate a degraded RAID setup.

Reply
Reply
P
pocio77
Posting Freak
Find
783
03-09-2020, 05:27 AM
#5
It requires a brief pause—about 1 to 2 seconds—before Windows starts loading. Initially, it remains stuck on the Asus logo. Once it finally boots, the process becomes smooth and fast.
Reply
Reply
P
pocio77
03-09-2020, 05:27 AM #5

It requires a brief pause—about 1 to 2 seconds—before Windows starts loading. Initially, it remains stuck on the Asus logo. Once it finally boots, the process becomes smooth and fast.

Reply
Reply
J
Jowa_02
Member
Find
53
03-11-2020, 03:16 AM
#6
You can either wait for the BIOS to finish rebuilding or restart the PC and boot into Windows. Both options are safe, but restarting is often faster and avoids potential issues during the rebuild process.
Reply
Reply
J
Jowa_02
03-11-2020, 03:16 AM #6

You can either wait for the BIOS to finish rebuilding or restart the PC and boot into Windows. Both options are safe, but restarting is often faster and avoids potential issues during the rebuild process.

Reply
Reply
I
ilija
Member
Find
206
03-11-2020, 04:05 PM
#7
I’ve moved away from RAID1 and returned to a standard legacy configuration. I’m not overly concerned about it, just in case a drive fails I can replace and rebuild it. If the mainboard fails or settings go wrong, things could get worse. I have two Seagate Exos drives—one inside my PC and another in an Orico HDD bay that I can activate when needed. I set up a task scheduler to run robocopy D: E: /MIR in mirror mode, which helps protect against data loss or ransomware. This approach gives me more peace of mind and security.
Reply
Reply
I
ilija
03-11-2020, 04:05 PM #7

I’ve moved away from RAID1 and returned to a standard legacy configuration. I’m not overly concerned about it, just in case a drive fails I can replace and rebuild it. If the mainboard fails or settings go wrong, things could get worse. I have two Seagate Exos drives—one inside my PC and another in an Orico HDD bay that I can activate when needed. I set up a task scheduler to run robocopy D: E: /MIR in mirror mode, which helps protect against data loss or ransomware. This approach gives me more peace of mind and security.

Reply
Reply