Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,884

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Make a request for it in the Nerdtools support thread.
  2. JorgeB
    If you have backups probably the best, you can still use the data on the working disks to avoid transferring everything.
  3. JorgeB
    Parity disk dropped offline, this is most often a connection issue, but since you've already swapped slots it might be the drive, post new diags after a power cycle so we can see the SMART for the drive.
  4. JorgeB
    If you finished the previous parity check run another one to see if no more errors are detected, if it didn't finish run a correcting check followed by a non correcting one.
  5. JorgeB
    Are you using custom docker network? If yes macvlan or ipvlan?
  6. JorgeB
    Please post output of df -h
  7. JorgeB
    Since disk4 is currently being emulated running it on /dev/md4 won't touch the actual SSD, but it won't enable the device, just fix the filesystem on the emulated disk, but because of parity it will allow you to access the data there.
  8. JorgeB
    There's always some overhead, but yes a PCIe 2.0 HBA would be enough for 8 HDDs, you can see some real world number here:
  9. JorgeB
    Not sure what you mean, latest Unraid release uses Samba 4.17.2 which is the latest Samba release currently available.
  10. JorgeB
    It was already disabled at boot, i.e., it got disabled before the update, but since SMART looks fine you can just re-enable the disk and re-sync parity, might also be a good idea to replace/swap cables before to rule them out if it happens again to the same disk. https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
  11. JorgeB
    Zeroing the log is IMHO your best bet but since the SSD is also being emulated you can repair that filesystem instead if you want and leave the original device untouched: -start the array in maintenance mode and type xfs_repair -vL /dev/md4 -when done stop array -start array in normal mode and the emulated disk4 should now mount, check contents
  12. JorgeB
    Then mount the SSD with UD, don't add it back to the array or it will be rebuilt on top.
  13. JorgeB
    Click the force log zeroing option, it's the only option when the log cannot be cleared with a mount, and while there's a chance of some data loss it's the only option, and usually most data is recoverable.
  14. JorgeB
    Like mentioned it will only work if you boot CSM, not UEFI.
  15. JorgeB
    Log is filled with the mover logging, but not seeing anything else of concern, reboot and post new diags after array start.
  16. JorgeB
    They were also always the same sectors. Mostly likely, looks like a controller problem.
  17. JorgeB
    Known issue with v6.11.2, update to v6.11.3
  18. JorgeB
    It's an option in the Unraid boot menu, must boot CSM.
  19. JorgeB
    Start by running memtest.
  20. JorgeB
    Look for a BIOS update, you could also try adding: split_lock_detect=off to syslinux boot options and see if it helps.
  21. JorgeB

    css bug

    JorgeB commented on zhangzhen's report in Stable Releases

    Changed Status to Closed Changed Priority to Other
  22. JorgeB
    Changed Status to Closed Changed Priority to Other
  23. JorgeB
    That's not a bug:
  24. JorgeB
    You have to download the permanent syslog from where you chose to save it, or if you enabled the mirror to flash option it will be in the flash drive, logs folder.
  25. JorgeB
    Diags are just after rebooting, enable the syslog server and post that after the problem occurs, would also recommended updating to latest stable first.
×
×
  • Create New...