Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


HostHatch Chicago data lost ? - Page 2
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

HostHatch Chicago data lost ?

24

Comments

  • @FrankZ said: The storage server blows up every few months for a day or two. I have never lost data and when it is running it is good, but it is too inconsistent IMO.

    I'm cursing myself with this comment but I have two storage servers there: a 3T and a 10T. Both of them have been 100% stable for me. My use case is pretty light though, primarily archive storage and some plex streaming, so I haven't noticed network issues.

    Thanked by 1FrankZ
  • @FrankZ said:

    @kend said:
    I’m in the same situation. Don’t know what’s going on now with Chicago Storage. I’ve submitted an emergency ticket 10 hours ago, when my storage VPS had already been down for 10 hours at that time. Still have got no reply.

    Don't expect a quick reply from HostHatch. The average ticket response time for me over the last year is about 3 1/2 weeks.

    With storage servers I put my data on a separate partition from the O/S. If I need to reinstall this server the data may still be there. Fingers crossed that I don't need to transfer everything from the backup backup server.

    I don't have a separate partition for O/S... :'(

  • FrankZFrankZ Veteran

    @skorous said:
    I'm cursing myself with this comment but I have two storage servers there: a 3T and a 10T. Both of them have been 100% stable for me. My use case is pretty light though, primarily archive storage and some plex streaming, so I haven't noticed network issues.

    Now I am jealous.

  • ticket replied

    Mike W — HostHatch Representative
    Hello,

    Apologies for the delayed response.

    We're still investigating the ongoing issue affecting the node STOR4.CHI.

    The node had disk errors and was hard rebooted, causing most VMs to have errors when booting up.

    We are still doing our best to restore all VMs back to their working state.

    If it is possible for you, we would recommend that we spin up a new VM for you with the same specifications and boot up RescueCD on the current/affected VM. You can then move over the data to the new VM. We can also move over your old IP address to the new VM if needed. Please let us know.

  • jason5545jason5545 Member
    edited March 2022

    @foitin said:

    @FrankZ said:

    Don't expect a quick reply from HostHatch. The average ticket response time for me over the last year is about 3 1/2 weeks.

    Mine over a month :/

    With storage servers I put my data on a separate partition from the O/S. If I need to reinstall this server the data may still be there. Fingers crossed that I don't need to transfer everything from the backup backup server.

    What's your experience with virmach storage VPS?
    Would you mind sharing your experience? since you're virmach enthusiastic, I'd like to know if it's a wise move to migrate from hosthatch to virmach.

    I have one Virmach storage VPS too, what my experience is, it's ok, but as you may know, Virmach have a strict resource policy than other providers, so when I use it, I need to take extra precautions to not hit the limit, which sometimes gives a little bit of inconvenience for me.
    Performance is average, no downtime till now.

  • FrankZFrankZ Veteran

    @FrankZ said:
    EDIT: I can see that files show to be there, but I don't know for sure that they are good yet.

    EDIT2: After O/S reinstall the files on the data partitions look good so far.

    After checking through all data partitions there is much corrupted data.
    For others on this node before relying on your data I would suggest you check your data partitions with fsck (ext*) or xfs_repair (xfs) or similar.

  • @FrankZ said:

    After checking through all data partitions there is much corrupted data.
    For others on this node before relying on your data I would suggest you check your data partitions with fsck (ext*) or xfs_repair (xfs) or similar.

    Yeah this thing is toast. My btrfs setup has no redundancy or error correction so I don't trust any of this data. I'm going to request a new VM and toss this one.

    Here is a scan 17gb out of 6.42tb lol. For anyone who doesn't know the error summary should be "Error summary: no errors found"

  • Daniel15Daniel15 Veteran
    edited March 2022

    @cablepick said: My btrfs setup has no redundancy or error correction

    It's usually not needed on a VPS if the host node has RAID and a filesystem like zfs or btrfs. Since the host handles it in that case, each individual virtual server shouldn't need to also do it. HostHatch say their storage VPSes have either RAID6 or RAID60 (can't remember which), so I'm not quite sure how the data could get so corrupted. Maybe a bad RAID card?

    Thanked by 1darkimmortal
  • @jason5545 said:

    Virmach have a strict resource policy than other providers, so when I use it, I need to take extra precautions to not hit the limit, which sometimes gives a little bit of inconvenience for me.

    How strict? in terms of IO, CPU and network usage.
    I've never used their VPS before. I ordered a Tokyo storage VPS from them last week.

    Performance is average, no downtime till now.

    I've had quite a few times of downtime from hosthatch LA storage server. Not going to renew it anymore.

  • cablepickcablepick Member
    edited March 2022

    @Daniel15 said: Maybe a bad RAID card?

    According to some old emails they replaced the raid card back in August 2021.

    The only way I could get BTRFS recovery would have been to split the server in half and ran a raid 1 setup. That would have protected me against bitrot but this problem would have still wiped me out.

    I don't really care. I prepared for hardware failures that are out of my control. I have another 10TB instance in LA that mirrors this one so I didn't lose anything. Biggest issue is that this Chicago server was the primary backup server that all my servers backup to. Quick DNS update and a reset of ssh host keys and now LA is the primary backup server. Once this is resolved Ill have Chicago be the backup mirror.

    I've got a 4TB storage server pre-ordered with VirMach so I'll have some resiliency between providers but they're both in the LAX Psychz datacenter so I'm sure an earthquake will ruin this plan someday.

  • Daniel15Daniel15 Veteran
    edited March 2022

    @cablepick said: I'm sure an earthquake will ruin this plan someday.

    I live in the San Francisco Bay Area so I'm not looking forward to 'the big one'

    On the positive side, I get 16ms ping to my HostHatch LA servers and haven't had any major issues with them :smile: (other than long-running connections dropping sometimes)

    My second storage VPS is with Servarica in Montreal, Canada. 3.5TB for US$84/year. I've also got a lifetime 4TB pcloud account that I rclone my important encrypted Borg backups into.

    Thanked by 1maverick
  • jason5545jason5545 Member
    edited March 2022

    @foitin said:

    @jason5545 said:

    Virmach have a strict resource policy than other providers, so when I use it, I need to take extra precautions to not hit the limit, which sometimes gives a little bit of inconvenience for me.

    How strict? in terms of IO, CPU and network usage.
    I've never used their VPS before. I ordered a Tokyo storage VPS from them last week.

    Performance is average, no downtime till now.

    I've had quite a few times of downtime from hosthatch LA storage server. Not going to renew it anymore.

    https://virmach.com/terms-conditions/

    D) High Usage Policy: Any usage by Customer that disrupts the overall performance of our server(s) is not permitted. Customer agrees to operate within the VirMach usage parameters, which are as follows:

    High CPU: Customer’s Service cannot burst to 95-100% usage for more than five (5) minutes and cannot average higher than 50% usage within any two (2) hour period. Packages advertised to include dedicated CPU, Services with the high CPU option, and any customized Service plans that include high CPU option may burst to 100% at all times.
    High Load: Customer’s Service cannot have a 15-minute load average higher than the number of full logical cores assigned and cannot have a 1-day load average higher than 70% of the number of full logical cores assigned.
    High Mail Volume: VirMach reserves the right to block port 25 on Customer’s Service. Customer cannot send more than 100 maximum e-mails per hour, and must maintain a similar average volume of mail on a week-to-week basis—no bursting permitted. VirMach reserves the right to waive this requirement for the purpose of a customized Service plan.
    High I/O: Customer’s Service cannot average more than 80 IOPS within any two (2) hour period, cannot burst above 300MB/s disk write average for more than ten (10) minutes, cannot average more than 300 write operations per second for more than 1 hour, and cannot be above 20% average utilization within any six (6) hour period.
    High Network Usage: Customer’s Service cannot have more than 50,000 conntrack sessions at any given time, and cannot use more than the allocated bandwidth. Customer understands that the network is shared and utilizing maximum network speed will not always be possible.

  • FrankZFrankZ Veteran
    edited March 2022

    Those terms and conditions are for the old servers and were not strictly enforced.

    @foitin - I expect the T&C to be updated for the new Ryzen based servers with less restrictions. Of course this is not guaranteed. But IMHO worrying about this is premature. I've always found that if you are reasonable, you will find that VirMach is too. The inverse is also true.

  • @cablepick said:

    @FrankZ said:

    After checking through all data partitions there is much corrupted data.
    For others on this node before relying on your data I would suggest you check your data partitions with fsck (ext*) or xfs_repair (xfs) or similar.

    Yeah this thing is toast. My btrfs setup has no redundancy or error correction so I don't trust any of this data. I'm going to request a new VM and toss this one.

    Here is a scan 17gb out of 6.42tb lol. For anyone who doesn't know the error summary should be "Error summary: no errors found"

    This is really strange, I don’t know how they can lose so much data at rest and still recover some meaningful data. This failure mode should not happen

  • @FrankZ said:

    Those terms and conditions are for the old servers and were not strictly enforced.

    @foitin - I expect the T&C to be updated for the new Ryzen based servers with less restrictions. Of course this is not guaranteed. But IMHO worrying about this is premature. I've always found that if you are reasonable, you will find that VirMach is too. The inverse is also true.

    Okay. Hopefully they can provision 1TB storage VPS in Tokyo.

    Thanked by 1FrankZ
  • server down for over 48 hours, still not resume yet... o:)

  • And their network status page is no longer updated or have I not found the right link?

  • kendkend Member

    @zqm840527 said:
    server down for over 48 hours, still not resume yet... o:)

    Same here. I've got a reply from them and requested spinning a new one, but got no response after 20 hours again. It's a 3rd level backup for me, so, the data loss would hurt but not that bad. Though, it might need a day or two to rebuild all the fresh backups again after the new install.

    To tell the truth, I'm now thinking of not renewing it this year. It's all fine when the servers are running well. But when the server has problems, Hosthatch's response time is still a bad example of service quality...sigh....

  • I had a similar issue happen in the last few days bit on the Sydney node to one of my VMs.

    Went to restart VM after the 'Dirty Pipe' vulnerability in Ubuntu, on restart VM wouldn't respond, no VNC, ping or SSH - down for 12 hours - then it all came good, didn't get to the bottom of it.

  • Daniel15Daniel15 Veteran
    edited March 2022

    What I'm concerned about is whether the same thing can happen in other locations... It's still unclear as to whether this failure mode (with large chunks of @cablepick's data being corrupted) is isolated to the particular hardware or software configuration used in Chicago, or whether it can potentially happen in their other locations. Seems strange that this'd happen with a RAID setup unless multiple drives failed / encountered corruption at the same time.

  • @Daniel15 said: What I'm concerned about is whether the same thing can happen in other locations...

    Your concern is not misplaced. Two weeks ago, my HostHatch storage VPS in Los Angeles experienced a similar kind of data corruption. I had separate partitions for OS and data (both XFS), and they both went FUBAR (at least beyond xfs_repair). I believe the corruption happened while the VM was online, because cleanly mounted XFS partitions suddenly detected serious data structure corruptions and panicked. To save myself time and energy, I chose not to open any tickets, and simply reinstalled the whole VM.

  • NoCommentNoComment Member
    edited March 2022

    @Daniel15 said:
    What I'm concerned about is whether the same thing can happen in other locations... It's still unclear as to whether this failure mode (with large chunks of @cablepick's data being corrupted) is isolated to the particular hardware or software configuration used in Chicago, or whether it can potentially happen in their other locations. Seems strange that this'd happen with a RAID setup unless multiple drives failed / encountered corruption at the same time.

    It is isolated to a single server in Chicago. I have a storage vps in Chicago which has been idling for 1+ year. When I checked, it had 100+ days uptime. Anyway, when you go for low end storage vps like these which are dirt cheap, the cost savings should easily justify making backups of backups.

  • @NoComment said:

    It is currently isolated to a single server in Chicago. I have a storage vps in Chicago which has been idling for 1+ year. When I checked, it had 100+ days uptime. Anyway, when you go for low end storage vps like these which are dirt cheap, the cost savings should easily justify making backups of backups.

    Fixed that for you. Since the cause isn't yet known we can't know whether it might also be an issue for other locations which is what Daniel was talking about.

    Thanked by 1Daniel15
  • See many players lose data, be careful to buy

  • @hosthatch or @Emil Do you have any updates as to what happened to STOR4.CHI and if it's an isolated case?

    @NoComment said: Anyway, when you go for low end storage vps like these which are dirt cheap, the cost savings should easily justify making backups of backups.

    I've got backups so I can restore everything in the case of any issues, but I also have close to 5TB of data on my VPS, and restoring 5TB of stuff over the internet is not fun.

  • @Daniel15 said:
    @hosthatch or @Emil Do you have any updates as to what happened to STOR4.CHI and if it's an isolated case?

    @NoComment said: Anyway, when you go for low end storage vps like these which are dirt cheap, the cost savings should easily justify making backups of backups.

    I've got backups so I can restore everything in the case of any issues, but I also have close to 5TB of data on my VPS, and restoring 5TB of stuff over the internet is not fun.

    I don't think they have proactive monitoring. I can say LSI/Broadcom absolutely sucks for that and most people script something up to grab status weekly. Also, they likely don't have background consistency checks scheduled since performance takes a hit during.

  • Server is still down. No updates from support.

  • same here as well, "invalid arch-independent elf magic"

  • FrankZFrankZ Veteran
    edited March 2022

    I woke up to a new $80 overdue bill from HostHatch, My storage service was not due to expire until November 2022.
    A ticket was open by them, as I did not open a ticket for this issue, stating.

    Hello,

    As you may be aware, the node on which your VM is hosted (STOR4CHI) has had issues in the past few days.

    Unfortunately, we're still having issues with booting up your current VM. The data on the disk is there, however due to the bootloader being corrupted, it is unable to boot up.

    We have created a new storage VM for you with the same specs. This VM is based on our new platform (available at cloud.hosthatch.com - please use the same login details as manage.)

    You can boot up rescue/liveCD on your current VM to move over the data. We can also boot this up for you if you would like, please let us know. While it may be possible to repair your existing VM, we would recommend moving over your data to the new VM so there are no further issues.

    We do apologize for the inconvenience caused by this and will make all efforts possible to make sure this does not happen again. We have also issued a one month compensation to your new server.

    Sincerely,

    HostHatch LLC

    Anybody else get billed?

    EDIT: Nice, the new server has only less then half the RAM as the old server, (1.8GB verse 3.9GB).

    Also for those of you who had account credit or a c/c on file, I expect they took your account credit, as they did mine, and paid or partially paid the new two year bill.

  • @FrankZ said:
    I woke up to a new $80 overdue bill from HostHatch, My storage service was not due to expire until November 2022.
    A ticket was open by them, as I did not open a ticket for this issue, stating.

    Hello,

    As you may be aware, the node on which your VM is hosted (STOR4CHI) has had issues in the past few days.

    Unfortunately, we're still having issues with booting up your current VM. The data on the disk is there, however due to the bootloader being corrupted, it is unable to boot up.

    We have created a new storage VM for you with the same specs. This VM is based on our new platform (available at cloud.hosthatch.com - please use the same login details as manage.)

    You can boot up rescue/liveCD on your current VM to move over the data. We can also boot this up for you if you would like, please let us know. While it may be possible to repair your existing VM, we would recommend moving over your data to the new VM so there are no further issues.

    We do apologize for the inconvenience caused by this and will make all efforts possible to make sure this does not happen again. We have also issued a one month compensation to your new server.

    Sincerely,

    HostHatch LLC

    Anybody else get billed?

    I get a bill too but without any ticket or explanation. It's for a new VM for another two years. Not going to pay it rn.

    Thanked by 1FrankZ
This discussion has been closed.