Unable to add new Hard drive?

Marcodian

Cadet
Joined
Feb 19, 2021
Messages
6
System Specs :

Asus P8H77-I Intel H77
Inet G2030
16GB DDR3
1 x Seagate 6TB - ST6000VN0041
2 x Seagate 3TB - ST3000VN000/ST3000DM001
1 x HGST 12TB - Drive not fully recognised - HGST HUH721212ALE6004
Intel ExpI9301CTBLK Network card
Sandisk Cruzer orbit 8GB- Boot Drive
OS - FreeNAS 11.3-Stable [release]
Hard drives are setup as JBOD - apologies if I have missed any details

I've been using Freenas for a few years now but I've only ever had it setup as JBOD, I started with one of the 3TB seagate drives, added another 3TB down the line and eventually a seagate 6TB, I recently bought a HGST 12 TB drive - which I used in my windows machine for a brief time, before more recently swapping it out for a 4TB with plans to add the 12TB into freenas, However I have run into a spot of trouble with that - from what I can see if I go into the GUI, seletc the storage drop down menu and then disks - the 12TB drive is not listed, what I do see listed is :

ada0 - this is the 6TB
ada1 - this is a 3TB
ada2 -this is a 3TB
da0 - this is the OS pen drive
da1 - I dont fully know what this is but Freenas gives the following information


Disk Type:
UNKNOWN
Description:
N/A
Model:
ONETOUCH MobileBroadBand
Transfer Mode:
Auto
Rotation Rate (RPM):
N/A
HDD Standby:
ALWAYS ON
Adv. Power Management:
DISABLED
Acoustic Level:
DISABLED
Enable S.M.A.R.T.:
true
S.M.A.R.T. extra options:
N/A

If I select Pools and try to create a new pool - the only option I have to create a new pool is with da1 which shows as 0B in size, no sign of the 12TB drive

I did some looking around and was unable to find any solution, but I did come across some information that may be helpful - If I use the command "camcontrol devlist" I get

<ST6000VN0041-2EL11C SC61> at scbus0 target 0 lun 0 (pass0,ada0)
<ST3000VN000-1H4167 SC43> at scbus0 target 1 lun 0 (pass1,ada1)
<ST3000DM001-1ER166 CC43> at scbus1 target 0 lun 0 (pass2,ada2)
<HGST HUH721212ALE604 LEGNW3D0> at scbus1 target 1 lun 0 (pass3,ada3)
<SanDisk Cruzer Orbit 1.26> at scbus5 target 0 lun 0 (pass4,da0)

Also with "gpart list"

gpart list
Geom name: ada0
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 11721045127
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: ada0p1
Mediasize: 2147483648 (2.0G)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r0w0e0
efimedia: HD(1,GPT,ec3a2ed4-d483-11e8-89a0-10bf487f5347,0x80,0x400000)
rawuuid: ec3a2ed4-d483-11e8-89a0-10bf487f5347
rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
label: (null)
length: 2147483648
offset: 65536
type: freebsd-swap
index: 1
end: 4194431
start: 128
2. Name: ada0p2
Mediasize: 5999027556352 (5.5T)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r1w1e2
efimedia: HD(2,GPT,ec4cf7a2-d483-11e8-89a0-10bf487f5347,0x400080,0x2ba60f408)
rawuuid: ec4cf7a2-d483-11e8-89a0-10bf487f5347
rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
label: (null)
length: 5999027556352
offset: 2147549184
type: freebsd-zfs
index: 2
end: 11721045127
start: 4194432
Consumers:
1. Name: ada0
Mediasize: 6001175126016 (5.5T)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r1w1e3

