rockbox948

Thanks! I appreciate your help.

@Frank1940 Thanks for your reply. That part is confusing but those arrows helped! Any thoughts on my other question - Am I able to pull the old drive out of the array without losing the data on it since I do not need it anymore? If so, are there specific steps to do so?

I am converting 2 drives from Reiserfs to XFS following these instructions; the drives being converted are one 4 TB and one 8 TB drive. If I have two 10 TB drives available, is it possible to just remove the old drives from the array after Step 14 without formatting them? I'm a bit paranoid and would like to keep the data on the drives just in case I find an issue later on. With two empty 10 TB drives available, I don't need to reuse the old drives at this point. Also, Step 15 is a little confusing to me. Wouldn't the new drive have the correct XFS filesystem at that point? Thanks.

Things seem to be working as expected!

@JorgeB Great! Thanks for your help again. @MAM59 Thanks for your help as well and for jumping into the conversation so quickly after I posted!

@JorgeB Thanks for your help. Of the two options you presented, which is the most fool-proof? Obviously, that is the one that I will need to use😁

Tasked completed and confirmed old cache is back.

@JorgeB Thanks using SB copy 1, bytenr 67108864

@JorgeB Label: none uuid: 67579e2f-140d-47d0-9633-67d6b6adbed1 Total devices 1 FS bytes used 144.00KiB devid 1 size 931.51GiB used 2.02GiB path /dev/nvme0n1p1

cylon-diagnostics-20230327-0639.zip Let me know if this is not what you requested.

That is correct.

You are correct, I completely missed the part about not working on a single device pool. The system is back up but without the old appdata.

I completely missed that strikethrough part. Here are the diagnostics because I do still need help. Any help you can provide is appreciated. cylon-diagnostics-20230327-0639.zip

I guess my question is how to start again? Do I stop the array, unassign the NVMe and reassign the old cache? Would doing that erase the old cache? I ask about the deleting of data because of what the second step in this process says.

"Next time"? So I go through the process again? Will the data on the original cache get erased if I set it back to being the cache and start over?

Well hell... I was definitely using Firefox so that explains why things didn't go as they were supposed to. What is the remedy?

I recently upgraded to v6.11.5 and installed an NVMe drive to replace the current SATA SSD cache drive using these instructions: Stop the array - Did this. On the main page click on the cache device you want to replace/upgrade and select the new one from the drop down list (any data on the new device will be deleted) - Did this. Start the array - Did this, however, the array did not start immediately. I received message from the browser that the page needed to be refreshed. When I did so, the Main page showed the array to still be offline. I opened the Main page in a different tab and still had the same result. There was no indication that anything was taking place and the only buttons available at the bottom of the Main page were Reboot, Shutdown, and Sleep IIRC. I rebooted and lost GUI access. The login screen would occasionally appear but would provide a 503 Service Unavailable error. This continued for 4 hours, during which I would check randomly to see if the status changed. After ~4 hours, I was able to login and GUI access was restored. The array was online without me turning it back on again. All buttons were available at the bottom and the Format button was added. The new NVMe drive was set to Cache but was unmountable because it had not been formatted. I ran the formatting process. A btrfs device replace will begin, wait for cache activity to stop, the stop array button will be inhibited during the operation, this can take some time depending on how much data is on the pool and how fast your devices are. - This and the remaining steps did not take place. Is there something else I was supposed to do in order to have my old appdata etc. move to the new cache drive? If I ran the Kluth CA Backup/Restore Appdata prior to the upgrade, can I do the restore on the new drive? Thanks in advance! cylon-diagnostics-20230326-1339.zip

Thanks for all of your help!

@JorgeB Finally finished the --rebuild-tree and new diagnostics. Please take a look when you have time. As you recommended, I will transition to xfs on my remaining drives. I just need to get some client work done before I can do so. Filesystem Repair Tree Results.txt diagnostics-20230324-1008.zip

Ok, thanks.

Thanks. I'm copying the data now. If I do the --rebuild-tree and then swap the drive with a new one, will I get a chance to change the filesystem or will the parity rebuild also include the old reiser filesystem?

Thanks, @JorgeB. Just before all of this took place, I had uploaded a lot of data to the server that may have been placed in Disk2. I did not have a chance to backup any of that new data before this issue happened. Will --rebuild-tree put that data at risk? Would I be able to restart the array beforehand to backup that new data first? I really appreciate all of your help and your patience with my questions.

@JorgeBBefore I do anything else, could you please take a look at the results of the check? Filesystem Check Results.txt

@JorgeB This is probably a stupid question but does this mean that I type in "--check" in to the blank and then push the "Check" button? https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui "If the file system is ReiserFS, then the options box will be blank initially, which implies the --check option. Always begin a ReiserFS drive test session with the --check option!"

@JorgeB - Thanks for the quick reply. I will check on that now.