Jump to content

JorgeB

Moderators
  • Posts

    67,415
  • Joined

  • Last visited

  • Days Won

    705

Everything posted by JorgeB

  1. That looks like a connection issue, check/replace cables on disk3.
  2. Either way you'll need to check the data on disk12, so whatever you prefer. Extended test takes several hours (2 to 3 hours per TB) and sometime can appear stuck.
  3. It can't hurt, though don't remember seeing any issues with current one.
  4. Did you reset the stats after replacing the cables? How to is in the link above.
  5. There's a recent extended SMART test and it passed, run a another one if still OK disk should be fine.
  6. Seems like a plan, if you still have old disk12 you can run a checksum compare between both, with for example rsync. Would also recommend converting all reiserfs disks, it's not recommended for some time now.
  7. Disk sdd dropped offline and reconnected as sde now, check/replace cables and try again. Next time please post the complete diagnostics, much more info, including SMART reports.
  8. There were read errors on disk13 duding the rebuild, which means disk12 is partiality corrupt. Any special reason for being on such an old release? Those diags are not so complete as the latest ones, and not so easy to say if it was a disk problem or not, but from what I can see disk look OK.
  9. Disk1 is completely empty, did you at any point (before or after the rebuild) press format?
  10. Download the latest firmware package from Broadcom's support site then boot with a DOS flash drive and follow the instructions included with the package.
  11. It's not an fs corruption problem, why I asked for diags after array start: Mar 26 09:53:38 unRAID root: mount: /mnt/disk1: unknown filesystem type 'xfs'. This happened one time before, it's like xfs is not installed, don't remember exactly what the problem was, but probably a corrupt Unraid install, take the opportunity to upgrade to v6.8.3 and reboot.
  12. Then dual parity isn't the reason for the slower performance, assuming the parity2 disk is working correctly, most likely it's copying small files or from a slower disk region.
  13. No, write performance should be the same, unless using a very old single core CPU.
  14. No expander, but you can use a single 16 port HBA, e.g.: LSI 9201-16i or 9305-16i
  15. What backplane? Does it have a SAS expander? If it's an expander backplane you can connect 1 or 2 miniSAS cables from the HBA to access all slots, if not you need 1 miniSAS cable for every 4 disks, but there are controllers that support 16 (or more) devices.
  16. Onboard SATA ports are usually good enough, but there are several Ryzen users that have issues with the onboard SATA controller where it stops responding, mostly if IOMMU is enable, you can try them and if there are issues use the HBA.
  17. Server shutting down is almost certainly a hardware issue, start by checking temps, if those are OK try a new PSU, also make sure to check this.
  18. If that's during boot like this thread is about redo your flash drive.
  19. It would be better to post diags after starting the array, but first check filesystem on disk1, post new diags if it doesn't help. https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui That's expected, replacing a disk won't fix filesystem corruption.
  20. Just did last night on one my servers, it killed a VM, going to lower allocated RAM for all VMs to see if having some more free RAM is enough, I have another server running it without VMs/dockers and no issue on that one.
  21. Not without the diagnostics, please start a thread on the general support forum and add the diags after a failed copy.
×
×
  • Create New...