jeremeyi

yea, I probably should have done a few smaller things first to see how it acted. I had done an entire media share so it took along time before it finished and I saw it removing the source. Just kinda freaked me out for awhile.

I am moving data from one drive to another using this plugin for the first time. I am using scatter/move and I can see the target drive filling up but the source drive remains the same? As I watch it working if I go and check the target drive the file has copied over but it still remains on the source drive. Am I missing something? Why are the files not being removed from the source drive as it is working?

It appears to be ok, data seems good, most recent files are there, etc. Again, thanks alot to the both of you!

Just an update, parity is being rebuilt, 8 hours until it is finished, fingers crossed. I have the array started in maintenance mode, I didn't normally do that but thought maybe a good idea from now on to avoid writing to the array during parity builds, drive upgrades? Hopefully this works out ok, guess we'll know bright and early tomorrow morning. Thanks to both of you I really appreciate the patience, help and advice on this. jeremey

You are correct, I do not want that, remember though, the 5tb parity drive that is in there right now is incomplete only making it about 50% through a parity build than this happened. The original 3tb parity drive is complete, but some data was written to the array after it was removed (in hind site bad yes I know this now). So what are my options knowing this? Thanks

The file system check went fine both ways, array stopped and started. I don't know what this means, but if I set disk 4 to no device, and set disk 5 to the drive that was disk 4 it says invalid expansion, but does show the temperature of the drive, and it is blue balled, not red.

yes i can access disk 4 booting from a different flash drive.

yes, if I mount the array normally, disks 1-3 are available normally, as in I can access them through samba as disk 1-3, not as a whole disk, if that makes any since. I have also attached a screenshot of the homescreen of the system when mounted as such.

so you want me to start the array in non maintenance mode and see if drives 1-3 are accessible? And yes, hot swap cages are now in the near future : ). I had not even considered the fact that you would not be messing with cables to be a selling point for them. If you confirm yes start the array up normally, I will and than take a screen shot of it started also.

Well, I'll have to wait until the file system check is completed to see, but if I change disk 4 from slot 4 to slot 5 it gives me a weird message, but I don't remember what it was for sure. With the array started in maintenance mode the way it is, it does not show disk four on the stats page, but shows the three other drives as 100% full, which they are not. Don't know if this is helpful.

oh yea, and while it is checking the drive, one of the last steps, I can see it checking the files that are on the drive, with file names and all if that helps.

It brings it up in maintenance mode, but still with drive 4 red balled, I am still confused by it saying configuration valid even with that drive red balled, and it bringing up the array, even with that drive red balled. when this first happened, and I went to shut it down to check cabling, I believe that auto start the array was enabled, I had went to disable it but forgot to hit apply is the only thing I can figure out. If that is the case is there anything that might need to be restored from the config directory on my flash drive backups maybe?

ok, it has finished, saying no corruptions found, what to do now? I have not rebooted or anything, drive still shows red ball.

It seems to be running fine, still going. I apologize for all the questions, just kind of freaked out at the moment about loosing data. : )

I ran this with the array stopped, did I want to run it with the array started in maintenance mode?