darrenyorston

The issue of my deluge container becoming unresponsive every view days has ceased after the recent container update.

I can SSH into unraid fine. The content in NAME_SERVER are the default when the template downloaded, I didnt change anything. They remain: 8.8.8.8,37.235.1.174,8.8.4.4,37.235.1.177

No. Whenever the webUI reports the container is down I have just been restarting the container. After a reboot it works fine. After a few days though the webUI becomes unavailable again.

When I attempt to open the webUI I receive the following error. It is only happening with this container. The log file is attached. To gain access to the webUI I have to restart the container. container log.txt

I seem to regular encounter an issue with my container crashing. My web browser reports the ip address/port cannot be reached. It works fine once I restart the container though. When it's down though sab won't work. Is there a way to tell deluge to regularly reboot? It seems to happen if the container runs for more than 2-3 days.

I have the same issue. I have not been able to find a setting to alter the content server's IP address. My network range 10.1.2.X so a content server of 172.17.0.8 clearly won't work. I am presuming its a Docker issue as I can access a Calibre content server running on one of my local machines.

I keep receiving the following two errors: Event: unRAID Cache 4 SMART health [198] Subject: Warning [TOWER] - offline uncorrectable is 1 Description: Crucial_CT525MX300SSD1_1701154383DE (sdk) Importance: warning this error was being preceeded by the error: Event: unRAID Cache 4 SMART health [5] Subject: Warning [TOWER] - reallocate nand blk cnt is 15 Description: Crucial_CT525MX300SSD1_1701154383DE (sdk) Importance: warning The second error is: /var/log is getting full (currently 55% used) Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages. A reboot of your server will at least temporarily solve this problem, but ideally you should seek assistance in the forums and post your My system has an uptime of 8d16h44m and I am runnign ver 6.3.5 Diagnostics attached tower-diagnostics-20171121-1018.zip

It may not have been the replacing of the SATA cable. As I mentioned originally one of the VMs was pausing. It looked like that unRAID was reserving 200GB of the cache. I had stopoed the Array to adjust the min free space on the cache, but also took the opprtunity to adjust the SATA cable at the same time. When I restarted the array all the problems occured. ie. One of the cache disks showed as unmountable and both docker and vms were inaccessible. The command line seemed problematic as well. The copy command you posted kept reporting the mounted /x disk was read only, I followed your guide, but when I utilised the mouse to select copy in midnight commander it worked fine. At the moment I have access to my files but docker containers dont appear to have access to the internet and VMs seem flaky, sometimes they work, other times they report not being able to find their vdisks. Seems to be a pretty serious problem and I am thankfull I didnt loose my data, though I did have an older back up of site if I had.

Here: If it mounts copy all the data from /x to other destination, like an array disk, you can use Midnight Command or your favorite tool, after all data is copied format the disk and restore data. The disc mounted and I was able to copy the data off the drive. The format of the disk though never worked. The GUi continued to report the disc required formatting. When I told it to format it would format for about 10sec or so then would show mountable again. So I removed the disc from cache and utilised unassigned devices to unmount it. I then utilised pre-clear disks to prepare the disc. I then re added the drive to the cache and it is working fine, or so it seems. I have had to delete the docker image and re add all the containers. The docker containers are not working correctly at the moment though as they dont seem to be able to see the internet. I also had to delete the VMs and start anew. I will probably look to move my data back onto Freenas now and just use unRAID for docker containers, Im concerned about unRAIDs stability. Removing and replacing a SATA cable shouldnt result in such problems. diagnostics.zip

I followed your instructions here

I posted that earlier: its reporting: "Cache pool BTRFS too many profiles X" with X being the SSD I just re-added.

When I browse the cahce folder from the gui the appdata and other folders are there. They are empty however. There is no libvirt.img. The only *.img file is docker.img. I have already uploaded the diagnositcs file.