Geom name: ada1
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 5860533127
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: ada1p1
Mediasize: 2147483648 (2.0G)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r1w1e1
efimedia: HD(1,GPT,ee685a51-d483-11e8-89a0-10bf487f5347,0x80,0x400000)
rawuuid: ee685a51-d483-11e8-89a0-10bf487f5347
rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
label: (null)
length: 2147483648
offset: 65536
type: freebsd-swap
index: 1
end: 4194431
start: 128
2. Name: ada1p2
Mediasize: 2998445412352 (2.7T)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r1w1e2
efimedia: HD(2,GPT,ee7434b7-d483-11e8-89a0-10bf487f5347,0x400080,0x15d10a308)
rawuuid: ee7434b7-d483-11e8-89a0-10bf487f5347
rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
label: (null)
length: 2998445412352
offset: 2147549184
type: freebsd-zfs
index: 2
end: 5860533127
start: 4194432
Consumers:
1. Name: ada1
Mediasize: 3000592982016 (2.7T)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r2w2e5

Geom name: ada2
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 5860533127
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: ada2p1
Mediasize: 2147483648 (2.0G)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r1w1e1
efimedia: HD(1,GPT,ce45d53f-d483-11e8-89a0-10bf487f5347,0x80,0x400000)
rawuuid: ce45d53f-d483-11e8-89a0-10bf487f5347
rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
label: (null)
length: 2147483648
offset: 65536
type: freebsd-swap
index: 1
end: 4194431
start: 128
2. Name: ada2p2
Mediasize: 2998445412352 (2.7T)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r1w1e2
efimedia: HD(2,GPT,ce547eca-d483-11e8-89a0-10bf487f5347,0x400080,0x15d10a308)
rawuuid: ce547eca-d483-11e8-89a0-10bf487f5347
rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
label: (null)
length: 2998445412352
offset: 2147549184
type: freebsd-zfs
index: 2
end: 5860533127
start: 4194432
Consumers:
1. Name: ada2
Mediasize: 3000592982016 (2.7T)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r2w2e5

Geom name: ada3
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 23437770711
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: ada3p1
Mediasize: 12000138584064 (11T)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r0w0e0
efimedia: HD(1,GPT,ac9f5f0c-72e9-11eb-827c-001b213a5b1c,0x28,0x574ffffb0)
rawuuid: ac9f5f0c-72e9-11eb-827c-001b213a5b1c
rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
label: (null)
length: 12000138584064
offset: 20480
type: freebsd-zfs
index: 1
end: 23437770711
start: 40
Consumers:
1. Name: ada3
Mediasize: 12000138625024 (11T)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r0w0e0

Geom name: da0
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 15633367
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: da0p1
Mediasize: 524288 (512K)
Sectorsize: 512
Stripesize: 0
Stripeoffset: 20480
Mode: r0w0e0
efimedia: HD(1,GPT,25be72cf-d309-11e8-a975-10bf487f5347,0x28,0x400)
rawuuid: 25be72cf-d309-11e8-a975-10bf487f5347
rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
label: (null)
length: 524288
offset: 20480
type: freebsd-boot
index: 1
end: 1063
start: 40
2. Name: da0p2
Mediasize: 8003739648 (7.5G)
Sectorsize: 512
Stripesize: 0
Stripeoffset: 544768
Mode: r1w1e1
efimedia: HD(2,GPT,25dbad4a-d309-11e8-a975-10bf487f5347,0x428,0xee87b0)
rawuuid: 25dbad4a-d309-11e8-a975-10bf487f5347
rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
label: (null)
length: 8003739648
offset: 544768
type: freebsd-zfs
index: 2
end: 15633367
start: 1064

and "sysctl kern.disks" gives - da0 ada3 ada1 ada0

So from what I can see, on some level Freenas can see the drive, ada3, but unable to let me use it? I'm not exactly sure, hopefully it is a simple fix, hope I have given enough information if not please feel free to ask.
 

Marcodian

Cadet
Joined
Feb 19, 2021
Messages
6
Just a bump to hoping to get some suggestions, I've not got any further myself with this
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
<HGST HUH721212ALE604 LEGNW3D0> at scbus1 target 1 lun 0 (pass3,ada3)
Looks to me like this is saying that ada3 is the 12TB disk.

What is zpool list -v showing you?
 

Marcodian

Cadet
Joined
Feb 19, 2021
Messages
6
Looks to me like this is saying that ada3 is the 12TB disk.

