StevieGee

@trurl Well, I replaced all the SATA cables, ran a diagnostic (attached), and re-enabled the disabled disk and started the parity rebuild. It seems to take about 3 days since parity building starts and stops from heat per the settings I've put in. I'll post another diagnostic once parity finishes. Thank you. ...Steve smg-nas-diagnostics-20260521-1557.zip

@trurl I checked connections and rebuilt parity to the same disk. Now, a week later, the same error. Should I rebuild parity on the same disk again? I have a Ting electrical monitoring device (a recent add) and no power burps or brown outs. I have attached diagnostics and checked connections again. Also, I did upgrade to 7.2.5 last week. Thank you for your help. ...Steve smg-nas-diagnostics-20260518-1151.zip

Also I got two other warnings: Warning [SMG-NAS] - udma crc error count is 2 WDC_WD80EFZZ-68BTXN0_WD-CA144PXK (dev3) (which is the parity drive) My plan would be to add a new parity drive, but I'm asking first. I was in the middle of a large copy from a remotely mounted windows share, which I have stopped. Diagnostics attached. The parity disk is disabled and will not spin up. I am not able to run extended diagnostics. ....Steve smg-nas-diagnostics-20260509-1746.zip

Attached. Oh, and another miracle, the dockers all work and appdata backup ended successfully. smg-nas-diagnostics-20260303-1626.zip

Trurl, Well, it looks to me like disk2 is empty (attached) And that appdata, domains, isos and system are all located on cache (attached) And that your patience is astounding. Thank you so much for your help, again!

Since I have misunderstood before, I'll check before I begin. You're saying appdata, domains, isos and system shares are all hanging off /mnt/user and should be moved to cache. I'll check where there is data and see where it's current (e.g., system share is recent on /mnt/user and empty on cache). Stop the VMs and Dockers. Copy the most recent data from system, appdata, domains and isos shares to cache in the correct subdirectory on cache. Go into VM Manager and change the default VM and isos paths to cache. Go into the share settings for system, appdata, domains and isos share settings, make sure all have cache as primary and array as secondary, and mover action is set from cache -> array. (Or do I set secondary storage as none? And if I do that, how do I back all these shares up in case the cache fails). Restart VMs and Dockers. Am I close?

You got it. smg-nas-diagnostics-20260228-1236.zip

Got it. The rebuild finished and the array is up. I'm freshening backups at this point. My plan is to add a second parity drive when it arrives. As you said, "Unrelated, your system share has files on the array." I'm thinking you're seeing the /isos and /system directories on disk2. Do I need to correct that? I am not sure how those directories got there.

@trurl Again, I can't thank you enough for your help. Attached is the Disk2 extended smart report, which unRAID says completed without error. (I need to do some reading about this tool. The text of the report has a lot of stuff that looks like errors, so I need to learn a little more about smarttool interpretation). Also, yes, I do have a backup of my data files to iDrive via Duplicati. I'm pretty sure that the backup is good. I have not tested a complete restore, but random file restores are successful. I also have a somewhat recent copy to a USB HDD. Here's what I think I need to do now. I'm planning this from unRAID doc located here The doc says I should run a parity check. Should I do that? Rebuild the disabled Disk 1 in place per the doc. The doc talks about doing an "automated xfs repair". The criteria for doing that are not clear to me. I've used file explorer from my pc to look at some files and they appear good. Run a parity check. Stop the array. Remove an old empty data drive from the array. Power down, replace with new drive. Power up. Assign the new drive as a parity device. Run a parity check. Does that sound right? Also, you said, "Unrelated, your system share has files on the array. Possibly these were created because you enabled Docker/VM Manager without cache. We can look at that later." How do I tackle that? Disk2-smg-nas-smart-20260227-0910.zip

