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.

adamreid

Members
  • Joined

  • Last visited

  1. Ok so I set it to no, re-ran the test and my parity1 drive is now showing 493 errors and unraid reports the following: Last check completed on Fri 17 Sep 2021 04:11:25 PM AEST (today) Finding 5789 errors Duration: 19 hours, 7 minutes, 57 seconds. Average speed: 87.1 MB/sec unraid-diagnostics-20210917-1615.zip Could this be from a failing sas to sata cable or a my hba failing? I suppose it could be the disk but just seems random that I've had two fail like this in the last month. At one stage during the check it slowed down to single digits megabytes /sec for a while as well. How should I proceed from here? Edit: I'm a fucking idiot and probably didn't un-tick write corrections to parity when I ran the check, I just un-ticked it in scheduler.
  2. You know what I have no idea, I must've set 'Write corrections to parity disk' to yes without thinking about it years ago. Should I set this to no?
  3. ughhhh, I had to turn the system off (gracefully) last night because one of the breakers in our house tripped so I shut everything down before resetting the RCD, I didn't see the results of my parity check until this afternoon. I'll watch for this happening again and then check syslog. Thank you.
  4. Sorry for being a noob, I just followed the guide to download diagnostics, could you please let me know where I could find these logs?
  5. I had 12 errors two weeks ago but nothing before this, ram has been stable in the system since I built it in 2018 but maybe the memory controller is degraded, I'll down clock it. Is there any way to tell from my logs which disks or files were impacted by the errors?
  6. HI there, When I've had failing disks before, unraid would show an error count on the main screen, however after the most recent parity check I've noticed that the system found and fixed 142 errors. I've attached my diagnostics and smart reports but I can't seem to figure out what drive or controller is causing the issue. Could somebody please point me in the right direction? My system is a Ryzen 2600, MSI B450-A Pro, 24gb ram @ 2933, LSI 6Gbps SAS HBA LSI 9200-8i = (9211-8I) IT Mode controller & Asus 1050ti Thanks in advance for your help Unraid issues.zip
  7. The array was showing as all fine but I'd been getting notifications from fix common problems that my drive (disk2) was failing and my weekly parity check had slowed down to a crawl. This is my old config I ordered a new drive, patiently waited for it to arrive, shut the system down, pulled the old disk. Put in a new one, booted back up. I assigned the new disk to the slot (disk2), started the array and clicked the button to format the new drive. I came back the next day to see that the new drive was in the array but it's empty. All the files that used to be on that disk were gone. Because I'm a complete idiot, in between these points I'd taken the failing disk and put it into my desktop and quick formatted it to NTFS. If I hadn't done this I'd be able to just mount it and copy the XFS files off the disk. Is there any chance that my old data could still be sitting in the parity? Does anyone have any clues as to how this could have happened? Appreciate your support and assistance. Thank you

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.