SOLVED Create a volume with 2 drives but the new volume doesn't show up

Status
Not open for further replies.
S

SubX

Explorer
Joined
Sep 15, 2017
Messages
56
Background
  • FreeNAS 9.10.2-u6
  • two drives (4T) with data just wiped the data, detached all 2 drives
  • create new volume with those 2 drives, select mirror, click add volume button
  • After above, the volume didn't show up as expected. Repeat wiping data and then re-create volume, same issue.
How to fix that issue and create new volume from 2 wiped drives? Please help and thanks in advanced.

S
 
wblock

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
SubX said:
the volume didn't show up as expected
Click to expand...
Please add more detail about what you mean by this. Didn't show up where?

If the volume didn't appear under Storage -> Volumes, how did you wipe the data the second time?
 
S

SubX

Explorer
Joined
Sep 15, 2017
Messages
56
Thanks wblock.

I go into storage -> view disks, select ada0 & ada1 --> Wipe again (quick) --> volume manager (create volume again).

Found this post, talking about dd method. However dd doesn't give me a clue what percentage has been completed before my putty session get terminated. How to tell if the zeroing has been completed?

In the article, it also suggest FreeBSD command - sysctl kern.geom.debugflags=0x10. I haven't tried it yet, should that helps.

https://forums.freenas.org/index.php?threads/cannot-create-volume-on-freenas-9-10-9-3.43857/

Thanks, S
 
wblock

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
No, do not use that sysctl. It means "let me erase disks that are in use".

dd should not be necessary, the wipe disk function should be enough.
 
S

SubX

Explorer
Joined
Sep 15, 2017
Messages
56
wblock said:
No, do not use that sysctl. It means "let me erase disks that are in use".

dd should not be necessary, the wipe disk function should be enough.
Click to expand...

The issue is that after I wiped those two drives (ada0 & ada1), gone through all the steps to create new vol, there is no new volume under storage. Go to volume manager, those 2 drives are still available for new volume. How to fix that?

Thanks,
S
 
wblock

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Are there any entries in the log files about this? Like in /var/log/messages?
 
wblock

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
I just tested this on 11.1-U1:

Select Volume Manager.
Enter tank as the volume name. (What is your volume name? Does it have special characters?)
Selected two disks and Mirror.
Click Add Volume.

This worked.
 
S

SubX

Explorer
Joined
Sep 15, 2017
Messages
56
Thanks. I dd ada0 last night and just start dd ada1 just now. Should I drop the dd and try your method about or should I wait until the dd is done (I don't know how long does it take, it won't give me a clue until the putty ssh finish itself).

I use iSCSI-110-4TR1, iSCSI4TR1 for the volume name. I have other volume similar to those two which works fine with no problem. Let me check the log file.

Thanks, S
 
S

SubX

