I do and I haven’t run into any issues using Aloha on mobile
Discussion Bunkr Discussion
- Thread starter Jerf
- Start date
CORE-Updates for JDownloader 2 have been released! All known bunkrr.su and cyberdrop.me issues have been fixed!
This has nothing to do with bunkr, we do not modify or compress files.
They are served "as is".
Meaning, whatever you download is the raw version the uploader uploaded it as.
Last edited:
Is there an ETA for the server #1 maintenance? feels like it's been down for ages now
Week and a half haha.
Should be up in like 14-16 hours from this message. Finishing last few GBs of uploads.
Actually a little bird told me maintenance is now finished 👀
Maintenance again? It'd be nice if at least only one of the two functions were broken at a time (ie preview works but download doesn't or viceversa) but as it stands right now it's just full of broken files for some reason
You only need unlock origin and enable the right filter lists.
Is there an ETA for maintenance on cdn4? It's already been a couple of weeks.
Also, is there always going to be one server under maintenance on some sort of rotating schedule?
Also, is there always going to be one server under maintenance on some sort of rotating schedule?
We've had the worst luck with this server, and here's the issues we've had to deal with:
We have had to completely replace the server, so before we did that we had to backup 80TB+ that this server alone has, which took like 3-4 days. Then we got the server replaced, the "new" server when we started to put load (restore the whole backup) it started to get 1000 up to 4000+ load, which made 0 sense.
Furthermore, because of this issue, the DC took a few days to check all drives, replace MB, OS drive, ram sticks, basically everything but the existing HDDs which made sense as it had already data on it. Found 1 drive about to fail, which we thought that was the problem.
At this point we are like 1.5 weeks in.
Then... when thought everything was fine, the newly refurbished server started to have 100 load again with 0 explanation.
Finally, the DC ordered new drives which also took them a few days to get there, and got them swapped and installed today, in fact like 3 hours ago.
We now are syncing current data with our backup just to make sure we have not missed anything.
Later today/tomorrow we will setup the new server and build the new raid array, this takes like 3 days. Then we can restore backup which is another 3-4 days.
So, TL:DR -> ETA at bare minimum 8 more days
Things could've been faster if we (the DC and myself) would be on the same time zone, but because we are not, a lot of the time when they needed my authorization to for example turn the server off, I'd be sleeping or working on my real job, etc. But it is what it is, rather had these drives fail while in maintenance rather than in production.
We have had to completely replace the server, so before we did that we had to backup 80TB+ that this server alone has, which took like 3-4 days. Then we got the server replaced, the "new" server when we started to put load (restore the whole backup) it started to get 1000 up to 4000+ load, which made 0 sense.
Furthermore, because of this issue, the DC took a few days to check all drives, replace MB, OS drive, ram sticks, basically everything but the existing HDDs which made sense as it had already data on it. Found 1 drive about to fail, which we thought that was the problem.
At this point we are like 1.5 weeks in.
Then... when thought everything was fine, the newly refurbished server started to have 100 load again with 0 explanation.
Finally, the DC ordered new drives which also took them a few days to get there, and got them swapped and installed today, in fact like 3 hours ago.
We now are syncing current data with our backup just to make sure we have not missed anything.
Later today/tomorrow we will setup the new server and build the new raid array, this takes like 3 days. Then we can restore backup which is another 3-4 days.
So, TL:DR -> ETA at bare minimum 8 more days
Things could've been faster if we (the DC and myself) would be on the same time zone, but because we are not, a lot of the time when they needed my authorization to for example turn the server off, I'd be sleeping or working on my real job, etc. But it is what it is, rather had these drives fail while in maintenance rather than in production.
Yes, we are aiming once per month to sync current data with our backup. This only takes like 1 day, these cases of the RAID array rebuild are one in a time type thing (unless a drive fails)
Last edited:
Bloody hell mate, sounds like a nightmare. Hope it all works out in the end, and thanks for the update!!
Agreed! Thanks for being transparent. Love the service, the fact that you are here, supporting us simps. Chef's kiss mate!
RAID sync has started, should take like 2.5 days to complete, then we will restore and backup and make the server available again! (we could do both at the same time but because its syncing the write speeds are super super limited, basically we would make the sync slower and consume more time)
(take a look at where it says finish=3519.1min - this is how long it will take to sync the array)
(take a look at where it says finish=3519.1min - this is how long it will take to sync the array)
And for you simps asking, such configs of these servers are:
RAID 6 or 10 (we are testing both on seeing which we see is more fit in our use case)
CPU: Minimum 2x E5 2690 V2
RAM: 128/256GB (256GB on newer servers as we are testing ram cache, older servers have 128GB)
DISK OS: 2x500 SSD in RAID 1
DISK STORAGE: 12x18 TB disks (216TB RAW) After RAID 6 155TB usable.
RAID 6 or 10 (we are testing both on seeing which we see is more fit in our use case)
CPU: Minimum 2x E5 2690 V2
RAM: 128/256GB (256GB on newer servers as we are testing ram cache, older servers have 128GB)
DISK OS: 2x500 SSD in RAID 1
DISK STORAGE: 12x18 TB disks (216TB RAW) After RAID 6 155TB usable.
Last edited: