Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,867

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Rebooting should bring the shares back. Unrelated but the external HDD is failing: 197 Current_Pending_Sector -O--CK 200 200 000 - 4
  2. JorgeB
    Everything looks good, log is clean, just cannot see if the disks are mounting since the rebuild was done in maintenance mode, start the array in normal mode, if all disks are mounting you are done, if not post new diags.
  3. JorgeB
    It's the way to fix this when it happens: Oct 1 03:12:29 T1 shfs: shfs: ../lib/fuse.c:1451: unlink_node: Assertion `node->nlookup > 1' failed. It's this issue:
  4. JorgeB
    I recommend riposting the existing UD support thread:
  5. JorgeB
    It's normal, dashboard stats include I/O wait.
  6. JorgeB
    You might get some help from others doing the same if you post here: https://forums.unraid.net/forum/46-virtualizing-unraid/
  7. JorgeB
    That suggests the disk dropped offline, check/replace cables (power cable also) and try again.
  8. JorgeB
    You've also tried with a different power cable correct? If yes I think trying with a different controller (or board) would be the next step.
  9. JorgeB
    Run it again, if it didn't finish it will resume, if it did it will show the stats, also you should use the actual console or something like screen to not close the terminal window, it will stop if it does.
  10. JorgeB
    Did you try the GUI mode boot option? For some reason sometimes it makes a difference.
  11. JorgeB
    mpt3sas_cm0: LSISAS3008: FWVersion(16.00.11.00), ChipRevision(0x02), BiosVersion(18.00.03.00) Try updating to latest LSI firmware, IIRC it's 16.00.12.00, and since there's a BIOS installed you should also updated it to latest.
  12. JorgeB
    dynamix.s3.sleep.plg - 2021.03.13 (Up to date) From the ones installed I would try uninstalling this one first, you can just rename the respective *.plg to for example *.bak on /boot/config/plugins to prevent the plugin installing after a reboot, if it's not this one not quite sure which one could be, I would remove a few at a time to try and drill down on the culprit.
  13. JorgeB
    Disk looks mostly OK, should fine to use, use a different power connect and SATA cable in case that was the problem.
  14. JorgeB
    We usually recommend once a month, it's enough.
  15. JorgeB
    Didn't see it before, I guess you edited the post? Should always do it in a new post. "2022-09-27T13:46:34.000Z","TheHub","TheHub kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]" Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
  16. JorgeB
    You can, but it should be 0, unless you typically get sync errors, if you don't I would just wait for the next scheduled check, assuming you do them regularly, like once a month.
  17. JorgeB
    There's really no way, parity was out of sync, now it's in sync, unless you were writing data to the array at the time the power failed everything should fine, and with just 4 sync errors it could not be writing much.
  18. JorgeB
    Nope. This is old, update to latest or try connecting that disk on an onboard SATA port if available, you can swap with another one, if it still fails post the complete diagnostics please.
  19. JorgeB
    You need a replacement for disk4 since apparently it's dead, same size or larger than the old disk. Once ddrescue finishes post the results and I can post the detailed instructions for your case.
  20. JorgeB
    Enable the syslog server on v6.11 and post that after a crash together with the complete diagnostics.
  21. JorgeB
    You're right, the other reported issue here should be fixed on the next related, so you can leave this one open for yours, hopefully a newer kernel will help, so you should also text any new release that includes one.
  22. JorgeB
    So the folders exist but are empty, at least the ones I can see in the screenshot, so you can just delete them.
  23. JorgeB
    That doesn't make much sense, go to Shares click on "compute all" and post a screenshot.
  24. JorgeB
    Nope, they are two separate things, a disabled disk isn't always unmountable and you can have an unmountable disk without it being disabled, but if it's both the filesystem should be fixed first, because there's no point in rebuilding if the filesystem cannot be fixed, especially when doing it on the old disk, it can limit your options.
  25. JorgeB
    Shares are just all top level folders, are the movies under /mnt/user? You should also post the diagnostics.
×
×
  • Create New...