1
I do not believe this to be an issue with formatting. Both Linux and Windows (64bit) see it as 2TB drive. However it is supposed to be a 3TB drive. It is in an enclosure, and I am wondering if perhaps the enclosure's controller is unable to support larger than 2TB drives? It is a WD MyBook and is not meant to be taken apart to plug in the drive directly into a PC... so before I rip it apart I thought id ask for advice here. It is a USB3.0 enclosure, I believe by the time USB3.0 came about we have resolved 32bit issues?
sudo fdisk -l /dev/sda1
Disk /dev/sda1: 1.8 TiB, 2000362143744 bytes, 3906957312 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Device Boot Start End Sectors Size Id Type
/dev/sda1p1 1920221984 3736432267 1816210284 866G 72 unknown
/dev/sda1p2 1936028192 3889681299 1953653108 931.6G 6c unknown
/dev/sda1p3 0 0 0 0B 0 Empty
/dev/sda1p4 27722122 27722568 447 223.5K 0 Empty
Under what circumstances will sda1p3 show up like that with all 0's ?
Drive's internal info states its a 3TB drive:
sudo hdparm -I /dev/sda1
/dev/sda1:
ATA device, with non-removable media
Model Number: WDC WD30EZRX-00D8PB0
Firmware Revision: 80.00A80
Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Supported: 9 8 7 6 5
Likely used: 9
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 5860533168
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
device size with M = 1024*1024: 2861588 MBytes
device size with M = 1000*1000: 3000592 MBytes (3000 GB)
df -lh
Filesystem Size Used Avail Use% Mounted on
/dev/root 59G 6.7G 50G 12% /
devtmpfs 484M 0 484M 0% /dev
tmpfs 489M 8.0K 489M 1% /dev/shm
tmpfs 489M 6.5M 482M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 489M 0 489M 0% /sys/fs/cgroup
/dev/mmcblk0p1 44M 22M 22M 51% /boot
/dev/sda1 1.9T 435G 1.4T 24% /media/ExternalHD
tmpfs 98M 0 98M 0% /run/user/1000
Any ideas?
Duxa
Posted 2019-03-11T05:58:02.420
Reputation: 133
You say it’s a MyBook enclosure. Did you install this hard drive manually or did it come in the enclosure? – Daniel B – 2019-03-11T06:16:34.813
I do not remember at this point. Ive had this hard drive for at least 5 years... I might have installed it in there or it might have come with it. This drive has been sitting in the closet for almost entirety of that time and I want to actually start using it, but before I load it up all the way with data I want to see if I can actually utilize the full 3TB.
Have you seen sda1p3 report all 0's like that before? – Duxa – 2019-03-11T06:51:12.220
1There's sure to be an exact model number on the enclosure somewhere. Please add it to your question. – Daniel B – 2019-03-11T07:13:04.530
You are onto something. wdbwlg0020hbk-04, which according to this (and the obvious 20 in P/N) points to 2TB drive https://support.wdc.com/product.aspx?ID=307&lang=en Now I wonder if there is a way to make a 3TB work with it (maybe a firmware flash to the controller or param change or something) ?
– Duxa – 2019-03-11T07:20:03.347Possible duplicate of 3TB SATA hard drives into an old Linux system
– Ramhound – 2019-03-11T11:07:45.550@DanielB Please write up an answer to this question so I can mark it and give you credit. I tried a different controller, drive came up as 3TB, i formatted it to 3TB then put it back into the original controller and it spit partition errors at me. After reformat it went back down to 2TB. So I swapped controllers permanently. Strange that a controller would enforce sizes like that (its not like its a controller from before 32bit issues were resolved), its likely something that is changeable on the controller (firmware maybe?). If you know how people share. Anyhow root cause was found. Thanks! – Duxa – 2019-03-12T21:04:13.120