Druiff

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by Druiff

  1. @JonathanM @JorgeB Thanks for the support! Have been able to recover the data of the failed disk. All the plugins are gone, but dockers and vm's were instantly up-and-running. (which made sense.. eventually) But can't figure out how to "edit" the dockers now, as none of them have edit buttons. Maybe it's a good moment to start over Thanks for the help! Much appreciated!
  2. Oef... those notifications haven't come in for a while as I had some issues with it and never bothered! But I was able to use the 'overheat' alerts to determine the slots! (messages were like Jan 2022, but I haven't changed anything since then.) So Plan now is (as soon as the new usb is in): Prepare new usb with trial version. Connect all the disks to the system. Assign all the disks to there original slots. (including the replacement disk in the slot of disk that is dead) Start the array (make sure "parity is valid" is checked) Stop the array remove/disconnect the replacement drive Start the array. (this should allow the data to be emulated.) Retrieve backup of USB Overwrite contents of the new/trial usb with the contents in the backup. (reboot the system?) Start the array, check everything is in working order stop the array, and assign the replacement disk on the place where the disk dead. It should start to rebuild the old data. In step3 I am not sure if you want me to only physically connect the drive or also assign it to the array. And would I lower the risk of faults using maintenance mode of the array.? That way it's read only correct? Or is my understanding wrong of the maintenance mode? Thanks for the help so far!
  3. I don't know exactly which disks are data and which is the parity drive. or in what sequence/diskslot they go. That's why I think I need the backup to be able to get that running. (Failed drive is a 6TB. I will be replacing it with a drive the exact spec of the Parity drive. So should be good) That is the assumption that when it said boom, it was still valid. So basicly at this point I just need to get the system online and see what's up. What would be the right step when I am not sure which drive belongs were?
  4. So I had a problem with my server which took down atleast the following: (probably a short-circuit as the smell of burnt plastic is very intense) - PSU - Motherboard - USB - backplane - 1 HDD Now I am looking to recover the data on the lost drive via the parity. But as my USB is gone AND the backup was made into the (encrypte) array.. How can I retrieve the USB backup? Or is there an other way to restore the unraid installation WITH parity so I can recover the lost disk? I do have the passphrase/key to decrypt the array. Not sure if/how to decrypt the array without unraid. I could connect each disk to my linux PC and try to mount the disks one by one in search of the USB-backup.
  5. its only at like 300 connections. but I will try lower. The low speeds issue has to do with the problems PIA has to fix?
  6. depends. have you run them through PIA as well? because the indexers might just block those vpn servers.
  7. So i am using the test release as well. Trying to connect to Amsterdam takes about 18-ish minutes. And after connect the speed doesnt get above 400-600kb/s. Any tips what I can try to improve this? edit: As soon as the docker is running... My internet connection gets unstable. Not sure why, but pinging to 8.8.8.8 or 1.1.1.1 often times out. and even a ping to my modem/router averages to 500ms response time. Might the docker/vpn overwhelm my modem or/and do I have a shitty modem? (this problem existed before PIA changed anything. But back then it only happend after a week or so.. and a restart fixed it.
  8. And make sure to use the right [ ' ]. Only use the one ' if you have any special characters in your passphrase. (i used printf as well instead of echo)