Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,797

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Also, update to v6.10.3, previous v6.10 releases with VT-d enable might cause some data corruption, your server is not one of the known affected, but can't rule out it could be.
  2. JorgeB
    Sorry, no more ideas, but I think it should work if SMB1 is enable, maybe look for way to check the SMB connection status, you can use PowerShell and 'Get-SmbConnection' to do that with Win10, see if you can find the equivalent for Win98.
  3. JorgeB
    This might need to be disabled for SMB1, but you can try first as is.
  4. JorgeB
    If you have a backup use that, as long as no disks changed since it was made.
  5. JorgeB
    Didn't notice this before: Hardware name: Apple Inc. Macmini5,3 It's notoriously hard to get Unraid booting on Apple hardware, you can try but it might be a lost cause to get that working reliably.
  6. JorgeB
    That's just for parity drive(s), as long as you know the previous assignments you can re-assign all the disks and check "parity is already valid" before array start, note that if you do assign a previous data drive to parity any data there will be lost.
  7. JorgeB
    Please use the existing plugin support thread:
  8. JorgeB
    Swap should not cause any issues, data is still the same, but can't really help with that, suggest you ask for help in the appropriate docker support thread, there's a likely a way to repair de db.
  9. JorgeB
    Try creating the flash drive manually: https://wiki.unraid.net/USB_Flash_Drive_Preparation
  10. JorgeB
    Because there wasn't one, all checks were non correct.
  11. JorgeB
    Jun 15 12:48:12 JOESERVER kernel: BTRFS error (device nvme0n1p1): block=411713536 write time tree block corruption detected This error means in memory corruption was detected before writing the data, this is usually due to bad RAM, start by running memtest.
  12. JorgeB
    No idea where that ._cache pool comes from, there's only a cfg for cache in the pools folder, I would suggest backing up current flash drive, then create a clean flash drive and for starters only restore the key, super.dat and pools folder from the backup, all in the config folder, then boot up and see if that weird pool is still there.
  13. JorgeB
    Start by running memtest, when there's no ECC, RAM is usually the first suspect for unexpected sync errors.
  14. JorgeB
    So main problem with lost files are disks 2 and 4, disk2 is healthy so data on the actual disk should be in a much better shape than the emulated disk2, what about disk4? You mentioned it's disconnected, do you know if it failed or it was just disconnected and assumed OK?
  15. JorgeB
    Forgot about that 😳
  16. JorgeB
    You need to have a little patience, support in the forum is mainly done by other Unraid users, answers can take some time, not everybody is constantly on the forum, also not every problem has a solution.
  17. JorgeB
    Try this: https://forums.unraid.net/bug-reports/stable-releases/6100-vnc-no-longer-connects-r1902/?do=findComment&comment=19746
  18. JorgeB
    Server load average is very high, shfs seems to play a big part of that, unfortunately and AFAIK not quite clear what causes this for some users. Depending on where you have the data for the worst offending dockers any chance you can change the mappings to use disk shares instead of user shares? E.g., lets say the data Duplicati is syncing is on a pool or a single disk, change the mappings form "/mnt/user/share" to "/mnt/pool_name/share" or "/mnt/disk#/share" and test.
  19. JorgeB
    Unfortunately there's nothing relevant logged, assuming the log covers the crash, if it remains stable with v6.9.2 it also doesn't look like a hardware issue, maybe your hardware and the newer kernel just don't get along, but in those cases there's usually something logged.
  20. JorgeB
    Just iommu.passthrough=0
  21. JorgeB
    Kind of expected that, but since we mostly tested with Intel and Nvidia it was worth a shot just to make sure, unfortunately I don't have any more ideas, but someone else might.
  22. JorgeB
    No, but I would try with a couple different flash drives if you have some lying around, you don't need a key, just to see if it boots.
  23. JorgeB
    If it was a bit flip it might be hard to catch any issues with memtest, still worth running a couple of passes, if no errors are found see how the next parity checks go.
  24. JorgeB
    Check for a lost+found folder in the emulated disk2 and the other repaired disks, if there's is one check contents, any files there could be lost data.
  25. JorgeB
    That's from the parity check tuning plugin. That's expected, it will remain disabled until it's rebuilt, same for disk4, you either need to replace the missing disk or remove it from the array.
×
×
  • Create New...