-
Vossy started following Red X - what am I looking for in the log , Random errors on hard drives , db_root: cannot open error and 3 others
-
Random errors on hard drives
Hoping someone can help. Whenever I try to do a parity check, almost instantly I get disk failures, sometimes same disk occasionally different disks. Whether new disk or all disks Same thing happen this morning when I enable turbo mode. I have attached a picture of the disks I have and diagnostics tower-diagnostics-20250118-0823.zip.crdownload
-
db_root: cannot open error
Hope for some help. Recently went to reboot my server and I get "db_root: cannot open: /etc/target" and various lines after. I cannot after. I cannot log in to the remote GUI. If in boot in safe mode still get the error but can get the GUI working. I had the error on the screen (I sometimes have a screen connect to my server) for a while. I was running 6.12.0 but everything was working. I tired many times to update from but kept failing. Someone it managed to upgrade to 6.12.4 and ow I have this. Not sure how to work this out. When I boot it normally it does allow SSH in but not sure what to do then. I thought it might the thumb drive so tired a new one using the back up file, but get a different error. "cannot mount bzmodules - press ENTER to reboot...." I have tired different USB ports on he motherboard and no difference A little lost and after some help please. tower-diagnostics-20230924-1721.zip tower-diagnostics-20230924-1621.zip
-
Help with X5690 Processors
Thanks all thats exactly what it was. Strange cause the last CPU had it and I didn't change BIOS. Thanks all again
-
Help with X5690 Processors
Hello, I recently upgraded my supermicro X8DT6 motherboard with 2 x 5690 Processors. I thought these CPU had 6 cores but 12 threads as below only showing 6 threads for both. What I am missing? tower-diagnostics-20220419-0844.zip
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
I have just started using Unraid and trying to get nextcloud access using letsencrypt. I have followed spaceinvaderone's tutorial to the letter. I get server ready in my letsencrypt logs. When I try accessing from external using https:// i get This site can’t be reached nextcloud.xxxxxxx.xxx refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED If I try using http:// I get my modem log in page and can log in and access my modem. Any thoughts?
Vossy
Members
-
Joined
-
Last visited