• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by itimpi

  1. The only way to do this will be to use Tools -> New Config. I would suggest that you start by using the option to retail current configuration and then return to the main tab to make the required changes. If you think parity is valid then you can tick the "parity is Valid" option to avoid an immediate parity rebuild, but if you do so I would recommend doing a parity check afterwards to make sure. The existing data drives will be left with their data unchanged, but keep the old drives intact until you are back up and running to keep a recovery option available.
  2. Yes - that is required to be able to boot in UEFI mode.
  3. Do you have single or dual parity? I am guessing single parity? UnRaid can never recover more drives than you have parity drives and with single parity if both a data drive and the parity drive missing the standard recovery will not work. Why did you remove these drives in the first place? If you give more background we are more likely to be able to help. It the drive are still physically connected to the unRaid server then posting your systems diagnostics zip file (obtained via Tools->Diagnostics) to your NEXT post will at least allow us to see the SMART information for the
  4. Just copy the pro .key file into the ‘config’ folder on the flash drive. As long as it is the one that corresponds to the flash drive that is all that is required.
  5. You cannot add a parity disk and another data drive at the same time. You should be OK if you do this in 2csteps.
  6. Do you have the USB stick set up to support UEFI boot (I.e. no trailing ‘~’ on the EFI folder)? I have seen the symptoms you describe on some newer systems unless you boot in UEFI mode.
  7. What happens when you try? you should provide your system’s diagnostics zip file (obtained via Tools -> Diagnostics) taken after attempting to add a disk attached to your next post if you want any sort of informed feedback
  8. You cannot do what you want as simply as you would like do you have Single or Dual parity? With single parity there is a way to achieve what you want while maintaining parity protection as the slot number is not part of the calculations for parity1. With dual parity it is not as easy as for parity2 the disk slot number is part of the parity calculation. regardless - I assume you have backups of this important data as parity is no substitute for a backup.
  9. Have you turned on mover logging to confirm what files are trying to be be moved? looking at the diagnostics I would expect the system to be trying to move appdata files from disk2 to the cache as there is space on it and that share is set to “use Cache = Prefer”.
  10. The sdX identifiers are not relevant to unRaid as it identifies disks by serial number (and the sdX designation is allocated dynamically and can change between boots). The only time it matters is if the disk drops offline after boot and then comes back with a different sdX designation as that scenario is not handled by unRaid.
  11. Chances are that the way you are selecting to move the files is creating the folders before moving their contents. The Split Level settings you have then force the content to the drive where the folders have been created.
  12. The way I would suggest to proceed that minimizes downtime is: Make a note of the serial numbers of the existing 4TB parity drives (just in case you need them later) Use tools -> New Config and select the option to keep data and cache assignments Assign the new 12TB parity and data drives (keeping the old 4TB parity drives unassigned at this point) Start the array to start to build new parity on the 12TB parity drives based on the drives currently assigned. The new 12TB data drives will show as unmountable and need formatting before they can be used to store
  13. It is probably worth pointing out than when you select a setting the text alongside this setting changes to tell you what action mover will take. This means you can tell without having to activate the help.
  14. @S80_UK Just thought I would let you know that your last set of feedback has allowed me to identify a point where I do not handle pause correctly for manual checks. It appears that the last update fixed the problem about the plugin getting confused about how the check was started but left behind a bug on acting correctly on this information for manual checks under some conditions.
  15. There is no SMART information for disk3 or disk4 in the diagnostics so I suspect that they have dropped offline and a power-cycle may be required to get them back online. Might be worth waiting to see if @JorgeB has a view as the expert in these matters.
  16. This will NOT be the cause of the problem as a parity check does not use any of your free space. Hopefully the diagnostics will provide a clue.
  17. A usb stick I have used successfully is the Kingston Data Traveller SE9. I think the larger size and metallic body help it run cooler and thus are better for use 24x7. Note that USB2 drives seem to be the most reliable for use with unRaid and since the USB drive has very little access after initial load of unRaid into RAM at boot time the extra performance of USB3+ is not needed.
  18. Your syslog seems to be full of error messages related to disk8 and suggesting you run a file system check/repair.
  19. What release are you upgrading from? note that the nvidia plugin that worked with Unraid 6.8.3 and used a custom build is not the same as the Nvidia Driver plugin used with 6.9.0 and does not need a custom build.
  20. You cannot get a USB stick un-blacklisted. If what you describe is accurate then the update would use the latest blacklist which explains your issue as transferring the licence to a new drive blacklists the old one. What happened to the USB drive you think you transferred the licence to? Do you have a copy of the licence .key file that went with that drive?
  21. You should include your system’s diagnostics zip file (obtained via Tools -> Diagnostics) attached to your next post if you want any sort of informed feedback rather than guesses.
  22. Have you actually tried plugging the Ethernet cable into the onboard NIC? It would not have worked with 6.8.3 which did not have a driver for it but 6.9.0 release does have the driver so it is likely that is the card that unRaid is currently trying to use. UnRaid will always use the NIC that is configured as eth0 for accessing the GUI. It is possible from the GUI to change which card is treated as eth0 if you want to force a specific card to be used as eth0.
  23. you should include a copy of your system’s diagnostics zip file (obtained via Tools->Diagnostics) attached to your next post to get any sort of informed feedback. Also turning on mover logging may give a clue.
  24. in the 6.9.0 release if you click on a cache pool and then go to the Balance section there is a drop-down to allow you to select what profile you want the Balance to use with the option being current profile, single, raid0 or raid1 profiles.
  25. That is a browser issue that is typically fixed by clearing the browser’s cache.