Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,737

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    This suggests you already have another disabled/invalid disk, please post the diagnostics.
  2. JorgeB
    Start by running memtest.
  3. JorgeB
    There are read errors in multiple disks: Dec 31 11:41:40 Tower kernel: md: disk1 read error, sector=5860527944 .. Dec 31 11:41:40 Tower kernel: md: disk6 read error, sector=5860527944 .. Dec 31 11:41:40 Tower kernel: md: disk2 read error, sector=3911257848 Need to fix that first, looks like a connection/power problem.
  4. JorgeB
    Bad idea performance wise to have a parity HDD for an all flash array, you mentioned not needing data protection so just don't assign one, or use another SSD.
  5. JorgeB
    Just to add that it's not required, CSM/legacy boot works with or without the dash in EFI.
  6. JorgeB
    That's about normal with parity present.
  7. JorgeB
    Controller is flashed to RAID mode and using the LSI MegaRAID driver, flash to IT mode, to use that RAID mode you'd need to create JBOD or RAID0 volumes for all drives in the controller BIOS, but that's not recommended.
  8. JorgeB
    Diags after array start in normal mode please.
  9. JorgeB
    Sorry, missed that those were from the flash drive. You need to increase the shutdown timeout, it's set at 90 seconds and Unraid was still in the middle of umonting the disks at that time, with the array running normally press stop and time how long it takes, add 30 seconds and set that as the new shutdown timeout, or just try setting to like 150secs or similar, should be enough.
  10. JorgeB
    Dec 29 11:58:06 Astro-Server kernel: sd 7:0:0:0: Power-on or device reset occurred Dec 29 11:58:06 Astro-Server kernel: sd 7:0:2:0: Power-on or device reset occurred Dec 29 11:58:06 Astro-Server kernel: sd 7:0:7:0: Power-on or device reset occurred This error repeating for multiple devices, this is most often a connection/power problem, you should also update the LSI firmware since it's quite old.
  11. JorgeB
    When Unraid can't shutdown cleanly it saves the current diags in the flash drive, logs folder, those diags might give a clue on what the problem is.
  12. JorgeB
    Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan might 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/
  13. JorgeB
    These mean data corruption is being detected, most often due to RAM issues, in your case and since you're running a Ryzen CPU with above max spec RAM speeds that would be the main suspect, could also just be bad RAM or other hardware issue. After the problem is fixed a scrub will list the corrupt the corrupt files in the syslog, those need to be deleted/replaced from backups.
  14. JorgeB
    Yep. No, with raid1 with will always be written to both devices and read also from both alternatively according to even/odd PIDs.
  15. JorgeB
    "Pools slots" replaces "cache" on older releases, because now Unraid supports multiple pools.
  16. JorgeB
    Yes, it failed to add the device to the pool, try this: -stop array -unassign cache2 -start array -to completely wipe the device type in the console: blkdiscard /dev/sdc -reboot -try again, post new diags if it still fails.
  17. JorgeB
    Please post the diagnostics.
  18. JorgeB
    Direct pool device replacement (for btrfs only) is currently broken, but you can still use this procedure: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923
  19. JorgeB
    You need to run it without -n or nothing will be done.
  20. JorgeB
    Check filesystem on disk2.
  21. JorgeB
    I would leave it for now vs running with the disk emulated, just make sure the parity check is non correct since read errors are expected, or skip the check until you replace it.
  22. JorgeB
    Please use the exiting plugin support thread:
  23. JorgeB
    SMART test failed, disk should be replaced, or at a minimum completely re-written to see if that sector gets remapped and it doesn't get anymore in the near future.
  24. JorgeB
    Yes, as long as the device is correctly added to the pool, in doubt you can post diags after doing it, it usually works without issues, but sometimes it doesn't.
  25. JorgeB
    Sorry, it's something I've never used so not sure what the options for enabling it are, searching the forum should return some results.
×
×
  • Create New...