Jump to content

JorgeB

Moderators
  • Posts

    67,808
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Any shares will show unprotected if they are in a single device cache or if parity doesn't exist or is not valid.
  2. That's expected, damage is done, try the recovery options then reformat.
  3. Enable the syslog server and post that after a crash.
  4. You just need to check if it's using the latest firmware, if not update:
  5. @Pluvichorsplit your post here since this isn't really about unclean shutdowns. There are errors on disks 1 and 2 immediately after array start, probably not coincidental that both disks are of the same model, first thing to try is to update the LSI firmware to latest, the one you're using has known issues, if that doesn't help try connecting those two disks to a different controller, you can swap with another two.
  6. Two controllers have (or are connected to) SATA port multipliers, that's very bad for performance and reliability, lots of ATA errors on the log.
  7. It's possible but the GUI only supports replacing devices from redundant pools, you could do it manually though.
  8. 2GB *should* be OK just for basic NAS, it won't hurt to try, and if it's not stable add more RAM.
  9. Looks more like a board/BIOS issue, you could try disconnecting any external devices, especially USB devices except the flash drive, to see if it makes any difference.
  10. No, but since the above procedure deletes that file it should fix it.
  11. Do the recover password procedure, should fix that: https://wiki.unraid.net/Manual/Troubleshooting#Lost_root_Password
  12. That's not possible, Unraid requires a specific partition layout and signature, you can mount the disk with UD plugin and copy the data to another disk(s) on the array.
  13. A redundant pool, similar to parity in this case, provides redundancy for a failed device, not for filesystem corruption.
  14. Filesystem corruption again and so soon after a format might indicate a hardware issue. Try with another device if you have one, pools won't help with filesystem corruption.
  15. Several crashes, start by running memtest, first crash mentions cifs, so could also be SMB related: Jul 13 09:06:59 MyUnraid kernel: cifs_filldir.constprop.0+0x3ac/0x4fd [cifs] Jul 13 09:06:59 MyUnraid kernel: cifs_readdir+0x5c7/0x639 [cifs]
  16. Parity drives have to be same or larger size than the largest data drive, so yes it can be 14TB.
  17. Pleas post the diagnostics, if you cannot access the GUI you can type diagnostics on the console.
  18. Which Unraid release are you running?
  19. Most likely this issue: https://forums.unraid.net/topic/40699-solved-irregular-speed-during-parity-check-sync-or-disk-rebuild/?do=findComment&comment=452618 Also note that the controller you are using has a SATA port multiplier and because of that it's not recommended.
  20. See if this about Ryzen servers helps: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
×
×
  • Create New...