Jump to content

JorgeB

Moderators
  • Posts

    67,416
  • Joined

  • Last visited

  • Days Won

    705

Everything posted by JorgeB

  1. Any data rebuilt after the second disk failed will be corrupt, but if you do a new config you can re-enable both disks, parity will need re-syncing.
  2. You should wait a few more hours, if the disk as slow sectors, and very likely there are some due to the very high number of raw_read_errors, it can take much longer than a healthy disk, SMART test should never get stuck, it either completes or aborts with an error.
  3. IIRC autostart currently only works after first array start, like after a reboot.
  4. Cache filesystem is corrupt, likely from an unclean shutdown, see here for some recovery options.
  5. That's not a problem, but IIRC this is: Formatted with type 2 protection 8 bytes of protection information per logical block If you google that you you'll find how to remove it.
  6. Changed Status to Closed Changed Priority to Other
  7. Please start a thread in the general support forum and include the diagnostics, you can get them by typing "diagnostics" on the console.
  8. No, but a single flash drive assigned as a data device is enough to qualify.
  9. Most likely a connection issue, recommend replacing cables (or swapping with another disk) to rule them out, this way if it happens again to the same disk it's likely a disk problem, despite the healthy SMART.
  10. You could try reformatting that one first, if still issues then replace. Yep
  11. Changed Status to Closed Changed Priority to Other
  12. This looks more like a general support issue, diags are after a reboot so not much help, see here to enable the syslog server then please start a thread on the general support forum and attach the diags and the saved syslog.
  13. All 6 ports are set to AHCI, you appear to be having flash drive issues: Mar 27 10:12:21 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 27 10:12:21 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Mar 27 10:12:21 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Mar 27 10:12:21 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 01 dd 14 20 00 00 01 00 Mar 27 10:12:21 Tower kernel: print_req_error: critical medium error, dev sda, sector 31265824
  14. After booting to Unraid go to Tools -> Diagnostics and attach the zip.
  15. Set them as SATA as post diags after boot.
  16. It is, if it sill happens with new cables (assuming you also replaced power cables) it could be a compatibility issue with board, though it would be strange one, since the Intel ports are usually problem free.
  17. Copying with the same device as source and dest will never give you optimal speeds, and never max speed.
  18. Unfortunately disk8 also appears to be failing, stop the rebuild and run an extended SMART test, take the opportunity and do the same for disks 10, 14 and 19.
  19. Not normal, but also not that unexpected, post new diags.
  20. rsync isn't built for speed, try the same copy with pv
  21. The usual way is freeing up one of the largest drives first, format to xfs, move data from the next largest drive to that one, format the now empty drive and so on.
  22. These chipsets have a separate BIOS setting for SATA ports 5/6, set them to AHCI, they have known issues in IDE mode.
  23. Disk8 dropped offline, looks more like a connection problem, cancel rebuild, replace cables on disk8 and try again. P.S. there were also a few read errors on disk19, and that looks like an actual disk problem, if it happens again the rebuilt disk can have some corruption.
×
×
  • Create New...