Pool read only while balancing

[ThePaladinTech]

I am working on my brothers drive pool, and when his pool is balancing it becomes read only until balancing is done. Why is that? How can I fix it?, mine doesn't act this way and our setups are about the same. Windows ten, lsi controller, etc. If there are any logs or information needed please let me know and I'll get it. Thanks

[montejw360]

is it "just balancing", or did you remove a drive? If you remove a drive it will go read only.

[ThePaladinTech]

Nope, its just balancing. An unlicensed pool will go read only too, but it's licensed

[Christopher (Drashna)]

It shouldn't become read only like this. 

 

There are two reasons that this would happen. 

1. Licensing status (but this doesn't make the pool completely read only),
2. A disk is dropping out from the system.

 More than likely, it's the second. The act of balancing is probably overloading one of the disks, and causing it to drop out of the system, temporarily.  This would cause the disk to be missing from the pool, and set the pool to a read only state.   Once the disk shows back up, it would return to normal. 

 

 

This should show up in the logs, if it's not showing up in the UI. 

 

You can upload the logs by running the StableBit Troubleshooter, and I can take a look. If you'd like. 

http://dl.covecube.com/Troubleshooter/StableBit.Troubleshooter.exe

 

 

 

 

And by chance, are you using a Silicon Images card, or a HighPoint card? 

[ThePaladinTech]

No, Using an LSI controller: SAS9211-8I

Windows 10 Creator Update

 

I few weeks ago we upgraded the whole computer. and discovered a few drives were suspect by StableBit Scanner (the drives not bad, but things known to stablebit message?) - Anyhow, we removed those 3 drives from the pool, and I brought 3 replacement drives up. The drives were removed from the pool Before april 15th.  On (I think) april 15th we added the new drives and did the balancing.  Looking at the logs (which I sent you) ... I see this error several times:

DrivePool.Service.exe	Warning	0	[RemoveDriveFromPool] Error shutting down in use applications. No action was taken as a system reboot is required	2017-04-15 20:37:52Z	288718450636
DrivePool.Service.exe	Information	0	[FsControl] Clear pool mode: PoolModeNoCreateDirectories (key=CoveFsPool)	2017-04-15 21:02:25Z	309803486377
DrivePool.Service.exe	Information	0	[FsControl] Set overall pool mode: PoolModeReadOnly, PoolModeNoReportIncomplete, PoolModeOverrideAllowCreateDirectories, PoolModeNoMeasure, PoolModeNoReparse	2017-04-15 21:02:25Z	309803489415
DrivePool.Service.exe	Warning	0	[RemoveDriveFromPool] Error on final delete after drive removal for \\?\Volume{4d6acdd6-0000-0000-0000-100000000000}\PoolPart.0f4421bc-176a-457a-90e3-f73b6df7acb0\. Unable to delete all files after removing pool part.	2017-04-15 21:43:30Z	345100228277

Please look over the logs I was there April 14-16 - One of those days was when we had the problem ... I think it was the 15th. And I do not know if it is still having problems.

 

Also on the 16th there are a TON of warnings, they appear to be related to non duplicated files? I don't see any errors after the 16th but don't know if that means it's 'better' or not.

 

Also - Should I upgrade to the latest Beta? I'm running the release version right now... It is Windows 10 Creator update, and I did see some updates related to windows 10 in the betas.  At home I have since upgraded to the latest beta, wondering if it would be a good idea for my brother as well.

 

Thanks, and glad you're feeling better.

[Christopher (Drashna)]

Well, if you were removing the disk from the pool, this does set the pool to a read only state.  That would be normal, and that is to help prevent any new files from being opened/locked, so that we can move the files around without issue. 

 

As for using the beta version, yes.  There are some significant changes to the balancing and measuring code, and there are some disk removal fixes, that may address the specific issue you're seeing.