MrLondon
-
Posts
341 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by MrLondon
-
-
Hi there,
I can see in my syslog lots of these error message
May 16 10:53:43 Tower kernel: ata2.00: status: { DRDY }
May 16 10:53:43 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED
May 16 10:53:43 Tower kernel: ata2.00: cmd 60/08:30:b0:89:2c/00:00:43:00:00/40 tag 6 ncq dma 4096 in
May 16 10:53:43 Tower kernel: res 40/00:00:a8:2d:79/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
May 16 10:53:43 Tower kernel: ata2.00: status: { DRDY }
May 16 10:53:43 Tower kernel: ata2.00: failed command: WRITE FPDMA QUEUED
May 16 10:53:43 Tower kernel: ata2.00: cmd 61/00:a8:a8:29:79/04:00:00:00:00/40 tag 21 ncq dma 524288 out
May 16 10:53:43 Tower kernel: res 40/00:00:a8:2d:79/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
May 16 10:53:43 Tower kernel: ata2.00: status: { DRDY }
May 16 10:53:43 Tower kernel: ata2.00: failed command: WRITE FPDMA QUEUED
May 16 10:53:43 Tower kernel: ata2.00: cmd 61/68:b0:a8:2d:79/02:00:00:00:00/40 tag 22 ncq dma 315392 out
May 16 10:53:43 Tower kernel: res 40/00:00:a8:2d:79/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
May 16 10:53:43 Tower kernel: ata2.00: status: { DRDY }
May 16 10:53:43 Tower kernel: ata2: hard resetting link
May 16 10:53:49 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)
May 16 10:53:53 Tower kernel: ata2: COMRESET failed (errno=-16)
May 16 10:53:53 Tower kernel: ata2: hard resetting link
May 16 10:53:54 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 16 10:53:54 Tower kernel: ata2.00: supports DRM functions and may not be fully accessibleis this from the SAS controller or a specific drive? any help greatly appreciated.
-
On 3/10/2022 at 6:13 PM, Josh.5 said:
I can possibly help...
How did you setup the server to that /dev/dri was available in unraid?I also have the error message [AVHWDeviceContext @ 0x5574e0b15d00] Error setting child device handle: -17 when trying to use the Intel TOP plugin, when I type in the console the intel_gpu_top I get the following:
intel-gpu-top: Intel Alderlake_s (Gen12) @ /dev/dri/card0 - 0/ 0 MHz; 100% RC6; 0.00/ 7.66 W; 0 irqs/s
ENGINES BUSY MI_SEMA MI_WAIT
Render/3D 0.00% | | 0% 0%
Blitter 0.00% | | 0% 0%
Video 0.00% | | 0% 0%
VideoEnhance 0.00% | | 0% 0%any assistance is greatly appreciated.
-
12 hours ago, SimonF said:
its a 12400k there on post on 12th gen thread.
@MrLondon have you blacklisted the i915 driver on rc3?
I have not blacklisted anything, do you believe that it would work if I blacklist it with Alder Lake?
-
yes I hace a 12400 Alder Lake CPU here is the diagnostics file
-
as 6.10 RC3 was released is the iGPU still not supported as the top plugin is still not working when I type intel_gpu_top it still does not find anything, or will this still take a while before this will be supported
-
Thanks for the update, I actually wanted to use the plugin for unmanic to concert my old movie files, I guess I have to wait till 6.10rc3 which is supposed to be the new kernel
-
I installed the Intel Top plugin and also plugged a dummy HDMI into the HDMI port on the motherboard but still getting the following error message in the terminal:
root@Tower:~# intel_gpu_top
No device filter specified and no discrete/integrated i915 devices found
root@Tower:~# modsense i915
bash: modsense: command not found
root@Tower:~# modprobe i915
root@Tower:~# ls /dev/dri
/bin/ls: cannot access '/dev/dri': No such file or directory
root@Tower:~# intel_gpu_top
No device filter specified and no discrete/integrated i915 devices foundDo I need to reboot the array? I have attached the diagnostic file
-
I was not able to use my z690 with i5-12400 with 6.9.2 I had to use 6.10-rc2 with that it is running, just the Intel 2.5 gbe NIC is not supported yet, that will be with rc3.
-
thanks you are correct, I have installed the plugin and all the fans are now showing.
-
ChatNoir you saved me, that was exactly the problem, would have never though of that. By the way has anybody managed to get the PWM controller working with the z690 board as somehow I was unable to get it detected, however sensors-detect is seeing it.
-
1
-
-
certainly looking great, cannot wait for version 1.7 fantastic work
-
1
-
-
sorry to hijack this thread, already asked in Discord but as others also have the MSI Z690 Pro -A wifi DDR4 I have updated the bios to the 13.12.2021 version and I am always getting into the bios screen it never seems to attempt to boot the unraid USB stick. I can see the UEFI USB key detected and I put it has highest boot priority and the bios is in UEFI mode and Secure boot is disabled but it never boots into UnRaid. Any suggestions what you did to get it working?
-
24 minutes ago, nikky said:
MYSQL_PORT_3306_TCP_ADDR'='192.168.0.24'
try changing this to -
MYSQL_PORT_3306_TCP_ADDR'='mysql'changed but still getting connection denied
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='snipe-it' --net='bridge' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'NGINX_APP_URL'='192.168.0.24' -e 'MYSQL_PORT_3306_TCP_ADDR'='mysql' -e 'MYSQL_PORT_3306_TCP_PORT'='3306' -e 'MYSQL_DATABASE'='snipeit' -e 'MYSQL_USER'='snipeit' -e 'MYSQL_PASSWORD'='snipeit' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -p '8084:80/tcp' -v '/mnt/cache/appdata/snipe-it':'/config':'rw' 'lscr.io/linuxserver/snipe-it'
b3fac5bf1a3e0644be10ee564f71c550f1a3086eb89dd36f159dd5da14c96b5e
-
37 minutes ago, nikky said:
could you please show a snippet of your compose file?
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='snipe-it' --net='bridge' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'NGINX_APP_URL'='192.168.0.24' -e 'MYSQL_PORT_3306_TCP_ADDR'='192.168.0.24' -e 'MYSQL_PORT_3306_TCP_PORT'='3306' -e 'MYSQL_DATABASE'='snipeit' -e 'MYSQL_USER'='snipeit' -e 'MYSQL_PASSWORD'='snipeit' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -p '8084:80/tcp' -v '/mnt/cache/appdata/snipe-it':'/config':'rw' 'lscr.io/linuxserver/snipe-it'
d53971dc1e875f73270fa5eff26eeeb25fe5184f7e9524d79e99371870c071c9
-
Hi there, just tried to install this but getting connection refused but the log file does not really show any errors
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/
Brought to you by linuxserver.io
-------------------------------------
To support the app dev(s) visit:
Snipe-IT: https://snipeitapp.com/donate
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid: 99
User gid: 100
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 40-config: executing...
[cont-init.d] 40-config: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.localhost refused to connect.
-
I have the same problem on my Windows 11, which I freshly installed, however I don't have these shares even visible therefore cannot remove them. I tried this workaround and was able to make 2 out of 10 shares others are failing again with the same error, very random.
-
I actually moved the new USB into a port on the motherboard with a usb2 slot.
I have now downgraded to 6.8.3 on the same USB key and the problems are no longer there. So it must have something to do withtower-diagnostics-20210305-2047.zip 6.9.0. I have logged a bug for this, hopefully it can be fixed.
-
so I am stumped, since the upgrade to 6.9 my usb key is giving errors as soon as I copy over a file, I have now purchased a brand new USB key and as soon as I copy over a file it behaves the same way, I never had this issue with 6.8.3 running for years. I have a diagnostic file tower-diagnostics-20210305-1908.zipand I am really concerned, I need help.
-
I upgraded today to 6.9 and suddenly unraid is telling me that my flash drive is having issues, it has been in the array without issues tower-diagnostics-20210303-1642.zipfor years. Should I run a checkdsk on a windows PC? I have now run the checkdsk on my Windows PC it did a fix run but did not find any errors, but when I started the array with the Flash drive it detected an unclean shutdown, so a parity check is currently running. Here is the diagnostic after the check
-
my Kodi was also upgraded to 19 and since then I am no longer able to play any media from the unraid server, there is already a big post in the Kodi forums but I now have to use a different player as nothing is working with kodi 19.
-
Just a quick question, do you use the cache drive as a cache drive, as I had to change my path to /mnt/user as I was not using the cache for cache itself.
-
7 hours ago, falconexe said:
Hey guys. We had a Corona virus scare over here (been super sick), so we've been dealing with that. I was hoping to have this out by tonight, but I am still working on it. I have the code written and the JSON is independently completed, but I have yet to integrate it into the UUD. And the the largest task of all is documentation and release notes (and that takes a LONG time). I've been going back and forth debating whether or not to release this independently as the Ultimate Plex Dashboard (UPD), or just integrate it into the UUD as version 1.5. I've decided to incorporate it into UUD, but for those of you who want a dedicated Plex Dashboard, I can release a standalone version of this as well, if there is enough demand. I'll post updates next week on a potential release date.
I hope you all have a fantastic Thanksgiving!
Hope you are feeling better and Happy Thanksgiving as well.
-
when you say you cannot edit anything, what do you mean. If you have no data, what this might mean is like me the utilization assumes that you are using a Cache drive, if you do not then you have to go into each of these settings and next to the name there is a arrow pointing down, here select edit and you can change the path from /mnt/user0 to /mnt/user this is the default path if no cache drive is being used. Which other settings are also not working?
-
you need an admin account at least as admin user type
-
1
-
since upgrade to 6.10 RC7 getting failed command: READ FPDMA QUEUED
in General Support
Posted
if I understand the logs correctly it appears to affect my first parity disk, do I understand this correctly? ata2.00: ATA-9: WDC WD140EDFZ-11A0VA0, 81.00A81, max UDMA/133