Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

klippertyk

Members
  • Joined

  • Last visited

Everything posted by klippertyk

  1. +1! I am also using the same board, with a 13500. I am also using slimsas cable with 4x sata cables. I'm using kingston memory with reports single bit ecc Total Width: 80 bits Data Width: 64 bits I use the ipmi card and it's very good. I get a lot of temperature monitoring and power info and use it to control the case fan speeds. I switched as the sensor driver is trying to use nct 6775 (if i remember correctly) which has a well documented bug, but there is a new driver in the 6.2 kernel coming - (whenever limetech move to that) very happy with the board, although it seems the top row of usb ports (looking at it vertically) are a bit picky on what they will detect, I had to plugin my UPS into a lower bank of usb ports to get it detected.
  2. Hi SimonF, Appreciate you sticking with me on this one. Sometimes the low tech way wins out. I just sat with the console open and ran lsusb over and over working though the ports each time and eventually..... Bus 001 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply appeared! Unraid picked it up and all is well, can see everything I need. Seems to me like the uppermost row of USB ports on this board (2x SS 1x "BIOS" and 1x (I think it's usb2) are particularly fussy about what's connected to them. I actually recall when I assembled the hardware on the motherboard box for validation and booted the board for testing I had issues with my USB keyboard and wireless mouse dongle when using that row, but didn't put 2+2 together as I dismissed it as a buggy bios (was much improved after an update) and just general first time setup "bedding in" the ports work, as I've had that usb drive plugged in them ok, but as to why they wont pick up some usb devices, someone more knowledgable will have to say.... again, I appreciate your time working through this with me, if you would still like the diagnostic I'm happy to provide.
  3. I was starting to worry I had some dodgy USB ports on the motherboard (i have not connected case headers) so after failing to get the ups detected again, i've plugged a usb pen drive in the same port as the ups was, and plugged the ups into a different port.. Bus 002 Device 003: ID 0781:5583 SanDisk Corp. Ultra Fit Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 004: ID 046b:ffb0 American Megatrends, Inc. Virtual Ethernet. Bus 001 Device 003: ID 046b:ff01 American Megatrends, Inc. Virtual Hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub still nthin. the port is live, that sandisk was the test device.
  4. Asus W680 IMPI https://www.asus.com/motherboards-components/motherboards/workstation/pro-ws-w680-ace-ipmi/
  5. lsusb from terminal shows... Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 003 Device 002: ID 1005:b155 Apacer Technology, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub so the course of action is clear, get that bus 003 device to appear on lsusb first eh. is there a command to get unraid to query usb ports for devices please?
  6. I'm viewing external devices in the qnap gui, USB is selected and both snmp and network share are grey'd out. I realise this doesn't quite answer your question so i'm currently googling how I get more info from a console.
  7. I plugged the UPS back into the Qnap and it is working, I see battery charge, est run time. Connected by USB It's an APC BACK-UPS ES 700G
  8. Alright, so... I think this isn't anything to do with unraid, but as it' that service I can't use... see what you think. I have two devices. 1. "qnap1" this runs a container for pihole. 2. "unraid2" this is my new unraid server. My Router performs DHCP - this is configured to use dns from qnap1. On pi-hole, both hostnames have a records in DNS. My laptop correctly ets its ip address from dhcp on the router, and the router is correctly making my laptop use the pihole dns. Nslookup confirms this when getting successful connections to both qnap1 and unraid2 hostnames. I can ping both as well. Until I turn on the NordVPN Windows client and make a connection. Then it gets a bit strange. On nordvpn, I can still ping qnap1, but not the unraid2. (both time out on their nslookups from pihole incidentally) The confusion is, as far as I can tell all elements are equal - therefore I should either be able to ping both, or neither. What's going on? Anyone got any ideas for trying to identify the issue? It's worth pointing out I did notice on the nslookups my machine was defaulting to NordVPNs DNS IPs and I thought I'd cracked the issue (despite STILL being able to ping qnap1!) and I added the pihole IP as a custom dns in the client, but unraid1 still doesn't work. I can still access shares on unraid via ip address, but I want to use the hostname (more to fix/understand this problem than anything else!) On a side note, I wanted to move my pihole service over to Unraid, but i'm getting the following error - docker: Error response from daemon: driver failed programming external connectivity on endpoint pihole (308e2f603d2e8bc6b9f4bc6c153122eb9fd0306efe5a447a0bd6ca17619bf476): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use. Port 80 is already in use? I ran sudo netstat -tunlp to check and found this... no idea what it is. tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3028/nginx: master How do I fix this please? I want to run pihole on unraid. Thanks for reading!
  9. mine is also the same. I have 13500
  10. Hi Simon, thanks for replying. Good shout - first rule of IT - is it plugged in. lsusb returns the following.. minus the unraid usb drive Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 004: ID 046b:ffb0 American Megatrends, Inc. Virtual Ethernet. Bus 001 Device 003: ID 046b:ff01 American Megatrends, Inc. Virtual Hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub So I'd say not? Curious. I can't do it now but I'll plug it back into the qnap and reconfim, I only unplugged it 2 days ago but you never know.
  11. Hello, Can anyone help me with some suggestions. I've got a very basic APS UPS, with the RJ11(?) to USB comms cable. I had this working great on my QNAP, which is currently being replaced by a new unraid server. I've tried connecting the UPS to the server via usb but I cannot seem to find the right combo of settings to get it detected. it's one of these. I don't know the exact model number but it looks like this https://www.dell.com/en-uk/shop/apc-back-ups-es-400va-230v-surgearrest-battery-backup-bs1363/apd/a8200252/pc-accessories I've tried a range of ups cables from the drop down and ups types but can't get a reading. Any pointers?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.