Jump to content

JorgeB

Moderators
  • Posts

    67,492
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. Would need the diags to confirm but based on the screenshot the disk is likely being detected with a small capacity difference, and if that's the case this would be a controller issue.
  2. These errors sometimes happen with some hardware, no one knows exactly why, unfortunately can't suggest anything other than trying different flash drives and/or a different board.
  3. The SAS expander shouldn't cause this, as it's a model widely used with Unraid, including by myself, though it could be the expander + those specific disks.
  4. Impossible to know without the previous diags showing everything what happened before the check, you did do a new config, so some (or a lot) of sync errors can happen, depending on the array status before.
  5. Log is completely spammed with errors from an external 4TB disk, can't see anything else, disconnect that disk, reboot and post new diags if/when there are more issues. That is the docker image.
  6. Unfortunately there's nothing in the log that gives a clue about the crash, it could be a hardware issue.
  7. 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.
  8. 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.
  9. 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.
  10. Those values are normal for Seagate drives, more info here.
  11. 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.
  12. 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
  13. 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.
  14. 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.
  15. See: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
  16. 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.
  17. You can use any other Linux distro or use a trial license.
  18. Writeback Cache is: Disabled Don't remember the command for SAS drives, but you should find it by searching the forum or googling it.
  19. Make sure it's not set to never spin down and try re-applying the general or that drive's spin down setting.
  20. 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.
×
×
  • Create New...