Upgrading hard drives

[TazgodX]

So i had 7 1TB HDDs in ZFS and one died, so i figured why not just upgrade them all to 2TBs. I went and bought 7 2TB HDDs. bought Seagate Barracuda's from multiple sources, spread over 3 weeks.
plugged the first in and had no problems swapping out the bad drive. I went to plug in the next drive and it read the drive as a 1TB drive, not a 2TB as it should be. plugged in 3 drives and they all read as 1TB. plugged in those drives into my mac computer and all read as 1TB in my mac too. tested the other 3 drives in my mac, and they read as 2TBs, but when plugged into the FreeNAS it says 1TB and when pluggin them back into my mac, they are 1TB there too. Not sure if there is something im doing wrong. im seriously totally confused on this issue. anyone have any ideas?

 

[Stephens]

Read noobsauce80's ZFS primer. Deal? OK. It's normal. You won't see them as 2TB drives until you've successfully replaced the last one.

 

[TazgodX]

Ok, maybe I was a little vague. Let me explain a little better.
I bought 2 TB drives, plug it into my Mac, and it shows that it's an Unformatted 2TB drive. Plug it into freenas select replace go to select new drive, only shows as a 1TB drive and when I try to replace it tells me new drive is not large enough to replace, and wont. I then take drive out of freenas and back into Mac and it now shows as 1TB in Mac also.
I realized I won't get the extra space till all the drives are replaced, but it won't let me replace the drive because it says it is too small. This isn't a problem of me replacing drives and not getting the extra TB, it's a problem of the new drives not being able to be replaced because they are showing half their size. The one that did work correctly showed the new drive as a 2TB, and worked fine. No issues with that drive.

 

[tingo]

Could be something specific with the drives you've bought.
Now, fess up the details: what drives (old and new, please)? What motherboard? what does the log (in FreeNAS say when you insert / boot with the new drives?

 

[TazgodX]

The old hard drives are SAMSUNG Spinpoint F3 HD103SJ 1TB
the new hard drives are Seagate ST2000DM001 Barracuda 7200RPM 2 TB
The motherboard is a Gigabyte GA-K8NE
There are no messages in FreeNAS that i can find, only when I go to replace a drive it lists it as a 1TB.

 

[paleoN]

There are no messages in FreeNAS that i can find, only when I go to replace a drive it lists it as a 1TB.

With the working? 2TB drive and at least one of the other 2TB drives in the system output of the following from an SSH session as root:

Code:

zpool status -v

camcontrol devlist

gpart show

glabel status

For each drive shown in camcontrol devlist, skipping the FN8 USB drive:

Code:

camcontrol identify adaX

You can drop the serial number & WWN lines if you like, but the rest of it if you please.

 

[TazgodX]

just so you know, ada1 is the working 2TB. ada0 is a 2TB, only recognized as a 1.
-Thanks

zpool status -v

pool: tank
state: DEGRADED
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://www.sun.com/msg/ZFS-8000-8A
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
tank DEGRADED 0 0 0
raidz1 DEGRADED 0 0 0
ada4 ONLINE 0 0 0
gptid/9920744d-0c33-11e2-87c6-001485d31703 ONLINE 0 0 0
ada6 ONLINE 0 0 0
ada2 ONLINE 0 0 0
ada3 ONLINE 0 0 0
14518921872551404709 UNAVAIL 0 0 0 was /dev/ada0
ada5 ONLINE 0 0 0

camcontrol devlist

<ST2000DM001-9YN164 CC4B> at scbus2 target 0 lun 0 (pass0,ada0)
<ST2000DM001-9YN164 CC4B> at scbus3 target 0 lun 0 (pass1,ada1)
<SAMSUNG HD103SJ 1AJ10001> at scbus4 target 0 lun 0 (pass2,ada2)
<SAMSUNG HD103SJ 1AJ10001> at scbus5 target 0 lun 0 (pass3,ada3)
<SAMSUNG HD103SJ 1AJ10001> at scbus6 target 0 lun 0 (pass4,ada4)
<SAMSUNG HD103SJ 1AJ10001> at scbus8 target 0 lun 0 (pass5,ada5)
<SAMSUNG HD103SJ 1AJ10001> at scbus9 target 0 lun 0 (pass6,ada6)
<SanDisk Cruzer Fit 1.26> at scbus10 target 0 lun 0 (pass7,da0)

gpart show

=> 63 31266711 da0 MBR (15G)
63 1930257 1 freebsd [active] (943M)
1930320 63 - free - (32K)
1930383 1930257 2 freebsd (943M)
3860640 3024 3 freebsd (1.5M)
3863664 41328 4 freebsd (20M)
3904992 27361782 - free - (13G)

=> 0 1930257 da0s1 BSD (943M)
0 16 - free - (8.0K)
16 1930241 1 !0 (943M)

=> 34 3907029101 ada1 GPT (1.8T)
34 94 - free - (47K)
128 4194304 1 freebsd-swap (2.0G)
4194432 3902834703 2 freebsd-zfs (1.8T)

glabel status

Name Status Components
ufs/FreeNASs3 N/A da0s3
ufs/FreeNASs4 N/A da0s4
ufs/FreeNASs1a N/A da0s1a
gptid/9920744d-0c33-11e2-87c6-001485d31703 N/A ada1p2

camcontrol identify ada0

pass0: <ST2000DM001-9YN164 CC4B> ATA-8 SATA 3.x device
pass0: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)

