Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

System slow and

Featured Replies

That is a good quality PSU, and it is only about two years old, so I would not buy a new one yet. If the tests below point at it, you can use its warranty.

When I compare all the errors so far with your power layout, it is less clear that the PSU is the cause:

- Disks on both power cables had errors: disk4 and disk5 on one, parity and disk1 on the other.

- Disk2 and disk3 share the cable with parity and disk1, and they never had an error.

- All the errors were on the onboard SATA ports. Disk6 and disk7 on the ASM1064 card have been clean since you removed the port multiplier.

So power is still possible, but the onboard SATA controller is now also a suspect. These tests should tell us which one it is:

1. Shut down. Move parity and disk1 to the free PSU cable, and replace their SATA cables if you have spares.

2. Start the server and test as planned: copy a large file from the wired Mac, or run a parity check for about 15 minutes. Then use the server normally for at least an hour and post diagnostics. Please also tell me which disks are on each power cable after the change.

3. If parity or disk1 still have errors, connect them to the two free ports on the ASM1064 card for a test. Unraid identifies the disks by serial number, so you don't need to change any assignments. If the errors stop, the onboard controller is the likely problem. If the errors follow the disks, power is more likely.

Thanks for confirming the Mac was on Wi-Fi. That explains the -50 error and the slow speed, so please use the wired Mac for future tests.

Please continue to hold off on the parity check and the cache pool until the log stays clean under load.

  • Author

I have switched the power so the parity is on a single line by itself (the one I has aside for pool cache) and disk 1,2,3 are on one and then 4,5,6,7 are on another. I have also been changing the SATA cables as you have recommended. I moved two files on the wired mac to unraid and they both went pretty quickly and were successful. I will post the diag once I get to work around 7:30-8:00 central time.

Edited by ProblemWithField

These diagnostics look good. There are no disk connection errors since the reboot, and the disks did have real load: about 5 GB was written to disk5, which also reads all the other data disks. All links are at full speed again, and SMART is unchanged.

It is too early to say it is fixed, though. Last time the log was clean for more than an hour before parity and disk1 failed. The best test now is a parity check. It loads all the disks for many hours, and you need one anyway because of the earlier unclean shutdown.

1. Start a correcting parity check now.

2. Check the speed now and then. It should stay at normal speed for the whole check.

3. If it slows down a lot, or the syslog shows lines like "hard resetting link", post diagnostics while the check is still running. Then the next test is to move parity and disk1 to the two free ports on the ASM1064 card. If the errors stop there, the onboard controller is the problem.

4. If the check finishes at normal speed with no errors, post diagnostics after it completes. Then you can set up the cache pool.

Good to hear the copies from the wired Mac went quickly.

  • Author

I have just started the parity check, it has started off well. I hope it keeps it up.

Thanks VERY much for all your incredible help with this. It is greatly appreciated!

  • Author

Noticed this warning just a little bit ago (the one at the bottom.

tower-diagnostics-20261112-1200.zip

It has considerably slowed down during parity, Froma right at 200 mb/s to about 150 mb/s

I have not stopped the parity check, it has about 3 hours to go.

and a whole list of :

Nov 11 13:50:25 Tower kernel: md: recovery thread: P corrected, sector=5712293864

In the log I can bring up directly in the console.

It also seems some data has disappeared.

warning.jpg

Edited by ProblemWithField

These diagnostics look good.

The connection problem looks fixed. There are no disk link errors since the reboot. That covers more than a day, including the whole parity check so far, which is the heaviest load the disks get. All disks show 0 errors.

About the speed: the check is past 90%, and it was still running at about 130 MB/s. Hard drives are slower near the end of the disk, so going from about 200 MB/s to 150 MB/s or lower at this stage is normal.

About the "P corrected" lines: these are expected. Parity was out of date in places because of the unclean shutdown and the earlier connection drops. This correcting check is fixing that. These corrections only update the parity disk. They don't change anything on your data disks. Unraid logs only the first 100 lines and then stops logging. The total so far is about 8000.

What I recommend:

1. Let the check finish.

2. Then run one more parity check, with "Write corrections to parity" unchecked. It should finish with 0 errors. If it does, the array is back in sync. If it finds errors again, post diagnostics after it completes.

About the disk5 SMART warning: the reallocated sector count went from 1 to 2. That means the disk replaced one more bad sector with a spare. One or two is not a reason to worry. Just keep an eye on it. If the number keeps going up, that disk should be replaced. After the parity checks you can also run an extended SMART test on disk5.

About the missing data: I don't see any sign of data loss in the diagnostics. Disk usage is the same as yesterday, and there are no filesystem errors. Can you give me some examples of what is missing (the share and folder or file names), and when you last saw them? If you use apps like Sonarr or Radarr, also check whether they renamed or moved those files. The log shows one TV episode that was no longer found under its old name.

After the second check comes back clean, you can go ahead with the cache pool.

  • Author

I am glad to hear that its looking much better. I have about an hour and 30 minutes till the first check finishes.

I have to admit I am a bit paniced about the data missing. I lost a drive from a power outage a while back, and lost a bunch of data.

If I may ask, when you loose a drive are you best to shut everything down until you can get a reaplacement in? I left it up and when I went to rebuild the new drive from parity, iit just spent days in a rebuild and then it was an empty drive when finished. I have rebuilt from parity before but I had a drive to slip in right away.

How I replaced the drive was I but the drive in and precleared it, then replaced the new drive with the old one and told unraid, but it had been about a week since the old drive had died, is that why I lost the old data?

I am missing Phony which had 3 epidoes to start and it appears that Season of Mike Judges Beavis and Buttheand (8 episodes at the time). But I havent been looking to hard.

I will follow your recommendations above.

  • Author

The Parity Check finished with a few errors...

image.png

3 hours ago, ProblemWithField said:

then it was an empty drive when finished

Probably you formatted it, perhaps because it showed as unmountable. Format is never part of rebuild. An unmountable disk has to be repaired with check filesystem. If the disk is emulated and unmountable, the emulated drive should be repaired before rebuilding.

I found your other thread. You mentioned formatting it on a PC to clear it. Format, whether on PC or anything else, will not result in a clear drive, it will result in a drive with an empty filesystem. Formatting on Windows probably created an empty NTFS filesystem.

Totally irrelevant though. Rebuild will completely overwrite whatever was on the disk before, and the result will be whatever was on the emulated disk. Don't know whether or not you formatted the emulated disk, but that seems likely.

  • Author

It just finished the second parity check with no errors. Yay! Thanks for all your help JorgeB!!!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.