Ewok

[jimnyc]

Anyone else effected by this disastrous server and it's latest failure? It went down around 7:30pm EST or so last evening, apparently due to an array failure. It took nearly 4 hours before the restore process was even started. Then I find out early this morning that the process died during the evening and they had to start again. It actually didn't start again for about 5 hours because there was apparent trouble finding a suitable replacement server, then problems with a rescue CD. Finally around noon today the restore process is started for a 2nd time. Now I find out at approximately 5pm that the restore died again and will likely need to be restarted.

What happened that so many servers died yesterday with array failures? I count at least 4 servers that had the same array issue and need to be restored, and all 4 remain down. And at least one other besides Ewok has failed again after all this time and needs to start from square one.

It's very discouraging to see so many issues with my server as of late. And it's taking very long just to get simple updates as to the status of the problems. I can't very well rely on the announcement thread for updates when it's only updated after 4 hours or so. I've been with Jaguar for over 4 years now, and have an SDX and a VPS package paying $70 per month, but I'm wondering if it might be time to start hunting around for a change.

[TahirMeer]

Anyone else effected by this disastrous server and it's latest failure? It went down around 7:30pm EST or so last evening, apparently due to an array failure. It took nearly 4 hours before the restore process was even started. Then I find out early this morning that the process died during the evening and they had to start again. It actually didn't start again for about 5 hours because there was apparent trouble finding a suitable replacement server, then problems with a rescue CD. Finally around noon today the restore process is started for a 2nd time. Now I find out at approximately 5pm that the restore died again and will likely need to be restarted.

What happened that so many servers died yesterday with array failures? I count at least 4 servers that had the same array issue and need to be restored, and all 4 remain down. And at least one other besides Ewok has failed again after all this time and needs to start from square one.

It's very discouraging to see so many issues with my server as of late. And it's taking very long just to get simple updates as to the status of the problems. I can't very well rely on the announcement thread for updates when it's only updated after 4 hours or so. I've been with Jaguar for over 4 years now, and have an SDX and a VPS package paying $70 per month, but I'm wondering if it might be time to start hunting around for a change.

I would like to raise the same question, what with RAID failure.... it seems strange that more less 4 server had raid failures within last 24hours? Ravin server was taken down for maintain last week and now the RAID... Just wondering what went wrong ?

[thinksmart12]

I would also like to know about what is going on with Sirius. My situation was the same, the backup failed and had to start over. Anyone else have any information on this?

[jimnyc]

This is becoming horribly unacceptable. Ewok, like other servers, has now been down for well over 36 hours and I still can't get appropriate answers and ETA's when speaking with the techs. Now I read that on "Rivan" that the backups are nearly 2 weeks old. If that happens when Ewok is completed, I'm taking my SDX and VPS packages and looking for an alternative.

At 1am this morning it was updated that Ewok was 85% restored. Now well over 10 hours later the techs are telling me that the status is 85% restored. I've asked MANY times about when the restore was being made from (date) and have yet to receive a reasonable reply other than "there shouldn't be any data loss". Shouldn't it be fairly easy to know which backup is being utilized to restore a server?

I've dealt with issues in the past and understand that sometimes things just happen. But the servers/support have been terrible the past few months and now this debacle appears to be the icing on the cake.

[threehundred]

This is becoming horribly unacceptable. Ewok, like other servers, has now been down for well over 36 hours and I still can't get appropriate answers and ETA's when speaking with the techs. Now I read that on "Rivan" that the backups are nearly 2 weeks old. If that happens when Ewok is completed, I'm taking my SDX and VPS packages and looking for an alternative.

At 1am this morning it was updated that Ewok was 85% restored. Now well over 10 hours later the techs are telling me that the status is 85% restored. I've asked MANY times about when the restore was being made from (date) and have yet to receive a reasonable reply other than "there shouldn't be any data loss". Shouldn't it be fairly easy to know which backup is being utilized to restore a server?

I'm on sirius and have all of the same concerns. Separate RAID arrays usually don't have anything to do with each other. It seems odd that the same problem is affecting separate arrays simultaneously.

[jimnyc]

Absolutely unbelievable!

Ewok was at 85% restored for over 10 hours, and now they are saying it's stuck and will likely have to be restarted again - that's the 4th time! Why in the world would it sit at 85% for over 10 hours before someone would realize it's no longer moving? And I've been asking support repeatedly about when the last backup was for my site, which date, and how I can go about getting a copy of it, and my question is repeatedly being ignored.

[jimnyc]

Very odd, literally a few moments after I was updated stating the restore would need to be restarted again, my site is now back online. Very weird things going on in the back end, and that support would think it needs to be restarted and yet it's online. I suppose I should just be happy that it's back.

[JPC-Masood]

Moved to appropriate forum.

[JPC-Masood]

Yes, the restore on a shared/sdx will be different because of different partition sizes and their order. It can jump from 85% to 100% in matters of few minutes. I have already filed a bug report to get this logic fixed.

[Ron]

Maybe there there is a verification process that can be turned off during the restore and then scanned afterward? Are you looking at other ways to speed this up?

[jimnyc]

And here we are the next day after the server was restored and Ewok is down once again. How can this server go up and down so many times? I was also under the impression that it was completely replaced, as per my ticket, so now a totally different server is already crashing as well? Members on my site are literally laughing at me, while others complain, and everyone asks why I just don't move somewhere more reliable.

Will these problems ever be resolved properly?

[jimnyc]

I'm very frustrated with support as well. I opened my ticket a short while ago, and 20 minutes later I get a response stating that the server was down for a few moments but once again back online.

Problem is, it's not back online, nor was it. I was on the network status page hitting "refresh" every minute or so monitoring it and it showed red icons the entire time. I also of course tried hitting my site throughout and it never loaded.

Seems as if I can't even get the server looked at properly.

[JPC-Masood]

Server status has 5 minutes delay.

[jimnyc]

Server status has 5 minutes delay.

That very well may be, but AFTER I was notified in the ticket that the server was back up, it was NOT back up, and wasn't for approximately another 10-20 minutes. Nor was it up in the mean time, regardless of what the server status page stated, as I was monitoring the site. So I'm unsure as to why the server went down, and why I was told it was up when it wasn't. After 2 replies all I get back from support is "the server was down for a moment and now back up".

As a high paying customer, I believe I'm entitled to ask WHY these problems happen, what the problems were and what is being done to ensure it doesn't keep repeatedly happening like this server has been doing for a few months now.

[JPC-Masood]

We have identified some hardware issues with it and are arleady working on it.