Jump to content

itimpi

Moderators
  • Posts

    20,789
  • Joined

  • Last visited

  • Days Won

    57

Everything posted by itimpi

  1. Not clear what you mean by a mount point? If you mean the sdX type device names then these are irrelevant as Unraid does not rely on them and anyway they can change between boots.
  2. It is risk v time balance. Doing them at the same time is faster, but doing them individually means your array remains protected against another drive failing during the process.
  3. Maybe it is an issue that is specific to ZFS pools then?
  4. I have just checked on my system and a share that has files on a redundant btrfs pool DOES show as green. What file system were you using on the pool you showed?
  5. Are you sure about this? I thought they were only orange in non-redundant pools.
  6. This sounds like you might have a motherboard problem?
  7. Do you have the EFI folder on the flash drive with no trailing additional character? That is required if you want UEFI booting to work.
  8. The sdX designations are not relevant to Unraid. In fact it is possible (although rare) for them to change after reboots without making any changes at the hardware level as they are assigned dynamically by Linux as it recognises drives coming online.
  9. The only reason one would expect to need to reassign drives is when the disk controllers they are connected to present the disk size or serial numbers differently.
  10. You should not need to reassign them as Unraid recognises drives by their serial number rather than by where they are connected.
  11. The same page that has the USB Creator tool for download also has the links to download the zip files for the latest Unraid releases that can be used with the manual install method.
  12. Those indicate corruption has been happening on the flash drive.
  13. The syslog seems to show the eth1 connection going up and down frequently. Have you tried changing the network settings so that eth0 is not bonded with eth1 to see if that helps?
  14. Are you sure that is the syslog produced by the syslog server? I would expect that to have entries from before the last reboot. It looks more like the standard syslog from RAM.
  15. You might want to consider installing the Parity Check Tuning plugin? This way although the elapsed time would be longer you could perhaps avoid the check running during prime time when you are likely to actually want to use the server. As was mentioned adding a second parity drive is quite likely to have no measurable effect on the party check speed but the only way to be certain is to try. You can always change your mind later if you decide the second parity drive slows things down too much.
  16. Do you have the Cache Dirs plugin installed? That will issue regular find commands to try and keep directory information cached in RAM.
  17. You might want to try enabling the syslog server (probably using the Mirror to flash option) and post the file that produces after the issue occurs so we can see if anything was logged leading up to the problem.
  18. Quite likely then. Have you tried power-cycling the server to see if that brings it online?
  19. Do you have 1 or 2 power connectors attached? You may well need 2 (ideally from different PSU leads) to get reliable operation.
  20. Do you have a docker container set up to use those ports?
  21. In either case when you start the array in normal mode then disk6 should be emulated and you can see if the emulated disk6 mounts OK, and if so you can rebuild is contents to another drive. You might want to post new diagnostics after starting the array in normal mode. The fact that the current disk6 failed the extended SMART test means it should be replaced.
  22. Is your system trying to boot in UEFI mode? If so make sure the ‘EFI’ folder on the flash dtive does not have a trailing character - if so remove it as the folder name needs to be exactly ‘EFI’ for UEFI boot.
  23. Data should be OK as you are using a file system that has built-in checksumming. The system does NOT avoid using those sectors because the drive should have reallocated them to use a good sector so it is transparent to the host.
  24. That syslog snippet look like what we normally see if there is a cabling or power issue with the dtive.
  25. I would not be happy with reallocated sectors on a new drive, particularly if the number keeps increasing. It would be worth checking if the fact they keep increasing is enough to get a RMA.
×
×
  • Create New...