Stubbs

Members
  • Posts

    207
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Stubbs's Achievements

Explorer

Explorer (4/14)

12

Reputation

  1. Are the Pure Power 11 FM and RM550x still the only known PSUs that are extremely efficient at low loads? I can't buy them anywhere.
  2. How do you refresh the admin token? Mine isn't working and I cannot login as an admin. I tried using what was in the .json file in appdata, but it did not work.
  3. The last two times I have shut down my server, a parity check is automatically initiated upon turning back on, presumably because a forced shutdown was initiated for whatever reason. I powered down the server through the GUI and not the power button. I just want to make sure these checks don't start every time there is a fake forced shutdown. I want to power off my server more often.
  4. I am hitting between 50W and 54W idle with 8 HDDs spun down, and running powertop --quiet --auto-tune. I am using a Seasonic Focus Gold 550W PSU. To clarify, would there be no benefit of changing to an ATX12VO PSU like an RM550x? The guide says to avoid buying one unless you can get down to 30W, but would using that PSU literally help me get closer to 30W from 50W? I could also go for a SeaSonic FOCUS Plus Platinum 550 W, but I'm not sure simply going to platinum is worth it.
  5. That was it, thanks. I forgot that Unraid has been problematic with NTP servers, at least for me it has.
  6. In the Bitwarden WebUI, I just go to Account Settings > Security > Two Step Login > Authenticator App (Manage). It generates a QR Code. I scan it with my phone using Aegis authenticator (also tried FreeTOP). Scanned fine, generated a code, but the Bitwarden WebUI refuses to accept it. [2023-06-19 03:44:13.177][vaultwarden::api::core::two_factor::authenticator][ERROR] Invalid TOTP code! Server time: 2023-06-18 17:44:13 UTC IP: my.ip [2023-06-19 03:44:13.177][response][INFO] (activate_authenticator_put) PUT /api/two-factor/authenticator => 400 Bad Request
  7. Swag, although I haven't tried the above solution provided yet. I'm sure that will work fine. The thing I really want to know now is why TOTP isn't working for me. I thought it would be straight-forward but even with two different TOTP apps, this container refuses to accept the code. TOTP works with NextCloud but not vaultwarden.
  8. How do you disable the admin interface on the nginx config? I want to be able to access it locally, but not over the internet. Also TOTP doesn't seem to be working for me, at least not with Aegis on Android. [2023-06-18 16:20:50.585][vaultwarden::api::core::two_factor::authenticator][ERROR] Invalid TOTP code! Server time: 2023-06-18 06:20:50 UTC IP: my.phone.ip.address
  9. Will all ATX3.0 Power Supplies be more efficient at idle than non-ATX3.0?
  10. My mistake, I forgot the disk and remote share boxes were separate. Nevertheless, as you found out the remote shares was empty too. Hopefully I'll figure it out one day.
  11. As I said, I deleted both those TrueNAS and JOHN-PC unassigned disks (mount points) as soon as I started having issues. Am I missing something with the deletion process? I don't see anything under /mnt/disks or /mnt/remotes either. I am not seeing any mentions of TRUENAS or JOHN-PC in my system log, which should be reflected in the last two diagnostics files I attached here:
  12. This was a test TrueNAS VM I made and created a mount point for on Unraid. The VM has been off for weeks now, and I deleted that mount point as soon as I started having this issue. I currently have zero unassigned devices, but I'm still having issues with the UI hanging randomly. Even if Unassigned Devices was trying to perform operations on an offline remote, I don't see why that would cause the whole server to have issues. Nothing I run depended on those unassigned remotes.
  13. In safe-mode, it took a long time to boot up and become accessible, but by the time it was, it seemed fine. It's hard to tell though, because even without safe mode it can perform fine, but then randomly things will start going wrong. Attached two diagnostics, both during and after safe mode. I don't understand. What remote server? Network? I didn't have any of these problems while I was on 6.11.5 stable. I virtualize my router through a pfSense VM with a quad NIC passed through. Again, worked fine on the last update. (22-05-2023) (reboot post-safemode) tower-diagnostics-20230522-1604.zip (22-05-2023) (safe mode) tower-diagnostics-20230522-1537(non-anon).zip
  14. I recently updated from 6.11.5 stable to 6.12 RC6, and since I did, Unraid performance has shocking. The WebUI hangs, SSH connections hang, docker containers randomly flicker between working and not responding, the "Main" page often takes forever to load all my array information. It gets especially bad when I stop the array; every single action seems to take forever while the array is stopped. To recount my actions before and during the update: I unstubbed my HBA Card. I was originally passing it through to a TrueNAS VM for a test zpool, but decided to let Unraid use it because of 6.12's zfs support. I changed the HBA card's PCIe slot from the second to the third (bottom) x16 slot. I did this because since Unraid will be using this card, I don't have to worry about IOMMU groups anymore. The bottom slot was always hard to separate from other interfaces. I installed a new Intel Optane P1600X M.2 SD in my motherboard's M.2 slot. In the system log I see a lot of this. I don't know if it's relevant, but there's a lot of it: May 21 21:49:11 Tower kernel: device veth7ada777 left promiscuous mode May 21 21:49:11 Tower kernel: docker0: port 10(veth7ada777) entered disabled state May 21 21:49:12 Tower kernel: docker0: port 10(vethb79be41) entered blocking state May 21 21:49:12 Tower kernel: docker0: port 10(vethb79be41) entered disabled state May 21 21:49:12 Tower kernel: device vethb79be41 entered promiscuous mode May 21 21:49:12 Tower kernel: docker0: port 10(vethb79be41) entered blocking state May 21 21:49:12 Tower kernel: docker0: port 10(vethb79be41) entered forwarding state May 21 21:49:12 Tower kernel: docker0: port 10(vethb79be41) entered disabled state May 21 21:49:12 Tower kernel: eth0: renamed from vethecd0195 May 21 21:49:12 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb79be41: link becomes ready May 21 21:49:12 Tower kernel: docker0: port 10(vethb79be41) entered blocking state May 21 21:49:12 Tower kernel: docker0: port 10(vethb79be41) entered forwarding state May 21 21:50:35 Tower kernel: docker0: port 1(vethbcd1caf) entered disabled state May 21 21:50:35 Tower kernel: vetha908dc1: renamed from eth0 May 21 21:50:35 Tower kernel: docker0: port 1(vethbcd1caf) entered disabled state May 21 21:50:35 Tower kernel: device vethbcd1caf left promiscuous mode May 21 21:50:35 Tower kernel: docker0: port 1(vethbcd1caf) entered disabled state May 21 21:50:45 Tower kernel: docker0: port 10(vethb79be41) entered disabled state May 21 21:50:45 Tower kernel: vethecd0195: renamed from eth0 May 21 21:50:45 Tower kernel: docker0: port 10(vethb79be41) entered disabled state May 21 21:50:45 Tower kernel: device vethb79be41 left promiscuous mode May 21 21:50:45 Tower kernel: docker0: port 10(vethb79be41) entered disabled state May 21 21:51:44 Tower kernel: docker0: port 1(vethe1280f3) entered blocking state May 21 21:51:44 Tower kernel: docker0: port 1(vethe1280f3) entered disabled state I attached two diagnostics. The one marked "initial" was right after the update when I booted the server back up. The one marked "21-05-2023" is one I initiated just now, with the whole system running horribly. (21-05-2023)tower-diagnostics-20230521-1505.zip initial-diagnostics-tower-diagnostics-20230520-0359.zip
  15. When writing echo med_power_with_dipm, how am I supposed to find out which disks are on which host? I know sdf and sde are connected to an ASMedia 1062 controller so I have to skip them. I don't see anything in disk information telling me what their host number is.