Jump to content

prostuff1

Moderators
  • Content Count

    6343
  • Joined

  • Last visited

Community Reputation

5 Neutral

About prostuff1

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • URL
    http://www.greenleaf-technology.com
  • Personal Text
    Greenleaf Technology

Recent Profile Visitors

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

  1. We do still build systems, though the builds have changed a bit so best to drop up an email. I am working on a new website though I do not know quite when it will go out.
  2. The latest update of the container breaking nextcloud was a big pain in the butt for me. I ended up without my nextcloud install for nearly a week before I got everything back up and running (probably could have gotten it figured out and reinstalled faster but just not enough time in the day). I had to downgrade the docker container with the "linuxserver/nextcloud:140 tag. From there I upgrade nextcloud from within the docker using the command line. But I could not just jump from version 13, which I think was the one within the docker for the tag I installed. I had to upgrade to 14, which had it's own set of issues, then to 15, which went fine, and then to 16 which also when fine. Once nextcloud was all up to date within the docker I had to manually run some fo the indices updates for nextcloud, and then remove the :140 tag from the docker container to get up to date on the latest docker. I did manager to get everything squared away and running again but it was not an overly easy process and for someone not comfortable with the command line might be more than they are willing to tackle.
  3. I just ran into this issue as well. I have a very old system built for a customer from nearly 10 years ago now. It is only ever used as a file server so there was no real reason to touch it. Well, parts finally started to fail (not the motherboard or processor but the drive cages). The customer was not interested in upgrading anything except for the unRAID OS version. I went to update it and of course nothing booted after 6.2.4. As soon as I put 6.3.5 on the USB drive and attempt to boot I would get the above mentioned error. I updated the BIOS on the board but that solved nothing. So some google-fu later I find this thread and the suggestion to add "root=sda" to the syslinux.cfg. That seems to have worked on the OLD Biostar A760G M2+ board with a Phenom II X4 in it. Not sure what in the kernel between 6.2.4 and 6.3.5 made it stop booting but the "root=sda" trick works fine on this old build.
  4. I am currently sitting on 296 days and counting on my main machine and my other machine is at 66 days.
  5. I have not had a chance to play with getting the docker up and running on my unRAID machine. I plan to play with it sometime this week and will be sure to do a writeup after I get it going.
  6. Duplicati docker backing up to an Amazon S3 account. That is likely what I will be doing for all my computers for an "offsite backup" replacement (had Crashplan Home). My next step is a Minio serice running on my server and then backing up via Duplicati to that to get full backups in 2 different locations.
  7. I just posted a request on the linuxserver.io forums (you can find it here https://forum.linuxserver.io/thread-585.html) about getting a Minio docker created. I found a blog article discussing the use on Minio and duplicati to mimic Crashplan Home. I will likely be combining duplicati with an Amazon S3 service to get the cloud backup portion taken care of; but that does not cover the Crashplan server I had running locally and was also backing up to. I believe I can get Minio and Duplicati to work together so that it will function the same or very close to how my local crashplan server did. I found a blog article talking about using these 2 apps together here (http://blog.quindorian.org/2017/08/diy-cloud-backup-replacing-crashplan-home-family-diy-style.html/) Thoughts and comments welcome.
  8. Install the "Command Line Tool" through Community Applications and try it out instead.
  9. Back in the day when i was running unRAID under ESXi I was using Plop to "load" the flash drive so ESXi could use it. Honeslty have not done and ESXi stuff in a while so not sure if that is still needed/used.
  10. I would also consider upgrading the CPU to at least a E3-1230 or better. The 1220 does NOT have hyperthreading. I would not bother with with VM1, VM2, or VM3. Get a big SSD and set it as a cache drive in unRAID. Use that as the VM location and go about creating your editing VM there. All the apps you want/need to run can be done via docker and take up less space then full blown VM's
  11. My dedicated crashplan backup server that runs unRAID is usually up for quite a while at a time as I do not usually bother updating with every unRAID release. My main server was up for nearly a year and a half at one point. I skipped one whole release of unRAID on my main server, mostly because it was a "if it aint broke don't fix it"
  12. Yeah, I am going to have to start looking at alternatives now. I am currently looking into https://www.duplicati.com/ and https://www.arqbackup.com/. Kind of want to see what a Duplicati docker would be like and if someone could get it up and running. I could just pay for an unlimited cloud storage at amazon, google, microsoft, etc on a per month and then send all the computers that i was sending to crashplan there. If anyone out there has played with either of the above mentioned please chime in on your opinions.
  13. The linked post above is from Limetech so you should be fairly confident in the information provided there. There is no 100% gaurentee that it will not change in the future but for now everything works as you would like. Limetech has been pretty understanding about the users needs/wants/desires.
  14. Ditto for me as well. I rarely restart my dedicated Crashplan box so it is not a huge deal for me but it is a little annoying.