All Activity

Sharing my experience with the manual installation process from a linux OS distro: Ubuntu 22.04 Initially I had formatted my USB drive from the "Files" (nautilus --browser) aka file explorer gui application by right clicking the USB and choosing format "For all systems and devices (FAT)" I double checked the format from the "Disks" utility to find W95 FAT32 (LBA) (0x0c) - I changed this to W95 FAT32 (0x0b) (As of this moment, I'm not sure if this matters.) After extracting the download archive for 6.12.10 onto the USB, I copied the `make_bootable_linux` file to my local hard drive and continued with the installation instructions. Here's what I found: "unmount (not eject) USB drive" step is unnecessary. The USB is unmounted from the script `make_bootable_linux.sh` that is called from `make_bootable_linux` the `mtools` package is required for manipulating MSDOS files (not included with Ubuntu 22.04 - `sudo apt install mtools`) certain files located in the download archive need need execute permission - the current `make_bootable_linux` script does not handle this. I commented out lines 86,87,98, and 99 to avoid overwriting and clean up of the /tmp/UNRAID/syslinux directory. Then added execution permissions to `/tmp/UNRAID/syslinux/make_bootable_linux.sh` and `/tmp/UNRAID/syslinux/syslinux_linux`. This step could be handled upstream so these files already have execute permissions when downloading the archive or modifications made to the `make_bootable_linux` script. also of note, the current script(s) do(es) not gracefully handle errors and appears to the user `INFO: the Unraid OS USB Flash drive is now bootable and may be ejected.` even if the above steps are not taken. After performing these steps, `sudo bash ./make_bootable_linux` from the directory I copied this file to, now works as intended. I was able to successfully make the USB bootable and startup Unraid.

good morning, I currently have 3 standard licenses attached to my account. However, I only use 2 of the 3. I would like to know what to do if I want to sell my third license to a third party. Basically, how do I detach it from my account? Thank you in advance for the information. Have a nice day! Cognotte

Does no one use IPv6 inside Unraids docker? Could someone do a ping test from inside a container to a public server and observe if some "address unreachable" occur? I still need to retest with a native portainer install. Somehow I got a feeling that this is an Unraid thing...

Can you please post your Diagnostics, I'm looking currently into a way to ignore the chip.

Was hast du denn alles auf dem alten am laufen? (VM/Docker/Shares/etc.) Dann mach die schnelle NVME zum Cachepool. Achte darauf das wenn du da deine Docker am laufen hast, das du die regelmässig sicherst. Wie willst du das umsetzen? Pack die langsame SSD ins Array. Sinnvoll und Sinnfrei ist immer Ansichtssache😊 Was genau ? (Docker umziehen / Daten verschieben /VMs umziehen) Die aktuelle SSD kommt ja mit in den Server, von daher easy. Wenn du die alte Platte im neuen PC integriert hast und du den USB stick am neuen System startetst, sollte die Kiste direkt laufen. Anschliessend stopst du mal das array und fügst einen Pool mit der NVME hinzu. Anschliessend unter Freigabe bei Appdata auf Cach only stellen (Achtung Appbackups einrichten nicht vergessen, weil du ja Cache only hast.) Deine Backups kannst du dann entweser auf eine Freigabe (z.B. Backup) packen. (die Begrenzung mit 50/50 256GB für Backups, macht für mich kein Sinn und wüsste ich garnicht wie man das umsetzen soll)

Es hat ja auch seine Vorteile. Aber die erkauft man sich eben mit diesen kurzen Spikes. Die Software läuft eben und das benötigt elektrische Energie.

You can do it either way and it doesn't matter much. I'm more comfortable pulling it from the source machine to the destination since it feels a bit more safe to me since you can write a script that is running on server start that starts the backup, shuts down the machine automatically if needed and if this machine is only powered on for a backup. Please don't use the root directory, you always have to use the id_rsa from the /luckybackup/.ssh directory not root because otherwise it will be wiped on a container update. Please post a screenshot from your Docker template. Then you selected the wrong keys. BTW You don't have to create new keys, please use the existing ones which are located in /luckybackup/.ssh since they are individually created for each installation and as said above, please don't use the keys from /root/.ssh

Does not work currently on 6.12.10 because the Kernel is simply too old. You have to wait for a 6.13.x RC release and try there, if it then is still not working then please report it here.

I don't know how they are doing it but it can't be a real WoL package because that simply won't work. No, but if you choose the power outlet method and bind the power outlets to your HomeAssistant instance then it would be of course possible. Than this is your best bet.

dann hol es mal runter, Neustart und schaue dann

Same. First time it happens below byte 22000000000000. So if I put the disk in the array as parity, can this be ok? Maybe it's related only to the plugin's zeroing process? Alternatively if the disk is no good, I'll still will get an error, and then I guess I'll replace it. Apr 25 01:57:41 preclear_disk_ZGG46T0A_10918: Zeroing: dd output: 21998195441664 bytes (22 TB, 20 TiB) copied, 98221.6 s, 224 MB/s Apr 25 01:57:41 preclear_disk_ZGG46T0A_10918: Zeroing: dd output: 10490310+0 records in Apr 25 01:57:41 preclear_disk_ZGG46T0A_10918: Zeroing: dd output: 10490310+0 records out Apr 25 01:57:41 preclear_disk_ZGG46T0A_10918: Zeroing: dd output: 21999774597120 bytes (22 TB, 20 TiB) copied, 98233.6 s, 224 MB/s Apr 25 01:57:41 preclear_disk_ZGG46T0A_10918: dd process hung at 21999776694272, killing ... Apr 25 01:57:41 preclear_disk_ZGG46T0A_10918: Zeroing: zeroing the disk started 2 of 5 retries... Apr 25 01:57:41 preclear_disk_ZGG46T0A_10918: Continuing disk write on byte 21999774597120 Apr 25 02:13:39 preclear_disk_ZGG46T0A_10918: Zeroing: dd output: Apr 25 02:13:39 preclear_disk_ZGG46T0A_10918: dd process hung at 0, killing ... Apr 25 02:13:39 preclear_disk_ZGG46T0A_10918: Zeroing: zeroing the disk started 3 of 5 retries... Apr 25 02:13:39 preclear_disk_ZGG46T0A_10918: Zeroing: emptying the MBR. Apr 25 08:01:50 preclear_disk_ZGG46T0A_10918: Zeroing: progress - 25% zeroed @ 270 MB/s

I also don't see why the devs don't just make a option to have both ipvaln and macvlan and have them veth/ @ tap tun to teh eth0 or interface of choosing in bridge... I have a few ideas to answer, but the devs would be better able to answer... as its is catered to the end users for point click done. Most of this has to go back to the original decision to move off macvlan due to nic promisic mode and not all nic supported it. Then the github macvlan bug report and later when they tried to remove macvaln and move to ipvlan.... Version 6.9 default didn't have a ipvlan docker driver and when they transitioned broke networking. I will never stop sharing this video and think it would enlighten you on to some of the ins and outs to docker networking.

Thank you! ....

the problem with unifi and ipvaln is that everything from dockers to services use the same mac address and are not logged correctly in the unifi application. macvlan must be used for unifi...

Ich hab das heute mal versucht, aber offensichtlich muss man da wohl sich an Nextcloud wenden (sorry aber mein English is not the Yellow from the Egg): weiss jemand was er mit dem Post Script meint?

per top in diagnostic you have a zombie process most likely a bad command that killed something but not its parent.. Still reviewing that latter. 32556 root 20 0 0 0 0 Z 0.0 0.0 0:00.00 sh ^-may have been caused by creating diagnostic... per diagnosis, you have a strange go file that remount the log file. Messing with docker system permissions... ^this could also be doing things it shouldn't... #!/bin/bash ##Enable Multi-Gen LRU for better memory management 6.12.x and higher## echo y > /sys/kernel/mm/lru_gen/enabled # Start the Management Utility /usr/local/sbin/emhttp -p 80 & #Bash Profile #Pulseway setup ###cp /boot/pulseway/config.xml /etc/pulseway/config.xml ###cp /boot/pulseway/pulseway.id /var/pulseway/pulseway.id ###Pulse way commands ###/etc/rc.d/rc.pulseway (stop/start/restart) ###/etc/rc.d/rc.pulseway start #Hardware video Transcode Enable and TMP File System #modprobe i915 ***line removed*** #chmod -R 777 /dev/dri #mkdir /tmp/PlexRamScratch #chmod -R 777 /tmp/PlexRamScratch #mount -t tmpfs -o size=32g tmpfs /tmp/PlexRamScratch mount -o remount,size=512m /var/log/ #Docker Shell cp /boot/custom/docker-shell /usr/local/bin chmod 755 /usr/local/bin/docker-shell #SSH Keys Copy and enable #mkdir /root/.ssh #chmod 700 /root/.ssh #cp /boot/config/ssh/authorized_keys /root/.ssh/ #chmod 600 /root/.ssh/authorized_keys Honestly, alot to go on here. Looks like your using ipvlan to your wireguard tunnel. you have disk write issues vias FCP in syslog... with weird docker bridging with dockers on the vpn. *When running Unifi I highly recommend to use macvlan... so turn off bridging. and have dockers custom network set to macvlan... Apr 24 04:10:00 Thor rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="19275" x-info="https://www.rsyslog.com"] rsyslogd was HUPed ### [PREVIOUS LINE REPEATED 4 TIMES] ### Apr 24 08:30:14 Thor root: Fix Common Problems Version 2024.04.14 Apr 24 08:30:19 Thor root: Fix Common Problems: Other Warning: Docker application unifi-controller has moderator comments listed Apr 24 08:30:23 Thor root: Fix Common Problems: Warning: Write Cache is disabled on disk9 ** Ignored if you have a docker set to host and this docker has a web ui it will override unraids web ui ports.. Honestly, with quite a bit going on it will be hard to pinpoint what causing the problems... looks like the system is getting an static ip: Then we have connections. Apr 22 20:31:31 Thor avahi-daemon[20172]: Registering new address record for 10.0.0.87 on br0.IPv4. But your system has a bunch of veth taped for ipv6... lo UNKNOWN 127.0.0.1/8 ::1/128 tunl0@NONE DOWN eth0 UP eth1 DOWN br0 UP 10.0.0.87/24 metric 1 vhost1@eth1 LOWERLAYERDOWN wg0 UNKNOWN 10.0.3.1/32 br-7f0a9fe8c228 UP 172.18.0.1/16 fe80::42:3fff:fee6:d8aa/64 br-d773e863805b DOWN 172.31.200.1/24 docker0 DOWN 172.17.0.1/16 veth3d6534d@if13 UP fe80::c49f:bfff:fe17:160e/64 virbr0 DOWN 192.168.122.1/24 veth71a1162@if48 UP fe80::d435:8ff:fe0a:26dc/64 veth5162665@if56 UP fe80::98e8:c2ff:fec8:643a/64 veth6f8d859@if58 UP fe80::d07d:3fff:fe38:afc7/64 vethefb7d55@if60 UP fe80::cc49:4dff:fe81:e468/64 veth5491d77@if62 UP fe80::58bc:efff:fe42:add0/64 vethf386ea9@if64 UP fe80::583b:e2ff:fec2:ecc5/64 veth53f22ab@if66 UP fe80::dc97:ceff:fee4:c25b/64 vethac7393c@if68 UP fe80::1458:5bff:fee5:8e26/64 vethe8f5bfa@if71 UP fe80::bc18:95ff:fe5a:13c7/64 veth95b8b55@if73 UP fe80::d3:f2ff:fe90:de58/64 veth1213c5f@if75 UP fe80::800b:55ff:feed:b1b6/64 veth467cf9c@if77 UP fe80::3cca:12ff:feb6:ff5d/64 veth9b30110@if79 UP fe80::840a:e2ff:fe75:7450/64 vethc107e26@if81 UP fe80::c4ef:31ff:fecc:4ec4/64 veth153f6d8@if83 UP fe80::70a6:1dff:fe16:3f50/64 vethfa5b6aa@if85 UP fe80::5028:8aff:fe5b:f40/64 Made harder as it apears you are trying to omit somethign in the logs... previous line repeated x times is not normal to see in dmesg... So my bet is a misconfigured bind that is caused as it appears the eth1 is the primary adapter due to how vhost taped it and that eth1 is down so is the bind to the web server... -Not sure where nginx web server configs is located, as this may need to be edited to change adapters and restarted to regain web UI. ^BUT! you have a lot going on without any other info so this is a guess... It appears to be an intermittent issue as well... Not sure where to start for you...

There is an app I'd like to run on my server: AIrenamer Not too sure how it works yet but I thought I'd ask here in case there is a more Unraid friendly option: Purpose of application: identify what is in the image and name the file accordingly with key words.

It can be 30 minutes or 2 hours, but I will lose access to the WebGUI. The browser will say it cannot access the server, but my router says it's still connected via ethernet. tower-syslog-20240425-0401.zip tower-diagnostics-20240424-2352.zip tower-diagnostics-20240424-1642.zip

The k10temp ones are the cpu, the cpu consist of 2 chiplets ccd1 and 2 i see them both in your drop down menu, the tctl is the total package temperature. Set the tctl as the cpu temp reader.

are unraid shares still accessible? ssh still accessible? website error # ? 500 / 404 ? reviewing current diagnostic.

Ja, das hatte ich damals als ich Unraid aufgesetzt habe mit installiert, weil es Teil vom Tutorial von "The Geek Freaks" war.

Another update thanks to realizelol! v0.2.8 - 2024/04/23 Forks and Spoons Only fix backup of VM names containing spaces (@realizelol) indentation fixes (@realizelol) update loops to break the row via semicolon (@realizelol) fix disk_prefix in $vdisk_path variable (@realizelol) fix counting vDisks by using Disks instead of "file sources" + Silence: STDERR output to /dev/null (@realizelol) add ability for the script to handle OS suspended VMs (@realizelol)

give this a try and add the parameter PHP_UPLOAD_LIMIT and set it to a bigger size

? have you tried to reboot the system since the power outage? you may have that ip address in use on the netwrok form your log: Apr 24 19:06:12 Tower root: Starting Nginx server daemon... Apr 24 19:06:12 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 127.0.0.1:445 failed (98: Address already in use) Apr 24 19:06:12 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 192.168.1.180:445 failed (98: Address already in use) Apr 24 19:06:13 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 127.0.0.1:445 failed (98: Address already in use) Apr 24 19:06:13 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 192.168.1.180:445 failed (98: Address already in use) Apr 24 19:06:13 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 127.0.0.1:445 failed (98: Address already in use) Apr 24 19:06:13 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 192.168.1.180:445 failed (98: Address already in use) Apr 24 19:06:14 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 127.0.0.1:445 failed (98: Address already in use) Apr 24 19:06:14 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 192.168.1.180:445 failed (98: Address already in use) Apr 24 19:06:14 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 127.0.0.1:445 failed (98: Address already in use) Apr 24 19:06:14 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 192.168.1.180:445 failed (98: Address already in use) whats the current output of terminal command ip a you may need to change the ip addresses to another ip on your network. One that is not in use on the network.

I've got unRAID version 6.12.10. Motherboard: Intel DQ87PG Network NIC: Intel I225-V The onboard NIC is working, but it seems the PCIE NIC is not being detected. The NIC is in the top-most PCIE port, and my LSI HBA is in the 16x PCIE port. Diagnostics attached, my gut feeling is the motherboard isn't playing nice with the NIC but wanted to see what others think. Thanks in advance! bigbessie-diagnostics-20240425-1608.zip