SOLVED N00B having trouble creating volume

Status
Not open for further replies.

KristofferD

Dabbler
Joined
Jul 31, 2015
Messages
13
edit: The solutioion for my problem was to put all the drives in my main windows machine, format them all and unallocated them.
Also found out there was an old raid 1 on two of the drives.


I created a new volume today, turned out I only got one drive in it out of my 6 drives so I detached the volume and try to create a raidz2 out of the 6x2tb drives I got.
Then I get "Error: Unable to GPT format the disk "ada0""
I try and wipe said drive and gets "Error: Failed to wipe ada0: dd: /dev/ada0: Input/output error 1+0 records in 0+0 records out 0 bytes transferred in 0.653818 secs (0 bytes/sec)"

Build FreeNAS-9.10.1 (d989edd)
Platform Intel(R) Core(TM) i5-2320 CPU @ 3.00GHz
Memory 32403MB
System Time Sun Aug 07 13:20:49 CEST 2016
Uptime 1:20PM up 1:09, 0 users
Load Average 0.16, 0.22, 0.25

Motherboard MSI B75MA-P45
Harddrives 6X Seagate Barracuda ST2000DM001 64MB 2TB

Is there any reasonable way to fix it and get all drives in one raidz2?
Never used freenas shell before but is used to windows powershell so will probably try and find shell commands that can wipe the drive and create the volume.
I'll keep reading all the guides and doc I can find but right now I've spent half day on this and a friendly nodge in the right direction would be really appreciated.
 
Last edited:

sfcredfox

Patron
Joined
Aug 26, 2014
Messages
340

gpsguy

Active Member
Joined
Jan 22, 2012
Messages
4,472

CraigD

Patron
Joined
Mar 8, 2016
Messages
343
I'm new to freeNAS so dropped the drives into a windows computer and removed all volumes from them

Have Fun
 

KristofferD

Dabbler
Joined
Jul 31, 2015
Messages
13
I googled 'freebsd Error: Unable to GPT format the disk "ada0"'
Found this:
https://forums.freenas.org/index.ph...rror-unable-to-gpt-format-the-disk-ada0.3738/

Might be worth a try if you haven't already tried some of these things. Looks similar.

Have tryed that as well now but no change
[root@freenas ~]# ls /dev/ada0
/dev/ada0
[root@freenas ~]# file /dev/ada0
/dev/ada0: character special (0/109)
[root@freenas ~]# gpart show ada0
=> 63 3907029105 ada0 MBR (1.8T)
63 1985 - free - (993K)
2048 3907026944 1 ntfs [active] (1.8T)
3907028992 176 - free - (88K)

