buzzra

Members
  • Content Count

    37
  • Joined

  • Last visited

Everything posted by buzzra

  1. Nevermind. Deleted it. doesn't work and no support.
  2. Hello, I just installed from Unraid Community Applications. No changes made to config. I go to http://myserver.mydomain.com:8438 and the Pinry homepage comes up. And that's it. I can't register, I can't login, and I don't know how to pin anything. Where do I go from here? I thought I read all the docs, but there is nothing about admin except editing the local_settings.py file, but no explanation of how to edit or why. Thanks buzz
  3. This definitely needs to happen. It has been promised for over 3 years. Or, at least, the Doc needs to be changed to reflect that we still only have NFSv3 and NFSv4 cannot be enabled. I tried to edit the wiki, but I don't have permissions. buzz
  4. That's wierd. I get connection failed in both Chrome and Firefox with HTTPS. Something strange about my setup I'll have to figure out. Thanks buzz
  5. So, it only works via HTTP, but the link on the Unbalance settings page goes to HTTPS and you get an error. buzz
  6. Yep, parity was good. So a precautionary step you could take would be to copy just the emulated disk's data somewhere else before you replace it, in case something like this happens during rebuild. Probably not necessary most of the time, but it is something you could do if you wanted to be extra sure not to lose data. I'll have to remember that, but I probably wouldn't have done it this time anyway. 🙄
  7. @jonathanm That's probably what I'm gonna do. It was all media files. I can get them again. I still need to sync a library and see what went away. Thinking about this, If a drive goes away and is being emulated, can I still copy the data from just that drive? Was there an emulated diks4 share? I have never looked to see if that was true when I've had one being emulated.
  8. Thanks @itimpi! it works great, but knowing the file type is not helping much. I guess I could rename with the correct type and then open and see what each is. But that would take YEARS with the thousands of files in the lost+found folder that have no identification. So still pretty much lost. It is very frustrating knowing that the total used space on that drive is almost exactly what the original was, but it is 97% in the lost+found with no identification of any kind.
  9. Well, I started the array after the reiserfsck --rebuild-tree completed. The array is up and shows healthy. BUT... There are a CRAPLOAD of files in the lost +found folder. A lot have names and are in folders but most are just files with numbers for names. Pretty much no way to figure out what they were. So in essence most of the data on that drive was lost. Most likely it is because I replaced a bad drive with a bad drive, but there were no errors with the drive in it's previous life. I have replaced drives before in Unraid with used drives I had, but never had this pro
  10. Running it now. Should I deal with any files in the lost+found folder before or after I start the array with maintenance mode unchecked?
  11. Well that didn't take as long as I expected. Ended saying I need to run with the --rebuild tree option. Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 24 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Sun Oct 6 16:27:48 2019 ########### Any recommendations before I run it?
  12. Thanks Squid. Running the reiserfsck --check now. The replacement disk was not new, but had not had any known errors in it's previous life. It only had a blank partition on it. Was I just lucky enough to use a bad drive to replace a bad drive? That would be par for the course 🙄. Also, do you think I've lost any data at this point if the drive gets repaired? I don't see it being emulated. I have some new larger drives and am planning to upgrade parity then use the new disks to upgrade to XFS. Just need to get one of those 'round tuits' 😉 buzz
  13. Hello everyone, I found disk 4 in my array had failed and was being emulated. I stopped the array and powered it off. I replaced the failed disk with another one of the same size. I powered on the array, chose the new disk as a replacement for the bad drive, and started the array. I noticed the unmountable error, but ignored it because the array was rebuilding. After the rebuild the array is up, parity shows valid and last check completed with no errors. The problem is that drive 4 still shows "Unmountable: No file system", and I still have the option to format the unmountable disk 4. All
  14. Funny you should ask. I was researching this too since my last post. My filesystem is ReiserFS, since I have had my Unraid up for quite a few years. I was thinking this may be the problem, because the only things I see about it online are problems with Windows NTFS and Mac HFS. I can move my cache drive to XFS, but that's not going to be any time soon. Does anyone else have this container running on a ReiserFS system? Any other suggestions are welcome. Thanks again for all your time on this. buzz
  15. Still no good. cannot get to the webui. Still the same errors creating the database. init_db.log: Installing MariaDB/MySQL system tables in '/config/mysql' ... 2019-02-09 12:42:35 23429459561352 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95 2019-02-09 12:42:35 23429459561352 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space 2019-02-09 12:42:35 23429459561352 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again. 2019-02-
  16. I understand that, but you didn't answer the question. I would still like to see a change log of what was updated. Does such a thing exist, and if not, why? buzz
  17. Is there anyway to see what changes are in each of these docker updates? I have done all of them, and the version number on the server management dashboard has not changed since v4.0.1.0. buzz
  18. I followed the instructions above. Still not working. After removing the appdata folder and restarting the container, it comes up for a few seconds, creates the appdata folder and everything beneath it, and then stops. The init_db.log file is created with the same error. If I restart the container, it comes up and stays up, but I still can't get to the webui. I verified the changes to the 'run' file were still there. Here are the contents of current 'run' file and init_db.log: #!/usr/bin/with-contenv sh set -e # Exit immediately if a command exits with a non-zero status. set -u
  19. Yep, works when set to /tmp/NginxProxyManager. Will not work set to any user share on the array or the cache drive. Any ideas why? I have other Dockers running fine using the appdata share on the cache drive. I also have VMs running on another cache drive only share. Thanks for the help buzz
  20. There are no errors in the Nginx logs, but this is the init_db.log: Installing MariaDB/MySQL system tables in '/config/mysql' ... 2019-02-01 2:06:01 22916083571592 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95 2019-02-01 2:06:01 22916083571592 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space 2019-02-01 2:06:01 22916083571592 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again. 2019-02-01 2:06:01 22916083571592 [ERROR] P
  21. I'm having a strange problem with this docker. I finally got the time to install it, and everything seemed to go fine. I left all the settings default, since there were no conflicts with other dockers or VMs my Unraid host. The problem is that I can't get to the webui. I try to connect to 'myunraidip:7818' and I get "This site can’t be reached x.x.x.x refused to connect." I can connect to :1880 and get the Nginx congratulations page. I did an Nmap scan of my host from another machine and I see all the ports I expect open, except 7818. Any ideas? buzz
  22. Thanks for the explanation. Makes complete sense. And thanks Djoss for packaging this up in an Unraid container. I hope no one was offended by my questions. I just saw both and had not seen an explanation of the relationship. I will be installing this and moving my other containers to it. It looks to be VERY easy to manage. I have been using a sort of 'automatic' reverse proxy named nginx-proxy (https://hub.docker.com/r/jwilder/nginx-proxy/~/dockerfile/) but it took a lot to get it working in Unraid. Thanks again to everyone supporting this project. buzz
  23. If I go to the homepage listed in the OP, https://nginxproxymanager.jc21.com, and then click on the githublink on that page, I get a different github repository than listed in the OP, https://github.com/jlesage/docker-nginx-proxy-manager. So which one is the correct one? It appears that the Unraid template is using the jlesage repository, but in a previous post here, someone requested feature requests and bugs be reported to the jc21 repository. So, what's the difference and which one should we be using? If I'm using jlesage version on Unraid, why report bugs to jc21? buzz
  24. What's the trick to using the F-keys from webterminal? I can't seem to make anything work but the arrow and tab keys. Thanks buzz Edit: Never mind I figured it out. I was remoting from work to my home PC and launching webterminal. That won't work. F-keys get lost in the translation.
  25. Can't believe this was taken away. I've never been on a forum that didn't let you search a specific topic. Any idea when this will be fixed? buzz