January 12, 201610 yr New install, low usage. Model: Custom M/B: Gigabyte Technology Co., Ltd. - F2A58M-HD2 CPU: AMD A6-7400K Radeon R5, 6 Compute Cores 2C+4G @ 3500 HVM: Enabled IOMMU: Disabled Cache: 128 kB, 1024 kB Memory: 8192 MB (max. installable capacity 8 GB) Network: eth0: 1000Mb/s - Full Duplex Kernel: Linux 4.1.13-unRAID x86_64 OpenSSL: 1.0.1p Parity TOSHIBA_DT01ACA200_84F77JGTS - 2 TB Disk 1 ST2000DM001-1ER164_Z500XGTH - 2 TB Disk 2 TOSHIBA_DT01ACA200_645J8PHGS - 2 TB Disk 3 ST2000DM001-1ER164_Z500Z0R0 - 2 TB Disk 4 TOSHIBA_DT01ACA200_645J01EGS - 2 TB Total Array of five devices 156 GB Used 7.84 TB Free Cache Devices Corsair_Force_LS_SSD_1442816800010167059E - 60.0 GB Boot Device Flash Cruzer - 4.02 GB vfat 142 MB Free Three Dockers, very low volume Mylar NZBGet Ubooquity A couple times now, after I've left it alone for quite some time, when I visit the main UI, it's responsive but empty. By "empty" I mean that pretty much everything on the Dashboard show nothing. No devices under Array Status, no values in System Status, etc. On the "Main" tab, there is nothing showing under "Array Operations". The dockers are typically still responsive via Web UI, and NZBGet still fetches the occasional file. I can SSH into the server. Any ideas what might be causing this or how to recover short of restarting?
January 12, 201610 yr Something about the symptoms rings a bell, next time it happens SSH in and try to get diagnostics, but if it fails, not just error messages, but fails to create the zip file, navigate to the /boot folder and see if there is any content there at all. I suspect the flash drive is dropping offline, which will make the diagnostics collection fail.
January 13, 201610 yr Author It's in this state right now. I can't download Diagnostics.zip; I can navigate to that section of the tools, but clicking the button gives me a 404. I'm connected with Transmit, and can see that clicking the button creates the Diagnostics-DATE-TIME folder at the root of the filesystem, but all the files within are 0 length. Is there another way to generate the diagnostics.zip? Alternatively, I can apparently grab whatever is needed straight from the filesystem. Trying to export the syslog also gives a 404, so I copy-pasted and attached it. I can connect to existing Dockers' web UIs and create new Dockers. I can connect via ssh and all seems to be in place: ? ~ ssh [email protected] [email protected]'s password: Last login: Wed Jan 13 15:21:48 2016 from 192.168.0.105 Linux 4.1.13-unRAID. root@Tower:~# ls /boot/ System\ Volume\ Information/ bzroot* config/ ldlinux.c32* license.txt* make_bootable_mac* packages/ bzimage* changes.txt* install.txt* ldlinux.sys* make_bootable.bat* memtest* syslinux/ root@Tower:~# cd / root@Tower:/# ls -diagnostics-20160113-1522/ bin/ dev/ home/ lib/ mnt/ proc/ run/ sys/ usr/ -diagnostics-20160113-1536/ boot/ etc/ init@ lib64/ opt/ root/ sbin/ tmp/ var/ root@Tower:/# cd mnt root@Tower:/mnt# ls cache/ disk1/ disk2/ disk3/ disk4/ user/ user0/ root@Tower:/mnt# ls disk1 Books/ Incoming-Comics/ Movies/ Music/ Software/ TV/ appdata/ docker.img nzbget_downloads/ templates/ root@Tower:/mnt# ls cache appdata/ apps/ docker.img root@Tower:/mnt# ls disk2 root@Tower:/mnt# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 128M 2.6M 126M 2% /var/log /dev/sda1 3.8G 136M 3.7G 4% /boot /dev/md1 1.9T 146G 1.7T 8% /mnt/disk1 /dev/md2 1.9T 33M 1.9T 1% /mnt/disk2 /dev/md3 1.9T 33M 1.9T 1% /mnt/disk3 /dev/md4 1.9T 33M 1.9T 1% /mnt/disk4 /dev/sdb1 56G 11G 46G 19% /mnt/cache shfs 7.3T 146G 7.2T 2% /mnt/user0 shfs 7.4T 156G 7.2T 3% /mnt/user /dev/loop0 10G 4.0G 5.1G 45% /var/lib/docker root@Tower:/# I will leave it in this state in case there's anything anyone wants/needs from it. There must be something simple in my hardware or maybe flash drive. This same piece of hardware has been running as a FreeNAS machine for about a year, so I think the hardware is not implicated. I did add a SATA PCI card, but since all the drives are still online [cache is on that card] it would seem that it's not implicated. I welcome suggestions. UNRAID-log.txt
January 13, 201610 yr Your array is pretty full, just wondering if it's anything to do with that and the mover....
January 13, 201610 yr Author My array has very little on it. Where are you seeing that it's pretty full? 146G used on 4 2T disks. /dev/md1 1.9T 146G 1.7T 8% /mnt/disk1 /dev/md2 1.9T 33M 1.9T 1% /mnt/disk2 /dev/md3 1.9T 33M 1.9T 1% /mnt/disk3 /dev/md4 1.9T 33M 1.9T 1% /mnt/disk4 also, what's this: "and the mover..." Hey, now Dashboard and Main are empty. No disks listed on either tab. df -h still shows them, though. Any suggestions before I reboot?
January 13, 201610 yr Ignore me.... I'm tired and was reading it as 1% free space not utilisation....
January 20, 201610 yr Author Back in this state. Everything seems to be working except the shares. I can connect via ssh, I can connect to all dockers, but cannot connect to the shares and all parts of the UI that have to do with shares is empty. How can i get to the bottom of this? The only error I can see in the syslog as the WebUI shows it to me is: Jan 17 03:40:01 Tower logger: /usr/local/sbin/mover: line 44: echo: write error: No space left on device which starts happening four days into the latest uptime. There is no filesystem in the machine that is anywhere near full so far as i can see: Last login: Wed Jan 13 18:19:10 2016 from c-75-72-234-181.hsd1.mn.comcast.net Linux 4.1.13-unRAID. root@Tower:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 128M 3.1M 125M 3% /var/log /dev/sda1 3.8G 145M 3.6G 4% /boot /dev/md1 1.9T 261G 1.6T 14% /mnt/disk1 /dev/md2 1.9T 33M 1.9T 1% /mnt/disk2 /dev/md3 1.9T 33M 1.9T 1% /mnt/disk3 /dev/md4 1.9T 33M 1.9T 1% /mnt/disk4 /dev/sdb1 56G 11G 46G 19% /mnt/cache shfs 7.3T 261G 7.1T 4% /mnt/user0 shfs 7.4T 271G 7.1T 4% /mnt/user /dev/loop0 10G 4.8G 4.4G 53% /var/lib/docker root@Tower:~# Suggestions welcome. There must be some way to figure out what's dying.
Archived
This topic is now archived and is closed to further replies.