Harro

I am happy to report that I have final finished converting all my disks to XFS format. This thread had been of great use, along with buying new 8TB drives. I did not use the recommended rsync command but opted for unbalance plug in. My transfer speeds where in the neighborhood of 55-65MB's. All along keeping a vaild parity, so I am happy. Thank you all for the help

If you are using the plugin with unassigned devices, there should be a red X next to the pre-clear that will stop it.

I had done 3 pre-clears on that drive. Now ready to install.

Just finished pre-clearing a 8TB Seagate Archive results: Cycle elapsed time: 45:07:31 | Total elapsed time: 45:07:33 # Step 1 of 5 - Pre-read verification: [15:03:56 @ 147 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [14:58:37 @ 148 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: [15:04:50 @ 147 MB/s] SUCCESS Thought that may help you on the time.

Read through that. It will help.

Everything went smoothly and I must had had some excess gas with a lot of brain farts the other day. Have drive converted to XFS now and will continue with the rest. Thank you all once again.

I will let everyone know tomorrow. Should have another drive empty tonight sometime. Ready for XFS . Thank you all.

This is exactly what I had done after removing all data from that disk. Problem was the format was grayed out and would not let me choose the xfs format, only could add back to array with the reiserfs format. That is why I went to the other steps, thinking that the disk was holding some info from preventing me to format to xfs. Like I previously stated, only empty share folders remained on disk... Would that prevent the disk from formatting? I am moving data from another drive now but will post a screenshot if I run across that again. .

I moved everything from disk3 to where ever....Stopped array and changed the format to xfs...started array but array just saw the disk as reiserf format. So need to rid the disk3 of that format. before I can add it back again. The array sees the same disk3 going back again and says hey it's a rfs , so nothing new here. But if I destroy that partion and then add it back, it will format to xfs. The disk in question previously had user shares on them, so what is left after the move with Unbalanced is empty folders. I could ssh into and delete this but seems just as simple to just delete from the Unassigned devices. The quote from unbalanced thread was from a parity disk going into the previous disk slot, so array saw that as no Fs on it.

Almost ready to start my conversion to XFS and wondering if I could go about it this way. No swap drive available but have enough storage on array to move data around. Ex: disk3 1).in global setting exclude this disk (disk3) from shares 2) use Unbalance to move the data off disk3. 3) stop array and No device 4) Click the disk3 unassigned on array and choose XFS for FS 5) Set the destructive mode in setting of Unassigned devices to enable. 6) Under unassigned devices disk3 is available to destroy the partition. 7) Destroy partition and add back into array under same slot it came. 8 ) Formatting starts with XFS as FS Pretty sure parity check will start also. But does this seem doable. Thanks

Just something I thought was appropriate .

I like that idea. Thank you. After everything is moved would I need to write a new config?

Ah yes that is my missing thinking about the system seeing the new format as empty. Thanks for enlightening me. But if no disaster happens from the time I reformat disk 1 to the time I move data back to disk 1, I would still then keep a valid parity? Or would I need to run a parity check after each successful move of data from each disk? My plan would run a parity first and then move data from one disk, reformat and move back to said disk. Follow this through until all disks have been reformatted and then run another parity check. I would move all the data with verification, as garycase suggested.

I also tried another browser (Chrome) and it does come up for me now. Thank you. Guess IE sucks

Maybe I am over thinking this. My mind thinks that if I moved the data from disk 1 to the cache, reformatted disk 1 that parity would be null while disk 1 is being reformatted. But after reformat parity would see disk 1 back in array and could rebuild it at that point if it needed to. But I move the data files from cache back to disk 1, thus giving parity back to valid. Is my thinking wrong ?

