Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,485

  • Joined

  • Last visited

  • Days Won

    706

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    OP mentioned 8TB NVMe devices, that should be enough for the weekend backup, or a multi-SSD cache pool, I have a 6TB usable SSD pool that I use for day to day data, so it's always fast, array is just for cold storage.
  2. JorgeB
    When possible I recommend buying from a known brand, e.g. I have one of these and it works great, but I also got one of these (no brand) and it's also working fine.
  3. JorgeB
    Looks more like a cable problem, check/replace/swap cables and if data looks correct in the emulated disk rebuild on top, if you don't replace the SATA cable monitor for more CRC_UDMA errors, if it keeps increasing there's still a problem.
  4. JorgeB
    Those values are normal for Seagate drives, more info here.
  5. JorgeB
    I suspect that it might be the problem, PMC controllers are very rarely used in general and with Unraid specifically, also the driver is likely not as mature and well tested as the LSI one with Linux. That would be a good option.
  6. JorgeB
    This is usually a flash drive problem try another one or re-create it manually following this: Backup your flash drive then open a command prompt window as administrator, then type, in this order: -diskpart -list disk -select disk x (x=your flash drive) -clean -create partition primary -format fs=fat32 label=UNRAID quick -active -assign -exit -close cmd window -Unzip Unraid release to flash drive and restore the config folder from the flash backup -execute make_bootable as admin
  7. JorgeB
    NetApp controller uses a PMC Sierra chip, and IIRC I've seen issues with those and Unraid before, if possible get an LSI HBA instead, though you'll to get need a different cable.
  8. JorgeB
    Best bet is to ask on the UD plugin support thread.
  9. JorgeB
    Next time please upload the single diagnostics.zip, much easier for us to check. Missed in the earlier post before (mostly because it's not so easy to read when not posted inside code tags) that parity as a FAILING NOW SMART attribute: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 184 End-to-End_Error -O--CK 097 097 099 NOW 3 So it needs to be replaced.
  10. JorgeB
    See: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
  11. JorgeB
    SAS spinners won't make much if any difference, maybe if you use 15krpm devices, SSDs or NVMe devices yes, I have an SSD pool thant can sustain writes of about 800MB/s, same for single device NVMe cache, but note that if your data is mostly small files it will likely be slower, but still faster than spinners.
  12. JorgeB
    On the SMART report. Yep, some stick, others not.
  13. JorgeB
    Yes, total length from HBA to disks.
  14. JorgeB
    You can use any other Linux distro or use a trial license.
  15. JorgeB
    You can copy over lan from the old server.
  16. JorgeB
    Writeback Cache is: Disabled Don't remember the command for SAS drives, but you should find it by searching the forum or googling it.
  17. JorgeB
    Make sure it's not set to never spin down and try re-applying the general or that drive's spin down setting.
  18. JorgeB
    If you believe the drive is good you can do a new config but must keep a few things in mind: if it's really a disk problem you'll lose the ability to rebuild it, you should make sure the disk is at least mounting correctly before doing the new config (you can use UD for that), you'll lose any data written to that disk (the emulated disk) once it got disabled and you'll need to re-sync parity or if the "parity is already valid" was checked you need to do a correcting check since a few sync errors are expected.
  19. JorgeB
    You can move from the old drives mounted with UD to a user share on the new array.
  20. JorgeB
    Copying smaller files is always slower, even from SSD to SSD, but spinners will be even slower.
  21. JorgeB
    Should be fine, but if you're going to use it with SATA drives don't forget the max cable length is 1 meter, since it doesn't have an expander.
  22. JorgeB
    Check filesystem on disk3, but note that a new config is not usually the right thing to after a disk drops, and you now need to run a correcting check.
  23. JorgeB
    Docker image is corrupt, delete and re-create, also due to a previous bug your cache pool is not redundant, see here.
  24. JorgeB
    If the extended SMART test passes the parity check should also complete without read errors.
  25. JorgeB
    That suggests there could be a real problem with the NVMe device, try the copy again, if you get the same errors probably not much more you can do, you can try reformatting the device but any more similar errors probably best to replace it.
×
×
  • Create New...