Jump to content

JorgeB

Moderators
  • Posts

    67,786
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. You might have a NIC that uses the tg3 driver, please post the diagnostics, you can get them from the CLI by typing 'diagnostics', they will be downloaded do the flash drive.
  2. Do you mind posting the diagnostics so we can see what hardware you're using and if there any signs of that issue?
  3. You can download from here: https://www.dropbox.com/s/yximuar3v3scf0g/unRAIDServer-6.8.3-x86_64.zip?dl=0
  4. Not AFAIK, any specif reason you want such an old release? I still might have it.
  5. You're using a RAID controller, those are not recommended, but if you want to use you might need to pass-through each device to the OS, some controllers require creating JBOD/RAID0 volume for each device.
  6. I would be cautious of suspecting a general issue after a single occurrence, lots of people using NVMe devices, I myself have eight between my two main servers, see if you can reproduce the issue with a different board, if not then we could try to find someone with the same one, it could just be some defective hardware.
  7. It's fine to have SSDs in the array, just be aware that they won't be trimmed.
  8. Run a scrub on all array drives, if no corruptions are found run a correcting check.
  9. You must disable vt-d, v6.10.2 looks for that, there are stability issues, even some possible filesystem corruption if vt-d is enable with those servers, problem is believed to be caused by the NIC driver when vt-d is enable.
  10. Change to ipvlan, it does look like that issue.
  11. Different driver: 01:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme II BCM5709 Gigabit Ethernet [14e4:1639] (rev 20) DeviceName: Embedded NIC 1 Subsystem: Dell PowerEdge T610 BCM5709 Gigabit Ethernet [1028:0237] Kernel driver in use: bnx2 Kernel modules: bnx2 As far as we know, not affected, so far all affected servers I found, about 10 in total, were using a NIC with the tg3 driver and that appears to be the only thing they had in common.
  12. Sorry for the late reply, missed this post before, please post the diagnostics.
  13. I didn't say you don't need to stop the array, you don't need to disable and rebuild the disk, was going to post the instructions but itimpi already did.
  14. Nope, no need to disable the drive and formatting will deleted everything, it can't be rebuilt from parity, procedure is: -move all data from that drive to another place -format it -restore the data
  15. Yes. Unless you have pre-existing checksums or are using btrfs there's no way of knowing if the sync errors are on the data or parity, in that case you should just run a correcting check.
  16. You haven't yet check this and if still issues post the full syslog from a syslog server after a crash.
  17. Might be something specific to your hardware, like with the Dell servers, though unfortunately the solution for that doesn't work for you, suggest creating a bug report.
  18. Try this: https://forums.unraid.net/topic/124055-unraid-6101-fails-to-boot-bzroot-checksum-error/?do=findComment&comment=1131675
  19. Unless I missed it not seeing any attempt to format the disk in the array, after adding a new disk you need to format it, next to array start/stop button.
  20. I would suggest redoing the flash drive done manually: Backup config folder from flash, then in Windows open a command prompt window as administrator, then type, in this order: -diskpart -list disk -select disk x (x=your flash drive) -clean -create partition primary -format fs=fat32 label=UNRAID quick -active -assign -exit -close cmd window -unzip new Unraid install to flash -restore the previously backed up config folder -execute make_bootable as admin
  21. I meant when you get this error ahd the linked post solves it it's a Dell server, but this error can have other reasons.
×
×
  • Create New...