Jump to content

JorgeB

Moderators
  • Posts

    67,125
  • Joined

  • Last visited

  • Days Won

    703

Everything posted by JorgeB

  1. Vdisks are already being detected as thin provisioned devices, so that part is OK, don't know why optimization is not available, but you can "resparsify" the large vdisks for now, and unmap should keep smaller for the future, to resparsify (with VMs shutdown): cp --sparse=always original.vdisk new.vdisk Then delete the original and rename new one to old name.
  2. Not necessarily, one of the cache devices might just be out of syn, run a scrub and make sure there are no uncorrectable errors, you should also post the diagnostics.
  3. According to google it's reverse breakout, the wrong cable:
  4. Are you using the right cables? Forward breakout and reverse breakout look exactly the same, only forward breakout will work in this case.
  5. Couple of those are FreeNAS servers, but yeah, almost have a full card 😋
  6. Yep, I tested on one of mine, and as you can see I'd really like it to work 😛: AFAIK these boards only accept these commands: ipmitool raw 0x30 0x45 0x00 Gets the mode 0/1/2/4 Standard/Full/Optimal/Heavy IO ipmitool raw 0x30 0x45 0x01 0x00 Sets the mode to Standard ipmitool raw 0x30 0x45 0x01 0x01 Sets the mode to Full ipmitool raw 0x30 0x45 0x01 0x02 Sets the mode to Optimal ipmitool raw 0x30 0x45 0x01 0x04 Sets the mode to Heavy IO (not available on these boards)
  7. These boards only support standard, full or optimal speed settings, looks like mostly dual socket models from this series, X9Dxx, support fine adjustment.
  8. For these type of errors better to backup the cache, format and restore data.
  9. Yes, click on it and on SMART settings unselect attribute 197
  10. What you did was a more complicated way of running a balance, likely you didn't use the correct command, but as long as it worked...
  11. Yep, don't know why, never seen this before but it looks like a bug. With the array stopped click on cache and change filesytem to btrfs.
  12. You'll still need to format them, if format fails after wiping post the diagnostics.
  13. clear both devices with: blkdiscard /dev/sdX
  14. Yes, performs similar to other software/fakeraid raid implementations.
  15. Yes, Unraid doesn't support most RAID controllers, and definitely not "fake" RAID like Intel RST or similar, you can use a btrfs pool and change the profile to raid0: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480421
  16. You can use this, there are some limitations but it works: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=462135
  17. NIC is found but driver isn't loading: Nov 1 17:41:50 Tower kernel: mlx4_core 0000:09:00.0: command 0xff6 failed: fw status = 0xb Nov 1 17:41:50 Tower kernel: mlx4_core 0000:09:00.0: RUN_FW command failed, aborting Nov 1 17:41:50 Tower kernel: mlx4_core 0000:09:00.0: Failed to start FW, aborting Nov 1 17:41:50 Tower kernel: mlx4_core 0000:09:00.0: Failed to init fw, aborting. ... Nov 1 17:41:50 Tower kernel: mlx4_core: probe of 0000:09:00.0 failed with error -14 Bad NIC? Or possibly some incompatibility with the board/slot, you can try googling the error.
  18. This shouldn't be a problem, please post your diagnostics, maybe something visible there: Tools -> Diagnostics
  19. You can still get similar performance to a mirror if you enable turbo write.
  20. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480420
  21. No. It's the same fstrim command.
×
×
  • Create New...