Jump to content

JorgeB

Moderators
  • Posts

    67,684
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. It is, and I didn't remember the other one, but like mentioned best thing to do would be getting a UPS.
  2. Only call traces I see are about the Realtek NIC: Aug 24 10:52:40 Unraid kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out It does appear to recover after a few seconds, but if issues persist try another NIC if available, Intel preferred.
  3. Not really, but there are many threads in the forum about that, probably a few guides/videos also.
  4. If the HBA issue is fixed, the emulated disk is mounting and contents look correct you can rebuild disk1 on top (and re-sync parity1 at the same time).
  5. You could spin up an Ubuntu VM and pass-trough those disks.
  6. It's not possible, since Unraid doesn't have the standard MDADM driver, it's uses a modified version for its driver, also next time please use the existing plugin support thread for any plugin related questions.
  7. No, this is the correct place, just a very specific question.
  8. That's very strange, like mentioned the VM settings (not the VM XL) are stored on the flash drive, once store, and they are now, it should never revert back, don't remember seeing this issue before.
  9. Those settings are saved on the flash drive, make some changes and post new diags (before rebooting).
  10. If it happens again see if you can get the syslog: cp /var/log/syslog /boot/syslog.txt This will copy it to the flash drive, then upload here.
  11. This was a SATA controller problem, quite common with some Ryzen boards, multiple disks dropped offline, reboot so they can come back online, start array and post new diags.
  12. https://forums.unraid.net/topic/111161-pcie-errors/?do=findComment&comment=1013378
  13. Correct, there can be up to 35 pools, of up to 30 storage devices per pool.
  14. They count for the license limit, also there's no 30 device limit license, there's 6 for Basic, 12 for Plus, and unlimited for Pro, there is a 30 device array limit, but pool devices don't count for that.
  15. You can do time xfs_admin -U generate /dev/sdab1 So you don't need a stopwatch.
  16. They were both wiped, this is why you needed to use the btrfs-select-super command, this was likely done by Unraid because of some misstep during the replacement, but if that was the only issue and it was a raid1 pool I would expect the good member to mount by itself, so there were/are other issues.
  17. I would think 10s would be enough, do it on the CLI and see how long it takes.
  18. There have been some spin up issue with some hardware, disable spin down to test and see if it makes any difference.
  19. Errors on multiple devices suggest a power/connection problem, could also be the HBA or enclosure, I have no experience with NetApp enclosures, because of how they work they were never interesting to me.
  20. Run a scrub and look at the syslog for the name of the corrupt files, then delete/restore from backup.
  21. It's still not mounting degraded, that means the missing device it not the only problem, you can try the other recovery options here to see if any of them work.
  22. OK, but now at least it's throwing an error that makes sense, strange it didn't show the same in the pool, it's not normal: Aug 23 19:02:32 DataStriver kernel: BTRFS error (device sdd1): devid 2 uuid 4b126ecf-990b-43f5-a5fd-1f31a15ab285 is missing Since the other device is out of sync, try this: mkdir /x mount -o degraded,ro /dev/sdd1 /x If it doesn't mount post the output, if it does you can browse /x to backup the contents.
  23. Unassign the device and try to mount it with UD, if it still doesn't post new diags (or just the syslog is enough now)
  24. Most likely, shame the NetApp enclosures don't pass the disks directly, that would be much better with Unraid.
×
×
  • Create New...