Results attached for all. Here's what I think, but I'd appreciate you proofreading: All the drives have prefailure flags. Are they all needing to be replaced? Parity is good Disk1 doesn't say failure, but it seems to be in communicado. I have two 8TB HDDs that are supposed to be here tomorrow. Disk2 restarted. The host interrupted the test. How the host interrupts one disk but not all, I don't understand. Disk3 OK Disk4 OK Again, thank you so much for your help. Disk3-smg-nas-smart-20260226-0903.zipDisk1-smg-nas-smart-20260226-0902.zipParity-smg-nas-smart-20260226-0900.zipDisk2-smg-nas-smart-20260226-0904.zipDisk4-smg-nas-smart-20260226-0904.zip

got it. they're all running now. I'm thinking I should replace the drives once the data are built back/safe. Do you agree? Also, should extended tests be run periodically?

OK. They are both started. Is there anything I should do after that or just send the two reports?

Yes. I thought I'd better do as you requested, so I stopped it and checked the connections. Should I restart it?

On Disk 1, the dead device, the dashboard says Device is disabled, Contents emulated Click to spin down device I don't know if that's helpful.

No splitters. Connections are good.

Oh gosh. It's been 4 years. I will power it down and look for power splitters. I'm pretty confident there aren't, but I will check. Please stand by.

SMART report attached smg-nas-smart-20260225-1105.zip

@trurl Well, I just read the "Need help? Read me first!" link in your signature line. Lesson 1: Almost always, the most important thing you need to do is capture your complete syslog, BEFORE YOU REBOOT! We usually need to see what went wrong BEFORE the reboot, because once you reboot, it's lost! So, I've screwed up already....sigh.

Thank you for such a prompt reply. The anonymized diagnostics are attached below. smg-nas-diagnostics-20260225-1053.zip

Hello, I have an unRAID NAS that hasn't burped in 4 years...til today. I'm not super experienced at linux, and, per the unRAID documentation ("Single parity risks: If you have single parity, you're at risk of data loss if another drive fails during the upgrade. Seek advice in forums if this happens.") Now that I see the Disk 1 in the attached, I am seeking advice. The snapshot does NOT reflect that Disk 1 had 1024 read errors. I panicked when I saw the red X and powered down the NAS so I could do some reading, so the error count got zeroed. I then ran a short SMART self-test and got the following: "Completed without error" I am very willing to replace the drive that is shut down, but because of the above warning about single parity, I don't want to screw up the replacement. What should be my next step? Should I run an extended SMART self-test? Should I run a parity check? I have never had any errors in a parity check. The last one ran fine: Last check completed on Sat 31 Jan 2026 01:38 AM (twenty-five days ago) Duration: 17 hours, 29 minutes, 44 seconds. Average speed: 127.0 MB/s Finding 0 errors Thank you very much in advance from a noobie. ...Steve

My hair is gone as well. I didn't pull it out, but let's set that aside. My SMB share stopped mounting, so I deleted the SMB, and remapping on my NAS did not work. It did not load my "server" (Windows PC) and would not load remote shares. I ended up having to re-share the Windows share on my PC (properties -> Sharing tab -> share button). Didn't make any changes in Windows other than hit the button and have the share files re-walked on the PC. I added the share on the NAS again, was able to load the "server" and load the remote share. Why it disappeared, I have no idea. I had updated the UNRaid OS to 6.12.10, but that was weeks ago. Boy, I hate computers...

Hello, I am new to unraid and a novice at Linux. That said, I was able to set up a NAS with unraid and get Duplicati running, WITH email notifications no less. It took me a month to get it going, but let's set that aside. I'm at the point now where I would like to backup my NAS to the cloud. I have about 6 TB of photos, music and Time Machine backups. Jottaclould seems to be the most cost-effective, but I have a concern. I have seen that Jottacloud changed their authentication, which seems to have been fixed in the Canary version of Duplicati. Canary Duplicati appears to be beyond beta. Should I be concerned? I see that it took some months to get it fixed. And Duplicati seems to be in perpetual beta. But Duplicati has 100,000,000+ downloads which speaks to its popularity and flexibility. Would anyone like to comment on this? Is Duplicati a bad idea? Is Jottacloud a bad idea? Also, if this is the wrong place for this question, would you let me know? I don't really have questions about the docker-ness of Duplicati, which is why I put it in this forum.