# Asian satellite 512bytes chunks only

**URL:** <https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320>\
**Category:** Node Operators\
**Created:** [March 17, 2021, 12:52pm UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320 "2021-03-17T12:52:16Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![zolbarna](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/zolbarna/32/1134_2.png) [@zolbarna](https://forum.storj.io/u/zolbarna)\
**Post date:** [March 17, 2021, 12:52pm UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/1 "2021-03-17T12:52:16Z")

</div>

I’ve seen few weeks now the [asia-east-1.tardigrade.io](http://asia-east-1.tardigrade.io) satellite sending only 512 bytes pieces.

The total daily ingress from this satellite is few hundred Mb, but it’s mostly contain a very small pieces.

![image](https://storj-s3.bcdn.literatehosting.net/original/2X/b/bc6740574a3e9e1caa01c7517eafe686f6759748.png)

I wondering if it’s could be a real data, but what is the purpose of it?

---

<div class="post-metadata">

**Author:** ![nerdatwork](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/nerdatwork/32/1135_2.png) [@nerdatwork](https://forum.storj.io/u/nerdatwork)\
**Post date:** [March 17, 2021, 1:11pm UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/2 "2021-03-17T13:11:18Z")

</div>

> [@zolbarna](#):
>
> could be a real data

What do you think is real data ?

---

<div class="post-metadata">

**Author:** ![zolbarna](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/zolbarna/32/1134_2.png) [@zolbarna](https://forum.storj.io/u/zolbarna)\
**Post date:** [March 17, 2021, 1:51pm UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/3 "2021-03-17T13:51:46Z")

</div>

> [@zolbarna](#):
>
> ng if it’s could be

Nope. But what is this for?

---

<div class="post-metadata">

**Author:** ![nerdatwork](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/nerdatwork/32/1135_2.png) [@nerdatwork](https://forum.storj.io/u/nerdatwork)\
**Post date:** [March 17, 2021, 3:02pm UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/4 "2021-03-17T15:02:35Z")

</div>

My best guess is metadata.

---

<div class="post-metadata">

**Author:** ![zolbarna](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/zolbarna/32/1134_2.png) [@zolbarna](https://forum.storj.io/u/zolbarna)\
**Post date:** [March 17, 2021, 3:09pm UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/5 "2021-03-17T15:09:53Z")

</div>

Only metadata, and nothing else from asia? 🙂

My logs contains about 3 days only: (since I rebuilded my containers)

 ![image](https://storj-s3.bcdn.literatehosting.net/original/2X/c/c75dc77ce9dbfd80b453017d39cb8b6b6d62e4ef.png)

---

<div class="post-metadata">

**Author:** ![phpbg](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/phpbg/32/1130_2.png) [@phpbg](https://forum.storj.io/u/phpbg)\
**Post date:** [March 20, 2021, 9:53am UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/6 "2021-03-20T09:53:21Z")

</div>

Same here, really bad news for 4K drives

---

<div class="post-metadata">

**Author:** ![twl](https://storj.bcdn.literatehosting.com/letter_avatar/twl/32/5_5575768a8748004e209b776fc1b2916d.png) [@twl](https://forum.storj.io/u/twl)\
**Post date:** [March 20, 2021, 10:14am UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/7 "2021-03-20T10:14:31Z")

</div>

Good thing there are next to no 4Kn drives at all

---

<div class="post-metadata">

**Author:** ![zolbarna](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/zolbarna/32/1134_2.png) [@zolbarna](https://forum.storj.io/u/zolbarna)\
**Post date:** [March 20, 2021, 10:37am UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/8 "2021-03-20T10:37:35Z")

</div>

Let me be honest with you. I blacklisted the satellite from asia since then. I was fed up to listening my HDD’s are ticking in every 0.5 seconds. Haven’t got soo much data from there anyway.

---

<div class="post-metadata">

**Author:** ![Storgeez](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/storgeez/32/68_2.png) [@Storgeez](https://forum.storj.io/u/Storgeez)\
**Post date:** [March 20, 2021, 2:31pm UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/9 "2021-03-20T14:31:07Z")

</div>

> [@twl](#):
>
> Good thing there are next to no 4Kn drives at all

What do you mean? Basically all new drives are 4K…

---

<div class="post-metadata">

**Author:** ![twl](https://storj.bcdn.literatehosting.com/letter_avatar/twl/32/5_5575768a8748004e209b776fc1b2916d.png) [@twl](https://forum.storj.io/u/twl)\
**Post date:** [March 20, 2021, 3:53pm UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/10 "2021-03-20T15:53:27Z")

</div>

> [@Storgeez](#):
>
> What do you mean? Basically all new drives are 4K…

I was talking about _4K native_ drives and nope, there are near to none of those - most drives these days are _512e_ drives.

---

<div class="post-metadata">

**Author:** ![Storgeez](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/storgeez/32/68_2.png) [@Storgeez](https://forum.storj.io/u/Storgeez)\
**Post date:** [March 20, 2021, 4:37pm UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/11 "2021-03-20T16:37:54Z")

</div>

> [@twl](#):
>
> I was talking about _4K native_ drives and nope, there are near to none of those - most drives these days are _512e_ drives.

Oh, apologies, I missed the n part. But the emulated or native isn’t really important as long as the drive is 4K on the hardware level, since it is getting the benefit of lower overhead. You can use it as a 4k sector drive or reformat it to 4Kn and again use it as 4k sector drive… Best to reformat to avoid any possible headaches.

---

<div class="post-metadata">

**Author:** ![twl](https://storj.bcdn.literatehosting.com/letter_avatar/twl/32/5_5575768a8748004e209b776fc1b2916d.png) [@twl](https://forum.storj.io/u/twl)\
**Post date:** [March 20, 2021, 4:52pm UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/12 "2021-03-20T16:52:17Z")

</div>

> [@Storgeez](#):
>
> Best to reformat to avoid any possible headaches

This is not a matter of “formatting”. There are certain Seagate drives that allow you to re-flash the controller and thereby switch the operating mode. Unless your drive supports such a technique, you are stuck with the state the drive was delivered in 🙂

---

<div class="post-metadata">

**Author:** ![Storgeez](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/storgeez/32/68_2.png) [@Storgeez](https://forum.storj.io/u/Storgeez)\
**Post date:** [March 20, 2021, 5:00pm UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/13 "2021-03-20T17:00:03Z")

</div>

> [@twl](#):
>
> certain Seagate drives that allow you to re-flash the controller and thereby switch the operating mode. Unless your drive supports such a technique, you are stuck with the state the drive was delivered in 🙂

Well I can’t speak for all the manufacturers, but in my experience, they were changed by using a “format” command. I suppose they do simply “switch” internally from outputting 512 bytes to 4k without a low level reformat, like you say.  
I guess the reason for factory 512e mode drives is that there is at least one software that would be incompatible with these sectors and there would be more than 0 irate customers “blaming” the drive manufacturer, as is the case usually. Probably why everyone stocks the 512e variants - safer for them.

---

<div class="post-metadata">

**Author:** ![jammerdan](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jammerdan/32/1121_2.png) [@jammerdan](https://forum.storj.io/u/jammerdan)\
**Post date:** [April 8, 2021, 8:42am UTC](https://forum.storj.io/t/asian-satellite-512bytes-chunks-only/12320/14 "2021-04-08T08:42:29Z")

</div>

This satellite is really weird. I am seeing sizes 512, 768 and 1536. Only put repairs have “normal” sizes like you would expect from uploads through different users/customer usage.
