robschaar

Members
  • Content count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About robschaar

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  1. If it helps, here is what it looks like when it finishes and mounts on 6.3.5 tower-diagnostics-20170619-2025.zip
  2. The motherboard has no floppy support. I don't really know why it thinks there is one connected.
  3. I will try to disable the floppy drive tonight. I formatted the flash drive and set everything to default. It still does the same thing. Attached is the diagnostics file. tower-diagnostics-20170619-1202.zip
  4. I just updated to the newest beta and tried again. It does the same thing. I did ssh into the server and saw the mounts are completing, but I am not able to see the shares on the network and the webservice quits working. It just stays on showing mounting drives. I attached the latest diagnostics. tower-diagnostics-20170619-0851.zip
  5. They do not show up on the network. The webserver also times out. It is not reporting to the webserver that it is finishing mounting the drives. Also none of the dockers load.
  6. I have it running on real hardware. Everything works while running 6.3.5, but when I try to run the beta, that is when the drives fail to mount. The machine is G41MT-S2PT with an Areca RAID controller.
  7. Here is the log after 7 minutes. tower-diagnostics-20170615-1520.zip
  8. I tried the previous beta version and now the latest beta version. My server is stuck at Mounting Disks, i've let it sit there for a couple hours and it never finishes mounting the disks. After awhile the web page will timeout and I need to ssh into the server to run the powerdown command. Attached is the log file. Does anyone have any hints as to what might be the cause? I also included the complete diagnostics after the powerdown. Thanks tower-diagnostics-20170615-0925.zip unraidlog.txt
  9. guess not....forgot to delete my data directory.
  10. So completely dumb.....I changed the name of the Docker to Pynab2 to give it one last shot and it worked right off the bat this time. I don't know what was sticking before, but now it is working (i mean waiting).
  11. same problem....not righting to the main folder
  12. i manually copied the files from /etc/postgresql/9.4/main to /data/main and now it is looking like it will work.
  13. it seems like it is during the postgres-initialise.sh *** Running /etc/my_init.d/003-postgres-initialise.sh... initialising empty databases in /data completed initialisation 2015-06-03 02:57:02,644 CRIT Supervisor running as root (no user in config file) 2015-06-03 02:57:02,647 INFO supervisord started with pid 55 2015-06-03 02:57:03,650 INFO spawned: 'postgres' with pid 59 2015-06-03 02:57:03,664 INFO exited: postgres (exit status 2; not expected) 2015-06-03 02:57:04,667 INFO spawned: 'postgres' with pid 60 2015-06-03 02:57:04,681 INFO exited: postgres (exit status 2; not expected) 2015-06-03 02:57:06,684 INFO spawned: 'postgres' with pid 61 2015-06-03 02:57:06,697 INFO exited: postgres (exit status 2; not expected) setting up pynab user and database 2015-06-03 02:57:09,703 INFO spawned: 'postgres' with pid 87 2015-06-03 02:57:09,715 INFO exited: postgres (exit status 2; not expected) 2015-06-03 02:57:10,717 INFO gave up: postgres entered FATAL state, too many start retries too quickly pynab user and database created building initial nzb import THIS WILL TAKE SOME TIME, DO NOT STOP THE DOCKER IMPORT COMPLETED *** Running /etc/my_init.d/004-set-the-groups.sh... Testing whether database is ready database appears ready, proceeding Traceback (most recent call last): File "/usr/local/lib/python3.4/dist-packages/sqlalchemy/pool.py", line 1033, in _do_get return self._pool.get(wait, self._timeout) File "/usr/local/lib/python3.4/dist-packages/sqlalchemy/util/queue.py", line 145, in get raise Empty sqlalchemy.util.queue.Empty For some reason it is not writing to the main directory inside config. That is I believe where my problem is. I tried to make sure it has permissions, but when I reboot all of it gets changed back to what it was.
  14. I have it setup with the exact same settings as my sabnzbd container.
  15. container and image
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.