I was attempting to convert a disk from reiserfs to xfs using the instructions here. However, now it's running a parity-sync/rebuild for some reason and I've lost all my docker containers.

 

I'm not that smart, I know, but unRAID has given me more trouble in the past month than I thought possible.

tower-diagnostics-20170807-1514.zip

 

All the data APPEARS to still be there in the "appdata" directory.

Edited August 7, 20178 yr by Netbug

Hi -

 

Which conversion method did you follow?  There are several in the wiki, some preserve parity while some do not.  It's possible a reboot will bring back Docker, but we don't want to cancel the parity sync if you're following an option that needs one.  It would help if you post the exact steps you took, in order.

Thanks for the quick reply. I think I'm going to have to wait for the parity check to finish and then cross my fingers. The procedure I linked is what I was following, but honestly, I may have fallen off the path as it got a little complicated.

 

Form memory, what I did was use unBALANCE to move the data off of the disk I wanted to convert (disk 1 in this case), stop the array, unassign the drive, format the drive, start the array and begin the rebuild.

 

I'm sure I've messed something up. Just starting to get frustrated with all the complications I'm causing for myself in trying to get the system back to stability.

What disk was docker.img on?

 

It's not entirely clear from your word choices whether it is rebuilding parity or rebuilding a formatted data disk, or what.

 

25 minutes ago, Netbug said:

Form memory, what I did was use unBALANCE to move the data off of the disk I wanted to convert (disk 1 in this case), stop the array, unassign the drive, format the drive, start the array and begin the rebuild.

 

This exact sequence is not really possible so that can't be what you did. A screenshot of Main would help clarify whether it is rebuilding parity or rebuilding a data disk.

Sorry about the lack of clarity. Just getting tired.

 

Here's a screenshot of "main" at present.

1 hour ago, Netbug said:

...and I've lost all my docker containers.

Your docker.img file was stored on disk 1, but your rfs -> xfs conversion process has more or less moved it to a different disk.

 

Settings - Docker - change the docker.img location to be the disk that now has the docker.img file on it, and then delete the docker.img that has wound up being recreated on disk 1

rm /mnt/disk1/docker.img

 

And you should be back in business.

 

Why its rebuilding disk 1 though I didn't look that in depth into the syslog to determine

Edited August 7, 20178 yr by Squid

9 minutes ago, Squid said:

Your docker.img file was stored on disk 1, but your rfs -> xfs conversion process has more or less moved it to a different disk.

 

Settings - Docker - change the docker.img location to be the disk that now has the docker.img file on it, and then delete the docker.img that has wound up being recreated on disk 1

rm /mnt/disk1/docker.img

 

And you should be back in business.

 

Why its rebuilding disk 1 though I didn't look that in depth into the syslog to determine

 

I have no idea. That was completely unexpected because disk 1 should be pretty much empty (I moved all data off of it).

 

Changing the docker location seems to have remedied it. Thank you very much.

 

I'd really love to know why it's doing the parity rebuild. It takes so long and it's rebuilding a disk that shouldn't have anything on it to start with. With my luck, it will rebuild it as reiserfs

2 minutes ago, Netbug said:

It takes so long and it's rebuilding a disk that shouldn't have anything on it to start with

The amount of data on a disk is irrelevant.  A rebuild is a one to one, byte for byte reconstruction of the disk.  If its 100% full or empty it will always take the same amount of time.

 

3 minutes ago, Netbug said:

With my luck, it will rebuild it as reiserfs

It won't.  Your screenshot explicitly shows an empty drive formatted as XFS

1 minute ago, Squid said:

The amount of data on a disk is irrelevant.  A rebuild is a one to one, byte for byte reconstruction of the disk.  If its 100% full or empty it will always take the same amount of time.

 

is there any way I could have skipped the rebuild then? I have to do this for a few more disks. I mean, my brain is saying I should be doing the following:

 

1. Use unBALANCE to free up the drive

2. Format the drive with XFS

3. Add formatted drive to the array

 

But I'm finding that difficult to execute.

I personally added a new drive to my array when I did what your doing. I used MC (MidNight Commander) and just moved everything from one drive to another running doing each drive over a course of what felt like a week. I didn't mess with User Shares I only moved files from Disk Share to Disk Share. 

1 minute ago, Netbug said:

 

is there any way I could have skipped the rebuild then? I have to do this for a few more disks. I mean, my brain is saying I should be doing the following:

 

1. Use unBALANCE to free up the drive

2. Format the drive with XFS

3. Add formatted drive to the array

 

But I'm finding that difficult to execute.

Steps 2 and 3 should be achieved by/;

• stop Array
• click on drive and change format to XFS
• start array.
• you should now be marked as unmountable and you are offered option to format drive.   Make sure it is the correct drive and if so, Do this (which takes just a few minutes), and drive is ready for use.

Parity is maintained throughout this so no rebuild is required.   The drive is part of the array the whole time so not sure what you are having to add a drive to the array (unless it is a new one).   i am not quite sure what you are doing that is different to the above and is thus causing the rebuild to take place.

Just now, kizer said:

I personally added a new drive to my array when I did what your doing. I used MC (MidNight Commander) and just moved everything from one drive to another running doing each drive over a course of what felt like a week. I didn't mess with User Shares I only moved files from Disk Share to Disk Share. 

 

I thought that was what I was actually doing, but clearly I've executed something incorrectly.

5 minutes ago, Netbug said:

 

is there any way I could have skipped the rebuild then? I have to do this for a few more disks. I mean, my brain is saying I should be doing the following:

 

1. Use unBALANCE to free up the drive

2. Format the drive with XFS

3. Add formatted drive to the array

 

But I'm finding that difficult to execute.

What you should be doing is: (very point form)

1. Free up the drive (unBALANCE, manual commands, whatever)
2. Format the drive as XFS
3. Done

Somewhere in between steps 2-3 I think that you set the drive to be not present in the array, re-added it, and formatted it as XFS.  Setting it to be not present, then re-adding it as disk 1 resulted in the rebuild which isn't necessary.

 

 

Just now, itimpi said:

Steps 2 and 3 should be achieved by/;

• stop Array
• click on drive and change format to XFS
• start array.
• you should now be marked as unmountable and you are offered option to format drive.   Make sure it is the correct drive and if so, Do this (which takes just a few minutes), and drive is ready for use.

Parity is maintained throughout this so no rebuild is required.   The drive is part of the array the whole time so not sure what you are having to add a drive to the array (unless it is a new one).   i am not quite sure what you are doing that is different to the above and is thus causing the rebuild to take place.

 

Right. Ok. That's what I was aiming for, but your specifics make it much easier to follow. I'll leave this comment open in a tab while I do the next one. Thank you.

1 minute ago, Squid said:

What you should be doing is: (very point form)

1. Free up the drive (unBALANCE, manual commands, whatever)
2. Format the drive as XFS
3. Done

Somewhere in between steps 2-3 I think that you set the drive to be not present in the array, re-added it, and formatted it as XFS.  Setting it to be not present, then re-adding it as disk 1 resulted in the rebuild which isn't necessary.

 

 

 

Ah. That makes sense. Ok.

 

I'll give it a go on the next disk without removing it from the array. If all goes well (as it should) I'll mark this as "solved."

 

Thanks, guys.