Jump to content

JorgeB

Moderators
  • Posts

    67,539
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Onboard SATA is set to IDE, change it to AHCI. Also, the LSI firmware needs to be updated: mpt2sas_cm0: LSISAS2008: FWVersion(20.00.04.00) All p20 releases before 20.00.07.00 have known issues. If still slow after please post new diags.
  2. You still need to rebuild, or do a new config and re-sync parity.
  3. I would say this is the most likely, if it does the same with a new flash.
  4. Like mentioned those it's an SMR drive, Seagate SMR drives usually perform OK with Unraid but that particular model has had other bad performance reports before.
  5. Procedure appears to have been correctly done but don't see a valid filesystem on disk4, this likely means parity wasn't valid, at least not 100% valid, still try running xfs_repair on the disk, maybe it will find a backup superblock.
  6. I would repair the fs first since that should be quick and make data on that disk available now, then rebuild, but either way you do it shouldn't be more or less risky.
  7. Tested also at work with different computers and it does appear to be fixed, but it was recent, v6.9-beta1 still has the issue, you get an i/o error about once every 10 times but just retry and it happily continues to copy the corrupt file. Also, have some doubts if this was really fixed or is just pure luck that it works correctly currently, I can't find any reference to this bug, when I google the only result I get is my original report here in the forum, but maybe I'm using the wrong keywords, not even sure this was a btrfs issue or Samba, I would assume Samba.
  8. Yes, I was referring to the docker image path, though it can also be easily recreated.
  9. All expect the disk assignments, everything else will use the defaults. You also need to copy the templates from the flash drive and configure the docker paths to be the same as they were, if not using default ones.
  10. It's not that healthy, in fact it appears to be failing, you can confirm by running an extended SMART test. You can do that now. Any LSI with a SAS2008/2308/3008/3408 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, 9400-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed.
  11. Try booting in safe mode, if that doesn't help you recretae the flash drive and restore only super.dat (disk assignments) and you key, if that helps then re-add the other config files a few at a time or just reconfigure the server.
  12. You added the old disk as a new disk, the easiest way now would be to get another disk to replace the disable drive.
  13. Try setting the DNS servers manually, or reset lan config by deleting/renaming network.cfg and network-rules.cfg (if it exists) both on the config folder of your flash.
  14. A few sync errors are normal, even expected after an unclean shutdown, just correct them.
  15. Please use the existing support thread:
  16. Default ISO storage path is invalid, go to Settings -> VM Manager and set a valid path.
  17. Disk7 looks healthy, but don't do a parity check and attempt to move data at the same time, do one or the other first.
  18. I can only see that they are logged as "medium errors", aka bad sectors, but these can sometimes be intermittent.
  19. Give it another chance but anymore errors recommend replacing.
  20. Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
×
×
  • Create New...