maximusfacq

@johnnie.black Thanks for the solution without the judgement! That did the trick!

Once the preclear on the new disk finished (disk11 Now), I added it to the array and started copying files to it, from disk9. disk9 is the disk I want to replace, with what is now disk11. How to I move disk9 out of the array, and keep the files on disk11, that I moved to it from disk9, all while making disk11, the new disk9?

Ok. So, I let my data get ahead of my storage capacity and I now have a problem. I have: A 10 TB Parity Disk Multiple 4TB Data Disks, Multiple 3TB Data Disks, and 2 8TB Data Disks (Now, totaling 11 Data Disks) 2 - 512MB M.2 SSDs as a Cache Pool I had high water settings on my Data Disks for 500GB, so as not to let them get too full. However, multiple disks are now hitting that mark and I needed to move some data around. I was doing some of this while the latest 8TB data disk addition was preclearing. But, there was only so much I could juggle with such limited free space available. disk9 (3TB), in my array is the disk I wanted to use disk11 to replace. However, I ran out of space before I could move all the data off of disk9. Then, the preclearing of disk11 completed, and I had this <sarcasm>Brilliant</sarcasm> idea to add that to the array, and move all the data off of disk9, remove disk9 from the array, and make the new disk11 become disk9. Then, just run the Tools > New Permissions task, and be all set, right? That's where the wheels started turning and I thought myself into a conundrum. If I do try to swap the new disk11 for the current disk9, won't a parity check try to overwrite disk11 with 0s, because I've cleared disk9 before removal? I've searched the forums a bit, and found similar questions, with different answers. I have a problem with that. There should be a definitive answer for this scenario. Will someone please save me from myself and help me with the correct steps to get out of this situation? The end goal is to make the small 3TB disk go away, and replace it with the new 8TB disk, and not suffer any data loss. Appreciate your time, in advance.

I can also confirm this process works. I have converted 6 of my 9 data disks to XFS from ReiserFS. I started by adding a new data disk as XFS. Then, migrated data from one disk to the next, stopped the array, changed the format setting, started the array, and hit the format button. It's really just that simple. Thanks @limetech!

Eureka!! Night and Day difference! 77.1 MB/s Data Rebuild now. Thanks for the head bonk @johnnie.black!! And remember kids... the AOC-SASLP-MV8 Controller DOES NOT LIKE the 16x PCIe slot! Seems to dig the 8x slot on my mobo.

I had the controller in a PCIe 16x slot. I seem to recall reading something about others having issues with that and my controller card. I've moved it to another slot. Will begin testing shortly.

@johnnie.black, Thanks for that info. I have the latest BIOS for my mobo. I have the latest version of unRAID (I only count stable, release versions). I've rebooted several times. At this point, the only option I see, if it's an IRQ issue, is to go into the BIOS and look for crap to disable. I will try that now. If anyone has any other ideas, please feel free to chime in.

Yes. Sorry. That file was generated just after I re-checked the BIOS to see if I'd missed any settings I needed to change, and prior to re-starting the Re-Build. Here's a new one. unraid-diagnostics-20160706-1452.zip

I was attempting to transfer some data from disk1 to disk8 in my array (I want to move all my data disk from ReiserFS to XFS). At some point in this ungodly slow transfer (60 KB/s, at times), disk8 started generating errors. This, of course, angered unRAID and it flagged disk8 as bad. A SMART test of the drive revealed it was fine. Nonetheless, due diligence warranted I replace the power and Sata cables connected to that disk. There was no Trust Array option I could find in 6.x, like I used to see in 5.x. So, I swapped out disk8 with a hot spare, pre-cleared disk, and initiated the Data Rebuild. It started slow, like usual, at 2.5MB/s. When I checked back, a few minutes later, it still was showing the rebuild at 2.5 MB/s. This struck me as odd, because when I upgraded the system last week, one of the first things I did was test the pre-clear process on a new disk. That was running at 170 MB/s, at times (This was an increase over what I'd seen with my old CPU, Mobo, and RAM ~130 MB/s peak). So, my expectation was that Data Rebuilds might also be a little faster than before. The last one I did peaked at ~70 MB/s. The slow rebuild continued for 12 hours overnight, still at 2.5 MB/s. I've attached the unraid-diagnostics report. I'm not sure what the root cause may be. But, this is extremely frustrating and I'm at a loss as to why things would be so slow with the huge upgrades I just did. Old CPU, Mobo, RAM: Intel i3 (Don't recall the model. 2130 perhaps?) Gigabyte Z68MX-UD2H-B3 4GB Ballistix RAM New CPU, Mobo, RAM: Intel i7 6700K Gigabyte Z170X-Gaming 7 Rev 1.0 32GB GSkill Ripjaws Any ideas as to what the issue may be? Thanks, in advance, for your time. P.S. Also running firmware 21 for my SuperMicro AOC-SASLP-MV8 Controller unraid-diagnostics-20160706-1359.zip

@jonathanm, Being that I had already pre-cleared the disk prior to setting it up as the cache disk, I expected to just be able to set it as a data disk and simply format it. I was mistaken. :'(

@RobJ, I posted this here due to the seemingly uncommon knowledge that the above behavior occurs when multiple disks are added as cache disks. There should be some kind of "WARNING:" or "NOTICE:" block of text in the Cache Devices screen that indicates what repercussions could be caused with actions therein.

@jonathanm, After recovering all the data, I re-added the 2 disks as a cache clustered-pair. I was able to force the formatting of the one unmountable cache disk. Then, I added the old cache disk to the data array. I'm now waiting, for who knows how long, for the WebUI to show that the disk is cleared. I wish there was a faster way to do this and still allow access to my shares. >.<

@jonathanm, Thanks for the tip on that plugin. I wasn't aware it existed and it's extremely helpful! I was able to mount my old cache disk and copy over my docker.img file as well as my missing shares and some items I'd forgotten were still waiting on the cache disk to be transferred to the array. Now, I just need to resolve the issues with my new cache disk pair. It looks like they also suffered from my aforementioned issue.

@itimpi, Thanks for the reply! No, I have not attempted to format the disk. I had hopes there might be some way to recover from this. The old format was ReiserFS. How would I go about "setting the format back?"

Couldn't tell you at the moment. Made the mistake of adding extra cache drives today. Docker is currently dead. Hoping to recover. I posted about the issue here: http://lime-technology.com/forum/index.php?topic=50074.0