Jump to content

JorgeB

Moderators
  • Posts

    63,550
  • Joined

  • Last visited

  • Days Won

    674

Everything posted by JorgeB

  1. No, current cache needs to be btrfs like it says on the notes. Yes, unless something goes wrong, that's way it's always good to backup any important data. Yes.
  2. Those are hardware errors and a general support problem, not a bug report, use the Nerdpack plugin to install mcelog, it may give some more info.
  3. https://lime-technology.com/forums/topic/46802-faq-for-unraid-v6/?do=findComment&comment=545988
  4. When a share is created it creates the folder on the first disk configured for that share, did you delete it?
  5. I believe so but I never had to update mine, as it was already 2.something, also I believe you need an HP controller to do the update.
  6. No such limit when crossflashed to LSI IT mode, LSI firmware limit is 256 non raid devices.
  7. Correct, use the 2 Intel SATA3 ports for the SSDs, SATA2 is enough for HDDs.
  8. No, those are the SCU ports, Marvell ports are the first 4 white ports 18-21
  9. It's a 5 bay external SAS enclosure with a built in expander.
  10. Yep, no problem, I have one on a server connected to 9 internal disks plus 5 external, and it's good for 150MB/s+
  11. Yes. It's SAS2 but unlike most SAS2 expanders it's SATA2 max, not SATA3 (and it requires a certain firmware, IIRC 1.80+), so half the total bandwidth of a SATA3 expander, 1100MB/s for single link, twice that for dual link.
  12. That's a flash drive problem, if using an USB 3.0 port try a 2.0, it can also be a failing flash drive.
  13. Depending on the disks used it can be a bottleneck on a PCIe 2.0 HBA, but not a significant one.
  14. I don't know of any 16i based on the SAS2308 chipset, there is a 16e, the 9206-16e, there are SAS3008 based 16i HBAs, but these are SAS3 so more expensive.
  15. A clean shutdown wouldn't create diags, they are only created unRAID coudn't do a clean shutdown after the set timeout.
  16. What unRAID version are you running? Try typing on the console: btrfs balance start -dconvert=raid0 -mconvert=raid1 /mnt/cache
  17. I'm seeing the same using the SASLP, looks like some issue with diskspeed and this specific controller, real world bandwidth of the SASLP is around 640MB/s, so just divide that by the number of disks you have connected and it will be max speed during check/rebuild.
  18. I don't see any attempt to format the cache pool, can you do that and post new diags if format fails.
  19. The only plausible explanation I can think of would be that the parity disk got disable on shutdown during array stop and there was no time for notifications to go out, because the array won't autostart with any missing disk (including parity) and you definitely get a notification if it gets disabled during normal use, in fact you usually get 2 notifications, one about array errors and another about the disabled disk.
×
×
  • Create New...