Jump to content

ssjucrono

Members
  • Posts

    97
  • Joined

  • Last visited

Posts posted by ssjucrono

  1. @trurl

    I powered down the server.

    I swapped all the SATA Cables with different SATA cables, checked the connection.

    I powered on the server, I did not start the array yet.

    I downloaded a diagnostics and attached it.

    I have not started the array yet or done anything else. I am waiting on anymore instructions. 

    Please let me know what else you may need.  

     

    unraid2-diagnostics-20190110-0956.zip

  2. @trurl

    Just to be clear the Disk 4 is disabled and is not spun up in the current array state. It will not let me run a smart test in this state. Last time when I rebooted unraid it remained disabled until I re-enabled it following the process I attached earlier. Just an FYI.

    When I get home later tonight I will power down, check all cables (most likely swap them). Power on and attach another diagnostic zip.

     

    Thank you again for your help thus far.  

  3. this is the first time it has happened. This is all new hardware to me that I got recently. I got the hardware used from a co-worker. That is a good tip about the troubleshoot mode.

    I was un-raring a large number of files as well as downloading data to the array. I left it for sometime and came back later to that original photo I attached. 

     

    Yes I am proceeding as normal to get the array back to normal.  

    I also have another disk, disk 1 which has UDMA errors that has crept up slowly. Could you look at that?  I have attached the smart report. 

    unraid2-smart-20190109-1127.zip

  4. The errors I saw was on the Main tab of unraid where it lists the read, writes, and errors.

    (Current screenshot, won't show error number as I am re-enabling the disk)

    image.png.125706b100df4dea4e206a68224049ed.png

     

    Also, I did do an xfs repair while the disk was still in the array. 

    This disk was disabled after rebooting the server. 

    I ran a smart test

    did the xfs repair in the array

    then because the drive was disabled, I re-enabled the drive following this process:

    https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive

     

    Please let me know if you have any other questions. 

  5. Helllo again,

     

    first thank you community for helping me so quickly with my previous issues! It is much appreciated.  Unfortunately I need to rely on you all again as I stumbled on this issue with my server last night. My Unraid server was unreachable, I connected a monitor to it and took the picture you see. I had to reboot the server twice. and then drive sdf had about 700 errors on it. I ran a smart test and it passed. I did an xfs repair on it and I am now re-adding it to the array. I have attached the photo and my diagnostics zip file. I am very curious as to what caused the issue on the server. Also I am concerned about the health of drive sdf.  Any help would be much appreciated. 

    Thank you 

    IMG_20190108_215104.thumb.jpg.a7e9989e3aa4c8baf96ac3f4197da027.jpg

    unraid2-diagnostics-20190109-0744.zip

  6. Thank you @Squid

     

    I do seem to have another issue. My array health report is showing failed. I have attached an updated Diagnostics  Zip.

     

    Also my NVME drive is constantly at 70C is this normal? It is a socket on the motherboard. There was a video-card near it but I removed the card and it made no difference in temp. 

     

    Not sure if you can help with this as well? 

    unraid2-diagnostics-20190102-0550.zip

  7. Hello,

     

    I just started a new unraid server with used hardware. I am checking everything and I came across this error in Fix Common Problems.:

     

    "Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged"

     

    I did not have mcelog installed so I installed and ran diagnostics. I have attached the diagnostics zip file. Any help advice would be much appreciated. I do have ECC RAM not sure how to determine if that was the issue.

     

    Thank you 

     

    unraid2-diagnostics-20190101-0755.zip

  8. Hello @Siwat2545,

     

    Thank you for all the hard work you are doing! It is very useful!

    I am trying to use the Home Assistant Control Panel and have not been able to get it started. I saw there was an update to the docker last night and update it but to no avail. Here is the log I am seeing:

     


    Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
    Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
    Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
    Get:4 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [274 kB]
    Get:5 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [122 kB]
    Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
    Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [744 kB]
    Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [585 kB]
    Fetched 1971 kB in 12s (160 kB/s)
    Reading package lists...
    File '/root/.homebridge/config.json' already there; not retrieving.
    Reading package lists...
    Building dependency tree...
    Reading state information...
    0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
    npm ERR! addLocal Could not install /
    npm ERR! Linux 4.18.17-unRAID
    npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "--unsafe-perm"
    npm ERR! node v8.10.0
    npm ERR! npm v3.5.2
    npm ERR! code EISDIR
    npm ERR! errno -21
    npm ERR! syscall read

    npm ERR! eisdir EISDIR: illegal operation on a directory, read
    npm ERR! eisdir This is most likely not a problem with npm itself
    npm ERR! eisdir and is related to npm not being able to find a package.json in
    npm ERR! eisdir a package you are trying to install.

    npm ERR! Please include the following file with any support request:
    npm ERR! /npm-debug.log

     

     

    Let me know if you need me to get the debug.log

     

    Thank you 

  9. Johnnie Thank you for your quick response and helpful information. I think this most likely happened when I was reconfiguring my LAN and flashing my router. I have not seen any more call traces since this. I will choose to ignore them for the time being.

     

    Thank you

  10. Hello,

     

    I have been receiving errors on my unraid server. it says I have call traces. I have looked through the logs but could not determine what exactly is the issue. I uploaded my Diagnostics. please if you need any other info I can get it. Or if I uploaded the diagnostics in the wrong way let me know and I can do it properly.

     

    Thank you for any help you can provide

    raid-diagnostics-20180305-1530.zip

×
×
  • Create New...