June 27, 201214 yr Seems like the wrong size is being shown in windows 7 for my array. Any ideas on how to remedy? Running 5.0 RC5 has been doing it since at least RC4. I think once I replaced my parity drive with a 3TB and added a 2TB it hasn't shown correctly.
June 27, 201214 yr Unraid reports drive size and free space calculated in base 10 while Windows reports it calculated in base 2. So when you put that new 2TB drive in your server, it reported it as having 2TB of free space. If you put that same drive, brand new, in your Windows computer it would report about 1.8TB free. If you convert all those free space listings on your server to base 2 and add them up you get about 3TB, which is what Windows is showing as the free space of your server.
June 27, 201214 yr I thought 6 TB disks would be closer to 12TB total? Windows is displaying the correct "formatted" size. Windows will display a 1TB drive as roughly 931GB once it is formatted, have a read of the following: http://en.wikipedia.org/wiki/Hard_disk_drive#Units_of_storage_capacity http://en.wikipedia.org/wiki/Terabyte The terabyte is a multiple of the unit byte for digital information. The prefix tera means 1012 in the International System of Units (SI), and therefore 1 terabyte is 1000000000000bytes, or 1 trillion (short scale) bytes, or 1000 gigabytes. 1 terabyte in binary prefixes is 0.9095 tebibytes, or 931.32 gibibytes. The unit symbol for the terabyte is TB or TByte, but not Tb (lower case b) which refers to terabit. Unfortunately as drive sizes get larger this gap is only going to increase, unless they change the naming convention (which is probably likely eventually) then drives will appear to start coming out in "funny" sizes. For a while they were thinking of renaming GB to BB (Gigabyte to Billion Bytes) to prevent confusion.. This would mean a 500GB drive would have had to have been sold as a 465BB.. Technically you are getting what you paid for, 12000000000000bytes
June 27, 201214 yr I thought 6 TB disks would be closer to 12TB total? 10.91TB usable space with 6x 2TB drives. 931GB usable per terabyte, times 12 terabytes, is 10.91TB. This is not unRAID's fault, this has been the case since the day hard drives were made. I'm kind of baffled how you claim it didn't do this before. Windows shows 43.6TB for me, which is 48TB worth of drives (51TB if you count parity).
June 27, 201214 yr I thought 6 TB disks would be closer to 12TB total? Windows is displaying the correct "formatted" size. Windows will display a 1TB drive as roughly 931GB once it is formatted, have a read of the following: http://en.wikipedia.org/wiki/Hard_disk_drive#Units_of_storage_capacity http://en.wikipedia.org/wiki/Terabyte The terabyte is a multiple of the unit byte for digital information. The prefix tera means 1012 in the International System of Units (SI), and therefore 1 terabyte is 1000000000000bytes, or 1 trillion (short scale) bytes, or 1000 gigabytes. 1 terabyte in binary prefixes is 0.9095 tebibytes, or 931.32 gibibytes. The unit symbol for the terabyte is TB or TByte, but not Tb (lower case b) which refers to terabit. Unfortunately as drive sizes get larger this gap is only going to increase, unless they change the naming convention (which is probably likely eventually) then drives will appear to start coming out in "funny" sizes. For a while they were thinking of renaming GB to BB (Gigabyte to Billion Bytes) to prevent confusion.. This would mean a 500GB drive would have had to have been sold as a 465BB.. Technically you are getting what you paid for, 12000000000000bytes I don't think they way drives are labeled will change. The way operating systems calculate disk sizes will change. OS X has calculated drive sizes in base 10 since 10.6 and Ubuntu is switching to base 10 as well. The problem is Windows with millions of customers who would not understand the change and would freak out were it to be changed (even though it would appear they are getting a bunch of additional storage space for free).
June 28, 201214 yr I don't think they way drives are labeled will change. The way operating systems calculate disk sizes will change. OS X has calculated drive sizes in base 10 since 10.6 and Ubuntu is switching to base 10 as well. The problem is Windows with millions of customers who would not understand the change and would freak out were it to be changed (even though it would appear they are getting a bunch of additional storage space for free). I also don't think the way the drives are labelled will change (I just know it was "discussed"), there's too many factors at play. The main one is how the drive is partitioned and formatted as this changes the "perceived size" of the drive. I wasn't aware Ubuntu was switching to base 10, sounds like a good way to do it. Does this mean program installs will display their required size also in base 10? I'm guess that will depend on how the software was written.
June 28, 201214 yr I don't think they way drives are labeled will change. The way operating systems calculate disk sizes will change. OS X has calculated drive sizes in base 10 since 10.6 and Ubuntu is switching to base 10 as well. The problem is Windows with millions of customers who would not understand the change and would freak out were it to be changed (even though it would appear they are getting a bunch of additional storage space for free). I also don't think the way the drives are labelled will change (I just know it was "discussed"), there's too many factors at play. The main one is how the drive is partitioned and formatted as this changes the "perceived size" of the drive. I wasn't aware Ubuntu was switching to base 10, sounds like a good way to do it. Does this mean program installs will display their required size also in base 10? I'm guess that will depend on how the software was written. That's a good question, I don't really know for sure. I'm guessing you mean in the Software Center? I'm guessing it depends on how the file sizes are reported to it. If it's in bytes it should display correctly in base 10. If not, it may appear wrong.
Archived
This topic is now archived and is closed to further replies.