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.

hawihoney

Members
  • Joined

  • Last visited

Everything posted by hawihoney

  1. Found a workaround. Deinstall packages fetched via un-get or other tools. Install that one from community store:
  2. Today I did install 7.0 on our Main Unraid Server. Update was a smooth experience with one exception. Our own software infrastructure is completely local and based completely on Python. For Python we need pip and additional modules. This does not work with 7.0 any longer because of SSL errors. This worked for the last couple of Unraid releases without any problems. And as you can see below the extra packages are rather old. Nothing changed with them. Only Unraid 7.0 is new. The list of additional modules: root@Tower:/boot/extra# ls -l total 45496 -rw------- 1 root root 3598592 Jul 4 2023 exiftool-12.64-x86_64-2cf.txz -rw------- 1 root root 1809344 Nov 3 2021 python-pip-21.3.1-x86_64-2.txz -rw------- 1 root root 18538524 Jan 16 2022 python3-3.9.10-x86_64-1.txz -rw------- 1 root root 290256 Mar 17 2022 rar-5.8.1-x86_64-1_SBo.txz -rw------- 1 root root 22115768 Jan 13 15:10 rclone-1.69.0-x86_64-1cf.txz -rw------- 1 root root 212716 May 6 2022 unrar-6.1.7-x86_64-1cf.txz Here the SSL errors we get: root@Tower:/boot/extra# python3 -m pip install --upgrade requests WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available. WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/requests/ WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/requests/ WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/requests/ WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/requests/ WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/requests/ Could not fetch URL https://pypi.org/simple/requests/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/requests/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping ERROR: Could not find a version that satisfies the requirement requests (from versions: none) ERROR: No matching distribution found for requests WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available. Could not fetch URL https://pypi.org/simple/pip/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/pip/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping Going back to 6.12.* the modules worked again. What is it? Thanks in advance.
  3. It's just a small annoyance and it needs a well defined order to see it: 1.) Start a parity check. Let it run for a minute or so. Cancel the parity check. Clear the current notification. Wait a day or so. 2.) Start a parity check and let it finish. --> The GUI notification shows a red icon even after a successful second run. The GUI notification will take the previously canceled parity check and it's result into account. Looking into the History you will see both lines in the correct order: --> The text shows the correct result: --> At that point the text and the notification don't match. As a said, just a small annoyance. But I always get a heart attack seeing that red icon Thanks.
  4. Thats not what I try to report. I open the Unraid GUI. This usually opens the Main tab. Within the Main tab the Array tab will be opened usually. Now the UD tab opens instead - always.
  5. Mit "Sie erhalten beim Kauf 24 Monate gesetzlichen Gewährleistungsrechte" ... Recertified bei Seagate bedeutet, dass die Platten Rückläufer sind, die von Seagate geprüft wurden und als "Neu" mit Nachlass verkauft werden, da sie einen "neuwertigen Standard" erfüllen. So wurde mir das mal von denen erklärt. Im Laufe der letzten Jahre habe ich exakt 30 Re-Certified Platten von ihm in diverse Server eingebaut. Die sind alle noch im Einsatz. Nicht ein einziger Ausfall bisher. Für den Hobby-Bereich ist das unschlagbar günstig. Für den Profi-Bereich nimmt man sowieso andere Platten. Da diskutiert auch niemand über einen u.U. doppelten Preis.
  6. Today, after installing the latest release of UD, I'm always sent to the UD tab (within the Main tab) instead of the Array tab. I'm using Page view=tabbed in Settings.
  7. Ich kaufe seit Jahren bei dem genau dieses Modell. Günstiger geht fast nicht: https://www.ebay.de/itm/185843432850
  8. Thanks for your fast answer. Hmm, I can reach everything from Google to IBM around the world. login.tailscale.com works but not the website. I jumped - via tailscale - on my Unraid server at home and did a traceroute from DE. Same result from ZA on Android: root@Tower:~# traceroute tailscale.com traceroute to tailscale.com (76.76.21.21), 30 hops max, 60 byte packets 1 fritz.box (192.168.178.1) 1.703 ms 2.283 ms 2.638 ms 2 p3e9bf1dc.dip0.t-ipconnect.de (62.155.241.220) 15.594 ms 15.627 ms 15.760 ms 3 d-ed5-i.D.DE.NET.DTAG.DE (217.5.110.90) 16.892 ms 16.884 ms 17.447 ms 4 d-ed5-i.D.DE.NET.DTAG.DE (217.5.110.90) 17.398 ms 23.944 ms 24.080 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 *^C
  9. Is it just me or is Tailscales website down? I can reach: https://login.tailscale.com/ but none of the static parts like https://tailscale.com/kb/ The result is "ERR_CONNECTION_TIMED_OUT". As I'm not in my own country currently I additionally tried a VPN to different countries but the result is the same. I thought that the installation of Tailscale might be the reason and stopped Tailscale. Without success again. The last time it worked for me is two days ago. Thanks.
  10. @EDACerton: In one of the complaints mentioned above, somebody wrote that MagicDNS would lead to relayed connections. As a network NOOB without a clue, I changed the address of my Unraid server in my Android tablet from the full tailscale domain to its IPv4. Seems a lot faster now. Switching these address from one type to another seems to confirm that. Pure luck or simply impossible?
  11. I don't even know what this is. Installed the plugin on Unraid, the app on Android, and added the full tailscale domain to my file manager on Android. That's all. No additional VPN, no NPM etc, bonding=yes, bridging=no, VLANs=no, macvlan on docker and host access=yes. No ports on router open, no proxys of any type. My tailscale account was still there, so installed it again - it's really fast to setup. Copied one file --> 62 kb/s. Dropped everything, started my Fritzbox VPN, copied one single file in several MB/s. Searching the web I find lots of complaints about tailscale and SMB. What's the magic?
  12. When I tried Tailscale some months ago on my Unraid server, copying files eg from an Android device over SMB was terrible, terrible slow. So i dropped it. Using that same two devices and SMB with other VPN solutions was way faster (MB/s instead of KB/s). Is this fixed now?
  13. I try to avoid that - thats my reason to ask. Three arrays were affected during the power outtage. 1 array was working and does parity check currently. 2 arrays were spun-down completely. Parity check on them takes 35 hours each. I'm pretty sure that a spun-down array is save, but only the developer knows.
  14. If the array is spun down after (in my case) 15 minutes, is it possible that it's content is not synced (cache written to disks and applied to parity)? We had a power outtage yesterday. I know that two DAS (Direct Attached Storage) boxes were spun down completely before this crash. Is it possible that parity is out of sync in that situation? I guess no, must be save. What do you think? Thanks.
  15. This setting is default: New single-device pool gets formatted as BTRFS. Why? Is there a hidden setting somewhere else? Thanks.
  16. My system has two NVMe attached to the motherboard. This combo worked throughout the latest releases without any problems. With the installation of 6.12.13 one of the two NVMe throws errors now: Aug 27 08:19:17 Tower unassigned.devices: Mounting partition 'nvme1n1p1' at mountpoint '/mnt/disks/NVMe2'... Aug 27 08:19:17 Tower unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime,discard '/dev/nvme1n1p1' '/mnt/disks/NVMe2' Aug 27 08:19:17 Tower kernel: XFS (nvme1n1p1): Mounting V5 Filesystem Aug 27 08:19:17 Tower kernel: XFS (nvme1n1p1): Ending clean mount Aug 27 08:19:17 Tower unassigned.devices: Successfully mounted '/dev/nvme1n1p1' on '/mnt/disks/NVMe2'. Aug 27 08:19:21 Tower emhttpd: shcmd (197): /usr/local/sbin/mount_image '/mnt/pool_nvme/system/docker/' /var/lib/docker 10 Aug 27 08:19:24 Tower emhttpd: shcmd (214): /usr/local/sbin/mount_image '/mnt/pool_nvme/system/libvirt.img' /etc/libvirt 1 Aug 27 08:35:19 Tower emhttpd: spinning down /dev/nvme1n1 Aug 27 08:35:19 Tower emhttpd: sdspin /dev/nvme1n1 down: 25 Aug 27 12:34:49 Tower kernel: nvme nvme1: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff Aug 27 12:34:49 Tower kernel: nvme nvme1: Does your device have a faulty power saving mode enabled? Aug 27 12:34:49 Tower kernel: nvme nvme1: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug Aug 27 12:34:49 Tower kernel: nvme 0000:09:00.0: Unable to change power state from D3cold to D0, device inaccessible Aug 27 12:34:49 Tower kernel: nvme nvme1: Removing after probe failure status: -19 Aug 27 12:34:49 Tower kernel: nvme1n1: detected capacity change from 1953525168 to 0 Aug 27 13:48:39 Tower kernel: XFS (nvme1n1p1): metadata I/O error in "xfs_imap_to_bp+0x50/0x70 [xfs]" at daddr 0x3ae0bca0 len 32 error 5 Aug 27 13:48:39 Tower kernel: XFS (nvme1n1p1): metadata I/O error in "xfs_imap_to_bp+0x50/0x70 [xfs]" at daddr 0x3ae0bca0 len 32 error 5 Aug 27 13:48:39 Tower kernel: XFS (nvme1n1p1): metadata I/O error in "xfs_imap_to_bp+0x50/0x70 [xfs]" at daddr 0x3ae0bca0 len 32 error 5 Aug 27 13:48:39 Tower kernel: XFS (nvme1n1p1): metadata I/O error in "xfs_imap_to_bp+0x50/0x70 [xfs]" at daddr 0x3ae0bca0 len 32 error 5 Aug 27 13:48:39 Tower kernel: XFS (nvme1n1p1): metadata I/O error in "xfs_imap_to_bp+0x50/0x70 [xfs]" at daddr 0x3ae0bca0 len 32 error 5 Aug 27 13:49:03 Tower kernel: XFS (nvme1n1p1): log I/O error -5 Aug 27 13:49:03 Tower kernel: XFS (nvme1n1p1): Filesystem has been shut down due to log error (0x2). Aug 27 13:49:03 Tower kernel: XFS (nvme1n1p1): Please unmount the filesystem and rectify the problem(s). Should I go back to to the previous Unraid release? Diagnostiics attached. Thanks in advance. tower-diagnostics-20240827-1549.zip
  17. Ooops, that it was. Thanks a lot. I switched that to once a month to avoid repeating notifications. Wish I could set it to notify once.
  18. I doubt that. My main server is at over 3 month uptime currently. Still no update notification. There must be something else that's failing.
  19. You're talking about these? Still no update banner in my browser. First time in many years as I wrote.
  20. I just noticed that there is a new Unraid release 6.12.11 by accident. Is there a reason why my three Unraid installations don't show the update banner? It's the first time in many, many years that the update banner doesn't show up. Diagnostics of bare metal server attached. tower-diagnostics-20240724-0718.zip
  21. Ich habe keine SAS3 Backplane, leite das also aus der Doku ab. SAS3 Modelle haben 4 (EL1) oder 8 (EL2) SFF-8643 Anschlüsse in Paaren angeordnet. Jedes Paar kann wahlfrei Eingang oder Ausgang sein. Der (EL1) oder die (EL2) Expander verhalten sich quasi wie Switche. Schließ einfach beide Ausgänge des 9300-8i an ein Paar der EL1 Backplane an. EL2 ist für Failover gedacht (z.B. 2 HBAs, einer fällt aus) EL1 und EL2 können kaskadieren (mehrere Backplanes hintereinander geschaltet) EL2 kann somit beides (mehrere Backplanes kaskadieren und Failover mit 2 HBAs) Doku zur Backplane hier: https://www.supermicro.com/manuals/other/BPN-SAS3-846EL.pdf Diese Kombination ist professionelles Server Equipment.
  22. Bei mir ist das ein SFF-8643/SFF-8087 Kabel. Was hattest Du noch mal für eine Backplane? Ausgang 9300-8i: 8643 (intern) Eingang Backplane: 8087 (BPN-SAS2-EL)
  23. Du denkst Du kannst das besser als der Linux Scheduler? Ist natürlich Deine Entscheidung. Viel Erfolg dabei.
  24. Die 9300-8i bzw. 8e sind standardmäßig im IT Modus. Ich habe sogar 2 neue günstig aus China bei eBay geschossen. Einfach eingebaut, lief (ohne Gewähr). Bei Gebrauchtkauf kann eine Kontrolle nicht schaden. Ich wundere mich gerade über die vielen verschiedenen passiven Lüfterbleche auf den HBAs diesen Typs bei eBay ... seltsam. Das Flashen ist hier irgendwo detailliert für Unraid beschrieben. Danach bin ich bei allen 9300ern vorgegangen um die Firmware zu aktualisieren. Da gibt es aber schon lange nix Neues mehr. Muss mal schauen ob ich das finde. Ich post es dann hier.
  25. Ich nutze seit vielen Jahren die Magenta App auf einem Fire-TV 4K Ultra Stick. Da ich auch Plex auf dem selben Stick nutze ist das eine sehr gute Abdeckung. Ich muss seit damals 5 EUR pro Monat zusätzlich zu meinem DSL Vertrag zahlen.

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.