HutchG

Array finally stopped and reboot worked, all seems fine now. Thanks

Hello there, I'm running 7.0.1 and I set up a job to move data from one folder to another. While it appears the job completed overnight, when trying to access the folders it disallows it with a small popup saying "Job Running." There are no jobs running that I can see. I have attempted to stop the array to reboot and now my toolbar is stuck on "Array stopping - Retry unmounting user share(s). I think the thing is frozen somehow. Here is my diagnostics. unraid-diagnostics-20250310-0905.zip

Has the button changed? On the tray allocations page it says to use the "Force Scan all" button under the "system" tab before deleting/adding devices manually, but when I go to the "system" tab the button is not there.

I think the easiest will be to replace the disk. I will do that and start a new thread if I need more help. Thank you @JorgeB for all your patience and help, beer money sent.

Okay now it appears I am back to square one, no errors and all drives show healthy. This is great so far. I ran a short SMART test on disk1, the previously errored drive, and it completed without error. I have the extended SMART test running and hope it runs fine. Where do you recommend I go from here? Remember, my original plan was to swap my 14tb parity drive with an 8tb drive as it was overkill for my array and I could use the 14tb as a USB backup device. If I retry that I might end up with errors again and be where I started this thread. Should I now prioritize replacing the possibly dying drive1 first or could I move the drive1 data and eliminate it as I have empty space in the rest of the array? Please advise

Okay, it says no corruption detected now, here is the latest diagnostics. unraid-diagnostics-20250212-1142.zip

Okay, now I'm here. Not sure exactly what this is this is telling me. Can I just mount, somehow run the log, then unmount using Unassigned devices or do I need to stop the array, re-add disk1, run the log, then remove again?

Do I press the FIX button?

Okay, I have followed instructions, original parity disk returned and errored disk shows unassigned. It shows parity is valid. Here is my new diagnostics. unraid-diagnostics-20250210-1610.zip

I don't have a replacement disk for disk 1 yet, the only "extra" disc I have is the original 14tb parity. It sounds like, following your instructions, I could return the original parity drive to the parity slot, check the two boxes, use the new parity drive as the drive 1 replacement. Am I understanding that correctly? Then I stop the array, unassign disk1 and restart the array in normal mode? Won't it then give me an error disk1 is missing? Thanks for the help.

unraid-diagnostics-20250208-1007.zip My largest array drive is 8tb an my parity drive was 14tb. I was swapping the 14tb drive with an 8tb drive as I had lots of wasted space and planned to use the 14tb as a USB backup. Also, as I have space on other drives, is another option to move the data from the errored drive to another healthy drive on the array? Update: Parity - sync completed - 98 errors - One disk has SMART error

I'm on 7.0.0 and did a parity drive swap. Before the swap I had a zero error parity check and all drives healthy. Now, as the parity-sync started, I have an array drive showing read errors. Can I stop the parity sync and revert back to my original parity drive? Then I could replace the array drive. Do I just let it run?

thank you

Something that kept me from seeing my SMB folder was that I had not set the Export option to Yes in the SMB security settings. You might try that.

I'm running 7.0.0 and I'm attempting to backup data from my Qnap NAS to my new Unraid server. They are on the same network, so the most obvious two options to my noob brain in the Qnap backup sync tool are Rsync and SMB. Thinking that Rsync would be faster I tried that first, but it only connects using root, not the user I created. I then tried the SMB sync and it connected using the user I created just fine. Should I just move forward with the SMB sync now that I have it connected fine? Am I missing out on performance benefits the rsync might have and if so, any idea why I can't connect using my non-root user? Also, is there a third option even better than these two I might be missing? Thanks in advance