Brydezen

@ljm42 I got a five unclean shutdown logs all referring to the same issue (the latest two already posted in this thread). That it is unable to unmount the cache drive where the docker.img file lives. I have since downgraded back to 6.1.5 and everything works just as expected again. All of them seems to have stopped the docker service. But is still unable to unmount for whatever reason.

Hi. I would like to add to this thread. This issue seems very random indeed. On the 4th of july (so two days from posting this) I disabled docker in the web ui. Since according to my logs from other days (with the same issue) it was docker that kept the disk unmountable. So I disabled docker before trying to shutdown the server. And to my surprise that worked - or so I thought. Then yesterday (5th) I tried the same thing again but with no luck this time. This issue seems so be somewhat random. I will add two logs. One from yesterday and the one from the 4th. EDIT: For the time being I think I will go back to 6.15 since I dont even use any of the newer features like ZFS or have rearranged much of the UI. I hope this issue will be addressed and fixed somewhat quickly tower-diagnostics-20230706-0047.zip tower-diagnostics-20230704-0055.zip

Hello. I have a weird problem I cannot figure out. Some time ago every time I shutdown my server (hitting the power button or using the webui) my unraid server seems to report it shutdown "unclean" and I have no idea why or how to fix it. I can't seem to find anything wrong. So I hope someone here is able to figure it out. I have looked through the logs on the usb stick multiple times but i'm totally lost. I have attatched two diagnostics. One that was generated when the server shutdown. And another right after it rebooted. Thank you! tower-diagnostics-20230227-1152 - shutdown.zip tower-diagnostics-20230227-1205 - rebooted.zip

That's great. I have tried this on my own VM. It does get more usable but is still unable to play games using it. So i'm shopping for new hardware soon. Was time for a upgrade anyways.

Hello. I just decided to take the jump to 6.9.2 today, as the threads seems to have slowed down on bug reporting. Everything worked just fine on 6.8.3. After the first reboot into 6.9.2 my main windows 10 vm was really slow. And I check the ssd and it seemed to have been effected in regards to the 1 MiB alignment "bug". So I moved everything from it and reformatted using unassigned devices plugin. And moved my vm's back. Everything seemed fine for around 30 minutes and it just crashed on me. The funny thing is that it works just fine using VNC. Their is no problems at all. Everything seems to work fine just up until the gpu driver seems to be loaded in windows. Then everything freezes or crashes. I have tried rebooting. removing the gpu from vfio and back in. Nothing seems to help me at all. - I then found this thread and followed the guide by removing all the gpu drivers using vnc. Added the gpu back in. Booted just fine into windows with display on my screens. Then when I tried installing the gpu driver it just crashed. And now i'm back to square one. I got a flash drive backup from before upgrading. So might just end up downgrading again. But I hope someone can help me out here. I get this line almost everytime I boot up a VM with my gpu passed through to it. Tower kernel: vfio-pci 0000:81:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 - not sure if this is intended or not. I have not seen it before. But could ofc be a 6.9 thing. Best regards, Brydezen tower-diagnostics-20210410-2236.zip

I only have one user named lol and the password is also lol. Does it only work if the username is admin? EDIT: I just tried doing the auth in a new browser (firefox) and it worked flawlessly. But chrome seems to mess me up.

- the error log says password mismatch and that is no way I typed "lol" wrong four times. And it also keeps saying that "admin" was not found. 2019/10/10 19:00:46 [notice] 1022#1022: signal process started 2019/10/10 19:01:00 [notice] 1031#1031: signal process started 2019/10/10 19:01:02 [error] 1032#1032: *115 user "admin" was not found in "/data/access/2", client: 176.XXX.XXX.X, server: portainer.domain.tld, request: "GET / HTTP/2.0", host: "portainer.domain.tld", referrer: "https://proxy.domain.tld/nginx/proxy"

Still can't get it to work.

anyone know how or if this awesome docker support htaccess password protection?

I'm running the nginx-proxy combo with let's encrypt companion. So i'm trying to directing it to a https version. So I can use it simple over the internet without fear of mitm sniffing of my password. Can get almost every other docker to work with it just fine. But keep getting 502 errors here. Best regards

Regarding the mineos docker; How can I get it to work with nginx-proxy on a remote server? No matter what I do i keep getting 502 errors bad gateway.

I keep getting a connection to server error when trying to sign in on the app store? I already own a mac, and know my account is working. And i didn't type the password wrong either. :-( followed the guide for high sierra on point