Well in that case something didnt work. I copied all the directories of the mount and it totalled only 60GB, it was 300GB or so prior to mounting the drive. At the moment none of my docker containers work, the VMs tab is blank, and I cannot access shares on the array.

No I have not copied everything of the cache. Why would I? The instructions I followed advised to copy the materials of one disk, not the entire cache. I am not feeling overly confident here. Seems the "fix" is worse than the problem. Atleast I had access to my files and docker. Now I have neither.

I have been able to format the disk, I had to remove it from the cache first. Now I am trying to restore the files back to it however the cache disk (/x) is reporting "Read-only file system (30)" unRAID Cache disk message is also reporting: "Cache pool BTRFS too many profiles X" with X being the SSD I just re-added.

I have attached the diagnostics file again. The drive won't format, it keeps saying its "Unmountable" in the GUI. A different cache disk, one I have not touched is now showing as a "New Device" This feels like a rat hole I have gone down. My initial problem was for a VM pausing, potentially due to a 200GB reserved space, I shut down the server and took the opportunity to adjust the path of a SATA cable, now I am in the situation that none of my Docker containers or VMs work. What is the best way to get to a functional system? tower-diagnostics-20171105-1139.zip

I have been able to copy all the material off the drive. I formated the disk as per however the disk still shows that it is unmountable.

I have found the directories using MC. What disk number will the /x drive be for the purposes of an MC copy? I tried "cp -r /mnt/x /mnt/disk4" however nothing happens. When I look at disk 4 no files have been copied. Ok. I have discovered that the command line doesnt work. I just utilised the menus instead.

I have presumed it's "mkdir /x" leading to "mount -o recovery,ro /devsdi1 /x". No errors reported and I am at the command prompt. where do I find the mounted disk to copy the files from? Nothing appears to have changed on the GUI.

You say to replace x with the actual device. So its going to be "mkdir /sdi1"? or mkdir /dev/sdi1"? Leading to "mount -o recovery,ro /dev/sdX1 /dev/sdi1"?

Well I ran it because that's what Fix Common Problems said to do if the disk was unmountable. Having looked at your link, could you provide some guidance? I dont utilise command line functionality so what's the starting point?

As I have posted elsewhere my PFSense VM has been pausing for two days now. I resume it however it pauses again shortly after. Someone suggested it might be a cache disk issue. I checked and unRAID has reserved 200GB og my cache. I have 2 x 120GB and 2 x 520GB SSDs as cache. They were less than 50% full, something like 38%. I shut down my server and adjusted a SATA power cable on one of the SSDs and now Fix Common Problems is reporting: cache (KINGSTON_SHFS37A120G_50026B7261075EF7)has file system errors (No file system (32)) If the disk if XFS / REISERFS, stop the array, restart the Array in Maintenance mode, and run the file system checks. If the disk is BTRFS, then just run the file system checksIf the disk is listed as being unmountable, and it has data on it, whatever you do do not hit the format button. Seek assistance HERE My SSD is BTRFS. I looked to run the File System Check however the option was grayed out with a message advising it was only available when the array was running in Maintenance mode. I restarted the array in Maintenance mode, selected File System Check, but it doesn't appear to be doing anything. The text box says "running" but its been like that for over 24hrs now. How long should it take to finish? I have attached diagnostics again. tower-diagnostics-20171104-1754.zip

I had shut down down the server and moved a SATA power cable. When I restarted it said one of the SSDs was unmountable. I started the system in Maintenance mode and started the Check File System on the dosk. How long should it take on a 520GB SSD? Its been running about 14 hours now and the "btrfs check status:" just says "checking extents" with "Running" next to the Cancel button.

That seems to be the case. I have 2 x 120GB SSDs and 2 x 525GB SSDs as my cache but its reserving 250GB for some reason.

I have this problem as well. I shut down my system and moved a SATA power cable, when I restarted I get a similar message. The part about just running file system check if the disk is BTRFS and listed as unmountable appears incorrect however. The option is grayed out with a message that it is only available when the array is in Maintenance Mode.