kevin182
-
Posts
41 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by kevin182
-
-
1 hour ago, JorgeB said:
Sep 21 02:01:22 Lucifer kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 21 02:01:22 Lucifer kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 21 02:01:22 Lucifer kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 21 02:01:22 Lucifer kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 04 25 78 00 01 00 00 Sep 21 02:01:22 Lucifer kernel: critical medium error, dev sda, sector 271736 op 0x0:(READ) flags 0x80700 phys_seg 32 prio class 2This time we can see it really is a flash drive problem.
6 minutes ago, JorgeB said:Post the complete diags please.
That is the complete diagnostics. Albeit just before trying to shut it down.
-
Also, when I try to stop the array I continuously get these errors.
-
Unfortunately, this has appeared again. Please let me know if you have any insights into what is causing this. Thank you.lucifer-diagnostics-20230921-0741.zip
-
Got a new license key and I believe the flash drive was the problem as the old 1 did have errors on it. Thank you.
-
1
-
-
Error: {"message":"Request failed with status code 403","data":{"error":"Cannot transfer GUID because you've already transferred 2 times in the past year. Please contact support for assistance."}}
I will contact support -
I removed the disk but unfortunately it happened again. Thank you.
-
OK. Thank you. I wish there was some way of logically disconnecting the disk. I was hoping to keep it in there to destroy the contents before I threw it out. I will let you know if it happens again. If it does, it will be in the 24 hrs.
-
After this, I run diagnostics, use the reboot command and wait over an hour. Eventually, I decided I need to hard reboot. Comes up for a while then repeats. Please help, thank you.
-
10 hours ago, JorgeB said:
If it's a one time thing you can ignore, if it keeps happening try limiting more the RAM for VMs and/or docker containers, the problem is usually not just about not enough RAM but more about fragmented RAM, alternatively a small swap file on disk might help, you can use the swapfile plugin:
https://forums.unraid.net/topic/109342-plugin-swapfile-for-691/
Great. Thank you for your help. I appreciate it.
-
I received this on my server this morning. Diagnostics attached. Thank you.
-
3 hours ago, DanielPetrica said:
When we update the container/app do we need to change the "Config" path to map this new path or is it automatic?
Mine did not automatically change. So I manually changed the config container path to
/home/node/.n8n/
After that, I updated the container and all my configuration settings came back once I logged in.
-
2
-
-
45 minutes ago, JorgeB said:
Looks like the same, I don't believe the other user created a bug report, you can create one if you want.
Thanks for your help. I appreciate it.
-
1
-
-
6 minutes ago, JorgeB said:
Cannot see what chip it uses, possibly there's no driver, or did it work before?
It did work before. I had eth1 assigned to it before upgrading from 6.11.5 to 6.12.2.
Here is the chip. It does say it needs a driver for Linux.
Here is another person having problems with it. Maybe the same? Over here you told them to submit a bug report.
-
5 hours ago, JorgeB said:
I'm not seeing it in the previous diags, do you know the chip it uses?
We can abandon this discussion here as we are discussing this here. Thanks.
-
5 hours ago, JorgeB said:
Not being detected, this is not a software issue, try a different PCIe slot.
Not seeing the Asus detected in the diags, were do you see it?
I will try a different PCIe slot
I did not have it plugged in at that time but I did see it when it was plugged in.
Any idea why the eth1 will not appear from the 1 that is in the diagnostics?
-
I cannot get eth1 to come back after upgrading to 6.12.2. I can see my NIC in the system devices but no new network adapter is appearing. I have tried three different NICs. Attaching diagnostics.
UGREEN USB to Ethernet Adapter
ASUS 2.5G Ethernet USB Adapter
Both of these appear in system devices but no eth1 in network settings
2.5GBase-T PCIe Network Adapter RTL8125B
This 1 does not appear at all in the system devices and I have added the plugin for the Realtek drivers.
-
4 hours ago, JorgeB said:
You also need to do this:
https://docs.unraid.net/unraid-os/release-notes/6.12.0#crashes-related-to-i915-driver
Thank you! This solved it for me.
I have 1 other issue. My USB ethernet adapter (2nd on the server) does not appear in the network configuration. Yet, it does appear in the system devices. I know I have seen it appear before and was using it as the docker network interface but it no longer appears. I tried renaming the network.cfg to reset the settings and that has not worked. Thanks.
-
I did have a total of 3 webgui's open at the same time. I rebooted. and there is barely any CPU now. Thanks for that.
However, after letting it sit just on the 1 webgui for about an hour, it became unresponsive again. This time it did not require a hard reboot. I was able to change the URL to base URL and refresh the webgui.I honestly think there is some hardware that is not compatible with 6.12. I should mention this is my second time upgrading to 6.12 from 6.11.5. First I upgraded to 6.12.0 and I was having these unresponsive bouts as well but no flash corruption then. I then downgraded thinking 6.12 was just not ready yet. It seems I have even more problems now.
On top of this, I upgraded to 6.12.2 yesterday to solve another problem. My btrfs cache pool had uncorrectable errors. I could not get it to reformat for the life of me. Erase would not erase. Still showed over 400 GB but I was able to successfully move everything off of it or so I think. Upgraded to 6.12.2 and converted the cache to ZFS and copied system and appdata shares back to cache.
All drives pass abbreviated smart test
Memory check done overnight last night. Passed
No dockers running
No VMs running
Attaching most recent diagnostics
-
I don't think it is false because the Windows computer does detect an issue with the USB and repairs it. The UI is very sluggish and finally stops responding.
My CPU is very active too, yet no docker or VMs running. Also, this pop up console windows just closes on it's own. This is very strange
-
5 hours ago, JorgeB said:
Did you see that during array start only or it's still showing?
It is still showing sporadically. I don't think it is related to the array starting because it could happen at any time. In fact, I do not think it is related to the USB flash drive at all because I have now a second flash drive it is reporting is corrupted. I have been shutting down, taking the flash drive to my Windows computer and repairing it. It still happens after.
-
Said to post my diagnostics to the forum. Just upgraded to 6.12.2 today. Here are the diagnostics. Let me know if you can help. Thank you.
-
My server keeps losing internet access. I have my DNS Set to Google in network settings. When I changed my router to OpenDNS, the internet immediately came back up but only for a few minutes. It is now back down. Any help would be appreciated. Thank you
-
36 minutes ago, kevin182 said:
I converted my paperless-ng container to ngx as described earlier in this post. I cannot access any of my files through the UI. Here is the error I get. Anyone else get this? Thanks.
Disregard. I got it working. For anyone interested. What I did is pull down original paperless-ng to the container. Made sure it was working properly. Then I just changed the repository to ghcr.io/paperless-ngx/paperless-ngx:latest. It worked this time. I do not know what I did wrong the first time.
-
I converted my paperless-ng container to ngx as described earlier in this post. I cannot access any of my files through the UI. Here is the error I get. Anyone else get this? Thanks.
"Docker Service failed to start" after a few hours of running
in General Support
Posted
If that's the case, I have had 2 flash drives go bad in less than 2 weeks. Seems quite unlikely this is my only problem and considering I purchased a very good quality flash drive for this replacement.