Jump to content

JorgeB

Moderators
  • Posts

    67,540
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Please post the diagnostics: Tools -> Diagnostics
  2. Replace SATA cable on disk6, go to BIOS and change the onboard SATA from IDE to AHCI, reboot, start array and post new diags.
  3. Plugin author has not posted or provided support for some time, made a note of that in the 1st post.
  4. Good idea to keep an up to date backup of libvirt.img.
  5. Yes, without counting parity devices.
  6. Run the diskspeed docker to check devices and controllers are performing normally.
  7. This was more about AV software, then best bet is to try a different PC or reformatting/new OS on that one.
  8. They are still being detected as 520B devices: Oct 25 12:07:29 Atheon kernel: sd 1:0:7:0: [sdi] Unsupported sector size 520. Oct 25 12:07:29 Atheon kernel: sd 1:0:6:0: [sdh] Mode Sense: b7 00 10 08 Oct 25 12:07:29 Atheon kernel: sd 1:0:7:0: [sdi] 0 512-byte logical blocks: (0 B/0 B) Oct 25 12:07:29 Atheon kernel: sd 1:0:7:0: [sdi] 520-byte physical blocks Oct 25 12:07:29 Atheon kernel: sd 1:0:7:0: [sdi] Write Protect is off Oct 25 12:07:29 Atheon kernel: sd 1:0:6:0: [sdh] Write cache: disabled, read cache: enabled, supports DPO and FUA Oct 25 12:07:29 Atheon kernel: sd 1:0:7:0: [sdi] Mode Sense: b7 00 10 08 Oct 25 12:07:29 Atheon kernel: sd 1:0:6:0: [sdh] Unsupported sector size 520. Oct 25 12:07:29 Atheon kernel: sd 1:0:7:0: [sdi] Write cache: disabled, read cache: enabled, supports DPO and FUA Oct 25 12:07:29 Atheon kernel: sd 1:0:6:0: [sdh] Attached SCSI disk Oct 25 12:07:29 Atheon kernel: sd 1:0:7:0: [sdi] Unsupported sector size 520. Did you reboot after?
  9. -beta25 to 30 shouldn't make much of a difference, you can also try the diskspeed docker to confirm all disks and controllers are performing normally.
  10. Limit for the array is 30 devices.
  11. Image transid suggest it's very new, possibly you have more than one, post output of: find /mnt -name libvirt.img
  12. Please post the diagnostics: Tools -> Diagnostics
  13. You can move the HBA on the 3rd slot to the bottom slot and use that one for the NIC.
  14. x4 PCIe 2.0 slot is still good for 2000MB/s (around 1600MB/s usable), so yes, it's enough, though note that the bottom one is shared with the DMI and anything using it, like the onboard SATA ports, if they are being used.
  15. cat /boot/config/share.cfg | grep shareCacheFloor
  16. That suggest a problem with PC NIC, cable or switch.
  17. mdcmd status | egrep "mdResync" It will display some values, including: mdResync=total parity size mdResyncPos=current position If it's still going.
  18. FYI log is filled with ATA errors, on multiple disks, and parity is disable, but for now try runing xfs_repair manually, start array in maintenance mode and post output of: xfs_repair -nv /dev/md6
  19. Never a good sign, but might be OK for now, assuming it's not new.
  20. Correct, if no partition exists, if it does first wipe with blkdiscard.
  21. There's no partition, but try this: wipefs -a /dev/sdb1 then wipefs - a /dev/sdb them try to format.
  22. Lots of nginx errors (also others but look unrelated), best bet is rebooting.
×
×
  • Create New...