Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,797

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    There was a preclear error, that's a different issue, check or post the preclear log.
  2. JorgeB
    You mean the pool right? You can clear it by wiping both devices with 'blkdiscard -f /dev/sdX' and 'blkdiscard -f /dev/nvme0n1', then start the array and format the pool. Again assuming the pool, yes use the single profile: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480421
  3. JorgeB
    Start the array without the disk, preclear should work then.
  4. JorgeB
    You can cancel, it won't work in the end anyway. Since the emulate disk was formatted if you remove the disks a parity sync is required.
  5. JorgeB
    Update to latest stable, if it still crashes enable the syslog server and post that after a crash.
  6. JorgeB
    Should be fine with 10.3
  7. JorgeB
    On the disk to be rebuilt only, parity won't be 100% in sync because you stared the array with one missing disk.
  8. JorgeB
  9. JorgeB
    Should be OK, but some filesystem corruption can happen.
  10. JorgeB
    Device is dropping offline, this is usually a power/connection problem, suggest replacing/swapping both cables, power and SATA.
  11. JorgeB
    It should work.
  12. JorgeB
    NVMe device dropped offline, if it's a reoccurring issue this can sometimes help: 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.
  13. JorgeB
    When you started the array with disk3 emulated it mounted, suggesting the problem is the disk not accepting the correct partition layout, you can try clearing or preclearing the disk and try again, but there could be some other issue.
  14. JorgeB
    xfs_repair should find a backup superblock, but there will likely be some metadata damage, another option is using a file recovery util like UFS explorer.
  15. JorgeB
    Jun 27 20:45:08 Tower kernel: BTRFS info (device sdg1): bdev /dev/sdf1 errs: wr 1592711, rd 617759, flush 127116, corrupt 878662, gen 0 This suggests sdf dropped offline in the past, see here for how to handle that.
  16. JorgeB
    Jun 27 10:01:34 VEYRON kernel: BTRFS: error (device nvme0n1p1) in btrfs_run_delayed_refs:2150: errno=-28 No space left As mentioned the pool ran out of space, that's why it went read-only, there are other options but easiest way to get out of this would be to backup the pool to the array (or use existing backups) and re-format.
  17. JorgeB
    Then it's likely a disk problem.
  18. JorgeB
    See if this applies to you, if yes, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.: 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/
  19. JorgeB
    Diags after array start please.
  20. JorgeB
    Read Device Identity failed: Unknown error Device is not responding to SMART, not sure if it could be a device problem or some compatibility issue, try in a different controller/computer if available.
  21. JorgeB
    Please post the diagnostics, ideally from before and after rebooting, if you don't have before post just the current ones.
  22. JorgeB
    All disks are mounting, I guess you're asking about the disabled disk, SMART is showing some issues so wait for the extended test to finish.
  23. JorgeB
    If the contents of the rebuilt disk4 look correct you don't need to do anything else, in doubt you can always mount the old disk with UD and compared data.
  24. JorgeB
    Good info about that below: https://forums.unraid.net/topic/123901-plex-issues-upon-upgrade-to-6101/?do=findComment&comment=1138715 https://forums.unraid.net/topic/75436-guide-how-to-use-rclone-to-mount-cloud-drives-and-play-files/page/115/#comment-1140504
  25. JorgeB
    Disk is still showing pending sectors, so it's likely still bad, like mentioned errors usually happen on reads, not writes, but if you want to confirm before replacing run a SMART extended test.
×
×
  • Create New...