thany

Members
  • Content Count

    115
  • Joined

  • Last visited

Community Reputation

0 Neutral

About thany

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. My server doesn't have a discrete GPU. The CPU is fine, and has been forever, so the IGP should be fine, too. This happened right after the failing upgrade to 6.9, and the crashing network driver, and re-enabling the onboard NIC. So video problems is yet another thing on the pile? Please tell me this isn't *another* thing to break.
  2. Sorry, but I disagree. That's too easy. I think an upgrade, especially one that contains breaking changes, should peform a readiness check before blindly applying the upgrade. Any mature OS does this to some kind of extend. I'll try that, thanks. This server doesn't have a discrete GPU... And since the CPU is working fine, and hasn't been touched, a GPU (IGP in this case) problem is extremely unlikely.
  3. I'm also getting this problem now: Feels like a separate problem, which is why I opened a new topic. But man, this 6.9.x release still feels like a beta even after a maintenance update. All the more reason, for me at least, to know how to safely perform a downgrade.
  4. Yeah I saw that as well, a bit after doing the upgrade. I'm sad that the upgrade didn't warn me for this. The installation knows it's using which drivers, and it knows which drivers are no longer going to work. It could've issued a warning. Anyway, long story short, I haven't yet gotten an answer to the question about downgrading.
  5. What's going on here? It's never done this before... It happened after plugging my network cable out of the (not yet working) 10Gb NIC, and into the built-in 1Gb NIC. The server was powered off during this replugging. What do I do now? Should I physically pull out the 10Gb NIC?
  6. So, is this actually being worked on? I.e. can I expect a fix within, say, a couple of days, or should I seek a more semi-permanent workaround? Like a downgrade? And how does that work? And if a downgrade is too tricky, what then can I do to get my server up & running again? I mean it's good to know that it's crashing, I guess, but that's only an explanation of why my problem occurs. It's not yet a solution. It also doesn't explain (to me) why my onboard NIC does show up as eth0, but isn't working.
  7. Here you are. Hope it helps. unraid-diagnostics-20210329-1318.zip
  8. That only half a solution, because that's still on the server itself. Do I then just pull the USB stick (can this be done safely??) or transfer over to another USB stick?
  9. Weird, after enabling the crappy onboard NIC, I can see eth0 appearing in ifconfig, but still no network access at all. So this is getting kind of urgent now... The onboard NIC used to work fine as well before I upgraded to the 10Gb card. Halp
  10. So I just upgraded to 6.9.1, and now there's zero network access. I can't find the eth0 in ifconfig even, and so pinging the server doesn't work, and pinging from the server also doesn't work. I would attach my diagnostics, but I'm not sure how to transfer them over without network access 🙈 I have two NICs: one is a onboard 1Gb thingy, which probably works, but is disabled in the UEFI. The other is a 10Gb NIC add-in card. It's a Buffalo LGY-PCIE-MG, but it worked fine in 6.8.3. For this reason, I'm guessing the upgrade must've done something to mess up the driver maybe?
  11. Can you explain how to do this? I know what a SRV record is, and I know how to add one. But what should it contain exactly? Should I put "_matrix._tcp.matrix.example.com" in there, given "example.com" is my domain? Or do I put in "_matrix._tcp.example.com"? And what are those "_matrix" and "_tcp" parts? And where do I put port 443? What does DNS have to do with port numbers?
  12. When I try that, I get this: $ register_new_matrix_user -c /data/homeserver.yaml http://0.0.0.0:8008 New user localpart [matrix]: Password: Confirm password: Make admin [no]: yes Traceback (most recent call last): File "/usr/local/lib/python3.7/dist-packages/urllib3/connection.py", line 170, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw File "/usr/local/lib/python3.7/dist-packages/urllib3/util/connection.py", line 96, in create_connection raise err File "/usr/local/lib/python3.7/dist-packages/urllib3/util/connection.py", line 86, in create_connection
  13. This. Synology could find usecases for this, because the usecases are there. What they are, is open to speculation, and not awefully relevant to the question whether we should have this feature in a future version, or not. Also keep in mind that if you specifically DON'T want a file manager built graphically into the WebUI, power to you - you're free to ignore it, and it won't get in your way. Everyone is different, and since unRAID is being used in a variety of scenarios, you can't say something always makes sense, or indeed never makes sense. I think this topic h
  14. Oh dear, you're right 😳 So sorry about that, I should've probably checked this first. I do wonder what `br0` was doing with the IP-address then. I understand that's not a physical NIC, but should `br0` get the IP-address instead of the physical NIC?
  15. Here you are. andy2-diagnostics-20201007-2243.zip