Jump to content

JorgeB

Moderators
  • Posts

    67,719
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Not really, that one should detect any major issues.
  2. No, you'd need to check the log or have this enable for all btrfs filesystems: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582
  3. Yes, video files might still play, but there could be some visible corruption during play.
  4. Thanks, I see that now it also works with user shares, but to be honest I don't think it's something LT changed, most likely some kernel/FUSE change that now allows for that to work with user shares.
  5. I would wait some time and run another scrub, if more corruption is found there's likely an underlying hardware issue.
  6. It should list the affect file in the syslog. It's up to you, but that if it's data corruption it's not a btrfs problem, it's only detecting corruption, of course xfs won't have that issue since it won't detect any data corruption.
  7. The most important part is the percent rescued, in the end it's usually 99.9% for most cases, though it can be much less for really bad disks, there's also an option mentioned in the FAQ that can list the affected files, so you can delete/restore them.
  8. That just means you need to stop the array, if you want to keep using the array without disk18 and can do a new config without it.
  9. If the controllers are bound to vfio-pci Unraid will not load the drivers and count the devices, I guess it depends on how you are passing them through.
  10. Disk 17 is on an LSI controller together with 7 other devices, and all are being detected, also unless you loaded an older Unraid config there are only 17 data disks, look at the screenshot you posted, there are 24 devices total, including cache devices, unassigned SSDs and disks, and an empty slot, you don't even have disk 17 there.
  11. If the other disks are passedthrough basic key should be enough, you can confirm by going to Tools -> Registration, it will list the total number of attached devices that count for the license.
  12. One thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  13. Looks like a drive problem, it's not even giving a valid SMART report.
  14. Please don't create multiple threads for the same issue, already replied in the other one. https://forums.unraid.net/topic/116238-parity-sync-with-errors-read-pending-sector-also-varlog-100/?do=findComment&comment=1056719
  15. Unfortunately there's nothing relevant logged before the crash, this usually suggests a hardware issue.
  16. Yes, if you can't boot using GUI mode. If you don't know use the ones from the example I gave. It's more complex than normal because you're using a direct network connection, it's much easier when using a router, since it will assign the IP addresses. You need a router to assign IP, don't you have one for Internet access?
×
×
  • Create New...