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.

1 failed device, reboot, parity check

Featured Replies

First disk fail for me since starting with Unraid.

The latest HDD "disc 8" I've added to Unraid array disconnected, it was unable to see SMART, is emulated (I have two parity disks). I tried to stop the array but it wouldn't stop.

Exported diagnostic(attached) & Shut down system.

Swapped the cables on disk8, boot up.

Disk8 is still disabled but I can see SMART with no issues, is emulated.

But right away a parity check started, it has ten hours to go & Sync errors corrected:960

Should I let it continue parity check, I'm confused about why it did a parity check. Or I can swap Disk8 with a new HDD

 

crower-diagnostics-20240611-1526.zip

Solved by JorgeB

  • Community Expert

Good for getting diagnostics before shutdown

 

Attach new Diagnostics from after you restarted to your NEXT post in this thread.

  • Author

Was running a Syncthing docker sync when problem occurred.

Disk8 (disabled, emulated) is running a SMART extended test but has been hanging at 10%

Parity check has slowed to a crawl, if it's not done by morning I assume to cancel it & replace the HDD & rebuild

Not clear why Unraid ran the parity check after reboot while an HDD is disabled, is normal?

Extended SMART test can take many hours to run. Be patient...

  • Community Expert
  • Solution

Constant ATA errors with parity2, replace cables and post new diags, also recommend replacing them for the disabled disk, since SMART looks fine.

  • Author

Disk 8 did end up passing Extended SMART test

Swapped cables on Disc8 & that Parity drive as well

On restart it allowed me to add this drive to the array & began to rebuild disk 8.

Pretty quick Disk8 went disabled again,  seeing things in the log I do not understand

(Trying to decide if I do a new HDD or continue troubleshooting computer parts.... thank you for all the assistance)

 

 

crower-diagnostics-20240612-1555.zip

  • Community Expert

Disk dropped offline, still looks more like a power/connection issue, swap both cables with another disk and retry, to see where the problem follows.

  • Author

in-progress update...

  • I swapped the Disk8 HDD out for a fresh HDD WS24QHAP & started a rebuild. After many hours it did end up getting disabled, at which point @JorgeB confirmed it didn't look like the HDD itself anyways
  • This morning I noticed the power cables had a gratuitous use of Molex to Sata splitters, so I rewired to something that appeared more sane & balanced. Didn't see a change. Noticing my PSU is quite old, maybe worth ordering a new one(?).
  • Swapped the SATA cable on Disk8 WS24QHAP with the SATA cable to WS24QGHA. This seems to be a good swap as they are both new cables added after the problem began & it swaps a mobo SATA & a PCIe card SATA.
  • Rebuilding. There's some errors in the log but looking to see if now WS24QGHA gets disabled

crower-diagnostics-20240613-1300.zip

  • Community Expert

Those ATA errors come from parity, and also look like a power/connection issue.

  • Author

Amazing, things seem back to normal. Will keep an eye out for repeat issues, diag atached.

when I rewired the Molex adapters my claim was "no change"... but that was the moment I probably should have rebuilt. Seems like that was the issue.

Thank you for all the amazing help, learned a ton of things to look for. Very appreciative Unraid comes with a great community!

(Now I have a Disk2 SMART error to deal with but that's something I have more of a handle on)

crower-diagnostics-20240614-1038.zip

  • Community Expert

Looks good for now.

  • Author

6/14/2024
Disk2 was showing SMART errors pointing to a potential fail
removed Disk2, started array & Disc2 appeared missing & emulated
shutdown, swapped a physical disk WS24PGY2, Selected it for Disk2 in array, started array in maintenance mode, Unraid requested a data rebuild & 10 hours later looked good.
(I should mention that this disk WS24PGY2 was previously "Disk9" that I had replaced troubleshooting an earlier problem. I've since read that this shouldn't cause issue but recommended to reformat before adding... which I did not do at the time)
6/15/2024
Disk2 WS24PGY2 has a green normal operation icon but is unmountable, not emulated
option at bottom was to format the HDD, I did not format. Started array in maintenance mode, ran a Check Filesystem Status on Disk2 WS24PGY2
After check, disk appeared to be part of array again, emulated & option to Data-Rebuild present... started  Data-Rebuild
6/16/2024
My first Parity HDD went down during the scan and the scan seems to be stuck with only option to cancel the scan. No reads or writes are happening & the estimated time isn't changing
Parity(1) is disabled (note that I have a 2nd parity disk)
Disk2 is still emulated
Exported diagnostic, curious if related to the other issues from this week. Guessing I'll have to cancel the in-progress Data Rebuild

crower-diagnostics-20240616-0900.zip

  • Community Expert
51 minutes ago, mathchris said:

but recommended to reformat before adding

That won' make any difference.

 

52 minutes ago, mathchris said:

not emulated

 

52 minutes ago, mathchris said:

After check, disk appeared to be part of array again, emulated & option to Data-Rebuild present... started  Data-Rebuild

Something is missing here, was it emulated or not?

  • Community Expert

Check filesystem would turn a disk emulated.

 

There are constant ATA errors with an Unassigned Seagate disk spamming the log, either disconnect it if you are not using it, or replace the cables, then post new diags after array start.

  • Author

I have a new PSU coming tomorrow, do any of these repeat troubles point to a potential PSU problem, this one is older than I had realized. Here's diagnostic with new SATA cable on Parity. Thank you.

crower-diagnostics-20240617-1348.zip

  • Community Expert

No ATA errors so far.

  • Author

Installed the new PSU with all new included power cables.

Disk 2 WS24PGY2 is giving troubles again. First a warning it can read but not write. Then "Unmountable: Unsupported or n file system".

It passed an Extended SMART check. Ran a Check Filesystem with no change. Log attached.

 

So this thread started when WS24PGY2 was Disk8 & it became unmountable, now that I've reformatted/rebuilt it as Disk2 is same problem. Maybe time to RMA WS24PGY2; does that seem plausible?

crower-diagnostics-20240620-1017.zip

  • Community Expert

Don't see anything suggesting a disk problem for now, only a filesystem issue, check filesystem on disk2, run it without -n

  • Author

Hmmm, as per the quote below, I can't get Disc 2 to mount. Guessing to do what it says, -L?

(I assume it's not safer to replace the HDD & build a new HDD from Parity... because it's not a disk issue & the issue may follow to the new HDD from the parity?)

Quote

ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

 

  • Community Expert
22 minutes ago, mathchris said:

do what it says, -L?

Yep

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.