Fransysco

Members
  • Posts

    22
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Fransysco's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Disks are in a DS-4246. The UPS isn't reporting any issues and none of my other equipment on it (Networking, Cisco UCS) showed any issues. Would there be anything within unraid that could help me try to figure out if thats the issue? The errors did increment so I shut down the array, even though its not being used outside of Plex normal data operations. I've also never seen RAM do this before is this just from a bunch of errors? riaahq-diagnostics-20210208-0133.zip
  2. I just got notified of read errors on all of my disks in my array (including parity) all disks show green still. Googling the error returned mostly posts about caches (my cache is not showing errors). Array wasn't being used at the time of errors being reported, and they are not increasing currently. Diagnostic file attached. riaahq-diagnostics-20210206-2258.zip
  3. The night before I did have what seemed like a weird brown out in the house but it was 6+ hours prior to any alerts coming in. I never got an email alert for power failure and the disk failure emails I got were 4 hours after the time of the UPS power failure reported above. Disks are all on the same two PSUs plugged into the same UPS. Attached is the diagnostic bundle after a reboot. What I've done so far: Rebooted the array, both disks showed as disabled. I ran SMART on both and they came back clean. I removed the Parity Drive, started the array, stopped the array, added the parity drive back, and am rebuilding the parity drive. diagnostics-20201101-0920.zip
  4. I attached it to the original post.
  5. I woke up to a few emails about disk errors randomly. Two of my disks have been taken out of the array and all but two of my disks are showing at least 1 error. I swapped hardware earlier this week but did a parity check afterwards with no errors. I have not touched anything what are my steps to recover from this without loosing data? diagnostics-20201031-1621.zip Edit: I stopped the array and got a notification of "array turned good Array has 0 disks with read errors". But the two drives are still showing disabled.
  6. It worked thank you! Is this expected behavior with the cache pool when swapping hardware? All of my array drives auto populated but the cache drives did not.
  7. So even if both show as "New Device" and blue I should start the array and the data should be there?
  8. I just moved hardware (everything new except hard drives and USB drive). Everything came up green on the new hardware except my cache pool. Both drives showed unassigned. Drive 1 of the cache pool did not show up in the system (I believe it's not seated properly but don't want to touch it yet) when I assign drive 2 to the second drive in the pool it's listed as a new device. Should I power down and reseat the drive or am I going to loose the data on the drives? Is there a way for me to just recover the data off one of the cache disks and then start fresh with the cache pool?
  9. That seemed to work. On bootup I didn't have the option to start my array it only listed reboot and shutdown. I did a reboot and everything seems good now. Do you think I should be concerned about this happening? Indication of my USB drive starting to fail? thank you!
  10. I plugged it into my win10 device and get this popup: I assume I should repair?
  11. I recently upgraded from 6.7.2 to 6.8.3 about a week ago and the last few days I've noticed some issues. I noticed that when I try to disable docker in the settings it acts like its going to but will just refresh and show "running" All of my Containers are listed as "unavailable" When I try to add a container I get the following error: "Warning: file_put_contents(/boot/config/plugins/dockerMan/templates-user/my-plex.xml): failed to open stream: Read-only file system in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 97" I did a clean reboot (stop array, I wait 5 minutes, then power down from GUI), however on power on it said it was not a clean shutdown so I did a parity check which ran normal and found no errors to correct but did throw this error: Warning: file_put_contents(/boot/config/parity-checks.log): failed to open stream: Read-only file system in /usr/local/emhttp/plugins/dynamix/include/DeviceList.php on line 447 Looking at different posts it does seem to be related to my docker image being full / corrupted but I really don't know how to verify that and I don't want to delete the wrong thing either.... Attached is the support bundle. Thanks for any help!
  12. Okay so the different slot seems to have worked... My concern is that its the same riser, so I guess the one slot on the card could be bad but I have my ethernet NIC in the old slot and it seems to be operating fine. I'm not sure if I can trust things, if I should get a new card, maybe just a whole new server at this point, or if I'm just being paranoid.... lol Attached diagnostics if interested. and thanks everyone for the help so far!
  13. thats what i was thinking based on most of the disks going away. Which log or what alert is the indication of the carding dropping? So I can just verify myself if it occurs on a different slot without having to post another diag and having someone else look?
  14. Okay so I did a extended smart test on the failed disk when I got my replacement fan and it passed without errors. I did new config of just the disks and did some file tests and everything seemed fine. I went to build parity and it failed with a large number of errors again: After I stopped the array a large majority of the disks are showing missing: I captured two diagnostics bundles (I wasn't sure if it was worth while to get it after the array was stopped because the disk status changed). Both were captured prior to any power off. -0817 is before the array is stopped and -0828 is after the array is stopped.