Jump to content

JorgeB

Moderators
  • Posts

    63,929
  • Joined

  • Last visited

  • Days Won

    675

Everything posted by JorgeB

  1. Yes. Dell/IBM need to be crossflashed, it's not difficult but it can be harder than a normal flash, still since that one is already pre-flashed it will be plug'n play.
  2. Yes, there are a lot of fakes on the internet, unfortunately a missing logo is not a way to tell, most fakes have the LSI logo, LSI makes OEM versions without the logo, I do usually recommend buying used server pulls instead of new ones from China, I prefer an used genuine over a new fake any day.
  3. Yes, it might need to be flashed to IT mode, but it's easy, like a bios update. It should work with most, can't say it will work with all
  4. For that board I recommend you install the IPMI plugin for fan control
  5. That's a SAS expander, still need an HBA to connect to it.
  6. There's no specific limit, depends mostly on the disk size and number of files, the more small files the worse.
  7. Yes for reiserfs disks, though performance can degrade even before that, not important for xfs or btrfs, but you'll want to leave always a few GB free.
  8. Likely the 3.3v issue, e.g., second post down from yours: https://forums.lime-technology.com/topic/62304-issues-reading-some-disks-on-flashed-lsi/
  9. Another possibility is that some drives harvested from external enclosures can be slightly smaller.
  10. No it shouldn't, but I also believe the script is not working correctly with latest unRAID, if you want to do that best to do it manually, see here: https://forums.lime-technology.com/topic/61614-shrink-array-question/?tab=comments#comment-606335
  11. Preclear partitions the disk, it's part of the signature for the disk to be considered clear, maybe there's an issue with such a large disk, you can clear the disk in unRAID
  12. You could try re-flashing the controller without a bios, bios is only needed if you need to boot from a device on the HBA.
  13. You're right, I meant the disk status is invalid, not disabled, but without parity the disk can't be emulated, so kind of a bug, but like I said the array is in an unusual state.
  14. OK, I think I understand now, disk3 is invalid (yellow) not emulated (red), array is in an unusual state but as long as data on disk3 looks correct if you start the array as is, without parity, you can do a new config, retain all and start the array, you can later (or now) add a new parity drive, but keep old disk3 intact in case anything goes wrong.
  15. You can use the replace cache procedure and format xfs instead of replace: https://forums.lime-technology.com/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923
  16. New config will lose any emulated disk, but didn't you un-assign parity? How do you have an emulated disk? You can also post current diags so I can see.
  17. Btrfs filesystem is fully allocated and needs to be rebalanced, see here: https://forums.lime-technology.com/topic/54533-624-cache-drive-reporting-quotno-space-left-on-diskquot/#comment-532931
  18. You can also see the difference form the previous diags:
  19. Yeah, parity drive looks bad, no pending sectors but these are bad signs: 1 Raw_Read_Error_Rate 0x000b 053 053 --- Pre-fail Always - 922755730 22 Helium_Level 0x0023 076 076 --- Pre-fail Always - 76 Raw Read Error rate should be zero on an healthy drive, and it's leaking helium, never seen a helium drive where this value wasn't 100.
  20. Grab and post new diags after the errors.
  21. You should cancel and reboot in safe mode, the start another check, you have syncthing and crashplan running and crashplan is using a lot of CPU.
  22. You could remount the array disks read-only, would still be able to wite to those shares if set to cache "yes", though you'd need to remount read/write before the mover ran.
  23. It looks to be resolved, I've disabled my weekly balance and so far so good, but I'd like to wait a few more weeks before saying it's fixed for sure.
×
×
  • Create New...