Explorer
Joined
Sep 15, 2017
Messages
56
Below please find the log file ouput (only copy and paste those related to the volume creation per time stamp).
It seems that ada0 & ada1 has invalid argument and the operation is not permitted. This might lead to unsuccessful volume creation here.
Any idea?
Thanks, S
Code:
Feb 19 20:37:04 freenas ctld[2087]: exiting on signal						   
Feb 19 20:37:04 freenas notifier: Stopping ctld.								
Feb 19 20:37:04 freenas notifier: Waiting for PIDS: 2087.					   
Feb 19 20:37:04 freenas notifier: geli: No such device: /dev/ada0p1.			
Feb 19 20:37:04 freenas notifier: geli: No such device: /dev/ada1p1.			
Feb 19 20:37:04 freenas GEOM_ELI: Device ada0p1.eli destroyed.				 
Feb 19 20:37:04 freenas GEOM_ELI: Detached ada0p1.eli on last close.			
Feb 19 20:37:04 freenas GEOM_ELI: Device ada1p1.eli destroyed.				 
Feb 19 20:37:04 freenas GEOM_ELI: Detached ada1p1.eli on last close.			
Feb 19 20:37:04 freenas syslog-ng[4405]: syslog-ng shutting down; version='3.6.4
Feb 19 20:37:06 freenas kernel: pid 4280 (zfsd), uid 0: exited on signal 11 (cor
e dumped)																	   
Feb 19 20:37:06 freenas notifier: Starting syslog_ng.						   
Feb 19 20:37:09 freenas notifier: Mounting late file systems:.				 
Feb 19 20:37:09 freenas notifier: Stopping collectd.							
Feb 19 20:37:09 freenas notifier: Waiting for PIDS: 3453.					   
Feb 19 20:37:09 freenas notifier: Starting collectd.							
Feb 19 20:37:10 freenas ctld[56305]: no LUNs defined for target "iqn.2005-10.org
.freenas.ctl:target-4tr1"													   
Feb 19 20:37:10 freenas notifier: Starting ctld.								
Feb 19 20:37:10 freenas notifier: ctld: no LUNs defined for target "iqn.2005-10.
org.freenas.ctl:target-4tr1"													
Feb 19 20:37:47 freenas notifier: swapoff: /dev/ada0p1.eli: No such file or dire
ctory																		   
Feb 19 20:37:47 freenas notifier: geli: No such device: /dev/ada0p1.			
Feb 19 20:37:48 freenas notifier: ada0 destroyed								
Feb 19 20:37:48 freenas notifier: ada0 created								 
Feb 19 20:37:48 freenas notifier: ada0 destroyed								
Feb 19 20:57:27 freenas notifier: swapoff: /dev/ada1p1.eli: No such file or dire
ctory																		   
Feb 19 20:57:27 freenas notifier: geli: No such device: /dev/ada1p1.			
Feb 19 20:57:28 freenas notifier: ada1 destroyed
Feb 19 21:13:01 freenas notifier: gpart: arg0 'ada1': Invalid argument		 
Feb 19 21:13:01 freenas notifier: gpart: geom 'ada1': Operation not permitted   
Feb 19 21:13:01 freenas notifier: gpart: arg0 'ada1': Invalid argument		 
Feb 19 21:35:40 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb
in/dmidecode -s system-product-name											 
Feb 19 21:35:40 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb
in/dmidecode -s baseboard-product-name										 
Feb 19 21:40:27 freenas notifier: swapoff: removing /dev/ada2p1.eli as swap devi
ce																			 
Feb 19 21:40:27 freenas notifier: swapoff: removing /dev/ada3p1.eli as swap devi
ce																			 
Feb 19 21:40:27 freenas GEOM_ELI: Device ada2p1.eli destroyed.				 
Feb 19 21:40:27 freenas GEOM_ELI: Detached ada2p1.eli on last close.			
Feb 19 21:40:27 freenas GEOM_ELI: Device ada3p1.eli destroyed.				 
Feb 19 21:40:27 freenas GEOM_ELI: Detached ada3p1.eli on last close.			
Feb 19 21:40:28 freenas notifier: 32+0 records in							   
Feb 19 21:40:28 freenas notifier: 32+0 records out							 
Feb 19 21:40:28 freenas notifier: 33554432 bytes transferred in 0.681548 secs (4
9232668 bytes/sec)															 
Feb 19 21:40:28 freenas notifier: dd: /dev/ada0: short write on character device
Feb 19 21:40:28 freenas notifier: dd: /dev/ada0: end of device
Feb 19 21:40:28 freenas notifier: 33+0 records in							   
Feb 19 21:40:28 freenas notifier: 32+1 records out							 
Feb 19 21:40:28 freenas notifier: 34430976 bytes transferred in 0.633562 secs (5
4345090 bytes/sec)															 
Feb 19 21:40:28 freenas manage.py: [middleware.exceptions:37] [MiddlewareError:
Unable to GPT format the disk "ada0"]										   
Feb 19 21:40:29 freenas manage.py: [rollbar:1265] Got unexpected status code fro
m Rollbar api: 403															 
Response:																	   
{																			   
  "err": 1,																	 
  "message": "project is not enabled"										   
}																			   
Feb 19 21:40:29 freenas manage.py: [rollbar:1097] Exception while posting item A
piError(u'project is not enabled',)											 
Traceback (most recent call last):											 
  File "/usr/local/lib/python2.7/site-packages/rollbar/__init__.py", line 1095,
