pietjebell

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by pietjebell

  1. Alright I thought to give a little update on my mistake. Because I did cancel the delete really quick, only some files from my config folder were deleted. So with the files I had left on the USB, my diagnostics file and the old backup I started puzzling. With that, I managed to get the server back up and running relatively easy. My dockers were still running, but I did lose all the templates. So I have to be very careful with there to re-create all of them with templates, but with portainer I can see the current settings of the running containers. So yeah, it all works again. Thanks for all the help, I think this thread can be closed. Or placed on a wall of shame 🙂
  2. Omg I found a flash backup from juli last year. I have not made any significant changes since then (I think). I did recently remove the cache disk and replaced it for another. I think this would result in a error when it is booting. I can then just reassign the new SSD as cache? What would be the best way to recover this? Manually copy the files or completely flash that zip again to the USB? Thanks a lot for your help, and let this be a lesson to other people who read this BEFORE they do anything stupid 😂
  3. I think I tried rebooting it via IPMI, but the server did not come back online. As I said, it is in a remote location, so other factors could be in play. I'm just not counting on it. So I guess files on the USB have been deleted. I'll go to the server tonight and see what files are still left and make a backup of those as well. But questions still are: Can I use the config files from the diagnostics report? Is it as simple as just replace those in a new install?\ And if that not works: I got an old backup somewhere on the array. Can I somehow boot the array with a new install and then 'reinstall' when I got my hands on the backup again? Thanks for the advice as well. I was in another directory with cd (could see that in the terminal). But apparently for all files in the folder to be deleted, you need to use ./*. Still would never do it again like this haha
  4. Hi guys, First: I have been a total idiot. I wanted to delete files from a folder, so using the terminal I used cd to get to that folder and then typed 'rm -rf /*'. I was hoping to delete all files from that directory, but I immediately saw that the UI was giving errors. After some googling I found out that I deleted files from the root (USB?). Needless to say I was a bit disappointed in myself. As I am licking my wounds, I'm trying to see how I can recover what can be recovered. The server is in another location, so as of now I don't have physical access and I do not know what has been deleted (I did cancel the delete quite rapidly). I found out that if the config folder still exist, I can recover everything, right? I did make a backup once (quite long ago), but I did store that on the array (which is now not accessible). However, I did download diagnostics just this morning, which also happens to have a config folder. Are these the same config files I need? It does also have the super.dat file. Or is there anything else I should check? And is there something else that might give some hope that I can be up and running quite soon again? Thanks for thinking with me
  5. This is great! Now the main paperless docker starts downloading the proper tesseract data. I think it is a problem with the Unraid template for the Docker and everybody using other then English OCR will run into this problem. How can the docker be updated with this other variable?
  6. Alright, I'll try that. It's gonna be a challenge, as the server will probably become unresponsive on the network after updating. I'll see what I can do
  7. Hi, sorry to bump this topic. Hopefully somebody knows an answer to this problem. Thanks!
  8. Hi guys, Thanks in advance for helping me with this problem. I tried the upgrade three times already, but I had to rollback to 6.7.2 every time. The first time, my dockers weren't able to connect to the network somehow, so I wasnt able to connect to my VPN or Plex server (or any other dockers). The same happend to second time I tried to upgrade to 6.8. Last week I tried again to upgrade to 6.8.2, but that time I wasn't able to connect to the server at all via any other device. I had to boot into the GUI on the server itself to rollback to 6.7.2, which it is now happily running again. From my brief moments with 6.8.2, it looked like the server was running as I could connect to it locally. Also the information on the screen connected to the server didn't show any errors. It showed that the server was started and available on the IP address I assigned to it. Now I understand that this it is difficult to help with this problem, as I don't have any logging information right now. Hopefully it is a known problem (although I couldn't find others on the internet with my problems) and it is easily fixed. Of course I can try to supply information when needed. Hopefully I can run Wireguard soon .. Thanks, Dirk
  9. Oke, that sounds like the simple solution I was looking for! Thanks
  10. Hi all, It seems like a simple question, but my situation is slightly different from the answers I searched for already. I started my Unraid array with an SSD as the only disk. I've got a separate Freenas box which I wanted to use for my storage, since I trust ZFS more than any other RAID solution. Now things have change slightly. I bought a simple harddisk which I want to use as main drive and have the SSD as a cache drive. So I want to remove the data from the SSD, remove it from the array and have the old data stored on the HDD. What is the best way to do this? My Docker containers are all referenced to the 'user' map, which data is stored on all the HDD's (I believe). So how do I clear my SSD so I can safely remove it and add it as an cache? Thanks for helping me! Dirk