Jump to content

Fransysco

Members
 View Profile  See their activity

  • Posts

    22

  • Joined

  • Last visited

 Content Type 

Posts posted by Fransysco

    Read errors on all disks

    in General Support

    Posted

    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.

    image.png.cb8ec1d0b8f61eddd6bc6929363fe075.png

    I've also never seen RAM do this before is this just from a bunch of errors?

    image.png.4386894aaa13eda1aa56ac9b006ca512.png

    riaahq-diagnostics-20210208-0133.zip

    Random Disk errors

    in General Support

    Posted

    4 hours ago, JorgeB said:

    Looks like the problem started with a power failure:

      

    
Oct 31 02:05:36 RIAAHQ apcupsd[3244]: Power failure.
Oct 31 02:05:38 RIAAHQ kernel: sd 2:0:0:0: device_block, handle(0x000a)
Oct 31 02:05:38 RIAAHQ kernel: sd 2:0:1:0: device_block, handle(0x000b)
Oct 31 02:05:38 RIAAHQ kernel: sd 2:0:2:0: device_block, handle(0x000c)
Oct 31 02:05:38 RIAAHQ kernel: sd 2:0:3:0: device_block, handle(0x000d)
Oct 31 02:05:38 RIAAHQ kernel: sd 2:0:4:0: device_block, handle(0x000e)
Oct 31 02:05:38 RIAAHQ kernel: sd 2:0:5:0: device_block, handle(0x000f)
Oct 31 02:05:38 RIAAHQ kernel: sd 2:0:6:0: device_block, handle(0x0010)
Oct 31 02:05:38 RIAAHQ kernel: sd 2:0:7:0: device_block, handle(0x0011)
Oct 31 02:05:38 RIAAHQ kernel: sd 2:0:8:0: device_block, handle(0x0012)
Oct 31 02:05:38 RIAAHQ kernel: sd 2:0:9:0: device_block, handle(0x0013)
Oct 31 02:05:38 RIAAHQ kernel: sd 2:0:10:0: device_block, handle(0x0014)
Oct 31 02:05:38 RIAAHQ kernel: sd 2:0:11:0: device_block, handle(0x0015)

     

    Are all the disks on the same UPS? Or are they in some kind of separate enclosure?

     

    Reboot to clear the errors (disable disks will remain disable), then start the array and post new diags.

    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

    Random Disk errors

    in General Support

    Posted · Edited by Fransysco

    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?

     

    image.thumb.png.5d2ca078ec0f97049f30a285b0f68b07.png

    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.

    Cache Pool After Swaping Hardware

    in General Support

    Posted

    2 hours ago, JorgeB said:

    Yes, if all members are there and in blue it will import any existing pool, though if you dind't already start the array once with no cache devices assigned to make sure pool config is "forgotten".

    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.

    Cache Pool After Swaping Hardware

    in General Support

    Posted

    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?

    [SOLVED] Number of Issues after moving from 6.7.2 to 6.8.3

    in General Support

    Posted · Edited by Fransysco

    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!

     

     

×
×
  • Create New...