• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
We have new content about Hotkey issue, Click here to check it out!
HP Recommended
z840
Microsoft Windows 10 (64-bit)

Hi all, 

 

I'm setting up a refurb z840 that shipped with 4 X 4 HP 4TB SAS drives. I decided to create a raid 10 in the LSI SAS bios utility. I couldn't find any very specific documentation on this and I wonder, how long does it take to become fully operational? It's been up about 20 hours now and there still seems to be constant disk access, and bizarre disk benchmark results. That said, it's entirely usable in Windows 10, it just doesn't feel very fast.

 

Within the LSI utility itself it still says 0% Initialized - it hasn't changed at all, as in the screenshot below.

 

Would be grateful if anyone who has any experience of this could offer any thoughts,

 

Ollie

 

 

20200911_200849.jpg

1 ACCEPTED SOLUTION

Accepted Solutions
HP Recommended

this behaviour is normal, during times of prolonged inactivity windows will instruct the disk controller to perform housekeeping tasks, such as defragging drives, checking file consistency and so on after a while this  will become a task that compleats quite quickly unless you have written many new files to the drive or changed many files on the drive

View solution in original post

9 REPLIES 9
HP Recommended

the onboard LSI ROC chip, like most lowend LSI cards can take anywhere from 20 min to over a day to finish the background initialization task

 

create the array, leave that screen (don't reboot, just back out), and then go back after an hour or two, it may show progress. Some controllers abort initialization during a restart, so you'll never see progress if you don't leave it alone.

 

and benchmarking a drive array that is doing a background init is sure to give crazy results so don't do it

HP Recommended

Many thanks for your help!

 

In the meantime I had left it in Windows over night and now it seems to be built,  and reports  Status - Optimal, Task - None in the LSI  bios., constant disk access has stopped.

 

Should I rebuild it any way as you suggested?

 

Best,

 

Ollie

HP Recommended

huh?.......in my reply to you i NEVER said to manually start a rebuild!!!

 

 

far from it,...i told you to leave it alone and let it finish the init by itself

 

go back and reread what i wrote carefully

HP Recommended

Apologies, it seems to have finished building overnight.

 

My question was that given I clearly didn't leave it when I first created it, whether I should delete this array and build it from scratch as you suggested.

 

 

HP Recommended

unless you like waiting for the background init to finish leave the array alone!!!!

 

there is no benefit to re-doing a working array

HP Recommended

All seems to be working well now after the initialisation finished, performance is decent.

 

However, there are occasional long bouts of noisy disk access that take place after the system has become idle. I can be working all day accessing the raid , with it almost whisper quiet, and after 20 mins or so or not doing anything, noisy disk accessing sounds start, while nothing is going on at an OS level. Just moving the mouse causes the noise to stop.  

 

Any idea what this could be? LSI bios does not report any errors. 

 

Many thanks

 

 

HP Recommended

this behaviour is normal, during times of prolonged inactivity windows will instruct the disk controller to perform housekeeping tasks, such as defragging drives, checking file consistency and so on after a while this  will become a task that compleats quite quickly unless you have written many new files to the drive or changed many files on the drive

HP Recommended

ok good to know, many thanks for the reply!

HP Recommended

DGroves was quite right, scheduled defragging was causing the issue. Once that was disabled the issue was resolved. 

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.