13 hours ago, itimpi said:

@gnollo What is the issue - that process looks correct (as far as the bit you have listed goes). You do not mention the other steps given that allow you to reformat the drive you have just emptied to a supported file system.

No issues, first time that I get that message so I thought to share for those who have not upgraded to the latest version of unraid.

Additional steps were listed on

https://docs.unraid.net/go/convert-reiser-and-xfs

I don't copy them all as I added the link above and the text is quite long.

1 hour ago, gnollo said:

No issues, first time that I get that message so I thought to share for those who have not upgraded to the latest version of unraid.

Additional steps were listed on

https://docs.unraid.net/go/convert-reiser-and-xfs

I don't copy them all as I added the link above and the text is quite long.

OK - just wanted to make sure that there was no issue.

Getting off reiserFS is getting more urgent as support from it will soon be removed from the Linux kernel, and thus any future Unraid release using kernels without reiserFS support.

OK started the drive post move check using TTerminal with
rsync -avhPX /mnt/disk4/ /mnt/disk12/
I can now see the files being listed one by one as it goes through
Thank you all for your help.

14 hours ago, gnollo said:

OK started the drive post move check using TTerminal with
rsync -avhPX /mnt/disk4/ /mnt/disk12/
I can now see the files being listed one by one as it goes through
Thank you all for your help.

sent 11.48M bytes received 308.27K bytes 18.43K bytes/sec

total size is 9.11T speedup is 773,026.16

Check completed some time earlier today so pretty quick in comparison to the previous checsum attempt. TTerminal returned to the root@tower green command line. I will swap the disks, format the rfs one to xfs and start moving the next drive.

On 1/24/2026 at 10:55 AM, gnollo said:

So I will run the emby docker over the weekend and start the procedure on Sunday late night.

1) click on the terminal icon on the unraid web interface

2) as my other largest (10TB) drive in the array is disk4, type: rsync -avpx /mnt/disk4/ /mnt/disk12/

3) prompt should return at the end with no errors showing

4) as I am paranoid, will check integrity with typing: rsync -rcvpx /mnt/disk4/ /mnt/disk12/

5) if all goes well it will just return to prompt

6) stop the array

7) Click on Tools, then New Config, then Preserve current Assignments

8) select All, then check Yes I want to do this, click Apply then Done (if unmountable disk(s) appear

then I need to select the correct file system for those disk(s) whichh in my case would be rfs for all but one disk)

9) I go back to the Main page and click on the dropdown for disk12 (the xfs drive) and unassign it (I click on "unassigned" or "no device")

10) I click on the dropdown for drive 4 (the one I already copied), and reassign it as disk 12

11) I click on the dropdown for the drive 12 and reassign it as the physical rfs drive I have just copied across

12) Click on each drive name and swap also the file system format of the drive - if it's ReiserFS change it to XFS, if it's XFS change it to ReiserFS

13) All array disks are with blue icons, and a warning (All data on the parity drive will be erased when

array is started), click on nthe check box for Parity is already valid, then click on start

14) stop the array and click the disk 12, and change the format to XFS, then click Apply and Done

18. Start the array; click on the Format button for drive 12

Ok so I followed the steps above and I am now ready to move the data over to disk 12 again, this time from disk 7.
Couple of points

1) I was lucky that when I started the array again after switching the drives it recognised all the rfs disks as rfs, because clicking on the disk to change the mode from auto to rfs is no longer an option in this version of the OS

2) this time I had the option to format the drive to XFS, which was much faster than CLEAR process I had to use for the parity drive last week. Why did I not get the option to format the parity drive instead of clear?

51 minutes ago, gnollo said:

1) I was lucky that when I started the array again after switching the drives it recognised all the rfs disks as rfs, because clicking on the disk to change the mode from auto to rfs is no longer an option in this version of the OS

2) this time I had the option to format the drive to XFS, which was much faster than CLEAR process I had to use for the parity drive last week. Why did I not get the option to format the parity drive instead of clear?

1)

Since rfs is deprecated, it won't let you format a disk to rfs so you can't select that.

2)

Formatting a disk just writes an empty filesystem to the disk, which is just a small amount of metadata to give you an empty top level folder ready to accept files and folders.

Clear writes zeros to every bit of the drive so it can be added to a new data slot without invalidating parity.

Parity has no filesystem, so no format.

7 weeks later, 12 drives moved to XFS format, 68TB copied from drive to drive

Removed drive 12 from the excluded list in Global Shares setting

Turned Tunable (md_write_method) back to Auto in Settings>>Disk Settings

Back in business, unless I have forgotten any other settings that need to be changed back?

Thank you all for all your help and advice.