Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,652

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    SMART looks good and the emulated disk is mounting so you can rebuild on top: stop array, unassign disk5, start array, stop array, re-assign disk5, start array to begin rebuild.
  2. JorgeB
    If possible yes, nfs is knwon to have issues with stale file handles, that can cause those shfs crashes.
  3. JorgeB
    Consult board manual, look for what slot is DIMM E1, replace it that DIMM, see if errors stop.
  4. JorgeB
    MCE is detecting a memory related hardware error, usually a bad DIMM, it needs to be identified and replaced or removed, system event log in the board BIOS, or the IPMI event log that can been checked with the IPMI plugin might contain more info.
  5. JorgeB
    Yes, shfs crashed, it's a known issue, if you don't need nfs disabling it might help with that, but every time this happens a reboot is needed.
  6. JorgeB
    Syslog shows memory errors correct by ECC, check system or IPMI event viewer, it should have more info on the affected DIMM.
  7. JorgeB
    There's something else you can still try with that disk, but first stop array, unassign one of the other data disks, not the same one you rebuilt, start array, emulated disk will likely also be unmountable but see if the now unassigned disk can be mounted with the UD plugin.
  8. JorgeB
    Did the rebuild finish?
  9. JorgeB
    Yes, nothing out of the ordinary logged at that time, but there are previous macvlan call traces, so worth checking this out to see if it applies to you: 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/
  10. JorgeB
    There was another unclean shutdown: May 27 09:59:52 Tower emhttpd: unclean shutdown detected
  11. JorgeB
    There are JMB585 controllers that can do that, they have 5 ports total, M.2 slots are SATA only:
  12. JorgeB
    See here:
  13. JorgeB
    Syslog starts over after a reboot, so we can't see what happened, make sure you check this and if it still keeps crashing enable this then post that log after a crash.
  14. JorgeB
    It's possible, data corruption can cause all sorts of issues.
  15. JorgeB
    Then they are old errors and can be reset, see here to reset and to better monitor the pool for the future: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582 It's not normal for data corruption to happen, next time it does act right way.
  16. JorgeB
    Because it needs better cooling? Parity works every time there are writes to the array.
  17. JorgeB
    Likely related to the megaRAID controller, see if it can be flashed to LSI IT mode but probably note, RAID controllers are not recommended.
  18. JorgeB
    Not really and not what I said to do, I said to rebuild only if the emulated disk mounted correctly, if it didn't you should never rebuild on top, but you can try running a filesystem check now.
  19. JorgeB
    See here for some examples: https://forums.lime-technology.com/topic/59589-solved-v635-advice-please-on-shares-settings/?do=findComment&comment=584558
  20. JorgeB
    Cache is detecting data corruption, you should run a scrub, if there are uncorrectable errors look at the syslog for the name of the files, those need to be deleted/restored from backups.
  21. JorgeB
    Enable legacy boot on the board BIOS or enable UEFI boot on Unraid by renaming EFI- to EFI on the flash drive, this can also be enable when creating the flash drive with the USB tool, but default is disable.
  22. JorgeB
    Yep, that's the downside, but also the only way to get more than around 50MB/s writes to the array.
  23. JorgeB
  24. JorgeB
    First check after fixing the problem can still find errors, but after that it should always be 0 errors, which is the only acceptable number of sync errors.
  25. JorgeB
    It passed so disk is OK for now, keep monitoring, especially this attribute, if it keeps climbing there will likely be more errors soon: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 5567 Disk is at 70K power on hours, so it's probably not going to last much longer anyway.
×
×
  • Create New...