Z10 Pro hard drive issue

I just got Zidoo Z10 Pro and WD Red Pro 18TB. I inserted the hard drive in the Z10 and formatted it in Media Center. Now it's not showing up and under advanced Android settings it says Corrupt (I doubt). Any way to fix this without having to buy external hard drive dock for PC to format with PC?

 

If it's a brand new HDD, you will have to create a partition and to format it with Windows Disk Management.

 

You need to format it at 17.5 TByte maximum using GPT+NTFS with W10 being SATA attached. This due to the Android 32-bit limitations according my info and understanding.

You can try Media Center with the 17.5 TByte limit too. Will be interesting to see if that then works as expected. I am in close dialog with Zidoo about this but did not get their test results yet.

 

I just plugged the hard drive into my PC to format it, it's not showing up..

 

update: Updated my PC's BIOS. The drive showed up after that and I formatted it NTFS with Windows 11 Disk Management app. Disk Management and the Zidoo report it as 16764GB. Windows drive properties window reports it as 16.3TB.

 

This is the big HDD size confusion. For a HDD that 18TByte is 18.000.000.000.000 bytes. But obviously memory is measured in 1024 units resulting in all kind of different values using k, M G, T displays.

It is formatted as full 18 TByte here. The maximum for Android is 16.300 GByte as seen with a Windows format. So I don't think it will work correctly under Android.

 

It works great

 

The question is if it still works without corruption when filled totally.
I did expect it to be seen by Android that is not the problem. Accessing all data in a reliable way is.

 

How do I format something to 17.5TB when it shows as 16.3TB?

 

Easy enough. Put it in a Windows PC and remove all partitions and next start Format. The window will show up with the default size in GByte to be formatted. Just reduce the suggested size with 500 GByte (which I think will be 16,300 GByte then)

 

It shows as 16,764GB in Windows Disk Management. It won't let me format it to anything above that.

 

Obviously as 16,764 GByte (binary) is the full 18 GByte (decimal). You need to reduce it to 16,300 Gbyte

 

Ok thanks. So you're saying if I don't do that my files will become corrupted?

 

I am not 100% sure but some reported this to me. Don't have a > 16 TByte HDD myself. According my calculations there is a maximum here with a 32-bit OS.

Asked Zidoo to check this but they did not report back to me yet.

 

I plugged the 18TB hard drive back into my PC and shrunk the partition by 1,000,000 megabytes just in case. Then put it back in Zidoo. You said the maximum is 17.5TB? I checked and now Android settings on the Zidoo say the drive is 16.95TB.

 

I said the maximum was 16.5 TByte or reducing by 1,500,000 megabytes.

 

You said 17.5 earlier in this thread

 

You are right should work. Read it in Gigabyte which is confusing.

Practical testing with Zidoo media players and a Seagate EXOS 18 TByte drive showed the limit to be just over 17.5 TByte (=16,300 Gigabyte). Exactly as calculated by me. I do expect it to apply also to other drives over 16 TByte and all Android based media players.

This is the whole HDD story:
https://www.futeko.com/newforum/index.php?topic=576.msg34186#new

 

I'm far away from using such a huge device on my Zidoo Z9X, but either way you guys should use properly calculated numbers as (at least) one of those numbers is off (I'm referring to 17.5TB vs 16.3TiB here, as 17.5TB != 16.3TiB). You've all heard that before, but let me explain:
17.5TB = 17,500GB = 17,500,000MB = 17,500,000,000KB = 17,500,000,000,000 Bytes
Now...
17,500,000,000,000 Bytes = 17,089,843,750KiB = 16,689,300.537109375MiB = 16,298.1450557708740234375GiB = 15.91615728102624416351318359375TiB

If you post numbers and other users may use those numbers to format his/her devices be at least sure that they are correct. Even if you "forgot" to convert the kilobytes to the bytes story it's still 16,298 and not 16,300 - but as I mentioned... I can't even check that as I don't own such a huge device. ;-)