Brandonb1987

Members
  • Posts

    69
  • Joined

Everything posted by Brandonb1987

  1. I seem to be having the same issue since upgrading to 6.12.3. I've disabled all plugins, docker and vm. Still pegging 80+ %CPU 2 things are using CPU: 1) find /mnt/plex_cache/Plex -type f -maxdepth 18 Not sure why this is being pegged when the only thing that uses that drive is Plex docker, but its currently disabled/not even started. 2) /usr/local/bin/shfs /mnt/user -disks 32767 -o default_permissions,allow_other,noatime -o remember=0 No clue what that is... Anyone able to help me pinpoint this further? unraid-diagnostics-20230827-1401.zip
  2. Well I'm not sure what was going on but it seems replacing the motherboard has "fixed" the issue. I replaced the mobo, upgraded to 6.12.3 shortly after and has been stable since? Currently up ~3 days without a reboot or stall so I will consider it having been the issue and solved. Thanks to everyone for helping.
  3. Well I'm not sure what was going on but it seems replacing the motherboard has "fixed" the issue. I replaced the mobo, upgraded to 6.12.3 shortly after and has been stable since? Currently up ~3 days without a reboot or stall so I will consider it having been the issue and solved. Thanks to everyone for helping.
  4. Well I have some progress... Turns out wasn't the PSU. Tried a new one and it was doing the same. Slowly ruled out parts one by one and looks like a dead mobo. Have a temporary replacement in while the actual one ships from china. ETA 2-3 weeks only, hopefully... After a handful of other issues with what I've ruled as a docker image corruption, things are back up and working perfectly on 6.11.5 However, a fresh 6.12.3 still hangs. I will report back when I have another moment to do an upgrade and capture the hang syslog.
  5. Well I have some progress... Turns out wasn't the PSU. Tried a new one and it was doing the same. Slowly ruled out parts one by one and looks like a dead mobo. Have a temporary replacement in while the actual one ships from china. ETA 2-3 weeks only, hopefully... After a handful of other issues with what I've ruled as a docker image corruption, things are back up and working perfectly on 6.11.5 However, a fresh 6.12.3 still hangs. I will report back when I have another moment to do an upgrade and capture the hang syslog.
  6. I'm starting to think this actually may be a failing power supply. I restored my 6.11.5 backup and now it powers off and on during the boot process. It is also doing it with 12.1/2/3. There is no specific point in the boot where it does it so I'm inclined to think this could be hardware related. I will be ordering a new one tonight to replace and will report back if this is the solution.
  7. I'm starting to think this actually may be a failing power supply. I restored my 6.11.5 backup and now it powers off and on during the boot process. It is also doing it with 12.1/2/3. There is no specific point in the boot where it does it so I'm inclined to think this could be hardware related. I will be ordering a new one tonight to replace and will report back if this is the solution.
  8. Ah ok I was not aware of that now that I’ve read the post on the syslog. I simply enabled syslog server. I will try and recreate the hang tonight when I get home and repost the diag file with it. thanks for the clarification.
  9. the diagnostic I posted above (1933) is that
  10. refer to the diagnostic I posted above
  11. There shouldn't be if its a fresh install, so that wouldn't be a reason for the hanging as it happens with any 6.12+ fresh install as well
  12. yes, problem persists on 6.12+ with a clean install using the usb creator tool
  13. Yes because I suspect it never even starts. It crashes before it starts the array. This happens without a single plugin installed (fresh USB), but starts fine if I start it in Safe Mode. Which is strange in itself. I'm going to try and see if 6.11.5 is any better because it's become a problem on all versions. I've since deleted my docker.img as well, that did not solve the issue either.
  14. Possibly but that wouldn't explain why its doing the same thing with a fresh install with no plugins installed.
  15. I've tried 6.12.0,1,2 and 3rc3 and they all are giving me issues. Basically what happens is I start the array, it hangs, UI goes unresponsive for a few minutes, then the login becomes available, login and the array is down. Try and navigate to something and it will hang in about 30-60s. I've got a syslog and diag attached. I've basically tried with a fresh USB install, tried without any plugins, docker disabled, copied only the settings cfg files, and it'll just hang every time. I tried playing around with it in Safe Mode and it seems to resolve the hanging issue. So not sure where to go from there. Please help. I've attached 2 different scenarios. unraid-diagnostics-20230714-1825.zip unraid-diagnostics-20230714-1933.zip
  16. Ok now this is strange. I've installed 6.12.3rc3 on the usb, only copied over the config files for settings and disks etc but without a single plugin, docker off, and letting it create all the random other files it auto populates. The array starts, but It does the same thing more or less. Got a syslog for this one too. Tried to install the unraid connect plugin, hangs, crashed, now my array is down. unraid-diagnostics-20230714-1933.zip
  17. I've tried 6.12.3-rc3 and now I cant seem to start the array. I think there's 1) something going on with my docker.img but I can't even start the array now with it disabled. 2) I briefly saw that my cache drives weren't visible after starting the array, right before the UI crashed. 3) It hangs for a few minutes then the UI starts again but the array is down and needs to be started. Then the UI crashes if I try to navigate anywhere. Not sure what's going on but I cant even log in anymore to get the syslog. Downgraded back to 6.11.5 and now I can't start the array on it either from backup. Got a syslog now that I can actually get it. unraid-diagnostics-20230714-1825.zip
  18. Seems like a common issue right now. Unraid becomes essentially unresponsive after a day on 6.12.0, 1 or 2. Has to rebooted in terminal. I'll be sticking with 6.11.5 until this is figured out since its actually stable and not "stable". unraid-diagnostics-20230701-1717.zip
  19. Well after a full afternoon of farting around...I managed to get it working again. I first started by unplugging everything that isn't needed just to boot. Still did it. Tried the internal header port with the new USB, nada. Plugged the new usb into a random port in the back, OF COURSE THAT WORKS. Try the old usb in the exact same port, nada. Try different ports with different usbs, nada. Plug the new usb into the known working port, LEAVE IT ALONE! So I think something must have happened to one of the controllers on the MB? Which then barfed on the USB and killed it? Either way, its working...FINALLY....
  20. Boots perfectly fine off the usb with my pfsense box. Im wondering if maybe the usb controller on the MB kicked the bucket?
  21. Clearly you didn’t read the post. that hasn’t solved the issue
  22. Hoping someone can help with this as I'm obviously not the only one experiencing this.
  23. No. I’ve tried using a different laptop to format the usb, different usb sticks, different versions, using and not using the unraid tool. Server is sitting there unable to boot anymore…. Not sure what to do anymore.
  24. Tried all that. Tried all different versions, full formatting of the usb, multiple usb types, brands, multiple attempts at replacing the all the files. Tried barebone downloads of the files, with replacing the files. Also confirmed sha256 and md5 hashes.
  25. Not entirely sure whats going on. I've been running the latest stable release and i had to restart the server today and now I can't seem to boot back into unraid. I've tried making a fresh usb, cant boot, 6.10, or 6.11. 6.9 gives me an ip6tables bond0 error and wont connect to my network? Tried 2 different usbs, including one of the exact same I've been using for years to no avail. I've done checksums on the files, all fine. I've done a bios reset, didn't do anything. I've tried adding the parms "intel_iommu=on iommu=pt" to my syslinux, nada.... I've tried fresh images, backups, NOTHING. No hardware has changed, no settings were changed.... Can't get you any diagnostics but have attached the photo of the error. PLZ HELP!