Jump to content
We're Hiring! Full Stack Developer ×

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    64,060

  • Joined

  • Last visited

  • Days Won

    676

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    No, those are the SCU ports, Marvell ports are the first 4 white ports 18-21
  2. JorgeB
    It's a 5 bay external SAS enclosure with a built in expander.
  3. JorgeB
    Yep, no problem, I have one on a server connected to 9 internal disks plus 5 external, and it's good for 150MB/s+
  4. JorgeB
    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.
  5. JorgeB
    Yes. There's no 2TB limit.
  6. JorgeB
    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.
  7. JorgeB
    A clean shutdown wouldn't create diags, they are only created unRAID coudn't do a clean shutdown after the set timeout.
  8. JorgeB
    ?
  9. JorgeB
    Post your diagnostics.
  10. JorgeB
    What unRAID version are you running? Try typing on the console: btrfs balance start -dconvert=raid0 -mconvert=raid1 /mnt/cache
  11. JorgeB
    Yes.
  12. JorgeB
    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.
  13. JorgeB
    I don't see any attempt to format the cache pool, can you do that and post new diags if format fails.
  14. JorgeB
    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.
  15. JorgeB
    Please post your diagnostics: Tools -> Diagnostics
  16. JorgeB
    If system notifications are enable you should have received a warning, your parity disk is not being detected, check connections and disk.
  17. JorgeB
    I never had SAS drives, and this issue only came up once or twice here in the forums, see below if you can find anything, if not you'll need to google it: https://forums.servethehome.com/index.php?threads/how-to-reformat-hdd-ssd-to-512b-sector-size.4968/
  18. JorgeB
    You can easily add it to unRAID, create a folder called extra on your flash drive, copy sg3_utils there, reboot and presto.
  19. JorgeB
    Just an FYI that's this last forum update didn't fix this, still happening.
  20. JorgeB
    https://lime-technology.com/forums/topic/46802-faq-for-unraid-v6/?do=findComment&comment=462135
  21. JorgeB
  22. JorgeB
    Some SAS drives have several adjustable sector sizes, you need to change it to 512 bytes.
  23. JorgeB
    Yes, unmount first then you can disconnect all, and only mount again when all are connected.
  24. JorgeB
    https://lime-technology.com/forums/topic/46802-faq-for-unraid-v6/?do=findComment&comment=462135
  25. JorgeB
    indeed
×
×
  • Create New...