The only caveat I'd add is to be sure the copies in both directions are done with verification. It's not the quickest way, but it's a VERY safe way to do the migration -- and considering that there's really no "rush" to change the format I'd be inclined to just do one "set" every few days until everything's migrated [where a "set" is 2 4TB drives and 1 2TB drive, since there's 10TB available for the data on the 2nd server]. Yes garycase that was my initial thought. Then I came up with the second idea , still haven't taken any solid direction in either case yet. But whichever it may be I would like it to be the safest as possible, barring any drives red balling on me. jbrodriguez: the 8TB drive will be replacing a 4TB parity drive once all is done with my upgrading/formatting. For your question on disk 1 without parity, my take on this is, Parity would rebuild disk 1 even if it were empty as long as I keep all disks in the same order and don't change it around. So if my copy fails from the 8TB back to disk 1, parity would see what is missing and rebuild. This is my thinking, but many on here are a lot more component and wiser than I on this. So I may be just blowing smoke out my *ss.

I never thought of keeping the dockers in play during the moving. So that brings me to this question; if dockers were left working on the 8TB drive, I would assume I would need to exclude the disk I am moving (disk 1) in the global setting to prevent any files from being written to that disk until the move, reformat and move back were complete. So in essence I would have to exclude the 8TB and the disk 1. I am moving, correct? I then would move on to next disk with same procedure until I had finished all.

I may have over simplified the procedure, but I do understand the parity reasoning. After thinking about all this, another thought for the conversion I have is to take my cache drive out, disable my dockers and mover, replace cache with my 8TB drive and move from within the array itself. If I did that I could move files from disk 1 to new drive, reformat disk 1 and move files back to disk 1.Thinking that should keep my parity valid without running new permissions. Is my thinking correct in that?

I have installed this plug in but can not seem to get it to display the GUI. running 6.3.2 My log file is such : I: 2017/02/21 14:08:09 unbalance.go:29: unBALANCE v2.1.0-714.67a61b3 starting up ... I: 2017/02/21 14:08:09 unbalance.go:39: No config file exists yet. Using app defaults ... I: 2017/02/21 14:08:09 server.go:50: Starting service Server ... I: 2017/02/21 14:08:09 server.go:67: Serving files from /usr/local/emhttp/plugins/unbalance I: 2017/02/21 14:08:09 server.go:97: Server started listening on :6237 I: 2017/02/21 14:08:09 core.go:114: starting service Core ... I: 2017/02/21 14:08:09 unbalance.go:49: Press Ctrl+C to stop ... W: 2017/02/21 14:10:26 server.go:246: closing socket (&{id: ws:0xc4201ae090 onMessage:0x472f20 onClose:0x472f70}): EOF W: 2017/02/21 14:15:40 server.go:246: closing socket (&{id: ws:0xc4201ae1b0 onMessage:0x472f20 onClose:0x472f70}): EOF W: 2017/02/21 14:34:06 server.go:246: closing socket (&{id: ws:0xc420136120 onMessage:0x472f20 onClose:0x472f70}): EOF I: 2017/02/21 14:34:42 unbalance.go:53: Received signal: (terminated) ... shutting down the app now ... I: 2017/02/21 14:34:42 core.go:141: stopped service Core ... I: 2017/02/21 14:34:42 server.go:102: stopped service Server ... Any help is much appreciated. Thanks

Thanks for the reply trurl. I have read the wiki 4 times on the reformatting section but not about the replacing the cache drive. Thanks again. I am still trying to figure out my plan of attack on this. My end goal is to replace the parity with a new 8TB and take old parity (4TB) and replace a 2TB in array, also to replace old blue cache drive with new ssd drive. My plan of attack in my mind is thus: My other array with nothing on (used as a test server) holds 10TB, so I could possibly move up to 3 disks in my current array(10-4TB and 6-2TB drives) to my test server, then format those 3 empty disks and move files back on the new reformatted disks. I know this will take time but little will be my time and all computer time. Does this sound like a reasonable plan or would there be a better way?

Waited till the forum migration was done to ask a few questions regarding this topic. I have an array with 16 data disks along with a parity and cache drive all in reiserfs, I have another array with nothing on it but with the xfs format, I read somewhere that moving the data from a reiserfs disc should be moved to another reiserfs disc, is this correct? Or since I am moving from one array to another array it will make no difference in the disc format? Another question is on my cache drive, which is holding my dockers, is it simply a copy the appdata folder to somewhere else and format the drive to xfs and copy back? My array isn't getting any smaller and would like to get this done before I have way too much to move. Thanks

Greetings, I had used a kodi headless install before on my unraid v5 and have a few questions now that I have gone to the 6.1.9. 1) What size container would be ideal? Since my kodi client now has 10gbs in the appdata/roaming folder and is still growing would setting a 25gb container be suggested? 2) On my old install of kodi headless, I triggered an auto update every x hours with cleaning by , first installing that addon on my client and then copying it over to the kodi headless install. Worked good, can this also be done on this headless install? For that matter can any addon be done this way? 3) Which is preferred for this docker, MySQL or MariaDB? Also as like question 1 , what would be a good docker size? Thanks