motophil

Das hatte ich vorhin auch mal. Einfach powertop nochmal starten.

Vielen Dank, halt' uns bitte auf dem Laufenden 😊

After reading about the discontinuation of mysqueezebox.com here I installed this plugin yesterday. Afer setting the network type to host (see here) everything worked like a charm. So thanks a lot for this plugin! So here it is mentioned that the squeezebox server should be run with the --nomysqueezebox command line option. How can I do this with the plugin, or is it already done?

Hi everybody, I'm stuck here: I can't get a wireguard client on my raspberry pi to work. I've set up some other clients - all were straight forward: read the conf file with the wireguard client, connect, done. Now what I've done on my raspberry pi: Set up a new wireguard peer (remote access to server) in the unraid VPN settings, unzipped the zip file and copied the .conf file to my raspi. On my raspi: sudo apt install wireguard copy .conf file to /etc/wireguard/wg0.conf phil@audrey:~ $ sudo wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.1.7/32 dev wg0 [#] ip link set mtu 1412 up dev wg0 [#] ip -4 route add 192.168.187.16/32 dev wg0 [#] ip -4 route add 10.253.1.1/32 dev wg0 Now this looks fine to me. But then: phil@audrey:~ $ ping -c 3 10.253.1.1 PING 10.253.1.1 (10.253.1.1) 56(84) bytes of data. --- 10.253.1.1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2040ms Now I'm no networking whiz, so this is as far as debugging this went: Pinging myself with the 10.* IP address works: phil@audrey:~ $ ping -c 3 10.253.1.7 PING 10.253.1.7 (10.253.1.7) 56(84) bytes of data. 64 bytes from 10.253.1.7: icmp_seq=1 ttl=64 time=0.169 ms 64 bytes from 10.253.1.7: icmp_seq=2 ttl=64 time=0.159 ms 64 bytes from 10.253.1.7: icmp_seq=3 ttl=64 time=0.128 ms --- 10.253.1.7 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2039ms rtt min/avg/max/mdev = 0.128/0.152/0.169/0.017 ms some more: phil@audrey:~ $ ifconfig wg0 wg0: flags=209<UP,POINTOPOINT,RUNNING,NOARP> mtu 1412 inet 10.253.1.7 netmask 255.255.255.255 destination 10.253.1.7 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 26 bytes 3848 (3.7 KiB) TX errors 0 dropped 10 overruns 0 carrier 0 collisions 0 phil@audrey:~ $ sudo wg interface: wg0 public key: (hidden by me) private key: (hidden) listening port: 45918 peer: (hidden by me) preshared key: (hidden) endpoint: [2001:16b8:a02f:a8eb:2e3a:fdff:fec7:1d80]:51968 allowed ips: 10.253.1.1/32, 192.168.187.16/32 transfer: 0 B received, 3.76 KiB sent phil@audrey:~ $ ip address show dev wg0 5: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1412 qdisc noqueue state UNKNOWN group default qlen 1000 link/none inet 10.253.1.7/32 scope global wg0 valid_lft forever preferred_lft forever Now I'm stuck. Any help is appreciated.

ASRock rechnet im Handbuch auf Seite 7 eine HDD mit 15W. Das ist für mein Gefühl zumindest beim Anlaufen eher niedrig gegriffen. Meine zwei Toshiba MG08-D versorgt das Board aber anstandslos, und zieht dabei DC beim Einschalten 60-70W.

RAID verbessert die Verfügbarkeit, die Datensicherheit aber kaum.

I learned that kvm does not remove the space freed by trim from the img file automatically. This can be done with the qemu-img convert command. qemu-img convert -c -O qcow2 input.img output.img This converts a disk image into another format - in this case, qcow2 format. Since input is qcow2 format already it is not converted, just copied - but empty space is omitted from the copy. The -c option also enables compression, which slows down access to the image but saves a lot of space. So to clean up and compress your image, power down your VM, open a root console, cd into the matching directory (usually /mnt/user/<VMName>) and do the following: mv vdisk1.img vdisk1.img.bak qemu-img convert -c -O qcow2 vdisk1.img.bak vdisk1.img chown nobody vdisk1.img chgrp users vdisk1.img chmod 777 vdisk1.img If your VM starts up fine, you can delete the vdisk.img.bak file.

Der ist Notwendig weil sonst die Temperatur der Platten beim parity check auf über 45°C geht. 200/min reichen aber dafür dass sie bei 40°C bleibt. Für den Prozessor ist er an sich nicht nötig, der drosselt halt wenn ihm zu warm wird. Ich habe ihn so eingestellt dass er ab 70°C Prozessortemperatur auf Vollast läuft.

Memtest sagt Errors: 0 nach einigen Stunden. Ohne manuelle Eingriffe in die Konfiguration. Hier ist mein Aufbau:

Hi all, I've found this and subsequently this thread, but nothing about linux guests. I would like to have my img files as small as possible (of course), so I tried to set it up as an SSD similar to Windows. This seems to work now, but I'm not very experienced with this stuff so this is a request for improvements as well as a how-to for others with similar little experience. When creating the VM, I chose: Primary vDisk bus: SCSI Primary vDisk type: qcow2 (if I choose raw here the img file will be full size even before first boot) Manually edited the VM XML file and added discard='unmap' <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback' discard='unmap'/> <source file='/mnt/user/domains/Geraldine/vdisk1.img' index='2'/> <backingStore/> <target dev='hdc' bus='scsi'/> <serial>vdisk1</serial> <boot order='1'/> <alias name='scsi0-0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> Now I installed ubuntu server minimal. This tells me to check lsblk --discard to see if my (virtual) drive supports trim, so I did: phil@geraldine:~$ lsblk --discard NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO sda 0 4K 1G 0 ├─sda1 0 4K 1G 0 ├─sda2 0 4K 1G 0 └─sda3 0 4K 1G 0 └─ubuntu--vg-ubuntu--lv 0 4K 1G 0 sr0 0 0B 0B 0 So the DISC-GRAN and DISC-MAX beeing non-zero tells me it does. Also, lvm.conf has issue_discards = 1 phil@geraldine:~$ fgrep issue_discards /etc/lvm/lvm.conf # Configuration option devices/issue_discards. issue_discards = 1 But my /etc/fstab knows nothing about discard: phil@geraldine:~$ fgrep discard /etc/fstab phil@geraldine:~$ so i added it manually phil@geraldine:~$ fgrep discard /etc/fstab /dev/disk/by-id/dm-uuid-LVM-kcbZKFWiEPoidmRd4HaCFzVI2y7GhD9QHQdKDxrBf5cDOvyjd4PTF0iX0wfApBXL / ext4 defaults,discard 0 1 /dev/disk/by-uuid/84b65076-9b7c-4efe-8ce8-06d5688c737f /boot ext4 defaults,discard 0 1 /dev/disk/by-uuid/0E6B-E392 /boot/efi vfat defaults,discard 0 1 phil@geraldine:~$ also did update-initramfs -c -k $(uname -r) because I wasn't sure if I had to and rebooted. Now the discs are mounted with the discard option. phil@geraldine:~$ mount | grep discard /dev/mapper/ubuntu--vg-ubuntu--lv on / type ext4 (rw,relatime,discard) /dev/sda2 on /boot type ext4 (rw,relatime,discard) /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,discard) Now hdparm still does not mention TRIM: phil@geraldine:~$ sudo hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Standards: Likely used: 1 Configuration: Logical max current cylinders 0 0 heads 0 0 sectors/track 0 0 -- Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 0 MBytes device size with M = 1000*1000: 0 MBytes cache/buffer size = unknown Capabilities: IORDY not likely Cannot perform double-word IO R/W multiple sector transfer: not supported DMA: not supported PIO: pio0 But it seems to be working: phil@geraldine:~$ sudo fstrim -A -v /boot/efi: 1 GiB (1118625792 bytes) trimmed on /dev/disk/by-uuid/0E6B-E392 /boot: 1.8 GiB (1898135552 bytes) trimmed on /dev/disk/by-uuid/84b65076-9b7c-4efe-8ce8-06d5688c737f /: 54.7 GiB (58719956992 bytes) trimmed on /dev/disk/by-id/dm-uuid-LVM-kcbZKFWiEPoidmRd4HaCFzVI2y7GhD9QHQdKDxrBf5cDOvyjd4PTF0iX0wfApBXL So, please feel free to comment. Thank you.

Never mind. I rebooted my server in GUI mode, it worked there. But why?

Hi there, I'm having trouble getting a trial key. What happened so far: I toyed around with UNRAID and a trial license on an old PC. Everything worked fine. This license may have expired, I'm not sure. Now I bought new hardware, including a new USB stick. Manually installed UNRAID 6.12.6 from scratch using my linux box. The USB stick is a 64GB Samsung Bar Fit, I'm not sure wether I should post the GUID here Boots fine. As soon as I log in with a browser on another machine, the "Let's unleash your hardware!" window has an error there: NetworkError when attempting to fetch resource. When I press the start trial button, this changes to: TypeError: NetworkError when attempting to fetch resource. So I searched the forum, here are a few outputs typing commands into the root console: root@Kenny:~# ping -c3 www.google.com PING www.google.com (216.58.212.132) 56(84) bytes of data. 64 bytes from ams15s21-in-f4.1e100.net (216.58.212.132): icmp_seq=1 ttl=119 time=6.46 ms 64 bytes from ams15s21-in-f4.1e100.net (216.58.212.132): icmp_seq=2 ttl=119 time=6.09 ms 64 bytes from ams15s21-in-f4.1e100.net (216.58.212.132): icmp_seq=3 ttl=119 time=5.89 ms --- www.google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 5.888/6.144/6.455/0.234 ms root@Kenny:~# date Fri Jan 5 15:56:42 CET 2024 root@Kenny:~# hwclock 2024-01-05 15:56:46.180539+01:00 root@Kenny:~# wget https://keys.lime-technology.com/account/trial --2024-01-05 16:01:55-- https://keys.lime-technology.com/account/trial Resolving keys.lime-technology.com (keys.lime-technology.com)... 54.149.176.35 Connecting to keys.lime-technology.com (keys.lime-technology.com)|54.149.176.35|:443... connected. HTTP request sent, awaiting response... 403 Forbidden 2024-01-05 16:01:56 ERROR 403: Forbidden. root@Kenny:~# So internet connection is fine, date/time and BIOS date/time seem to be fine, but the key server returns forbidden. Any ideas? kenny-diagnostics-20240105-1603.zip

Ich glaub da probier ich lieber mal das von der Kompatibilitätsliste. Ich werde berichten.

Funktioniert einfach nur so im Betrieb oder hast Du mal memtest86 drüber laufen lassen?