in _send_payload																
	_post_api('item/', payload, access_token=access_token)					 
  File "/usr/local/lib/python2.7/site-packages/rollbar/__init__.py", line 1138,
in _post_api																	
	return _parse_response(path, SETTINGS['access_token'], payload, resp)	   
  File "/usr/local/lib/python2.7/site-packages/rollbar/__init__.py", line 1274,
in _parse_response															 
	raise ApiError(json_data.get('message') or 'Unknown error')				 
ApiError: project is not enabled												
Feb 19 21:44:09 freenas notifier: gpart: arg0 'ada0': Invalid argument		 
Feb 19 21:44:09 freenas notifier: gpart: geom 'ada0': Operation not permitted   
Feb 19 21:44:09 freenas notifier: gpart: arg0 'ada0': Invalid argument		 
Feb 19 21:44:22 freenas notifier: gpart: arg0 'ada1': Invalid argument		 
Feb 19 21:44:22 freenas notifier: gpart: geom 'ada1': Operation not permitted   
Feb 19 21:44:22 freenas notifier: gpart: arg0 'ada1': Invalid argument		 
Feb 19 21:46:11 freenas notifier: swapoff: /dev/ada2p1.eli: No such file or dire
ctory																		   
Feb 19 21:46:11 freenas notifier: swapoff: /dev/ada3p1.eli: No such file or dire
ctory																		   
Feb 19 21:46:12 freenas notifier: 32+0 records in							   
Feb 19 21:46:12 freenas notifier: 32+0 records out							 
Feb 19 21:46:12 freenas notifier: 33554432 bytes transferred in 0.609013 secs (5
5096406 bytes/sec)															 
Feb 19 21:46:12 freenas notifier: dd: /dev/ada0: short write on character device
Feb 19 21:46:12 freenas notifier: dd: /dev/ada0: end of device				 
Feb 19 21:46:12 freenas notifier: 33+0 records in							   
Feb 19 21:46:12 freenas notifier: 32+1 records out							 
Feb 19 21:46:12 freenas notifier: 34430976 bytes transferred in 0.634074 secs (5
4301197 bytes/sec)	 
   raise ApiError(json_data.get('message') or 'Unknown error')				 
