Jump to content

newbie_dude

Members
  • Content Count

    65
  • Joined

  • Last visited

Community Reputation

0 Neutral

About newbie_dude

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. init: cannot execute "/bin/sh" init: cannot execute "/bin/sh" init: cannot execute "/bin/sh" init: cannot execute "/bin/sh" init: cannot execute "/bin/sh" init: Id "c6" respawning too fast: disabled for 5 minutes init: cannot execute "/bin/sh" init: Id "c3" respawning too fast: disabled for 5 minutes init: cannot execute "/bin/sh" init: cannot execute "/bin/sh" init: Id "c4" respawning too fast: disabled for 5 minutes init: cannot execute "/bin/sh" init: Id "c1" respawning too fast: disabled for 5 minutes init: cannot execute "/bin/sh" init: Id "c5" respawning too fast: disabled for 5 minutesinit: cannot execute "/bin/sh" init: cannot execute "/bin/sh" init: Id "c2" respawning too fast: disabled for 5 minutes Everything was fine up until I upgraded to 6.4. Now I get this while booting and it's stuck after that. I saw in another thread to check if the USB drive had any issues by plugging it into a windows computer. I did and there was no issues. And also renamed the EFI- folder to EFI. No change. Still stuck here. Is anyone else having this issue? If so, solution? Thanks!
  2. Thanks for the clarification. Just wanted to make sure I wasn't the only one getting the issue. I guess I'll just keep disconnecting and reconnecting until I see the update dialogue box and go from there. Cheers
  3. Is anyone getting the issue where you can't click inside the filezilla interface? I can click on the initial "OK" Button, but when filezilla GUI starts, nothing responds. Edit: Submitted too early. I suspect it has something to do with the update filezilla dialog box. If I keep reloading the page, after a long time, I might get the update filezilla dialog box to show up inside the docker. Most of the time, it doesn't appear. And then I can click "no don't update" and go on as normal. I hope that wasn't too confusing
  4. I want to try and install django on unraid to run a simple app server. So I ended up here: https://hub.docker.com/_/django/ But from the comments, someone posted this: https://github.com/morninj/django-docker I added that to my template repositories list, but that repo does not show up in the container list when I go to add a container. I also added "https://github.com/docker-library/official-images" to the list of repos but none of those dockers are part of the list. Is there a tutorial I can follow to install https://github.com/morninj/django-docker? Thanks!
  5. Well, it's definitely that .... When I started parity check: Mon Feb 1 22:07:02 EST 2016 k10temp-pci-00c3 Adapter: PCI adapter temp1: +56.0°C (high = +70.0°C) nct6776-isa-0290 Adapter: ISA adapter Vcore: +1.23 V (min = +0.00 V, max = +1.74 V) in1: +1.86 V (min = +0.00 V, max = +0.00 V) ALARM AVCC: +3.38 V (min = +2.98 V, max = +3.63 V) +3.3V: +3.36 V (min = +2.98 V, max = +3.63 V) in4: +1.63 V (min = +0.00 V, max = +0.00 V) ALARM in5: +1.72 V (min = +0.00 V, max = +0.00 V) ALARM in6: +1.00 V (min = +0.00 V, max = +0.00 V) ALARM 3VSB: +3.46 V (min = +2.98 V, max = +3.63 V) Vbat: +3.38 V (min = +2.70 V, max = +3.63 V) fan1: 809 RPM (min = 0 RPM) fan2: 3176 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) SYSTIN: +40.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor CPUTIN: +56.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor AUXTIN: +0.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP: +0.0°C PCH_MCH_TEMP: +0.0°C intrusion0: ALARM intrusion1: ALARM beep_enable: disabled When I decided to chicken out: Mon Feb 1 22:10:33 EST 2016 k10temp-pci-00c3 Adapter: PCI adapter temp1: +74.6°C (high = +70.0°C) nct6776-isa-0290 Adapter: ISA adapter Vcore: +1.06 V (min = +0.00 V, max = +1.74 V) in1: +1.85 V (min = +0.00 V, max = +0.00 V) ALARM AVCC: +3.38 V (min = +2.98 V, max = +3.63 V) +3.3V: +3.36 V (min = +2.98 V, max = +3.63 V) in4: +1.64 V (min = +0.00 V, max = +0.00 V) ALARM in5: +1.72 V (min = +0.00 V, max = +0.00 V) ALARM in6: +1.02 V (min = +0.00 V, max = +0.00 V) ALARM 3VSB: +3.46 V (min = +2.98 V, max = +3.63 V) Vbat: +3.38 V (min = +2.70 V, max = +3.63 V) fan1: 817 RPM (min = 0 RPM) fan2: 3176 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) SYSTIN: +41.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor CPUTIN: +71.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor AUXTIN: -0.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP: +0.0°C PCH_MCH_TEMP: +0.0°C intrusion0: ALARM intrusion1: ALARM beep_enable: disabled Now: Mon Feb 1 22:17:44 EST 2016 k10temp-pci-00c3 Adapter: PCI adapter temp1: +62.0°C (high = +70.0°C) nct6776-isa-0290 Adapter: ISA adapter Vcore: +1.06 V (min = +0.00 V, max = +1.74 V) in1: +1.86 V (min = +0.00 V, max = +0.00 V) ALARM AVCC: +3.38 V (min = +2.98 V, max = +3.63 V) +3.3V: +3.38 V (min = +2.98 V, max = +3.63 V) in4: +1.65 V (min = +0.00 V, max = +0.00 V) ALARM in5: +1.72 V (min = +0.00 V, max = +0.00 V) ALARM in6: +1.05 V (min = +0.00 V, max = +0.00 V) ALARM 3VSB: +3.46 V (min = +2.98 V, max = +3.63 V) Vbat: +3.38 V (min = +2.70 V, max = +3.63 V) fan1: 817 RPM (min = 0 RPM) fan2: 3183 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) SYSTIN: +42.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor CPUTIN: +62.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor AUXTIN: -3.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP: +0.0°C PCH_MCH_TEMP: +0.0°C intrusion0: ALARM intrusion1: ALARM beep_enable: disabled The CPU temp is going up, but what is going up even more is the PCI device. Which is my sata controller card (I think. I have a pci-e sata card and a pci video card and that's it). It doesn't have a fan. But I guess it's time for me to put in a fan on the side vent to cool it and see what happens! Is there even remotely a possibility that this might be an unraid issue? I have had the same setup for about 8 months or so. And only recently upgraded to unraid 6 when this started happening. Thanks so much!!
  6. Thanks so much! That actually giving me a lot to think about. The only reason I suspected HD overtemp was because the very first time this happened, I got an email with HD Temp warning because I do have notifications setup. Then I noticed the server had shut down. Ever since then I do not get a warning email, the server just shuts down. And I just assumed it was the same issue. I will install the Dynamix System Temperature plugin and check to see what's happening. I have a cheap amd sempron 145 in the system because I didn't want anything fancy. But if it's overheating, maybe it's time for an upgrade This is what I get when I follow https://lime-technology.com/wiki/index.php/Setting_up_CPU_and_board_temperature_sensing: k10temp-pci-00c3 Adapter: PCI adapter temp1: +53.5°C (high = +70.0°C) nct6776-isa-0290 Adapter: ISA adapter Vcore: +1.06 V (min = +0.00 V, max = +1.74 V) in1: +1.86 V (min = +0.00 V, max = +0.00 V) ALARM AVCC: +3.38 V (min = +2.98 V, max = +3.63 V) +3.3V: +3.38 V (min = +2.98 V, max = +3.63 V) in4: +1.62 V (min = +0.00 V, max = +0.00 V) ALARM in5: +1.72 V (min = +0.00 V, max = +0.00 V) ALARM in6: +0.96 V (min = +0.00 V, max = +0.00 V) ALARM 3VSB: +3.46 V (min = +2.98 V, max = +3.63 V) Vbat: +3.38 V (min = +2.70 V, max = +3.63 V) fan1: 804 RPM (min = 0 RPM) fan2: 3183 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) SYSTIN: +38.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor CPUTIN: +54.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor AUXTIN: +3.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP: +0.0°C PCH_MCH_TEMP: +0.0°C intrusion0: ALARM intrusion1: ALARM beep_enable: disabled Should I be keeping an eye on CPUTIN? 54 seems very high for idle does it not? I haven't started the array yet since it will start a parity check. I will run sensors over ssh every 30 seconds and see what happens to it and when it shuts down with root@Tower:~# while true; do date; sensors; sleep 30; done I hope it's not the power supply though. It's a 1000w supply that is supposed to be good This is just a very odd issue. It will shut down for a few times, and then complete the parity check without shutting down. No idea why. I will be back. Thanks so much for the hints!
  7. Hi All, My parity checks have become a source of pain since last month. Unraid will start a parity check and then shut down without any notice. I think it might be temperature related, but that should be a clean shoutdown right? I have clean powerdown installed. The next time I start the array, it detects an unclean shutdown. Is there any way for me to confirm? To see if there was any logs, I ran "tail -F /var/log/syslog" over ssh to try and capture any output. Unfortunately, the only output I see after starting parity check and before shutdown is this: Feb 1 18:05:13 Tower emhttp: shcmd (80): /usr/sbin/hdparm -y /dev/sdg &> /dev/null SDG is my cache drive. Would the rest of the log help? I have what I captured from syslog over ssh. Is there anything I can do to track down the cause? Thanks so much!
  8. I have a simple script that needs 3.5. Is there a way I can install it and not interfere with the existing python install that's on the server? I don't want to break anything. Unfortunately there seems to be no plugins for installing it Thanks so much!
  9. I hoping I'm doing something stupid. My server configuration is attached. I use Viscosity in my mac for VPN. But I can't seem to connect to my unraid server It fails on TLS handshake. I've opened port 1194 in my router. Here is what I see on client side: Jan 08 14:32:22: Viscosity Mac 1.5.11 (1314) Jan 08 14:32:22: Viscosity OpenVPN Engine Started Jan 08 14:32:22: Running on Mac OS X 10.7.5 Jan 08 14:32:22: --------- Jan 08 14:32:22: Checking reachability status of connection... Jan 08 14:32:22: Connection is reachable. Starting connection attempt. Jan 08 14:32:22: OpenVPN 2.3.8 x86_64-apple-darwin [sSL (OpenSSL)] [LZO] [PKCS11] [MH] [iPv6] built on Sep 23 2015 Jan 08 14:32:22: library versions: OpenSSL 1.0.2d 9 Jul 2015, LZO 2.09 Jan 08 14:32:23: Control Channel Authentication: using '/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/connection.puyVrx/ta.key' as a OpenVPN static key file Jan 08 14:32:23: UDPv4 link local: [undef] Jan 08 14:32:23: UDPv4 link remote: [AF_INET]99.XXX.XXX.XXX:1194 Jan 08 14:33:23: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Jan 08 14:33:23: TLS Error: TLS handshake failed Jan 08 14:33:23: SIGUSR1[soft,tls-error] received, process restarting Do I need to open more ports? Or is there something else with the configuration that's incorrect? Thanks for your help!
  10. I'm an utter fool. I knew this couldn't have been an unique problem. I just don't know how to search. Even after Squid told me exactly what to search for. In short, this problem was discovered and the solution posted ages ago. I just had to go through a few google suggestions before I ended up back in this forum! http://lime-technology.com/forum/index.php?topic=12404.0 Thanks everyone for your help! I hope it will work from now on!! Cheers!
  11. Thank you so much for looking into it! I'm going to google some more. It's very odd I'm going to attach my system log here incase someone can spot something in there that I can't: http://pastebin.com/0jN4D8hp
  12. Thankyou so much! I ran the command and it seems to have worked. But the drives are still not being recognised by Unraid This is the logfile: sas2flash.efi -l Flashlog.txt -o -f 2118it.bin -b mptsas2.rom Advanced Mode Set Adapter Selected is a LSI SAS: SAS2008(B2) Executing Operation: Flash Firmware Image Firmware Image has a Valid Checksum. Firmware Version 19.00.00.00 Firmware Image compatible with Controller. Valid NVDATA Image found. NVDATA Version 11.00.00.00 Checking for a compatible NVData image... NVDATA Device ID and Chip Revision match verified. NVDATA Versions Compatible. Valid Initialization Image verified. Valid BootLoader Image verified. Beginning Firmware Download... Firmware Download Successful. Verifying Download... Firmware Flash Successful. Resetting Adapter... Adapter Successfully Reset. Executing Operation: Flash BIOS Image Validating BIOS Image... BIOS Header Signature is Valid BIOS Image has a Valid Checksum. BIOS PCI Structure Signature Valid. BIOS Image Compatible with the SAS Controller. Attempting to Flash BIOS Image... Verifying Download... Flash BIOS Image Successful. Updated BIOS Version in BIOS Page 3. Finished Processing Commands Successfully. Exiting SAS2Flash. Should I try upgrading to 20? But the rom you pointed to is named "mptsas2.rom" but the official one form lsi is named "ebcsas2.rom". Not sure if they are the same Thanks for your help!
  13. Thanks! But now I have some really stupid questions that hopefully you're willing to suffer I'm following the instruction from here: http://lime-technology.com/forum/index.php?topic=12767.msg121131#msg121131 (p10.zip) Which lists the following steps: 7) Launch each step, Step 1, 1.bat (This will dump all the information about your card to a file Named ADAPTERS.TXT In this file is your SAS Address which will be required for step 6 (6.bat) Example: HW Configuration ================ SAS Address : 500605b001f31fa0 Step 2, 2.bat will save your current controllers SBR to a file Mega.sbr, please rename it to the cards model your using this on, example IBM M1015, rename mega.sbr to SBRM1015.bin and post on the forum (would like to collect all SBRs) 9) Step 3, 3.bat will wipe your current SBR and clear your controllers BIOs. 10) Set 4, Shutdown your system now, plug your USB stick in another system were you can get at the ADAPTERS.TXT (that was dumped in step 1) file to write donw your SAS Controllers Address 11) Put back usb stick in the system with the Mega card and boot to usb again. 12) In step 5 you can Flash your card to either IT or IR mode by lauched the respective batch file (5IT.bat or 5IR.bat) This will file your mega controller to SAS2008 firmware P10 (lastest as of time posted) 13) Step 6, 6.bat will echo out the command you need to run manually in a commandline to re-program back your SAS Address you obtain when you shutdown your system and wrote it down from the ADAPTERS.TXT file However, When I run 1.bat which has, MegaCli.exe -AdpAllInfo -aAll -ApplogFile AdaptersInfo1.txt To get my address, it only returns "Exit Code: 0x01" and no address. This command definitely worked when I was setting up the card. Does that mean I don't need to run any steps other than step 5 which actually upgrades the bios? and for that, do I take the "2118it.bin" file from the "LSI MegaRAID to SAS2008(P10).zip" file and "ebcsas2.rom" file from "UEFI_BSD_P19.ZIP" and run step 5? Step 5: sas2flsh.exe -l Flashlog.txt -o -f 2118it.bin -b mptsas2.rom Thanks so much! I can't believe I didn't save the files from last time
  14. I think I found the IDE problem. Apparently AMD motherboards have this weird setting for sata IDE combined mode for ata5: http://forums.tweaktown.com/asrock/49745-970-extreme4-need-uefi-setup-manual.html I disabled it. And now I have this: Dec 19 10:19:57 Tower kernel: ata5.00: ATA-8: HGST HDS5C4040ALE630, PL1331LAGHZAUH, MPAOA580, max UDMA/133 Dec 19 10:19:57 Tower kernel: ata5.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Dec 19 10:19:57 Tower kernel: ata5.00: configured for UDMA/133 Which seems to have fixed it. Thanks! johnnie.black: I remember following the posts posted on this site to upgrade the firmare for the card and put it into IT mode. I just checked those threads and there doesn't seem to be an updated firmware. (To be honest, I don't know what I'm looking for exactly There are soo many models and numbers and variations) Is there a spot I can check for updated firmware that will put the card in IT mode for unraid? Thanks so much for your help!