Jump to content

JorgeB

Moderators
  • Posts

    67,406
  • Joined

  • Last visited

  • Days Won

    705

Everything posted by JorgeB

  1. No problem, I expect this to be fixed next release.
  2. Unlikely to be the controller, or multiple disks would have been affected, problem looks like a connection issue, though some times a healthy looking disk still has issues, hence why I recommended swapping cables, if the same disk fails again after that it's likely a disk problem.
  3. Since the pool was already converted it's not possible to maintain the old profile, that would only be possible if you hadn't started the array with a missing device.
  4. When adding an extra device two a single device pool it will always convert to raid1, you can then convert to raid0, after that it will stay raid0 even if you add more devices.
  5. If rebuilding to the same disk recommend replacing/swapping cables, just to rule them out if it happens again to the same disk.
  6. Do you mean raid1? Pool was converted to single profile because it was started with a single device, you can now add back the original device and it will be convert to raid1, but best to wipe old device before adding.
  7. Instead of: /boot/your.script use bash /boot/your.script
  8. No sorry, I don't use encryption, but just unassigning the cache devices is safe, you do need to have some attention when re-assigning them back, you first need to start the array without any device assigned to the pool to make Unraid "forget" current cache config, then stop array, reassign all cache devices and start array, there can never be a warning like "all data on this device will be delete at array start", existing pool will be imported.
  9. In that case I believe you can't use UD.
  10. You can now use the UD plugin for that.
  11. Backup config folder, recreate flash, restore config folder.
  12. Where are those folders? Those do not exist by default.
  13. Yes, they both should have the same filesystem, and neither has one, like the superblock was wiped.
  14. Disk1 appears to be failing, you can run an extended SMART test.
  15. Your cache pool is completely full, you need to free up some space, then recreate the docker image.
  16. They should work in ethernet mode, they won't work in infiniband mode.
  17. Yes to the first question, you could then pass-trough the NIC to the VM or select it as the virtual interface to use.
  18. Because it's not a clean shutdown: Mar 9 21:30:21 unMediaServer emhttpd: unclean shutdown detected Start by looking at this, sync errors (and btrfs checksum errors) are probably RAM related (either overclocked of bad RAM): https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  19. First thing to do is to boot in safe mode to rule out any plugins, also if not needed delete the "extra" folder on the flash drive.
  20. Pool has a missing device, despite both being assigned, to make sure there aren't surprises adding the device back and since current pool has multiple profiles it's best to backup and re-format the pool.
  21. Disk was already disabled at boot so we can't see what happened, best to replace/swap cables to rule them out them rebuild.
  22. I can't tell you what happened because whatever it was it happened before this boot but no btrfs filesystem are being detected which suggest cache devices were wiped.
×
×
  • Create New...