I tried the first commands with the smartfan - and apperently the cpu_1 is the only one willing to change the rpm. Linux 4.9.30-unRAID. root@Tower:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 17 | CPU_FAN1_1 | Fan | 700.00 | RPM | 'OK' 18 | CPU_FAN2_1 | Fan | 700.00 | RPM | 'OK' 19 | REAR_FAN1 | Fan | N/A | RPM | N/A 20 | REAR_FAN2 | Fan | N/A | RPM | N/A 21 | FRNT_FAN1 | Fan | 700.00 | RPM | 'OK' 22 | FRNT_FAN2 | Fan | 900.00 | RPM | 'OK' 23 | FRNT_FAN3 | Fan | 900.00 | RPM | 'OK' 24 | FRNT_FAN4 | Fan | 1200.00 | RPM | 'OK' 25 | CPU_FAN1_2 | Fan | N/A | RPM | N/A 26 | CPU_FAN2_2 | Fan | N/A | RPM | N/A root@Tower:~# ipmi-raw 00 3a 01 01 64 64 64 64 64 rcvd: 01 00 root@Tower:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 17 | CPU_FAN1_1 | Fan | 2000.00 | RPM | 'OK' 18 | CPU_FAN2_1 | Fan | 700.00 | RPM | 'OK' 19 | REAR_FAN1 | Fan | N/A | RPM | N/A 20 | REAR_FAN2 | Fan | N/A | RPM | N/A 21 | FRNT_FAN1 | Fan | 700.00 | RPM | 'OK' 22 | FRNT_FAN2 | Fan | 900.00 | RPM | 'OK' 23 | FRNT_FAN3 | Fan | 900.00 | RPM | 'OK' 24 | FRNT_FAN4 | Fan | 1200.00 | RPM | 'OK' 25 | CPU_FAN1_2 | Fan | N/A | RPM | N/A 26 | CPU_FAN2_2 | Fan | N/A | RPM | N/A root@Tower:~# ipmi-raw 00 3a 01 01 32 32 32 32 32 rcvd: 01 00 root@Tower:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 17 | CPU_FAN1_1 | Fan | 1100.00 | RPM | 'OK' 18 | CPU_FAN2_1 | Fan | 1200.00 | RPM | 'OK' 19 | REAR_FAN1 | Fan | N/A | RPM | N/A 20 | REAR_FAN2 | Fan | N/A | RPM | N/A 21 | FRNT_FAN1 | Fan | 700.00 | RPM | 'OK' 22 | FRNT_FAN2 | Fan | 900.00 | RPM | 'OK' 23 | FRNT_FAN3 | Fan | 900.00 | RPM | 'OK' 24 | FRNT_FAN4 | Fan | 1200.00 | RPM | 'OK' 25 | CPU_FAN1_2 | Fan | N/A | RPM | N/A 26 | CPU_FAN2_2 | Fan | N/A | RPM | N/A root@Tower:~# ipmi-raw 00 3a 01 01 00 00 00 00 00 rcvd: 01 00 root@Tower:~# ipmi-sensors -t fan ID | Name | Type | Reading | Units | Event 17 | CPU_FAN1_1 | Fan | 0.00 | RPM | 'At or Below (<=) Lower Non-Critical Threshold' 18 | CPU_FAN2_1 | Fan | 700.00 | RPM | 'OK' 19 | REAR_FAN1 | Fan | N/A | RPM | N/A 20 | REAR_FAN2 | Fan | N/A | RPM | N/A 21 | FRNT_FAN1 | Fan | 700.00 | RPM | 'OK' 22 | FRNT_FAN2 | Fan | 900.00 | RPM | 'OK' 23 | FRNT_FAN3 | Fan | 900.00 | RPM | 'OK' 24 | FRNT_FAN4 | Fan | 1200.00 | RPM | 'OK' 25 | CPU_FAN1_2 | Fan | N/A | RPM | N/A 26 | CPU_FAN2_2 | Fan | N/A | RPM | N/A

Hi guys, I have an AsRock EP2C602 dual socket motherboard, with two CPU fans (that is getting auto-detected by the configure button) - but got 4 more fans, all connected to the FRNT_FAN's 1 thru 4 - but none of them are getting detected like the CPU fans. But they are all getting listed in the Readings tab in the IPMI plugin. Both my BIOS (1.80) and BMC (02.07.00) is the newest versions available on ASRocks website for my mb. I have tried so many things now. Deleting the plugin, deleting the config files from the boot usb, reinstalled the plugin rebooted the server. But nothing seems to help me. Can someone please help me the fans are slowly killing me with their high rpm Best regards, Bryde