Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,831

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Yes, no link is being detected on any NIC, onboard NIC is currently eth4: Settings for eth4: ... Link detected: no driver: e1000e
  2. JorgeB
    Again, you can use old disk2 in the new array.
  3. JorgeB
    Looks more like a hardware problem, you can enable the syslog server but doubt it will catch anything, PSU, board, RAM would be the main suspects, also UPS if you have one.
  4. JorgeB
    Docker image was created new at first array start after boot: Jul 14 17:46:10 Tower emhttpd: shcmd (89): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20 Jul 14 17:46:10 Tower root: Creating new image file: '/mnt/user/system/docker/docker.img' size: 20G This means one didn't exist, maybe you have some script deleting the image on array stop/shutdown? Post new diags after this last boot to see if the same thing happened.
  5. JorgeB
    Syslog is completely spammed with a mac related SMB issue so we can't see what happended, disk looks OK, swap cables, both power and SATA with a different disk to rule that out, if the problem follows the disk replace it.
  6. JorgeB
    That's expected, you still have the failing cache device installed, you need to replace it.
  7. JorgeB
    Reboot. Device disconnected, one of the reasons we don't recommend USB devices in the array/pools. Aug 12 21:57:28 Tower kernel: usb 3-5: USB disconnect, device number 2 Aug 12 21:57:39 Tower kernel: usb 3-5: new high-speed USB device number 5 using xhci_hcd
  8. JorgeB
    Only way would be to downgrade Unraid and replace there, then upgrade back, but you'll run into the same issue in the future, I would recommend recreating all the SSDs with the new partition, you can do one by one, once this is done there won't be any further issues with this.
  9. JorgeB
    There's no link detected in any of the 5 NICs.
  10. JorgeB
    Are you using a rootshare? IIRC someone else had shares issues recently because of that.
  11. JorgeB
    Enable the syslog server and post that together with the complete diagnostics after a crash.
  12. JorgeB
    You can, and check that the emulated disk mounts, you should then replace the missing disk ASAP.
  13. JorgeB
    SMB is single threaded, for 10GbE I would expect a possible bottleneck, but that CPU should be enough for 2.5GbE, if you have an array disk still empty, and because disks are much faster in the outer sectors, enable turbo write and write directly to the array, it should be capable of 200MB/s+, just to check if if the pool is under performing.
  14. JorgeB
    With a fast NVMe device you can basically get line speed with 10GbE, note that not all NVMe devices can sustain high write speeds, cheaper devices use SLC or pseudo SLC cache and can only sustain max write speed for a few GBs. See here for a recent discussion about existing options.
  15. JorgeB
    2nd one is JMB585, but both chips are fine.
  16. JorgeB
    IMHO disk9 is lost.
  17. JorgeB
    So why are you saiyn it's lost? Like mentioned just do a new config with it and the remaining disks. You can, it will resume from where it was.
  18. JorgeB
    It's not normal, diags might show something.
  19. JorgeB
    Wasn't disk2 mounting with UD? ddrescue is your best bet for disk9, if that doesn't work UFS explorer won't also, UFS explorer might help on the cloned disk if there are fs issues.
  20. JorgeB
    Unraid doesn't need internet to check the license, except for trial keys, and you still would have GUI access, you can try renaming /config/network.cfg and use the default DHCP setting to see if it works.
  21. JorgeB
    Yes, unless the errors coincided with empty space on the rebuilt disk. Looks like it, they are logged as disk errors, and SMART doesn't look good for both, you can run an extended SMART test to confirm. I would recommend dual parity for such a large array, even with errors in two extra disks dual parity would still help unless both disks had errors in the same sectors.
  22. JorgeB
    See below: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
  23. JorgeB
    write time tree block corruption detected This usually is a sign of bad RAM or other kernel memory corruption. Unrelated: Aug 6 01:30:56 unraid kernel: macvlan_broadcast+0x116/0x144 [macvlan] Aug 6 01:30:56 unraid kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)).
  24. JorgeB
    Try a different one, don't see how Unraid can kill a flash drive after one boot.
  25. JorgeB
    It's still using macvlan.
×
×
  • Create New...