-
No WebGUI when restoring from backup
When I initially restored from the Unraid Connect backup I couldn't get to the Unraid web interface as described in my initial post. Then I created a fresh flash drive with the Unraid usb creation tool and copied over my config files from the Unraid connect backup. This gave me back the Unraid GUI but no network access. I could be wrong but I believe Unraid could not see either of my two Realtek network ports because I had Realtek drivers installed from community applications. Once I deleted those two driver packages I rebooted and Unraid was able to pick up the two network interfaces. I can't even remember why I had those installed in the first place. I assume my 2.5gb network card wasn't supported natively at one point on an older version of Unraid. Everything seems to be working now thanks to Unraid Connect having an online backup of my configuration. Lesson learned is that I also need to set up CA Backup to save the flash backup outside of the array. Thanks for all you do Squid!
-
No WebGUI when restoring from backup
Multiple hours later I think I figured it all out. I just need to restore my previous plugins and I think I'm good to go. I'll mark this as solved.
-
No WebGUI when restoring from backup
Help please. I tried to upgrade to the latest version when the webgui just froze. Eventually I forced a reboot of the server and it will not boot - seeing critical errors on sda. Believing the USB drive has failed I restore my Unraid connect backup to a new USB drive. I get the new drive to boot but no Webgui over the network. I then boot into safemode with gui and same thing, no unraid interface within the local firefox. I am not a linux master so please explain what I should do next. I did have the server backup plugin running but obviously I can't access the array where they are saved. What am I missing? Please help!
-
help upgrading transcode gpu in unraid 7
I came to the forums looking for an answer to this exact question. I think people aren't responding to you because this question has already been asked in other threads. Here is one for example:
-
Machine Check Events detected on your server
Regarding post #2 in this thread - (From another thread) I noticed this was mentioned in the release notes at one point: https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.10.0#Base_Packages I'm still looking for information regarding post #1 in this thread. Is this error something I should be worried about?
-
Machine Check Events detected on your server
Also, Fix Common Problems says this in the logs: Apr 23 04:30:06 Tower root: Fix Common Problems: Error: Machine Check Events detected on your server Apr 23 04:30:06 Tower root: mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead. How do I go about using the edac_mce_amd module?
-
Machine Check Events detected on your server
Anything I should do with this error? It literally says "no action required" but I would like to know what might have caused this. Found this in the logs: Apr 19 08:36:47 Tower kernel: mce: [Hardware Error]: Machine check events logged Apr 19 08:36:47 Tower kernel: [Hardware Error]: Corrected error, no action required. Apr 19 08:36:47 Tower kernel: [Hardware Error]: CPU:1 (19:21:2) MC25_STATUS[-|CE|-|-|-|-|-|-|-]: 0x8000000100cbd163 Apr 19 08:36:47 Tower kernel: [Hardware Error]: IPID: 0x0000000000000000 Apr 19 08:36:47 Tower kernel: [Hardware Error]: Bank 25 is reserved. Apr 19 08:36:47 Tower kernel: [Hardware Error]: cache level: L3/GEN, tx: INSN Thank for looking. tower-diagnostics-20230424-0935.zip
-
BTRFS issues
There may have been some tension on the SATA cable. I rerouted and reseated the SATA cable. I ran another Scrub and no errors are being reported. I reset the BTRFS stats according to the post you referenced about the BTRFS monitor script. After re-running the script all errors are now 0. The script is now scheduled to run daily to monitor the cache pool. Once again, thank you JorgeB. I would be lost without you.
-
BTRFS issues
JorgeB to the rescue again! I ran the script and I have tons of errors: [/dev/sdb1].write_io_errs 0 [/dev/sdb1].read_io_errs 0 [/dev/sdb1].flush_io_errs 0 [/dev/sdb1].corruption_errs 0 [/dev/sdb1].generation_errs 0 [/dev/sdc1].write_io_errs 304324335 [/dev/sdc1].read_io_errs 4301948 [/dev/sdc1].flush_io_errs 2290865 [/dev/sdc1].corruption_errs 14826483 [/dev/sdc1].generation_errs 16809 Do you recommend I replace the cache2 cable and then run another scrub?
-
BTRFS issues
Okay, I have recreated the docker image and my docks are all working again. I'm just not sure what the underlying issue is/was. Can anything be determined from the logs?
-
BTRFS issues
This is the last thing in the log when I try to start the Docker service: Sep 16 21:06:08 Tower root: mount: /var/lib/docker: wrong fs type, bad option, bad superblock on /dev/loop2, missing codepage or helper program, or other error. Sep 16 21:06:08 Tower kernel: BTRFS error (device loop2): bad tree block start, want 24931565568 have 6449542684566666880 Sep 16 21:06:08 Tower kernel: BTRFS error (device loop2): bad tree block start, want 24931565568 have 12792500698256506278 Sep 16 21:06:08 Tower kernel: BTRFS warning (device loop2): couldn't read tree root Sep 16 21:06:08 Tower kernel: BTRFS error (device loop2): open_ctree failed Sep 16 21:06:08 Tower root: mount error Sep 16 21:06:08 Tower emhttpd: shcmd (651): exit status: 1 Should I recreate the docker image file or is something bigger happening here?
-
BTRFS issues
I noticed all my Dockers were not working. Upon trying to restart the Docker service I was getting "Docker service unable to start." I did a reboot to see if that would fix the issue. The diagnostics posted are before the reboot. Upon reboot, Docker failed to start again. I noticed a lot of BTRFS errors on my cache drives in the logs. So I ran a Scrub. No help - tons of errors in the logs. I don't know what to do next. These are relatively new redundant cache drives, just a few weeks old. The first diagnostics was right when I first noticed the problem. The second diagnostics is after the reboot and scrub. Please help! Brad tower-diagnostics-20220916-2012.zip tower-diagnostics-20220916-2055.zip
-
Slow Parity Checks
I tried another controller and it appears to be negotiating at x4! SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] Broadcom / LSI Serial Attached SCSI controller Type: Onboard Controller Current & Maximum Link Speed: 5GT/s width x4 (4 GB/s max throughput) I'm hoping the next parity check is much faster! Thanks again JorgeB!
-
Slow Parity Checks
I'm on the latest BIOS. I have another controller card to try out. Thanks, as always JorgeB. If anyone else has ideas please chime in!
-
Slow Parity Checks
Yes, a Nvidia GTX1060 in the x16 slot (for Plex). I also have 2.5G network card in slot 2. The LSI card is in the third slot which is supposed to be x4 speed according to the manual. Something must be hogging up the lanes. I'm guessing though as my knowledge in "lanes" is very limited. I can put some of my drives on the MB SATA ports as a workaround - but what a waste of a nice LSI card to be limited to 500 MB/s.
BradJ
Members
-
Joined