protocol ATA/ATAPI-8 SATA 3.x
device model ST2000DM001-9YN164
firmware revision CC4B
serial number ******XX
WWN ***************X
cylinders 16383
heads 16
sectors/track 63
sector size logical 512, physical 4096, offset 0
LBA supported 268435455 sectors
LBA48 supported 1953569134 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM 7200

Feature Support Enabled Value Vendor
read ahead yes yes
write cache yes yes
flush cache yes yes
overlap no
Tagged Command Queuing (TCQ) no no
Native Command Queuing (NCQ) yes 32 tags
SMART yes yes
microcode download yes yes
security yes no
power management yes yes
advanced power management yes no 0/0x00
automatic acoustic management no no
media status notification no no
power-up in Standby no no
write-read-verify yes no 0/0x0
unload no no
free-fall no no
data set management (TRIM) no

camcontrol identify ada1

pass1: <ST2000DM001-9YN164 CC4B> ATA-8 SATA 3.x device
pass1: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)

protocol ATA/ATAPI-8 SATA 3.x
device model ST2000DM001-9YN164
firmware revision CC4B
serial number ******XX
WWN ***************
cylinders 16383
heads 16
sectors/track 63
sector size logical 512, physical 4096, offset 0
LBA supported 268435455 sectors
LBA48 supported 3907029168 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM 7200

Feature Support Enabled Value Vendor
read ahead yes yes
write cache yes yes
flush cache yes yes
overlap no
Tagged Command Queuing (TCQ) no no
Native Command Queuing (NCQ) yes 32 tags
SMART yes yes
microcode download yes yes
security yes no
power management yes yes
advanced power management yes yes 32896/0x8080
automatic acoustic management no no
media status notification no no
power-up in Standby no no
write-read-verify yes no 0/0x0
unload no no
free-fall no no
data set management (TRIM) no

camcontrol identify ada2

pass2: <SAMSUNG HD103SJ 1AJ10001> ATA-8 SATA 2.x device
pass2: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)

protocol ATA/ATAPI-8 SATA 2.x
device model SAMSUNG HD103SJ
firmware revision 1AJ10001
serial number ************XX
WWN ***************
cylinders 16383
heads 16
sectors/track 63
sector size logical 512, physical 512, offset 0
LBA supported 268435455 sectors
LBA48 supported 1953525168 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM 7200

Feature Support Enabled Value Vendor
read ahead yes yes
write cache yes yes
flush cache yes yes
overlap no
Tagged Command Queuing (TCQ) no no
Native Command Queuing (NCQ) yes 32 tags
SMART yes yes
microcode download yes yes
security yes no
power management yes yes
advanced power management yes yes 128/0x80
automatic acoustic management yes yes 128/0x80 254/0xFE
media status notification no no
power-up in Standby yes no
write-read-verify no no
unload no no
free-fall no no
data set management (TRIM) no

camcontrol identify ada3

pass3: <SAMSUNG HD103SJ 1AJ10001> ATA-8 SATA 2.x device
pass3: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)

protocol ATA/ATAPI-8 SATA 2.x
device model SAMSUNG HD103SJ
firmware revision 1AJ10001
serial number ************XX
WWN ***************
cylinders 16383
heads 16
sectors/track 63
sector size logical 512, physical 512, offset 0
LBA supported 268435455 sectors
LBA48 supported 1953525168 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM 7200

Feature Support Enabled Value Vendor
read ahead yes yes
write cache yes yes
flush cache yes yes
overlap no
Tagged Command Queuing (TCQ) no no
Native Command Queuing (NCQ) yes 32 tags
SMART yes yes
microcode download yes yes
security yes no
power management yes yes
advanced power management yes yes 128/0x80
automatic acoustic management yes yes 128/0x80 254/0xFE
media status notification no no
power-up in Standby yes no
write-read-verify no no
unload no no
free-fall no no
data set management (TRIM) no

