Jump to content

JorgeB

Moderators
  • Posts

    67,797
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. First things to do is to check/replace cables for disk2 and the 2TB pool disk, then post new diags after array start.
  2. Those controllers work like a standard HBA, you just need to power down, swap controllers and power back up, all disks should be correctly re-assigned and ready for array start.
  3. Don't remember seeing that before, recommend shutting down, disconnecting that device and powering back on.
  4. If it's a RAID controller in JBOD mode it might require re-assigning all the disks, and possibly the partitions will be invalid, if you want post current diagnostics, they might give a better idea.
  5. Corefreq plugin is crashing, uninstall it.
  6. Assuming no RAID controllers are involved you just need to swap controllers and that's it, devices are tracked by serial number, though always good to save the diags or take a screenshot of the GUI before starting.
  7. I split your latest post to the KVM forum, much more likely to get pertinent help there.
  8. Should still see something after the BIOS, like "no boot device found" or something similar.
  9. Quick search does indeed point to a problem in the in tree Linux driver, it's rumored next Unraid release will have a better way of installing/managing out of tree drivers, but that can take some time to be available.
  10. Possibly a driver issue, not uncommon with Realtek, but if you delete network.cfg and downgrade to -rc2 it works?
  11. Do you mean right after the BIOS, i.e., you don't even see the Unraid boot menu? If that's true can't see how it can be because of the update.
  12. Possibly, that's something I don't know much about, hopefully someone else can help you.
  13. Unlikely, AFAIK the only thing that changed is the device detection during boot, that looks more like driver/initialization issue, I would recommend starting a new thread in the general support forum and please don't forget the diagnostics.
  14. Do you know the previous release you were running? If it's one of those you downgrade to and now it doesn't work suggests it's some flash/install issue.
  15. First set appdata to cache=no then run the mover so that data from the other share can be moved to the array, once that's done set appdata back to cache=prefer and run the mover again, then post new diags.
  16. Jun 14 14:55:21 Tower kernel: BTRFS info (device sdi1): bdev /dev/sdj1 errs: wr 772370105, rd 641390571, flush 4473716, corrupt 4949264, gen 0 Jun 14 14:55:21 Tower kernel: BTRFS info (device sdi1): bdev /dev/sdi1 errs: wr 1603125, rd 1089630, flush 8890, corrupt 3731, gen 0 Both cache devices are showing a very large number or read and write errors, this means both have been dropping offline, see here for better pool monitoring.
  17. Please post a screenshot of the GUI after the plugin update completes.
  18. Take a screenshot of the old disk assignments then go to tools and do a new config, re-assign all the disks to their original slots, check "parity is already valid" and start the array.
  19. Docker image went read-only for an apparent lack of space, would should balancing the cache filesystem. Cache device didn't drop again but it's still showing several ATA errors, still looks like a cable/connection problem, I would suggest trying it in a different controller, swap with another disk if you don't have other free ports.
  20. This is no longer needed for v6.10.3, it already comes by default with iommu=pt.
  21. Possibly, but make sure SMB1 is enabled in Unraid, or it won't work for sure.
  22. I didn't noticed before, you quoted the default Unraid command, use the one below that posted by Forusim.
×
×
  • Create New...