Parzival_PRO Posted July 31, 2021 Share Posted July 31, 2021 (edited) Hey guys, I’m having a problem with my unraid server. I added another cache drive last night after finally getting my other one to show back up and booted the server up and it was stuck starting the array for a while. I shut it down and removed the second cache drive and booted back up, now the GUI won’t load. I can ping the IP but even on the console, the GUI doesn’t load. Any ideas on how to fix this? EDIT: the gui finally loaded, but is starting the array, its been sitting there for a bit. I do see the cache drive is completely full. Do I need to clear it out? Edited July 31, 2021 by Parzival_PRO Quote Link to comment
Squid Posted July 31, 2021 Share Posted July 31, 2021 There's probably a ton of errors relating to the full drive (I'm assuming it's btrfs) You can always post your diagnostics. Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 2 minutes ago, Squid said: There's probably a ton of errors relating to the full drive (I'm assuming it's btrfs) You can always post your diagnostics. I'll post the diagnostics here shortly, as soon as it lets me get to it. When the GUI is working, it is really slow, and keeps going from responsive to unresponsive. Give me a few mins and I'll post it. Thanks! Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 I was downloading the diagnostics (well running it) and now the GUI isn't loading at all. What should I try to do? I don't want to mess it up any more than I already have Quote Link to comment
Squid Posted July 31, 2021 Share Posted July 31, 2021 Look on the flash drive in the logs directory. There should be a diagnostics zip file generated from today. Upload it. If not, then when you regain access from the command prompt, diagnostics And a new set will get saved in the logs folder. Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 Here are the logs from yesterday. I tried the diagnostics command from the terminal and it gave me this error: "Starting diagnostics collection.... mkdir: cannot create directory '/boot/logs' : Input/output error. Luckily it did have the logs from yesterday, which is when this happened. tower-diagnostics-20210730-2131.zip Quote Link to comment
Squid Posted July 31, 2021 Share Posted July 31, 2021 Reseat the cabling to the cache drive (power and sata). It dropped offline in the those diagnostics. The can't create /boot/logs implies that either you pulled the flash drive out or it also dropped offline. Reseat it (if it's a continuing problem, try a different port, ideally USB2) Either one of these will cause the issues you're seeing. Ultimately your only recourse is a power down. Try at the terminal powerdown To see if it can gracefully shut itself off. Otherwise do a hard shutdown. Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 Ok, I’ll give that a try. I did reseat the connections last night and moved the usb to other port. But I’ll try it again and see what happens. Will report back shortly. Thanks! Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 I reseated the connections and booted back up. I’m in the terminal window and typed diagnostics and it’s starting collection but has been sitting there for about 15 mins or so. Should I close the window? Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 It isn't saving the diagnostics for some reason. No clue what to do now.. Quote Link to comment
Squid Posted July 31, 2021 Share Posted July 31, 2021 From the webGUI, diagnostics *should* pop up a window that gives the current command that it's running. What is it? Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 This is where it gets stuck at. Quote Link to comment
Squid Posted July 31, 2021 Share Posted July 31, 2021 Your best solution is to restart the server in Maintenance mode, then run the file system checks https://wiki.unraid.net/Check_Disk_Filesystems against the cache drive Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 Ok, is maintenance mode the same as safe mode? I try to reboot from the GUI and it doesn't reboot. It just hangs. So I have to do a hard reboot. Quote Link to comment
Squid Posted July 31, 2021 Share Posted July 31, 2021 No. Once the GUI is loaded you have to stop the array and then restart in Maintenance Mode. (There's a checkbox). If you can't do that, then on the flash drive edit /config/disk.cfg on the flash drive and change startArray="yes" to instead be "no" Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 Thanks. I booted into Safe Mode while I was waiting on your reply and I was able to run the diagnostics. Here it is. Earlier, I took the cache drive out and put it in my windows machine, but couldn't see any files, which it isn't formatted for windows, so I knew I probably wouldn't be able to see anything, but figured I would try. I was going to try and delete come stuff off the cache drive and free up some space. Right now, there is zero bytes free on it. tower-diagnostics-20210731-1536.zip Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 So I rebooted out of Safe Mode back into normal mode and the cache drive is unmountable it says. But it shows the drive is healthy. Quote Link to comment
Squid Posted July 31, 2021 Share Posted July 31, 2021 1 hour ago, Squid said: run the file system checks https://wiki.unraid.net/Check_Disk_Filesystems against the cache Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 9 minutes ago, Squid said: Quote [1/7] checking root items [2/7] checking extents [3/7] checking free space tree [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/sdb1 UUID: 3594b843-5bb0-41e9-bc0b-27444cb4e218 found 253503082496 bytes used, no error found total csum bytes: 225188500 total tree bytes: 361480192 total fs tree bytes: 64487424 total extent tree bytes: 25853952 btree space waste bytes: 57938359 file data blocks allocated: 278173122560 referenced 253071593472 This is what the "check" shows Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 I tried to mount the drive as an unassigned device, but I get this: Quote Jul 31 18:04:55 Tower kernel: BTRFS error (device sdl1): devid 2 uuid f714ffd2-7bbe-4e8b-bf2f-f6d3f95ed41d is missing Jul 31 18:04:55 Tower kernel: BTRFS error (device sdl1): failed to read chunk tree: -2 Jul 31 18:04:55 Tower kernel: BTRFS error (device sdl1): open_ctree failed Jul 31 18:04:55 Tower unassigned.devices: Mount of '/dev/sdl1' failed: 'mount: /mnt/disks/OCZ-VERTEX4_OCZ-8D9YG33K3FHS360Q: wrong fs type, bad option, bad superblock on /dev/sdl1, missing codepage or helper program, or other error. ' Quote Link to comment
Parzival_PRO Posted July 31, 2021 Author Share Posted July 31, 2021 (edited) i took a backup of my unraid server back on 7/20 and i installed a new drive and am trying to get my dockers/appdata back, if i do a restore, will it restore the apps/dockers back without me having to reconfigure everything? Edited July 31, 2021 by Parzival_PRO Quote Link to comment
trurl Posted August 1, 2021 Share Posted August 1, 2021 Restore appdata and recreate docker.img, then Previous Apps on the Apps page will let you reinstall any and all dockers exactly as they were using the templates saved on flash when you installed them before. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.