Jump to content

JorgeB

Moderators
  • Posts

    67,662
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. In red is normal since they will still be disable, unmountable not, post new diags after array start.
  2. Run it again without -n or nothing will be done, if it asks for -L use it.
  3. Formatting is never part of a rebuild/data recovery, the disks looks fine, first thing to do is to fix the filesystem on both emulated disks: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
  4. Since you cross-posted there also going to lock this one.
  5. That looks fine, it's using a standard sector size and no protection, but can't really help anymore since you're running Windows.
  6. Some NVMe devices have issues with power states on Linux, try this, on the main GUI page click on flash, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (on the top right) and add this to your default boot option, after "append initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 Reboot and see if it makes a difference.
  7. Next time please use that thread instead for any plugin related issues/questions.
  8. Only if you saved some diags, check the logs folder in the flash drive.
  9. Please use the existing support thread:
  10. Changed Status to Closed Changed Priority to Other
  11. This issue was already reported and fixed for the upcoming release: https://forums.unraid.net/bug-reports/stable-releases/691-setting-warningcritical-temperature-in-smart-settings-not-possible-r1376/?do=findComment&comment=14183
  12. Not if you're still having macvlan/br_netfilter call traces.
  13. Still having errors in multiple disks, still looks like a connection/power problem, could also be the HBA, good idea to update it to latest firmware. You also need to fix filesystem on disk6.
  14. Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  15. These are data corruption errors, you should run memtest.
  16. That will happen if the minimum free space for the share is not set to more than the largest file you copy to that share, usually recommendation is to set to twice that. That's about right for default writing mode, see turbo write.
  17. Should be fine them, I would recommend replacing/swapping both cables/slot just to rule that out then keep monitoring.
  18. It's logged as a disk problem, but it's weird that it was sector 0: UNC at LBA = 0x00000000 = 0 Run an extended SMART test (or another parity check, but in that case replace/swap cables first to rule that out).
  19. Make sure you're booting CSM/legacy, memtest doesn't support UEFI boot.
  20. There fs corruption again: Jul 1 11:33:13 Tower kernel: BTRFS error (device dm-5): bad tree block start, want 204523241472 have 7362525906269925244 This is a new filesystem? If so you likely have a hardware issue, start by running memtest.
  21. Yeah, can't really help with that, you should create a new post about it in the KVM subforum.
  22. We can't, it's a separate database, there's a copy option but never used it before and not sure how it works.
  23. Did a quick test without the plugin installed, if a rebuild is running at the time scheduled for a parity check it will attempt to start one but since the rebuild is already running nothing happens, on the other hand if the rebuild is paused, I did it manually but it would be the same if paused by the plugin, then it re-starts the current rebuild from the beginning, so it's an Unraid bug, it's a minor one and one that won't affect many users but it might still be worth reporting.
×
×
  • Create New...