camcontrol identify ada4

pass4: <SAMSUNG HD103SJ 1AJ10001> ATA-8 SATA 2.x device
pass4: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)

protocol ATA/ATAPI-8 SATA 2.x
device model SAMSUNG HD103SJ
firmware revision 1AJ10001
serial number ************XX
WWN ***************
cylinders 16383
heads 16
sectors/track 63
sector size logical 512, physical 512, offset 0
LBA supported 268435455 sectors
LBA48 supported 1953523055 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM 7200

Feature Support Enabled Value Vendor
read ahead yes yes
write cache yes yes
flush cache yes yes
overlap no
Tagged Command Queuing (TCQ) no no
Native Command Queuing (NCQ) yes 32 tags
SMART yes yes
microcode download yes yes
security yes no
power management yes yes
advanced power management yes yes 128/0x80
automatic acoustic management yes yes 128/0x80 254/0xFE
media status notification no no
power-up in Standby yes no
write-read-verify no no
unload no no
free-fall no no
data set management (TRIM) no

camcontrol identify ada5

pass5: <SAMSUNG HD103SJ 1AJ10001> ATA-8 SATA 2.x device
pass5: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)

protocol ATA/ATAPI-8 SATA 2.x
device model SAMSUNG HD103SJ
firmware revision 1AJ10001
serial number ************XX
WWN ***************
cylinders 16383
heads 16
sectors/track 63
sector size logical 512, physical 512, offset 0
LBA supported 268435455 sectors
LBA48 supported 1953523055 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM 7200

Feature Support Enabled Value Vendor
read ahead yes yes
write cache yes yes
flush cache yes yes
overlap no
Tagged Command Queuing (TCQ) no no
Native Command Queuing (NCQ) yes 32 tags
SMART yes yes
microcode download yes yes
security yes no
power management yes yes
advanced power management yes no 0/0x00
automatic acoustic management yes no 0/0x00 254/0xFE
media status notification no no
power-up in Standby yes no
write-read-verify no no
unload no no
free-fall no no
data set management (TRIM) no

camcontrol identify ada6

pass6: <SAMSUNG HD103SJ 1AJ10001> ATA-8 SATA 2.x device
pass6: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)

protocol ATA/ATAPI-8 SATA 2.x
device model SAMSUNG HD103SJ
firmware revision 1AJ10001
serial number ************XX
WWN ***************
cylinders 16383
heads 16
sectors/track 63
sector size logical 512, physical 512, offset 0
LBA supported 268435455 sectors
LBA48 supported 1953525168 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM 7200

Feature Support Enabled Value Vendor
read ahead yes yes
write cache yes yes
flush cache yes yes
overlap no
Tagged Command Queuing (TCQ) no no
Native Command Queuing (NCQ) yes 32 tags
SMART yes yes
microcode download yes yes
security yes no
power management yes yes
advanced power management yes no 0/0x00
automatic acoustic management yes yes 128/0x80 254/0xFE
media status notification no no
power-up in Standby yes no
write-read-verify no no
unload no no
free-fall no no
data set management (TRIM) no

 

[paleoN]

Use [code][/code] tags next time. It will preserve the formatting unlike quoting.

Now for your unusual problem, you need a BIOS update or to throw that motherboard in the trash. Gigabyte apparently had some genius BIOS coders in the past. Two relevant threads on the Seagate Forums, Re: My Barracuda 1.5TB ST31500341AS fw.CC1H is affected by firmware Issues & 1TB (1000MB) Drives shrinked to 31MB / 32MB / 33MB causality.

You may need to load up SeaTools, DOS version, to fix the 2TB drives back to being 2TB drives. I would switch to IDE mode in the BIOS first and switch back to AHCI afterwards. The motherboard/BIOS update needs to be taken care of first.

 

[TazgodX]

Thanks for the info. I was planning on upgrading the Mobo anyways because I wasn't able to get it to recognize the max allowed RAM. This just gives me another reason. so I purchased a new Mobo CPU and RAM, ill test again with the new hardware, and hopefully get better results.

-Thanks!

 

[TazgodX]

All my new parts are in and installed. powered up (with little tweaking), ran seatools for DOS and now everything is working.

Thanks a TON! now to wait 30+ hours for each drive to resliver :)

 

[TazgodX]

Ok so i got one drive reslivered. went to go Detach, and it never Detached. rebooted, still won't. took out another drive, and verified files still working, and they are. So the resliver worked, and the new drive is working as it should, but it won't detach. ran a resliver on the 3rd drive and it finished, but also won't detach.

Code:

  pool: tank
 state: DEGRADED
