Jump to content

JorgeB

Moderators
  • Posts

    67,616
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. OK, just wanted to make sure since some users expect replacing cables/controller fixes a disable disks. First diags show a successful rebuild, second ones show a rebuild in progress, there are some ATA errors though, you say it's always the same disk that gets disable, even if you connect it to a different controller?
  2. xfs_repair didn't damage anything since it was run in read-only mode (-n), but it was a waste of time.
  3. I did ask if it was XFS... Try rebuild the superblock, then you'll need to run reiserfsck again with --rebuild-tree: https://wiki.unraid.net/Check_Disk_Filesystems#Rebuilding_the_superblock
  4. JMB585 usually works fine with Unraid. Not clear if you then rebuilt the disk and it happen again, because once a disk is disable it needs to be rebuilt.
  5. In the board BIOS there should be a "idle power supply control" setting.
  6. Diags are all after rebooting so not much to see, you can try this but by the description it sounds more like a hardware issue, and in that case it may not log anything.
  7. Best bet is to post on the docker support thread, if there is one:
  8. That and your other problem suggest the flash drive is not mounting correctly, recreate it or try a different one.
  9. Respect max officially support RAM speeds with Ryzen or you'll likely run into trouble.
  10. Make sure mover logging is enable, run the mover then grab and post diags.
  11. After booting type "diagnostics" in the console and then attach them here.
  12. Not just that, also netfilter call traces mentioned in the second link, also worth trying this: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/?do=findComment&comment=14530
  13. This will happen if the share's minimum free space setting is not correctly set, it should be set to twice the max file size you expect to copy to that share.
  14. Sounds like a plex problem then, you can try the plex forum or the docker support thread.
  15. For any further controller related discussion please use the new thread:
  16. You can also try this: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/?do=findComment&comment=14530
  17. Once a disk gets disable it needs to be rebuilt (or do a new config).
  18. I meant does it get better if you stop everything after the problem starts?
  19. The easiest solution is to rebuild them one by one so the partition can be correctly recreated: https://forums.unraid.net/topic/84717-moving-drives-from-non-hba-raid-card-to-hba/ If it's really a RAID controller you should avoid that, or may need to repeat the same if you change controllers again in the future.
  20. Sorry meant disk1, disk9 is also showing a pending sector, but could also be a false positive, but yeah also run an extended test on it.
  21. Didn't notice you don't have parity, yes, in that case you just need to restart the array for Unraid to re-detect the disk.
×
×
  • Create New...