Windows 10: RAID Drive becomes unavailable

I am running Win 10 Pro 64 bit. I have a RAID drive set up on my F drive. When I turn on my system it runs fine and is available, but after the PC sits idle for some time none of the files inside of it are available. In My PC I can still see the F drive listed, but I cannot open any of the folders/files inside of it. Any suggestions? Currently my PC is set to never turn off monitor/never put PC to sleep. Thanks in advance for any help you might offer.

Sam

:)

 

RAID recovery

I moved C: drive to RAID along with root partition for linux DURING the installation procedure . Then it asked me to create a root again as root partition was unavailable as i moved both of them to RAID. Then i installed linux. Right now i have 260 GB

free space 250GB RAID 300 GB NTFS (E And some other drives of linux. I dont have any important data on linux , so i can wipe it. (But how will i recover my C: Without an OS, I dont know about RAID at all, i was experimenting, how will i move C: to where it
was before?) I HAVE a windows 10 bootable USB with me as of now and i can access command prompt,

please help me out!

 

W10 corrupts W7 hard drive

W8.1 was working fine as a removable hard drive. W7 installed on a RAID array as multi partitions. Works fine and both OS can be booted and W8.1 reads the RAID array when booting as W8.1

W10 upgrade completed on removable 8.1 drive, but then checked RAID drives for errors and changed them.

W7 on raid no longer boots. After severel hours W7 finally re-installed on RAID array. (data is on other partition so ok.) Tested working all data recovered.

Here's the kicker.

As soon as I boot from W10 it says "reboot required to fix drives" then corrupts the Windows 7 install... Which doesn't need fixed!!

The drive containing W7 OS becomes unreadable although other data partitions on the RAID array are OK.

W7 recovery tries to fix the hard drive then fails.

W10 changed drive letters first attempt, so I thought this an easy fix, but in fact every fresh W7 install is corrupted as soon as I boot from W10.

This is a major problem. Why is W10 changing the drive parameters on a completely seperate fully operational operating system?

 

Tell us about the RAID.

What level is it. Specifying RAID without the level is meaningless.
Is it software RAID, implemented by the motherboard, or a separate controller.
What drives are being used.

 

Sorry, it is an external RAID array. I can see it in device manager/disk drives/ HzW RAID10. I have it as my F: drive

I believe that makes is a separate controller.

 

It sounds like power saving mode , the Drive has gone to sleep or been turned off to save power, either in the Power Scheme under Hard-drives or perhaps at the Controller if you allow Link Power Management ,which you may also see in your Power Scheme.

External Drives Hibernate too ....

 

If you use a Hardware Raid controller, when you restart the computer, you will have a quick screen asking if you want to boot into the RAID control panel using a key combo, like CTRL+S Here you can view the array, and check the health of each drive. and the health of the array. With a RAID 10, If one of your drives fails, you can replace it, boot into this control panel and Rebuild the Array and not loose any data.

 

I've not seen such a screen. I see a screen to boot into bios, but not into the raid array.

I have this device.

Mediasonic

https://dl.dropboxusercontent.com/u/...Manual-1.7.pdf

Now the lights on my device look the same as the right side of page 14. RAID 10Mirroring + Striping

I tried going into power management and changing when hard drives sleep to 0, but that did not work. I still lost the RAID after I left the PC alone for awhile this evening.

 

I have the same enclosure actually but the non raid version but have it running on USB3 instead of esata as my MB's Esata ports didn't do port replication properly , so I could only see 1 drive.

how old is it ? I know for mine there was a firmware released for a HD spindown issue But that was 3 yrs ago I think ?

are you connected to MB or Mediasonic's add in Esata Card? it may need a newer Driver version ?

It's not on the Product page but on the Forum there is a SW download for the onboard Raid Controller so you can manage it Mediasonic Forum • View topic - Jmicron HW Raid Manager Software for 4 Bay and 8 Bay Raid

I still suspect a power/hibernation issue , did you disable link power management too ?

are you set for s3 suspend in the Bios?

 

I am connected to my MB through eSATA. I have never updated the firmware on it and have owned it for more than 3 years. Where did you see the firmware update link ? I looked at the post, but the download links were no good. My firmware is V0.958 [11/17] Do I need it? I couldn't tell from the instructions as they don't mention that firmware.

I have a P8Z77-V PRO motherboard, and I am not sure if it supports Port Multiplier w/ FIS-based switching. I can just see the one drive, but that's what I thought would happen with the RAID 10 setting. Should I change the setting from eSATA

 

The link was to the JMicron Raid Controller Software for your ProBox , not to the Firmware which is in this post, but you need to email them for it at rma_east AT mediasonic.ca. (replace the AT and spaces with @)

Mediasonic Forum • View topic - Firmware Ver# 0.20.03.00.04 and hard drive Spin Down issue
---------------------------------------------------------------------------------------------
Note: If your enclosure does not have firmware version
0.20.03.00.04 on it. or the serial # of your enclosure starts with ***13 *** 14
(i.e. FEB13, APR13 etc..) Do NOT USE these Firmware Bellow

NOTE: Not for Rev. 02 or Rev. 03 enclosures
---------------------------------------------------------------------------------------------

are you sure about that firmware version ? What revision is the ProBox ?

Your 4 drives would show as 1 as you are using Raid , unlike my non-raid version , so I just used USB3 since I saw no advantage to esata , and I would of had to buy a esata Card with Port multiplier capability to get it.

Try it with USB3 and see if you have the same issue.

 

That was the firmware version I saw in the JMicron Raid Controller Software that you sent me earlier. Maybe that's just the software firmware version....

The serial number on the back is FEB 13***** So that means I do not need to update the firmware, right?

 

Two different things I think (below) but no it sounds like you are okay same as me with a unit made in '13 .....

V0.958 [11/17] = Raid Controller inside the ProRaid Box ? (can't confirm as I don't have Raid in my Probox)

255.31.3.41.22 or 0.20.03.00.04 = MediaSonic Firmware of the ProBox Motherboard

The Jmicron Software will let you fix/create the raid and verify it etc , at least that's what the Intel Raid software on my Motherboard does. You won't see the Boot message as mentioned above as the Raid Controller isn't on the MBoard.

I turned Link management off under PCIE on my system too (its a power saving scheme )

Try the USB3 hookup and see if the issue is the same

 

What do these numbers reflect about the state of the drive being scanned?






Everything here looks good....I think.

HzW RAID10 (EXRRUIW50BSAIIDTB76E);2016/07/09 06:39:59;0;3;HzW RAID10 (EXRRUIW50BSAIIDTB76E);ST2000DM001-1CH164 (Z1E4AE19);0;1;0
HzW RAID10 (EXRRUIW50BSAIIDTB76E);2016/07/09 06:39:59;0;3;HzW RAID10 (EXRRUIW50BSAIIDTB76E);ST2000DM001-1CH164 (Z1E4AE4S);1;1;0
HzW RAID10 (EXRRUIW50BSAIIDTB76E);2016/07/09 06:39:59;0;3;HzW RAID10 (EXRRUIW50BSAIIDTB76E);ST2000DM001-1CH164 (Z1E4AE1W);2;1;0
HzW RAID10 (EXRRUIW50BSAIIDTB76E);2016/07/09 06:39:59;0;3;HzW RAID10 (EXRRUIW50BSAIIDTB76E);ST2000DM001-1CH164 (Z1E4AE1K);3;1;0


A member disk is plugged in.
HzW RAID10 (EXRRUIW50BSAIIDTB76E) is in NORMAL state.

I also have turned Link management off under PCIE


I now have my device connected via USB3. We'll see if that solves the problem. I'll let you know. Thanks again for your help.

 

For Smart info I usually check this page......

List of S.M.A.R.T. Attributes