[root@freenas ~]# dd if=/dev/zero of=/dev/ada0 bs=1M count=10
dd: /dev/ada0: Input/output error
1+0 records in
0+0 records out
0 bytes transferred in 0.647446 secs (0 bytes/sec)
[root@freenas ~]# dmesg | grep ada
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 00 00 00 40 00 00 00 01 00 00
(ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error
(ada0:ahcich0:0:0:0): Error 5, Retries exhausted[/CODE]

You should be able to wipe the disk from the GUI. See the second to the last paragraph in this section -
http://doc.freenas.org/9.10/freenas_storage.html#view-disks

Or from the CLI, look at zpool labelclear

Yes I should be but I get same error message "Error: Failed to wipe ada0: dd: /dev/ada0: Input/output error 1+0 records in 0+0 records out 0 bytes transferred in 0.653818 secs (0 bytes/sec)" no mather if I try to it in the GUI or by the Shell.

I'm new to freeNAS so dropped the drives into a windows computer and removed all volumes from them

Have Fun

I do start to lean towards put them in my main pc and run complete disk formating on them all.
Hopefully that would do it.
 

KristofferD

Dabbler
Joined
Jul 31, 2015
Messages
13
Ended up moving all of the drives into my main pc and run disk formating on them but I still get "Error: Unable to GPT format the disk "ada0"" even do it worked 100% fine after formating on my windows machine.
Guess I'll simply have to throw that drive out the window and buy a new one.

edit: when I check my drives I've my 6 drives named "ada" from 0 to 5 but when I check "import disk" I've some with different names:
  • ada0s1 (2TB)
  • ada1p2 (2TB)
  • ada2s1 (2TB)
  • ada3 (2TB)
  • ada4 (2TB)
  • ada5p2 (2TB)
  • ada1p1 (134.2MB)
  • ada5p1 (134.2MB)

print screen: freenas.png
Is that "normal" for freenas or is something really wrong now?
 
Last edited:

CraigD

Patron
Joined
Mar 8, 2016
Messages
343
Remove the volume in disk manager is will work
 

KristofferD

Dabbler
Joined
Jul 31, 2015
Messages
13
Remove the volume in disk manager is will work
It dosn't exist a single volume on the nas at this moment, only the drives and I can't wipe ada0 for some reason using either the GUI or shell.
Have tryed every shell command I can find on link and the drive still it refuce to play ball.
 

CraigD

Patron
Joined
Mar 8, 2016
Messages
343
I was talking about doing this in windows, sorry for not being clear MAKE SURE YOU ARE ON THE CORRECT DRIVE WHEN DELETING

The unallocated black bar is what you want not a blue bar
 

KristofferD

Dabbler
Joined
Jul 31, 2015
Messages
13
I was talking about doing this in windows, sorry for not being clear MAKE SURE YOU ARE ON THE CORRECT DRIVE WHEN DELETING

The unallocated black bar is what you want not a blue bar

Have done it now and my nas is alive after another ~2 hours of swearing! :D
Might have found the main reason for my problems and it was an old rst raid 1 on two of the drives that I had upgraded from in my main pc.

Will keep Cyberjock's guide for n00bs in my e-reader by the bed for the next couple of weeks so I don't have to ask for more n00b related stuff :)
 

KristofferD

Dabbler
Joined
Jul 31, 2015
Messages
13
Got a little follow up question, I was sending over some files, mostly movie rips, and I feel that the nas is a bit slow. Around 50MB writes no mather if the source was hdd, ssd or even ramdisk on the main rig.
Have run write and read test on the nas and I feel it's a bit low but can also be normal speeds since I'm not that used to the system get and would like some input from any more experienced person :)
Cifs is activated on the nas since main rig runs windows, opend the nas as a network folder on the pc rig. Not sure if I should have used a ftp software for transferering, could that result in better performance?

The read/write test simply gives me 159MB write and 88 MB read.
[root@freenas ~]# dd if=/dev/zero of=testfile bs=1024 count=50000
50000+0 records in
50000+0 records out
51200000 bytes transferred in 0.321156 secs (159424068 bytes/sec)
[root@freenas ~]# dd if=testfile of=/dev/zero bs=1024 count=50000
50000+0 records in
50000+0 records out
51200000 bytes transferred in 0.577740 secs (88621186 bytes/sec)

6 drives in 1 raidz2 configuration and both the pc and nas got Gbit network.
If I wanted bether perfomence should I've opted for 2x3 drives in raidz1 instead?
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Got a little follow up question, I was sending over some files, mostly movie rips, and I feel that the nas is a bit slow. Around 50MB writes no mather if the source was hdd, ssd or even ramdisk on the main rig.
Have run write and read test on the nas and I feel it's a bit low but can also be normal speeds since I'm not that used to the system get and would like some input from any more experienced person :)
Cifs is activated on the nas since main rig runs windows, opend the nas as a network folder on the pc rig. Not sure if I should have used a ftp software for transferering, could that result in better performance?

The read/write test simply gives me 159MB write and 88 MB read.
[root@freenas ~]# dd if=/dev/zero of=testfile bs=1024 count=50000
50000+0 records in
50000+0 records out
51200000 bytes transferred in 0.321156 secs (159424068 bytes/sec)
[root@freenas ~]# dd if=testfile of=/dev/zero bs=1024 count=50000
50000+0 records in
50000+0 records out
51200000 bytes transferred in 0.577740 secs (88621186 bytes/sec)

6 drives in 1 raidz2 configuration and both the pc and nas got Gbit network.
If I wanted bether perfomence should I've opted for 2x3 drives in raidz1 instead?
Start at the beginning.... Run iperf and see if the network layer is working as expected.

If you have Realtek NICs on either side, I'll bet that networking won't be in order.
 
Status
Not open for further replies.
Top