Jump to content

meep

Members
  • Joined

  • Last visited

  1. 72 hours with no sleeps. Considered fixed. Likely cause was a failing USB boot drive.
  2. So I have an update; Came to my desk this morning and my server was still chugging away, not asleep. I checked the system log and it's clean as a whistle. While I don't have a definitive action I took to effect this change, I did encounter a significant problem since I last posted that's more than likely related if not the root cause: a failing boot thumb drive. Through the various restarts I conducted yesterday to check BIOS settings etc., I started experiencing GUI lockups of increasing rapidity a couple of minutes after restart. Checking the logs, I noticed reports of USB access issues leading to errors with device SDA, my boot drive. I tried swapping it around between ports, changing between efi and non efi boot etc., to no avail. I bit the bullet and transferred to a new boot drive (my 4th in 16 years, not bad going). Boot up was noticeably snappier and the USB errors stopped immediately. It looks like my USB boot drive had been on its way out. I was possibly missing the errors as they were getting lost in log spamming from another failing unassigned device in my older system, and I'd implemented a user script to clear syslogs overnight to prevent the system crashing from full logs. I'm not sure how the failing USB caused the system to go to sleep overnight, and maybe its unrelated. I'll keep everything as is for a few days for observation before I attempt an upgrade to 7.1.x. As this system has had a complete heart & lung transplant (MB, CPU, RAM, GPU, Case, Cooling, Some drive swaps) I would expect little niggles here and there so will remain on high alert. Fingers crossed. Thanks for all the input.
  3. Yes indeed. It's conveniently placed but there's nothing brushing against it. I just checked and a short press of the power button will cause a full shutdown. (Spacebar will not reactivate it, so it's not asleep like the overnight issue I'm experiencing). I'll have another look through Bios now that I'm restarting to see if I've missed anything, otherwise will let it do its thing overnight tonight with full logs in place and see what's what tomorrow.
  4. No pets, it's in my office. Though I will check what happens on a short power button press to see if that replicates the status I find the system in. Thanks
  5. Will check power contacts for sure, though the system has logged the same entry at 4.40 for the past 2 nights, then nothing more I til I wake it up, so unlikely to be a freak contact. Won't rule it out though.
  6. I'll see what happens tonight. I had a script that deleted system logs overnight as they were filling up on my old server and causing it to crash. I've disabled that script as the logging issue is no longer happening on this newer machine. So tomorrow I hope to at least have more logs of what's happening on the build up to the sleep event.
  7. Yes, very sure. Fans switch off, server cannot be reached on network but a tap of the spacebar brings it back to life.
  8. No, not installed and never previously installed. I was thinking of installing it and setting it to 'never sleep', if that's even a thing, but thought I'd ask first.
  9. Hi folks Looking for pointers on this I 've just upgraded my unraid system from a threadeipper 2950 to a 3960X on a ROG Zenith II Extreme Alpha motherboard. No changes to drives or USB boot stick. Everything went very smoothly and all services and functionality is as before. However, I've noticed that my system is now going into sleep mode overnight. Whenever I get to my desk in the morning, it's sleeping. A tap on the keyboard will wake it up. I'd prefer to not have the system sleeping as it runs some home automation VMs and Dockers. Here's the log after I wake it up; Last action was at 4.40am, until I woke it around 8.43. I had a good look around the MB bios but don't see anything obvious in any power settings. I don't have anything sleep related in my unraid setup either. Any tips on where to look? I'm still on 6.12.13. I'd panned to update to current after this hardware change, but would like to get this issue solved before doing so. Thanks for looking.
  10. @HHUBS I don't believe an isolated CPU can be utilised by the OS. The help on CPU Isolation settings says the following; CPU isolation allows the user to specify CPU cores that are to be explicitly reserved for assignment (to VMs or Docker containers). This is incredibly important for gaming VMs to run smoothly because even if you manually pin your Docker containers to not overlap with your gaming VM, the host OS can still utilize those same cores as the guest VM needs for things like returning responses for the webGUI, running a parity check, btrfs operations, etc. That would indicate to me that an isolated core is reserved exclusively, and not used by OS. It's typically recommenced that you never isolate, assign or pin CPU 0 as this is favoured by unRaid for OS specific tasks and processing. If you have CPU 0 pinned or assigned to Docker or VMs, that might contribute to your 100% usage issue? As always, I could be wrong, and other more knowledgeable may row in.
  11. I use HDBaseT to run displays and peripherals from a VM on my unRaid server to a desk in a different building. I write a bit about it here; https://mediaserver8.blogspot.com/2019/07/routing-vms-anywhere.html I'm currently pushing a single display 1920x1080 @ 60Hz, and you'd need one transmitter / receiver per display. Not sure if they hit 144HZ, but you could check specs on AV Access devices, or similar technology. Mine runs across about 60M of Cat6A cable and is very stable.
  12. Ah, something that must not have come through when I migrated, or perhaps something new. Is this what you refer to? So maybe my Switch Ultra could have worked after all?
  13. The device shows as adopting; Then goes offline for a moment; Then repeats on a loop. On the first try, my logs show success; But the adopting / offline loop just keeps going. Docker Inspect shows the docker IP to be 172.17.0.10 When I had the Ultra, I couldn't SSH into it (not supported), but your post just reminded me this was a switch with SSH supported; I did a set inform to the IP of my unraid server, et voila, it worked! Though that brings up my next question....... Whenever I have occasion to stop and restart this docker, my USG-Pro-4 'forgets' its inform UL and I need to log in to the device UI and reset it. I suspect I'm going to have the same issue with this switch. Any thoughts on that?
  14. I migrated from the legacy Unifi docker to this a few months ago and all seemed well, but now I'm having trouble adopting devices. (on repo /unifi:8.3.32-unraid) I had a Switch Ultra that started acting up and went into some kind of adoption / offline loop, and though it worked OK , and showed as adopted in logs, I could not access or configure it in the UI. I contacted Unifi support who ultimately requested that I DMA the switch. However, Now I've acquired a USW-Pro-24-PoE and it's doing the exact same thing!! I like running my controller in unRaid, but with the deprecation, migration hassle, and now this nonsense, I'm thinking of abandoning it and getting a Unifi key altogether. Any insights?
  15. Oh sure. This was not a response to anything, just a general interjection.