Albullit
Cadet
- Joined
- May 10, 2016
- Messages
- 1
I have a brand new clean install of 11.2 U4, using the hardware below.
on all 8 drives to set the sector size to 512 (these are old NetApp drives I'm reusing for a homelab box).
Now however, when I go to create a pool via the web GUI, one drive, da0, misreports its size as 32MiB, rather than 558.91 GiB as the other sever drives do. Thus the GUI won't let me use that drive in the pool as there is a size mismatch. The drives though are all identical and all report the same in dmesg
and with diskinfo
I've tried wiping the disk from the GUI (quick never completes, zeros runs into hundreds of thousands of percent done), and also running gpart manually to verify the disk, which all look fine. But the GUI still misreports the size and won't let me use the drive. I've rebooted a few times, 'cos, Windows.
If I go to command line and create the pool manually, then import it into the GUI, its fine.
So what about sg_format could have caused the GUI to become confused, and stay confused through reboots and wipes? Possibly this more a bug report than a request for help, I admit. But if anyone has come across this before I'd love to know if you solved it so the GUI works.
- Dell R710, 2xL5640, 72GB.
- 8 Hitachi HUC106060CSS600 drives.
- Dell PERC H200 flashed to IT mode.
Code:
sg_format -v --format --fmtpinfo=0 --pfu=0 --size=512 --six /dev/da0
on all 8 drives to set the sector size to 512 (these are old NetApp drives I'm reusing for a homelab box).
Now however, when I go to create a pool via the web GUI, one drive, da0, misreports its size as 32MiB, rather than 558.91 GiB as the other sever drives do. Thus the GUI won't let me use that drive in the pool as there is a size mismatch. The drives though are all identical and all report the same in dmesg
Code:
root@freenas[~]# dmesg | grep ^da0 da0 at mps0 bus 0 scbus1 target 0 lun 0 da0: <NETAPP X422_HCOBD600A10 NA02> Fixed Direct Access SPC-4 SCSI device da0: Command Queueing enabled da0: 572325MB (1172123568 512 byte sectors)
and with diskinfo
Code:
root@freenas[~]# diskinfo -v /dev/da0 /dev/da0 512 # sectorsize 600127266816 # mediasize in bytes (559G) 1172123568 # mediasize in sectors 0 # stripesize 0 # stripeoffset 72961 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. NETAPP X422_HCOBD600A10 # Disk descr. PZHUEG5D # Disk ident. No # TRIM/UNMAP support 10020 # Rotation rate in RPM Not_Zoned # Zone Mode
I've tried wiping the disk from the GUI (quick never completes, zeros runs into hundreds of thousands of percent done), and also running gpart manually to verify the disk, which all look fine. But the GUI still misreports the size and won't let me use the drive. I've rebooted a few times, 'cos, Windows.
If I go to command line and create the pool manually, then import it into the GUI, its fine.
Code:
root@freenas[~]# gpart create -s gpt /dev/da0 da0 created root@freenas[~]# gpart add -a 4096 -i 1 -s 2g -t freebsd-swap /dev/da0 da0p1 added root@freenas[~]# gpart add -a 4096 -i 2 -t freebsd-zfs /dev/da0 da0p2 added root@freenas[~]# gpart create -s gpt /dev/da1 da1 created root@freenas[~]# gpart create -s gpt /dev/da2 da2 created root@freenas[~]# gpart create -s gpt /dev/da3 da3 created root@freenas[~]# gpart create -s gpt /dev/da4 da4 created root@freenas[~]# gpart create -s gpt /dev/da5 da5 created root@freenas[~]# gpart create -s gpt /dev/da6 da6 created root@freenas[~]# gpart create -s gpt /dev/da7 da7 created root@freenas[~]# gpart add -a 4096 -i 1 -s 2g -t freebsd-swap /dev/da1 da1p1 added root@freenas[~]# gpart add -a 4096 -i 1 -s 2g -t freebsd-swap /dev/da2 da2p1 added root@freenas[~]# gpart add -a 4096 -i 1 -s 2g -t freebsd-swap /dev/da3 da3p1 added root@freenas[~]# gpart add -a 4096 -i 1 -s 2g -t freebsd-swap /dev/da4 da4p1 added root@freenas[~]# gpart add -a 4096 -i 1 -s 2g -t freebsd-swap /dev/da5 da5p1 added root@freenas[~]# gpart add -a 4096 -i 1 -s 2g -t freebsd-swap /dev/da6 da6p1 added root@freenas[~]# gpart add -a 4096 -i 1 -s 2g -t freebsd-swap /dev/da7 da7p1 added root@freenas[~]# gpart add -a 4096 -i 2 -t freebsd-zfs /dev/da1 da1p2 added root@freenas[~]# gpart add -a 4096 -i 2 -t freebsd-zfs /dev/da2 da2p2 added root@freenas[~]# gpart add -a 4096 -i 2 -t freebsd-zfs /dev/da3 da3p2 added root@freenas[~]# gpart add -a 4096 -i 2 -t freebsd-zfs /dev/da4 da4p2 added root@freenas[~]# gpart add -a 4096 -i 2 -t freebsd-zfs /dev/da5 da5p2 added root@freenas[~]# gpart add -a 4096 -i 2 -t freebsd-zfs /dev/da6 da6p2 added root@freenas[~]# gpart add -a 4096 -i 2 -t freebsd-zfs /dev/da7 da7p2 added root@freenas[/dev]# glabel status | grep 2$ | cut -d " " -f 1 gptid/274b85e9-87d9-11e9-b362-0024e834acb2 gptid/396b5e78-87d9-11e9-b362-0024e834acb2 gptid/3a17b057-87d9-11e9-b362-0024e834acb2 gptid/3a7d1c6a-87d9-11e9-b362-0024e834acb2 gptid/3afbdfda-87d9-11e9-b362-0024e834acb2 gptid/3b65196f-87d9-11e9-b362-0024e834acb2 gptid/3bf2beec-87d9-11e9-b362-0024e834acb2 gptid/3c806743-87d9-11e9-b362-0024e834acb2 root@freenas[~]# cd /dev root@freenas[/dev]# zpool create -R /mnt -o failmode=continue plunge raidz2 gptid/274b85e9-87d9-11e9-b362-0024e834acb2 gptid/396b5e78-87d9-11e9-b362-0024e834acb2 gptid/3a17b057-87d9-11e9-b362-0024e834acb2 gptid/3a7d1c6a-87d9-11e9-b362-0024e834acb2 gptid/3afbdfda-87d9-11e9-b362-0024e834acb2 gptid/3b65196f-87d9-11e9-b362-0024e834acb2 gptid/3bf2beec-87d9-11e9-b362-0024e834acb2 gptid/3c806743-87d9-11e9-b362-0024e834acb2 root@freenas[/dev]# zpool export plunge
So what about sg_format could have caused the GUI to become confused, and stay confused through reboots and wipes? Possibly this more a bug report than a request for help, I admit. But if anyone has come across this before I'd love to know if you solved it so the GUI works.