ApiError: project is not enabled												
Feb 19 21:44:09 freenas notifier: gpart: arg0 'ada0': Invalid argument		 
Feb 19 21:44:09 freenas notifier: gpart: geom 'ada0': Operation not permitted   
Feb 19 21:44:09 freenas notifier: gpart: arg0 'ada0': Invalid argument		 
Feb 19 21:44:22 freenas notifier: gpart: arg0 'ada1': Invalid argument		 
Feb 19 21:44:22 freenas notifier: gpart: geom 'ada1': Operation not permitted   
Feb 19 21:44:22 freenas notifier: gpart: arg0 'ada1': Invalid argument		 
Feb 19 21:46:11 freenas notifier: swapoff: /dev/ada2p1.eli: No such file or dire
ctory																		   
Feb 19 21:46:11 freenas notifier: swapoff: /dev/ada3p1.eli: No such file or dire
ctory																		   
Feb 19 21:46:12 freenas notifier: 32+0 records in							   
Feb 19 21:46:12 freenas notifier: 32+0 records out							 
Feb 19 21:46:12 freenas notifier: 33554432 bytes transferred in 0.609013 secs (5
5096406 bytes/sec)															 
Feb 19 21:46:12 freenas notifier: dd: /dev/ada0: short write on character device
Feb 19 21:46:12 freenas notifier: dd: /dev/ada0: end of device				 
Feb 19 21:46:12 freenas notifier: 33+0 records in							   
Feb 19 21:46:12 freenas notifier: 32+1 records out							 
Feb 19 21:46:12 freenas notifier: 34430976 bytes transferred in 0.634074 secs (5
4301197 bytes/sec)															 
Feb 19 21:46:12 freenas manage.py: [middleware.exceptions:37] [MiddlewareError:
   raise ApiError(json_data.get('message') or 'Unknown error')				 
ApiError: project is not enabled												
Feb 19 21:44:09 freenas notifier: gpart: arg0 'ada0': Invalid argument		 
Feb 19 21:44:09 freenas notifier: gpart: geom 'ada0': Operation not permitted   
Feb 19 21:44:09 freenas notifier: gpart: arg0 'ada0': Invalid argument		 
Feb 19 21:44:22 freenas notifier: gpart: arg0 'ada1': Invalid argument		 
Feb 19 21:44:22 freenas notifier: gpart: geom 'ada1': Operation not permitted   
Feb 19 21:44:22 freenas notifier: gpart: arg0 'ada1': Invalid argument		 
Feb 19 21:46:11 freenas notifier: swapoff: /dev/ada2p1.eli: No such file or dire
ctory																		   
Feb 19 21:46:11 freenas notifier: swapoff: /dev/ada3p1.eli: No such file or dire
ctory																		   
Feb 19 21:46:12 freenas notifier: 32+0 records in							   
Feb 19 21:46:12 freenas notifier: 32+0 records out							 
Feb 19 21:46:12 freenas notifier: 33554432 bytes transferred in 0.609013 secs (5
5096406 bytes/sec)															 
Feb 19 21:46:12 freenas notifier: dd: /dev/ada0: short write on character device
Feb 19 21:46:12 freenas notifier: dd: /dev/ada0: end of device				 
Feb 19 21:46:12 freenas notifier: 33+0 records in							   
Feb 19 21:46:12 freenas notifier: 32+1 records out							 
Feb 19 21:46:12 freenas notifier: 34430976 bytes transferred in 0.634074 secs (5
4301197 bytes/sec)															 
Feb 19 21:46:12 freenas manage.py: [middleware.exceptions:37] [MiddlewareError:
 
S

SubX

Explorer
Joined
Sep 15, 2017
Messages
56
After DD both ada0 & ada1, the vol creation works fine. Thanks, S
 
leenux_tux

leenux_tux

Patron
Joined
Sep 3, 2011
Messages
238
SubX said:
Background
  • FreeNAS 9.10.2-u6
  • two drives (4T) with data just wiped the data, detached all 2 drives
  • create new volume with those 2 drives, select mirror, click add volume button
  • After above, the volume didn't show up as expected. Repeat wiping data and then re-create volume, same issue.
How to fix that issue and create new volume from 2 wiped drives? Please help and thanks in advanced.

S
Click to expand...
When you create the pool via the GUI have you tried doing a zpool status from the command line ?

Sent from my A0001 using Tapatalk
 
Status
Not open for further replies.

Similar threads

TonyToews
  • Locked
Creating a volume doesn't appear to work. Probably me but ...
Replies
1
Views
2K
TonyToews
TonyToews
n9nu
  • Locked
REQ: Help on the 'spare' option located in 'Create a new volume'
Replies
2
Views
1K
Bohs Hansen
B
elangley
  • Locked
SOLVED Pool online but not showing in Storage/Volumes
Replies
2
Views
2K
Chris Moore
Chris Moore
T
  • Locked
"Force 4096 bytes sector size" Weird Behaivor
Replies
3
Views
3K
bollar
B
T
  • Locked
"Create A New Volume" IS the creation of a new zPool, Right?
Replies
2
Views
1K
TDPsGM
T
Top