January 9, 201610 yr I started memtest last night so far so good. It is on Test #6 how long should it run for? chip, have you run memtest for 24 hours? That would be useful to check your memory is good. Also post your full machine specs here as well. Also chip, how much memory have you allocated to the VM?
January 9, 201610 yr Author Sorry about that I have 8gb. 2gb dedicated to VM. As a starting point I have purchased more memory so my board will be maxed out at 16gb. I wanted to max it out anyway. Also someone PMd me this - https://lime-technology.com/forum/index.php?topic=45286.msg432335#msg432335 So it might be Docker/cpu related as well.
January 9, 201610 yr You're not using SABNzbd though? I'd be interested in whether more memory solves this, but to be honest allowing 6GB for Unraid I would have thought would be sufficient and I'm not convinced it will be the cause of your issues? What's your network setup like? Could it be a faulty ethernet cable / switch / router? You say you can login to cmd prompt but wasn't clear whether that was local or over telnet/SSH
January 9, 201610 yr Author It was over telnet using putty. Trying to figure what this means from the syslog - Jan 8 21:22:51 HPTower kernel: general protection fault: 0000 [#1] PREEMPT SMP Jan 8 21:22:51 HPTower kernel: Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_amd kvm vhost_net vhost macvtap macvlan tun ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod k10temp i2c_piix4 pata_atiixp r8169 ahci mii libahci acpi_cpufreq [last unloaded: md_mod] Jan 8 21:22:51 HPTower kernel: CPU: 5 PID: 7353 Comm: shfs Not tainted 4.1.13-unRAID #1
January 11, 201610 yr Anyone on the recent data I posted? Haven't followed / read the complete thread, but have you tried to redownload the unRAID zip file and put a fresh copy of bzoot and bzimage on your flash device? As an extra security matter I would take the flash drive out and do a disk check to ensure there is no corruption prior to copying the files above.
January 12, 201610 yr Author Not got a clue chip on that last error. You stuck the new memory in yet? No I just ordered late Friday so hopefully see it late this week. Also don't want to do everything at once as I want to know what the issue is. I am hoping memory will help with some of the issues.
January 14, 201610 yr Author Ok added memory to it yesterday. Turned on 3 dockers I have running at all times. Didn't spin up the VM yet as I want to just test the Dockers to see if they crash it.
January 17, 201610 yr Author Hung up already and couldn't get to web, shares, or run diagnostics from putty or from console directly. Running memtest since this is new memory. Than I guess I will implement one of the other changes I mentioned on page 1.
January 19, 201610 yr Hung up already and couldn't get to web, shares, or run diagnostics from putty or from console directly. Running memtest since this is new memory. Than I guess I will implement one of the other changes I mentioned on page 1. This is my normal. Wasn't the mem as I let the memtest run and had 0 errors. When mine crashes it seems to shut everything down... USB, HDMI, DVI, LAN, etc
January 26, 201610 yr Author Ok it was up for 7 days and yesterday I got home from work and it was hung up again. No web access Shares showed up but couldn't access Could putty to it but not run diagnostics Couldn't reboot from putty or console screen. Had to do a hard reboot.
January 29, 201610 yr Author OK crashed again. Can't get to web/shares. Can putty but running diagnostics just hangs. I was running makemkv as I was ripping something. Also have LMS running - odd thing is my music is still playing and I can still access that interface OK. Here is a screenshot of the monitor and what was on the screen.
January 29, 201610 yr My guess... Seems like a dying drive. and as the OS retries the drive, the whole crawls to a halt. Reboot. Stop the array. try to gather the diagnostics. look at the smart reports for each drive. You have a drive that might be throwing smart errors.. or just have a faulty cable connection.
January 29, 201610 yr Author I just ran smart tests on all the drives a week ago and all reports were good. I did short and long tests. How do I know which cable is bad?
January 30, 201610 yr Community Expert Post the SMART reports or look at attribute 199, UDMA_CRC_error, any value above 0 could indicate bad SATA cable, but could also be old errors, so if any disk is above 0 monitor value, if it keeps increasing replace cable.
January 30, 201610 yr Chip, That SanDisk Ultra Fit. I have one like it but my problem was every time unraid would boot on it, it would unmount and no matter what it would not re-mount. Have you tried coping to a new different (make/model) of stick and running it that way. FYI, this stick would also do this during windows installs. You'd have to remove it and put it in a new port to get it work.
January 30, 201610 yr Author Ok I will try both mentioned items. I thought those thumb drives were rated good?
February 1, 201610 yr Author Here is disk 4 disks. looks like they all read 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 WDC_WD30EZRX-00D8PB0_WD-WMC4N0K0KHFS-20160131-1634.txt WDC_WD30EZRX-00D8PB0_WD-WMC4N0K9CA77-20160131-1634.txt WDC_WD30EZRX-00DC0B0_WD-WMC1T1698640-20160131-1634.txt WDC_WD30EZRX-00SPEB0_WD-WCC4E3LXUC3F-20160131-1634.txt
February 1, 201610 yr Community Expert You disks look fine, and the ata12 error in the previous screenshot is from your bd drive ata12.00: ATAPI: HL-DT-ST BD-RE WH14NS40, K9HC79F3352, 1.03, max UDMA/100 Doubt that’s the problem but you can disconnect it and try, other than that I'd start by running in safe mode with all dockers off, if it doesn’t crash turn them on one at a time.
February 4, 201610 yr Ok I will try both mentioned items. I thought those thumb drives were rated good? The Non-Ultra ones are rated good. They have not rated these ones which are only 2nd the extreme pro sticks.
February 5, 201610 yr I have the same problem: Dynamix webinterface not responding. Other webinterfaces of dockers continue to respond nominal. I had this happen a few times already, all v6 and last week on a near-new installation. When its idling, nothing goes wrong. This time it was restoring disk1 (i put in a 6TB hdd) and i enabled virtualbox. It worked at that time, but not shortly after. The syslog is: Feb 5 19:10:35 bTower dnsmasq[13042]: read /etc/hosts - 1 addresses Feb 5 19:10:35 bTower dnsmasq[13042]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Feb 5 19:10:35 bTower dnsmasq-dhcp[13042]: read /var/lib/libvirt/dnsmasq/default.hostsfile Feb 5 19:10:35 bTower kernel: virbr0: port 1(virbr0-nic) entered disabled state Feb 5 19:16:02 bTower rc.virtualbox[16378]: Plugin configuration written Feb 5 19:16:22 bTower emhttp: cmd: /usr/local/emhttp/plugins/virtualbox/scripts/rc.virtualbox install Feb 5 19:16:22 bTower rc.virtualbox[16555]: Installing Virtualbox package (v5.0.14)... Feb 5 19:16:31 bTower groupadd[16820]: group added to /etc/group: name=vboxusers, GID=999 Feb 5 19:16:31 bTower groupadd[16820]: group added to /etc/gshadow: name=vboxusers Feb 5 19:16:31 bTower groupadd[16820]: new group: name=vboxusers, GID=999 Feb 5 19:16:32 bTower kernel: vboxdrv: Found 8 processor cores Feb 5 19:16:32 bTower kernel: vboxdrv: TSC mode is Invariant, tentative frequency 2659870408 Hz Feb 5 19:16:32 bTower kernel: vboxdrv: Successfully loaded version 5.0.14 (interface 0x00240000) Feb 5 19:16:32 bTower kernel: VBoxNetFlt: Successfully started. Feb 5 19:16:32 bTower kernel: VBoxNetAdp: Successfully started. Feb 5 19:16:32 bTower kernel: VBoxPciLinuxInit Feb 5 19:16:32 bTower kernel: vboxpci: IOMMU found Feb 5 19:16:32 bTower rc.virtualbox[17062]: Installation of Virtualbox package v5.0.14 succeeded Feb 5 19:16:32 bTower rc.virtualbox[17063]: /boot/custom/vbox does not exists - Cannot change VirtualBox symlink Feb 5 19:16:32 bTower rc.virtualbox[17064]: Installing Virtualbox Extension package (v5.0.14)... Feb 5 19:16:35 bTower rc.virtualbox[17154]: Installation of Virtualbox Extension package v5.0.14 succeeded Feb 5 19:23:25 bTower rc.virtualbox[19622]: Plugin configuration written Feb 5 19:23:33 bTower emhttp: cmd: /usr/local/emhttp/plugins/virtualbox/scripts/rc.virtualbox start_vboxwebsrv Feb 5 19:23:33 bTower rc.virtualbox[19846]: /opt/VirtualBox/VBoxManage setproperty websrvauthlibrary null Feb 5 19:23:33 bTower rc.virtualbox[19861]: vboxwebsrv service started Feb 5 21:29:06 bTower sshd[17897]: Accepted password for root from 192.168.2.89 port 50513 ssh2 Feb 5 21:36:34 bTower emhttp: main: can't bind listener socket: Address already in use Note after i used the webinterface to enable virtualbox, it stopped working. Perhaps the line Feb 5 19:23:33 bTower emhttp is related..? So i tried restarting the web interface: killall emhttp nohup /usr/local/sbin/emhttp & But to no avail. Then i remembered i changed the Dynamix webinterface port from 80 to 8888, because i needed port 80 for a docker. I cant remember where i set that. I'd rather not powercycle and lose the preclear its doing on my new drive.. update 1 - To the powers that be: perhaps changing the Dynamix port would be a good feature to add. update 2 - i just unforgot how i set the Dynamix port. http://lime-technology.com/forum/index.php?topic=24730.0 root@Tower:/var/log# killall emhttp emhttp: no process found root@Tower:/var/log# nohup /usr/local/sbin/emhttp -p 8888 & [1] 26291 root@Tower:/var/log# nohup: ignoring input and appending output to ‘nohup.out’ [1]+ Segmentation fault nohup /usr/local/sbin/emhttp -p 8888 root@Tower:/var/log# But.. nothing. what .. wait .. SEGFAULT ?! This same hardware (case+psu+mobo+ram+cpu) ran Windows for years without problems.. i really think its the software at fault here..
Archived
This topic is now archived and is closed to further replies.