What is zpool list -v showing you?

Yeah it is picking up the 12TB disk as ada3 but only in select areas it seems, zpool list -v gives :

root@freenas[~]# zpool list -v
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
Data0 10.9T 9.76T 1.12T - - 37% 89% 1.00x ONLINE /mnt
gptid/ce547eca-d483-11e8-89a0-10bf487f5347 2.72T 2.69T 27.8G - - 65% 99%
gptid/ec4cf7a2-d483-11e8-89a0-10bf487f5347 5.44T 4.37T 1.06T - - 9% 80%
gptid/ee7434b7-d483-11e8-89a0-10bf487f5347 2.72T 2.69T 27.6G - - 67% 99%
freenas-boot 7G 4.55G 2.45G - - - 64% 1.00x ONLINE -
da0p2 7G 4.55G 2.45G - - - 64%
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
So ada3p2 is:
ac9f5f0c-72e9-11eb-827c-001b213a5b1c

Which is none of the gptids in your pool (not surprising).


ada2p2 is:
ce547eca-d483-11e8-89a0-10bf487f5347

which is the first disk in your pool


ada1p2 is:
ee7434b7-d483-11e8-89a0-10bf487f5347

which is the third disk in your pool

ada0p2 is:
ec4cf7a2-d483-11e8-89a0-10bf487f5347

which is the third disk in your pool


So back to your original problem, why is ada3 not available when you try to extend your pool? Have you tried wiping it from Storage | Disks ? (or are you saying it isn't in that list?)
 

Marcodian

Cadet
Joined
Feb 19, 2021
Messages
6
So ada3p2 is:
ac9f5f0c-72e9-11eb-827c-001b213a5b1c

Which is none of the gptids in your pool (not surprising).


ada2p2 is:
ce547eca-d483-11e8-89a0-10bf487f5347

which is the first disk in your pool


ada1p2 is:
ee7434b7-d483-11e8-89a0-10bf487f5347

which is the third disk in your pool

ada0p2 is:
ec4cf7a2-d483-11e8-89a0-10bf487f5347

which is the third disk in your pool


So back to your original problem, why is ada3 not available when you try to extend your pool? Have you tried wiping it from Storage | Disks ? (or are you saying it isn't in that list?)
Yeah ada3 is not showing up in my storage I disks which has got me stumped
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
I guess cleaning it will be the next thing to try...

gpart destroy -F /dev/ada3

You might then need to reboot or reconnect the disk if it's in a hot-plug pay.
 

Marcodian

Cadet
Joined
Feb 19, 2021
Messages
6
ada3 disk destroyed, system rebooted, storage/ disks still doesnt show the 12TB, is the next step:

gpart create -s gpt ada3 ?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
is the next step:

gpart create -s gpt ada3 ?
Well, adding the disk to the pool should cause the middleware to do that for you, but you can do it manually if we have no other choice:
gpart create -s gpt /dev/ada3

Then we create the swap and data partitions:
gpart add -s 2G -t freebsd-swap /dev/ada3

gpart add -t freebsd-zfs /dev/ada3

Then you look for the ada3p2 raw uuid value and use it to extend the pool:
zpool add <poolname> gptid/<rawuuid of data partition from gpart list>

Then zpool status -v to make sure it all looks right.
 

Marcodian

Cadet
Joined
Feb 19, 2021
Messages
6
Well, adding the disk to the pool should cause the middleware to do that for you, but you can do it manually if we have no other choice:
gpart create -s gpt /dev/ada3

Then we create the swap and data partitions:
gpart add -s 2G -t freebsd-swap /dev/ada3

gpart add -t freebsd-zfs /dev/ada3

Then you look for the ada3p2 raw uuid value and use it to extend the pool:
zpool add <poolname> gptid/<rawuuid of data partition from gpart list>

Then zpool status -v to make sure it all looks right.
That worked perfectly - the Hard Drive is now in the Pool, every other time I've added a drive I've just gone to storage and drives - extend pool, completely out of my depth here - many thanks
 
Top