Jump to content

TarrifMan

Members
  • Content Count

    15
  • Joined

  • Last visited

Posts posted by TarrifMan


  1. On 3/15/2020 at 11:51 PM, Dissones4U said:

    I assume the original "disk disabled" problem is resolved and now your only issue is docker connectivity? 

    So is this just cosmetic?

    My guess is that the above errors are generated due to a lack of internet access and are directly related to the docker updates showing as not available. With that in mind, I'd start with some basic network troubleshooting. Try to rule out one hardware component at a time such as the ethernet cable, NIC, (maybe SSD that houses Docker but I doubt it). Then move to software settings such as unRaid network settings, docker configuration, CA auto update applications settings etc. If you haven't already, you should enable syslog server just in case and always include your latest diagnostics... On a final note, if your original issue of 'disk disabled' is resolved you may want to either change the title to better reflect the current problem or start a new thread. A disabled disk is pretty basic whereas docker connectivity is a whole different specialty.

    yeah, I redid all the network paths and everything was back. Not sure how it broke in the first place tho! thanks for the help


  2. On 3/9/2020 at 6:38 PM, Dissones4U said:

    Looking at the smart data for the disabled disk above, it looks fine BUT the disk was disabled for a reason, if you overwrite the existing disk (re-enable) then you'll have limited recovery options. Best practice dictates that you rebuild to a new disk, read here. I don't think you have FS corruption on the disabled disk as I'd expect to see an error like: "XFS (md3) Metadata corruption detected" or something similar. even so, do not proceed with any type of rebuild, format etc until you understand the potential for data loss.

    I can't tell for sure if it is or not but make sure your flash is on USB 2 not USB 3, otherwise it won't work and could cause various errors including disabling disk due to dropped connectivity.

    Is the disabled disk on USB 3 as an unassigned device? USB 3 may affect that too but someone else will need to confirm...

    Some of these may indicate a network issue but I think they are irrelevant to your disabled disk. Squid's Fix Common Problems is really good about telling you what's wrong, if you can't figure these errors out then consider posting in the CA thread for support.

     

    On 3/10/2020 at 2:42 AM, johnnie.black said:

    Disk was already disabled at boot so we can't see what happened, best to replace/swap cables to rule them out them rebuild.

    I did a rebuild on the disk and now my dockers versions say "not available" but the dockers are running and the webiu is accessible.  I've restarted docker service, restarted the system, and checked for updates. However, when I checked for updates, it just stalls and never finishes. 

    TTIdJwb.png
    edit: 1 hour later, the Shinobi and radarr containers changed to "not available" 
    image.png.3db557b2dc611c0b95040cf016e898eb.png


  3. I finally rebooted the system to update to 6.8.2 and suddenly I lost internet to the internet. I downgraded back to 6.8.0 and I still have no internet.

    I can ping local devices but cannot ping google.com or 8.8.8.8.  Server is connected to a unifi switch which is connected to a unifi USG. All my other devices have internet access (Wired and wireless).   I've noticed a "default" route is missing. 

    PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
    64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.019 ms
    64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.039 ms
    64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.041 ms
    64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=0.041 ms
    64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=0.032 ms
    64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=0.040 ms
    64 bytes from 192.168.1.2: icmp_seq=7 ttl=64 time=0.039 ms
    64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=0.041 ms
    64 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=0.039 ms
    64 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=0.032 ms
    
    --- 192.168.1.2 ping statistics ---
    10 packets transmitted, 10 received, 0% packet loss, time 9189ms
    rtt min/avg/max/mdev = 0.019/0.036/0.041/0.006 ms
    root@Titan:~# ping google.com -c5
    ping: google.com: Name or service not known
    root@Titan:~# ping 8.8.8.8 -c5
    ping: connect: Network is unreachable

    Network Settings:

    http://prntscr.com/r7qg7g

    http://prntscr.com/r7qgnt

     

    What I tried so far:

    disable/re-enable bonding (this resulted in me losing access to the server and had to disconnect power to get it to reboot)

    disable/re-enable bridging

    changing DNS (this resulted in me losing access to the server and had to disconnect power to get it to reboot)

    rebooting the switch/ USG

     

     

    I will send logs via pm

    diagnostics-20200225-2354.zip


  4. 1 minute ago, BRiT said:

    Reboot or power cycle.

    I pressed stop array 15 mins ago and it's still not done... " Array Stopping•Retry unmounting disk share(s)."

    Me deleting /dev/ files might have broke unassigned devices too....

    "Fatal error: Uncaught UnexpectedValueException: RecursiveDirectoryIterator::__construct(/dev/disk/by-id/): failed to open dir: No such file or directory in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php:122 Stack trace: #0 /usr/local/emhttp/plugins/unassigned.devices/include/lib.php(122): RecursiveDirectoryIterator->__construct('/dev/disk/by-id...', 4096) #1 /usr/local/emhttp/plugins/unassigned.devices/include/lib.php(1232): listDir('/dev/disk/by-id...') #2 /usr/local/emhttp/plugins/unassigned.devices/include/lib.php(1294): get_unasigned_disks() #3 /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php(269): get_all_disks_info() #4 {main} thrown in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 122"

     

    Should I just turn the power off?


  5. I was trying to delete some files via the console. Types in /d and tab, enter without reading it until after the action was performed which resulted in /dev/ files being deleted (folders within are still there because I didn't do "rm -r").

     

    Where can I get those files? What should I do? 


  6. 3 minutes ago, trurl said:

    SSDs in the array are not recommended. They cannot be trimmed, some implementations might invalidate parity, and in any case they can't be written faster than parity anyway so I don't know why you would want to do this.

     

    SSDs in the cache pool or as Unassigned Devices is what everyone else does.

    Thanks, I'll use it as cache then.


  7. GPU: (AMD Radeon RX580)

    Since Ryzen 3700x has no integrated graphics, I had a GPU plugged in the first time I booted unraid. It started but just kept saying "amd-vi: completion-wait loop timed out." Eventually, I just shut it off, removed the GPU and it booted up fine. IOMMU is enabled in the BIOS and SVI is also enabled. I rebooted again, this time, I checked the BIOS to make sure the m.2 ssd is detected; it is but it's not showing in unraid.

    UPDATE:

    System boots and detected the GPU only if IOMMU is disabled. 

     

    Parts:

    • Crucial 32GB CT2K16G4DFD8266 ECC
    • EVGA 650W Supernova GQ 80+ Gold
    • DELL YT674 PRO/1000 VT PCI-E NIC 4-PORT GIGABIT SERVER ADAPTER EXPI9404VT
    • (AMD Radeon RX580 8GB)
    • WD Blue SN500 500GB NVMe Internal SSD - Gen3 PCIe, M.2 2280, 3D NAND - WDS500G1B0C

     

    • Model: Custom

      M/B: ASRock B450M Steel Legend Version 

      BIOS: American Megatrends Inc. Version P2.50 (7/25/2019)

      CPU: AMD Ryzen 7 3700X 8-Core @ 3600 MHz

      HVM: Enabled

      IOMMU: Enabled

      Cache: 512 KiB, 4096 KiB, 32768 KiB

      Memory: 32 GiB DDR4 (max. installable capacity 128 GiB)

      Network: bond0: fault-tolerance (active-backup), mtu 1500 
       eth0: 1000 Mbps, full duplex, mtu 1500 
       eth1: interface down
       eth2: interface down
       eth3: interface down
       eth4: interface down

      Kernel: Linux 4.19.56-Unraid x86_64

      OpenSSL: 1.1.1c