Now I want to nail this. Does df -h show the right size?
Out of town for the weekend. Will let you know asap.
Only waiting for you.... [emoji28]
Right... sorry, i already added the drive to my array
I have a precleared 4TB drive that also shows a disk size of 2.2TB. Like mr-hexen wrote in another post, df -h does not show any information on the disk because it is not mounted. Here is some other information on the disk:
root@uwer:~# lsblk /dev/sdd
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdd 8:48 0 3.7T 0 disk
??sdd1 8:49 0 2T 0 part
root@uwer:~# blockdev --getsize64 /dev/sdd
4000787030016
root@uwer:~# blockdev --getsize64 /dev/sdd1
2199023255040
root@uwer:~# /boot/custom/preclear_disk.sh -t /dev/sdd
Pre-Clear unRAID Disk /dev/sdd
################################################################## 1.15
Model Family: Seagate Desktop HDD.15
Device Model: ST4000DM000-1CD168
Serial Number: Z300119S
LU WWN Device Id: 5 000c50 04f1e88ef
Firmware Version: CC43
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Disk /dev/sdd: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdd1 1 4294967295 2147483647+ 0 Empty
Partition 1 does not start on physical sector boundary.
########################################################################
========================================================================1.15
==
== DISK /dev/sdd IS PRECLEARED with a GPT Protective MBR
==
============================================================================
Also saw some strange behavior when testing preclear signature. Disk was in standby when preclear test command was issued. While drive was spinning up, unassigned devices tab was dimmed except for spinning wheel. Then unassigned devices tab refreshed with correct drive size. After another refresh, the unassigned devices tab again shows incorrect drive size.
Thank you for the debug info, Freddie.
This is a very odd behavior; the lsblk and the blockdev commands work fine when reading the disk, but not when reading the partition. I'm unable to debug this right now, since I don't have a spare 2TB+ hdd around. If anyone found a solution, please let me know.