Hard disk capacity discrepancy between enclosures
up vote
1
down vote
favorite
I recently bought a 3 terabyte internal hard drive to replace a 2TB drive I
filled. Using the same enclosure that's been housing my 2TB drive, Ubuntu
reports the capacity of the new drive as 802 gigabytes.
I also have a multi-purpose SATA-to-USB-and-power adapter. When the new
drive is connected using that device, Ubuntu reports the full 3 terabytes.
I'm seeing the same behavior whether I use gpt or msdos partition tables.
This seems like a limitation of the enclosure, but I can't explain why it
recognizes the complete 2TB of one drive but only 800 gigabytes of a larger
drive.
Can this be explained by the capabilities of the hard disk enclosure? Can I
verify that by inspecting the system state? Is there some feature I need to
search for when buying a new enclosure?
When the disk is mounted through the USB dongle, Ubuntu's "Disks" utility
reports the following:
- Model: ST3000DM 008-2DM166 (0006)
- 3.0 TB (3,000,592,982,016 bytes)
- Serial number: 20140404
But when mounted through the enclosure:
- Model: ST3000DM 008-2DM166 (0103)
- Size: 802 GB (801,569,726,464 bytes)
- Serial number: ST3000DM00_Z505FLQF
partitioning usb hard-drive external-hdd
edited Nov 23 at 17:45
Byte Commander
62.1k26167279
asked Nov 23 at 17:43
Mike
82
New contributor
Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
1
down vote
favorite
I recently bought a 3 terabyte internal hard drive to replace a 2TB drive I
filled. Using the same enclosure that's been housing my 2TB drive, Ubuntu
reports the capacity of the new drive as 802 gigabytes.
I also have a multi-purpose SATA-to-USB-and-power adapter. When the new
drive is connected using that device, Ubuntu reports the full 3 terabytes.
I'm seeing the same behavior whether I use gpt or msdos partition tables.
This seems like a limitation of the enclosure, but I can't explain why it
recognizes the complete 2TB of one drive but only 800 gigabytes of a larger
drive.
Can this be explained by the capabilities of the hard disk enclosure? Can I
verify that by inspecting the system state? Is there some feature I need to
search for when buying a new enclosure?
When the disk is mounted through the USB dongle, Ubuntu's "Disks" utility
reports the following:
- Model: ST3000DM 008-2DM166 (0006)
- 3.0 TB (3,000,592,982,016 bytes)
- Serial number: 20140404
But when mounted through the enclosure:
- Model: ST3000DM 008-2DM166 (0103)
- Size: 802 GB (801,569,726,464 bytes)
- Serial number: ST3000DM00_Z505FLQF
partitioning usb hard-drive external-hdd
edited Nov 23 at 17:45
Byte Commander
62.1k26167279
asked Nov 23 at 17:43
Mike
82
New contributor
Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Is drive partitioned as gpt, some have proprietary MBR partitioning for backwards compatibility. Then drive is not fully see as partitioning is not the correct gpt type. Also in past many older USB converters & encloses did not work with larger drives or gpt drives. So I would expect if issue then it is enclosure. From Ubuntu post this on 3TB drive:sudo gdisk -l /dev/sdXwhere sdX is 3TB drive, sdb, sdc or whatever.
– oldfred
Nov 23 at 18:08
This is normal because if it only support 2TB, it truncates LBA address to 32-bit(Max size 2^32*512), so 800 GB is the lowest 32bit your 3TB drive reports.
– Alvin Liang
Nov 24 at 3:50
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I recently bought a 3 terabyte internal hard drive to replace a 2TB drive I
filled. Using the same enclosure that's been housing my 2TB drive, Ubuntu
reports the capacity of the new drive as 802 gigabytes.
I also have a multi-purpose SATA-to-USB-and-power adapter. When the new
drive is connected using that device, Ubuntu reports the full 3 terabytes.
I'm seeing the same behavior whether I use gpt or msdos partition tables.
This seems like a limitation of the enclosure, but I can't explain why it
recognizes the complete 2TB of one drive but only 800 gigabytes of a larger
drive.
Can this be explained by the capabilities of the hard disk enclosure? Can I
verify that by inspecting the system state? Is there some feature I need to
search for when buying a new enclosure?
When the disk is mounted through the USB dongle, Ubuntu's "Disks" utility
reports the following:
- Model: ST3000DM 008-2DM166 (0006)
- 3.0 TB (3,000,592,982,016 bytes)
- Serial number: 20140404
But when mounted through the enclosure:
- Model: ST3000DM 008-2DM166 (0103)
- Size: 802 GB (801,569,726,464 bytes)
- Serial number: ST3000DM00_Z505FLQF
partitioning usb hard-drive external-hdd
edited Nov 23 at 17:45
Byte Commander
62.1k26167279
asked Nov 23 at 17:43
Mike
82
New contributor
Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I recently bought a 3 terabyte internal hard drive to replace a 2TB drive I
filled. Using the same enclosure that's been housing my 2TB drive, Ubuntu
reports the capacity of the new drive as 802 gigabytes.
I also have a multi-purpose SATA-to-USB-and-power adapter. When the new
drive is connected using that device, Ubuntu reports the full 3 terabytes.
I'm seeing the same behavior whether I use gpt or msdos partition tables.
This seems like a limitation of the enclosure, but I can't explain why it
recognizes the complete 2TB of one drive but only 800 gigabytes of a larger
drive.
Can this be explained by the capabilities of the hard disk enclosure? Can I
verify that by inspecting the system state? Is there some feature I need to
search for when buying a new enclosure?
When the disk is mounted through the USB dongle, Ubuntu's "Disks" utility
reports the following:
- Model: ST3000DM 008-2DM166 (0006)
- 3.0 TB (3,000,592,982,016 bytes)
- Serial number: 20140404
But when mounted through the enclosure:
- Model: ST3000DM 008-2DM166 (0103)
- Size: 802 GB (801,569,726,464 bytes)
- Serial number: ST3000DM00_Z505FLQF
partitioning usb hard-drive external-hdd
partitioning usb hard-drive external-hdd
edited Nov 23 at 17:45
Byte Commander
62.1k26167279
asked Nov 23 at 17:43
Mike
82
New contributor
Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 23 at 17:45
Byte Commander
62.1k26167279
asked Nov 23 at 17:43
Mike
82
New contributor
Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 23 at 17:45
Byte Commander
62.1k26167279
edited Nov 23 at 17:45
Byte Commander
62.1k26167279
edited Nov 23 at 17:45
Byte Commander
62.1k26167279
62.1k26167279
asked Nov 23 at 17:43
Mike
82
New contributor
Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 23 at 17:43
Mike
82
asked Nov 23 at 17:43
Mike
82
82
New contributor
Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Mike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Is drive partitioned as gpt, some have proprietary MBR partitioning for backwards compatibility. Then drive is not fully see as partitioning is not the correct gpt type. Also in past many older USB converters & encloses did not work with larger drives or gpt drives. So I would expect if issue then it is enclosure. From Ubuntu post this on 3TB drive:sudo gdisk -l /dev/sdXwhere sdX is 3TB drive, sdb, sdc or whatever.
– oldfred
Nov 23 at 18:08
This is normal because if it only support 2TB, it truncates LBA address to 32-bit(Max size 2^32*512), so 800 GB is the lowest 32bit your 3TB drive reports.
– Alvin Liang
Nov 24 at 3:50
add a comment |
1
Is drive partitioned as gpt, some have proprietary MBR partitioning for backwards compatibility. Then drive is not fully see as partitioning is not the correct gpt type. Also in past many older USB converters & encloses did not work with larger drives or gpt drives. So I would expect if issue then it is enclosure. From Ubuntu post this on 3TB drive:sudo gdisk -l /dev/sdXwhere sdX is 3TB drive, sdb, sdc or whatever.
– oldfred
Nov 23 at 18:08
This is normal because if it only support 2TB, it truncates LBA address to 32-bit(Max size 2^32*512), so 800 GB is the lowest 32bit your 3TB drive reports.
– Alvin Liang
Nov 24 at 3:50
1
1
Is drive partitioned as gpt, some have proprietary MBR partitioning for backwards compatibility. Then drive is not fully see as partitioning is not the correct gpt type. Also in past many older USB converters & encloses did not work with larger drives or gpt drives. So I would expect if issue then it is enclosure. From Ubuntu post this on 3TB drive:
sudo gdisk -l /dev/sdX where sdX is 3TB drive, sdb, sdc or whatever.– oldfred
Nov 23 at 18:08
Is drive partitioned as gpt, some have proprietary MBR partitioning for backwards compatibility. Then drive is not fully see as partitioning is not the correct gpt type. Also in past many older USB converters & encloses did not work with larger drives or gpt drives. So I would expect if issue then it is enclosure. From Ubuntu post this on 3TB drive:
sudo gdisk -l /dev/sdX where sdX is 3TB drive, sdb, sdc or whatever.– oldfred
Nov 23 at 18:08
This is normal because if it only support 2TB, it truncates LBA address to 32-bit(Max size 2^32*512), so 800 GB is the lowest 32bit your 3TB drive reports.
– Alvin Liang
Nov 24 at 3:50
This is normal because if it only support 2TB, it truncates LBA address to 32-bit(Max size 2^32*512), so 800 GB is the lowest 32bit your 3TB drive reports.
– Alvin Liang
Nov 24 at 3:50
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
I would look for data from the manufacturer. Pending on what hardware / firmware is build into your enclosure it might just be old or that might just be the part that they saved money on.
It is not uncommon to get stuck at the 2 TB barrier.
So if you are lucky you can get a firmware update for the enclosure or it might just be that a different driver (I doubt it) exists.
In terms of "quick driver check" you might get yourself a knoppix and boot from that CD (www.knoppix.org) that is the best I have seen in terms of hardware recognition.
If knoppix sees the drive in the enclosure correctly that ther is a way your ubuntu can do that as well.
answered Nov 23 at 19:16
Steffen
263
New contributor
Steffen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
You're correct. I should have read the product page more closely: it's mentioned by verified owners and the technical specifications. So, time for a new enclosure. Thanks!
– Mike
Nov 25 at 0:32
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
I would look for data from the manufacturer. Pending on what hardware / firmware is build into your enclosure it might just be old or that might just be the part that they saved money on.
It is not uncommon to get stuck at the 2 TB barrier.
So if you are lucky you can get a firmware update for the enclosure or it might just be that a different driver (I doubt it) exists.
In terms of "quick driver check" you might get yourself a knoppix and boot from that CD (www.knoppix.org) that is the best I have seen in terms of hardware recognition.
If knoppix sees the drive in the enclosure correctly that ther is a way your ubuntu can do that as well.
answered Nov 23 at 19:16
Steffen
263
New contributor
Steffen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
You're correct. I should have read the product page more closely: it's mentioned by verified owners and the technical specifications. So, time for a new enclosure. Thanks!
– Mike
Nov 25 at 0:32
add a comment |
up vote
1
down vote
accepted
I would look for data from the manufacturer. Pending on what hardware / firmware is build into your enclosure it might just be old or that might just be the part that they saved money on.
It is not uncommon to get stuck at the 2 TB barrier.
So if you are lucky you can get a firmware update for the enclosure or it might just be that a different driver (I doubt it) exists.
In terms of "quick driver check" you might get yourself a knoppix and boot from that CD (www.knoppix.org) that is the best I have seen in terms of hardware recognition.
If knoppix sees the drive in the enclosure correctly that ther is a way your ubuntu can do that as well.
answered Nov 23 at 19:16
Steffen
263
New contributor
Steffen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
You're correct. I should have read the product page more closely: it's mentioned by verified owners and the technical specifications. So, time for a new enclosure. Thanks!
– Mike
Nov 25 at 0:32
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I would look for data from the manufacturer. Pending on what hardware / firmware is build into your enclosure it might just be old or that might just be the part that they saved money on.
It is not uncommon to get stuck at the 2 TB barrier.
So if you are lucky you can get a firmware update for the enclosure or it might just be that a different driver (I doubt it) exists.
In terms of "quick driver check" you might get yourself a knoppix and boot from that CD (www.knoppix.org) that is the best I have seen in terms of hardware recognition.
If knoppix sees the drive in the enclosure correctly that ther is a way your ubuntu can do that as well.
answered Nov 23 at 19:16
Steffen
263
New contributor
Steffen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I would look for data from the manufacturer. Pending on what hardware / firmware is build into your enclosure it might just be old or that might just be the part that they saved money on.
It is not uncommon to get stuck at the 2 TB barrier.
So if you are lucky you can get a firmware update for the enclosure or it might just be that a different driver (I doubt it) exists.
In terms of "quick driver check" you might get yourself a knoppix and boot from that CD (www.knoppix.org) that is the best I have seen in terms of hardware recognition.
If knoppix sees the drive in the enclosure correctly that ther is a way your ubuntu can do that as well.
answered Nov 23 at 19:16
Steffen
263
New contributor
Steffen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 23 at 19:16
Steffen
263
New contributor
Steffen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 23 at 19:16
Steffen
263
answered Nov 23 at 19:16
Steffen
263
263
New contributor
Steffen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Steffen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Steffen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
You're correct. I should have read the product page more closely: it's mentioned by verified owners and the technical specifications. So, time for a new enclosure. Thanks!
– Mike
Nov 25 at 0:32
add a comment |
You're correct. I should have read the product page more closely: it's mentioned by verified owners and the technical specifications. So, time for a new enclosure. Thanks!
– Mike
Nov 25 at 0:32
You're correct. I should have read the product page more closely: it's mentioned by verified owners and the technical specifications. So, time for a new enclosure. Thanks!
– Mike
Nov 25 at 0:32
You're correct. I should have read the product page more closely: it's mentioned by verified owners and the technical specifications. So, time for a new enclosure. Thanks!
– Mike
Nov 25 at 0:32
add a comment |
Mike is a new contributor. Be nice, and check out our Code of Conduct.
Mike is a new contributor. Be nice, and check out our Code of Conduct.
Mike is a new contributor. Be nice, and check out our Code of Conduct.
Mike is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1095452%2fhard-disk-capacity-discrepancy-between-enclosures%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Is drive partitioned as gpt, some have proprietary MBR partitioning for backwards compatibility. Then drive is not fully see as partitioning is not the correct gpt type. Also in past many older USB converters & encloses did not work with larger drives or gpt drives. So I would expect if issue then it is enclosure. From Ubuntu post this on 3TB drive:
sudo gdisk -l /dev/sdXwhere sdX is 3TB drive, sdb, sdc or whatever.– oldfred
Nov 23 at 18:08
This is normal because if it only support 2TB, it truncates LBA address to 32-bit(Max size 2^32*512), so 800 GB is the lowest 32bit your 3TB drive reports.
– Alvin Liang
Nov 24 at 3:50