status: One or more devices has experienced an error resulting in data
	corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
	entire pool from backup.
   see: http://www.sun.com/msg/ZFS-8000-8A
 scrub: resilver completed after 39h51m with 35198 errors on Thu Nov  1 23:39:43 2012
config:

	NAME                                              STATE     READ WRITE CKSUM
	tank                                              DEGRADED     0     0 34.4K
	  raidz1                                          DEGRADED     0     0 68.7K
	    ada3                                          ONLINE       0     0     0
	    gptid/9920744d-0c33-11e2-87c6-001485d31703    ONLINE       0     0     0  370M resilvered
	    ada1                                          ONLINE       0     0     0
	    ada4                                          ONLINE       0     0     0
	    ada2                                          ONLINE       0     0     0
	    replacing                                     DEGRADED     0     0     0
	      14518921872551404709                        UNAVAIL      0     0     0  was /dev/ada0
	      gptid/9eb618c0-2250-11e2-b13c-485b39b64d0b  ONLINE       0     0     0  377M resilvered
	    replacing                                     DEGRADED     0     0 42.5M
	      7931052446525337501                         UNAVAIL      0     0     0  was /dev/ada5
	      gptid/2d1a4869-2359-11e2-aac7-485b39b64d0b  ONLINE       0     0     0  900G resilvered

errors: 35198 data errors, use '-v' for a list

The drives still say they are replacing, but they are completed, and working. Just won't detach.
Pool lists as degraded bcause they are still saying replacing.

http://forums.freenas.org/showthrea...ment-issues-(ZPOOL-DEGRADED)&highlight=detach
^seems to be the same issue, with no results.

 

[Yell]

do you get an error if you detach the UNAVAIL drive from the raid?

Code:

zpool detach tank 14518921872551404709
zpool detach tank 7931052446525337501

Btw how did you replaced the drive?
(looks like you set up your raid from command line [ada1-4], but replaced them with the webGUI [gptid])

 

[TazgodX]

When trying to detach from command line i get

Code:

zpool detach tank 14518921872551404709
cannot detach 14518921872551404709: no valid replicas

When i first set this up it was set up with FreeNAS 7.2 GUI. and then exported command line, and imported command line into FreeNAS 8. Attempting to replace with the GUI.

 

[Yell]

Try this:

Code:

zpool export tank

Code:

zpool import tank
zpool scrub tank

detach [in reversed order]

Code:

zpool detach tank 7931052446525337501
zpool detach tank 14518921872551404709

I think this happend because you didnt detach the disk after the first resliver.

Sidenote:
- You should review the error mentioned by "zpool status". [ i hope you have a backup]
- You might also want to destroy and receate the pool with FreeNas 8 GUI]
- Btw a raidz1 with more than 6 disks is risky, because chances that 1 drives dies while resilver is great.

 

[TazgodX]

I did those steps, still same error, can't detach.
I did detach each disk after each resliver, but they didn't detach. i unplugged another disk to see if it was actually reslivered and working and it was so i tried the next drive, and now both have same error. I know it says there are errors, and ive looked at what it is and it lists every file i have on my disk (a lot of MP3s) and played most of them and they are playing just fine. I don't see any trouble with the actual files they all play fine.

I'm now thinking about unplugging the new 2 TB drives and plugging back in the 1TBs since they won't detach. and just build a brand new zpool and raidz2 with 8 2TB drives and then just move the data over from old drives to new ones.

It's been such a headache just getting these upgraded.

-Thanks for the help. I still don't know what to do, but ill keep reading.

 

[cyberjock]

WOW. You're only about 2 hours from me. Before you try going back to the 1TB drives I'd make sure the array didn't expand to fill the 2TB drives, otherwise you won't be able to go back to smaller disks.

 

[TazgodX]

2 hours? from Chicago? you must drive slow....
Im about an hour from anywhere in Chicago.

Ok, well out of the 7 drives ive gotten 3 replaced and from what i understand it won't expand to use up the extra space until all 7 are replaced. I've also not written any new data to my FreeNAS drive since i started this.
My FreeNAS still lists the same drive size. so from my assumption it should be good, right?

Ill have to start looking into replacing a RaidZ1 with a RaidZ2 pool. before i go much further with this all.

 

[cyberjock]

You may not have written any new data to the FreeNAS zpool, but I promise you some data has certainly been written. Logs like to be updated from time to time, system accessing various file system data, etc.

You are correct that the vdev won't expand until the last drive is replaced and resilvered(and potentially a reboot of the server). You're good though.

I Googled Hanover Park and it looked like it was in the outskirts of the Chicago area. I'm in the small town of Ottawa, IL. I consider anything in the "greater chicago area" to be Chicago. It's all about the same to me... big city. :P