The volume ROOT state is UNKNOWN

Status
Not open for further replies.
P

P33444

Cadet
Joined
Nov 4, 2018
Messages
6
Hello everyone,
Screen Shot 2018-11-18 at 7.37.43 PM.png

My system has a 8x10Tb in RAIDZ, 7 directly attached to motherboard and one to expansion card.

Make story short, I have inadvertently switched cables between some of the HDs and getting the: The volume "ROOT" state is UNKNOWN error.

Is there any way, outside trial and error to fix this?

Thank you for help,
Petr


Nov 18 19:17:03 freenas kernel: re0: link state changed to DOWN
Nov 18 19:17:03 freenas kernel: re0: link state changed to DOWN
Nov 18 19:17:03 freenas kernel: re0: link state changed to UP
Nov 18 19:17:03 freenas kernel: re0: link state changed to UP
Nov 18 19:17:04 freenas ntpd[2225]: ntpd 4.2.8p10-a (1): Starting
Nov 18 19:17:14 freenas root: /etc/rc: WARNING: failed precmd routine for minio
Nov 18 19:28:23 freenas GEOM_ELI: Device gptid/563b1c79-cce4-11e8-8936-0024219c327c.eli destroyed.
Nov 18 19:28:37 freenas GEOM_ELI: Device gptid/532c67ec-cce4-11e8-8936-0024219c327c.eli destroyed.
Nov 18 19:28:37 freenas GEOM_ELI: Device gptid/53f3775c-cce4-11e8-8936-0024219c327c.eli destroyed.
Nov 18 19:28:37 freenas GEOM_ELI: Device gptid/54ae6569-cce4-11e8-8936-0024219c327c.eli destroyed.
Nov 18 19:28:37 freenas GEOM_ELI: Device gptid/557470ca-cce4-11e8-8936-0024219c327c.eli destroyed.
Nov 18 19:28:37 freenas GEOM_ELI: Device gptid/570e06b8-cce4-11e8-8936-0024219c327c.eli destroyed.
Nov 18 19:31:03 freenas GEOM_ELI: Device gptid/532c67ec-cce4-11e8-8936-0024219c327c.eli created.
Nov 18 19:31:03 freenas GEOM_ELI: Encryption: AES-XTS 256
Nov 18 19:31:03 freenas GEOM_ELI: Crypto: software
Nov 18 19:31:03 freenas GEOM_ELI: Device gptid/53f3775c-cce4-11e8-8936-0024219c327c.eli created.
Nov 18 19:31:03 freenas GEOM_ELI: Encryption: AES-XTS 256
Nov 18 19:31:03 freenas GEOM_ELI: Crypto: software
Nov 18 19:31:03 freenas GEOM_ELI: Device gptid/54ae6569-cce4-11e8-8936-0024219c327c.eli created.
Nov 18 19:31:03 freenas GEOM_ELI: Encryption: AES-XTS 256
Nov 18 19:31:03 freenas GEOM_ELI: Crypto: software
Nov 18 19:31:03 freenas GEOM_ELI: Device gptid/557470ca-cce4-11e8-8936-0024219c327c.eli created.
Nov 18 19:31:03 freenas GEOM_ELI: Encryption: AES-XTS 256
Nov 18 19:31:03 freenas GEOM_ELI: Crypto: software
Nov 18 19:31:03 freenas GEOM_ELI: Device gptid/563b1c79-cce4-11e8-8936-0024219c327c.eli created.
Nov 18 19:31:03 freenas GEOM_ELI: Encryption: AES-XTS 256
Nov 18 19:31:03 freenas GEOM_ELI: Crypto: software
Nov 18 19:31:03 freenas GEOM_ELI: Device gptid/570e06b8-cce4-11e8-8936-0024219c327c.eli created.
Nov 18 19:31:03 freenas GEOM_ELI: Encryption: AES-XTS 256
Nov 18 19:31:03 freenas GEOM_ELI: Crypto: software
Nov 18 19:31:20 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=6101513576394797243
Nov 18 19:31:35 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=6264427186477707529
Nov 18 19:31:35 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=13357247756435181852
Nov 18 19:31:49 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=7129007276595544499
Nov 18 19:31:49 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=16763856345661737768
Nov 18 19:31:49 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=11672369870299984770
Nov 18 19:32:04 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=4865005178264087716
Nov 18 19:32:04 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=5440176513673927910
Nov 18 19:32:05 freenas uwsgi: [middleware.notifier:2527] Importing ROOT [16805045382313555006] failed with: cannot import 'ROOT': no such pool or dataset
 
Chris Moore

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
Strange error. Did you name your storage pool "ROOT"? Please share with us the output of zpool status delivered within code tags:
upload_2018-11-18_19-7-25.png

Should look something like this:
Code:
  pool: Emily
 state: ONLINE
  scan: scrub repaired 0 in 0 days 05:23:05 with 0 errors on Tue Nov 13 05:23:07 2018
config:

		NAME											STATE	 READ WRITE CKSUM
		Emily										   ONLINE	   0	 0	 0
		  raidz2-0									  ONLINE	   0	 0	 0
			gptid/af7c42c6-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/b07bc723-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/b1893397-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/b2bfc678-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/b3c1849e-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/b4d16ad2-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE	   0	 0	 0
		  raidz2-1									  ONLINE	   0	 0	 0
			gptid/bc1e50e5-c1fa-11e8-87f0-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/a03dd690-c1fb-11e8-87f0-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/a6ed2ed5-c240-11e8-87f0-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/b9de3232-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/baf4aba8-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/bbf26621-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE	   0	 0	 0
		logs
		  gptid/ae487c50-bec3-11e8-b1c8-0cc47a9cd5a4	ONLINE	   0	 0	 0
		cache
		  gptid/ae52d59d-bec3-11e8-b1c8-0cc47a9cd5a4	ONLINE	   0	 0	 0

errors: No known data errors
 
Chris Moore

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
PS. Simply changing what port a drive is connected to should not be a problem. It would only be a problem if the drive was not detected because it has a bad connection or is not powered on.
 
P

P33444

Cadet
Joined
Nov 4, 2018
Messages
6
Yes I did named the root drive ROOT, unimaginative, I know :)

The Bios does detect all the drives, and I can see them in FreeNAS drive list. You can see them behind the error message.

What preceded is that: I got new sata cables and when started the system one of them was bad, so the system was telling me that one drive is failing, but there is enough data to recover.

I did fiddle with cables, before realizing that one of the drives is not being seen by the system, went back, found the fault and reconnected drive, after turning system off.

Now the drive show LOCKED status, there is no option to Unlock the drive (yes I did downloaded the key):

Screen Shot 2018-11-18 at 10.29.18 PM.png


When I look at Status of Volume I get this:


Request Method: GET
Request URL: http://192.168.1.6/admin/storage/volumestatus/datagrid/?id=1&dojo.preventCache=1542598168118
Software Version: FreeNAS-11.1-U6 (caffd76fa)
Exception Type: IndexError
Exception Value:
list index out of range
Exception Location: ./freenasUI/middleware/zfs.py in parse_status, line 761
Server time: Sun, 18 Nov 2018 22:29:28 -0500

Environment:

Software Version: FreeNAS-11.1-U6 (caffd76fa)
Request Method: GET
Request URL: http://192.168.1.6/admin/storage/volumestatus/datagrid/?id=1&dojo.preventCache=1542598168118


Traceback:
File "/usr/local/lib/python3.6/site-packages/django/core/handlers/exception.py" in inner
42. response = get_response(request)
File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py" in _legacy_get_response
249. response = self._get_response(request)
File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py" in _get_response
178. response = middleware_method(request, callback, callback_args, callback_kwargs)
File "./freenasUI/freeadmin/middleware.py" in process_view
162. return login_required(view_func)(request, *view_args, **view_kwargs)
File "/usr/local/lib/python3.6/site-packages/django/contrib/auth/decorators.py" in _wrapped_view
23. return view_func(request, *args, **kwargs)
File "./freenasUI/freeadmin/options.py" in wrapper
210. return self._admin.admin_view(view)(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/django/utils/decorators.py" in _wrapped_view
149. response = view_func(request, *args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/django/views/decorators/cache.py" in _wrapped_view_func
57. response = view_func(request, *args, **kwargs)
File "./freenasUI/freeadmin/site.py" in inner
142. return view(request, *args, **kwargs)
File "./freenasUI/freeadmin/options.py" in datagrid
961. context.update(self.get_datagrid_context(request=request))
File "./freenasUI/storage/admin.py" in get_datagrid_context
415. pool = notifier().zpool_parse(volume.vol_name)
File "./freenasUI/middleware/notifier.py" in zpool_parse
3386. parse = zfs.parse_status(name, doc, res)
File "./freenasUI/middleware/zfs.py" in parse_status
761. status = data.split('config:')[1]

Exception Type: IndexError at /admin/storage/volumestatus/datagrid/
Exception Value: list index out of range


Request information
GET
Variable Value
id '1'
dojo.preventCache '1542598168118'
POST
No POST data

FILES
No FILES data

COOKIES
Variable Value
fntreeSaveStateCookie 'root%2Croot%2F1%2F5%2Croot%2F158'
csrftoken '********'
sessionid 'kan364s36nrfpypidvcwiqst10mp2ooa'
 
P

P33444

Cadet
Joined
Nov 4, 2018
Messages
6
...the zpool status returns:



[root@freenas ~]# zpool status
pool: External1Gb
state: ONLINE
scan: none requested
config:

NAME STATE READ WRITE CKSUM
External1Gb ONLINE 0 0 0
gptid/46f59ba1-ce25-11e8-a6c6-0024219c327c ONLINE 0 0 0

errors: No known data errors

pool: freenas-boot
state: ONLINE
scan: scrub repaired 0 in 0 days 00:01:08 with 0 errors on Sun Nov 18 03:46:08 2018
config:

NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
da6p2 ONLINE 0 0 0
da5p2 ONLINE 0 0 0

errors: No known data errors
[root@freenas ~]# c


=not seeing the zvol?!
 
Chris Moore

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
You have given me things I did not ask for and the thing I asked for in the wrong format. Attention to detail.

What you have used is CMD tags.
upload_2018-11-18_22-0-30.png

They should be used to surround single items like zpool status to set them apart from the rest of the text in a line.

I asked for CODE tags.
upload_2018-11-18_22-0-54.png

Which would be used to surround a longer listing such as this:
Code:
  pool: Irene
 state: ONLINE
  scan: scrub repaired 0 in 0 days 02:56:12 with 0 errors on Sat Oct 13 18:13:20 2018
config:

		NAME											STATE	 READ WRITE CKSUM
		Irene										   ONLINE	   0	 0	 0
		  raidz2-0									  ONLINE	   0	 0	 0
			gptid/8710385b-becf-11e8-b1c8-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/87e94156-becf-11e8-b1c8-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/88db19ad-becf-11e8-b1c8-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/89addd3b-becf-11e8-b1c8-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/8a865453-becf-11e8-b1c8-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/8b66b1ef-becf-11e8-b1c8-0cc47a9cd5a4  ONLINE	   0	 0	 0
		  raidz2-1									  ONLINE	   0	 0	 0
			gptid/8c69bc72-becf-11e8-b1c8-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/8d48655d-becf-11e8-b1c8-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/8e2b6d1f-becf-11e8-b1c8-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/8efea929-becf-11e8-b1c8-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/8fd4d25c-becf-11e8-b1c8-0cc47a9cd5a4  ONLINE	   0	 0	 0
			gptid/90c2759a-becf-11e8-b1c8-0cc47a9cd5a4  ONLINE	   0	 0	 0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:08:34 with 0 errors on Sun Nov 11 03:53:35 2018
config:

		NAME											STATE	 READ WRITE CKSUM
		freenas-boot									ONLINE	   0	 0	 0
		  mirror-0									  ONLINE	   0	 0	 0
			gptid/f659fd6d-4b12-11e6-a97c-002590aecc79  ONLINE	   0	 0	 0
			gptid/f6a61d33-4b12-11e6-a97c-002590aecc79  ONLINE	   0	 0	 0

errors: No known data errors
root@Emily-NAS:~ #

Please use them properly.
 
Chris Moore

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
P33444 said:
Yes I did named the root drive ROOT, unimaginative, I know
Click to expand...
The storage pool is not the ROOT drive and naming it that way can create problems.
P33444 said:
Now the drive show LOCKED status, there is no option to Unlock the drive (yes I did downloaded the key):
Click to expand...
You have an encrypted pool? That is something you should have been especially careful about. You may be screwed. I hope you have a backup.
 
Chris Moore

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
When you put a listing in CODE tags, it makes them easier to read.
Code:
Nov 18 19:17:03 freenas kernel: re0: link state changed to DOWN
Nov 18 19:17:03 freenas kernel: re0: link state changed to DOWN
Nov 18 19:17:03 freenas kernel: re0: link state changed to UP
Nov 18 19:17:03 freenas kernel: re0: link state changed to UP
Nov 18 19:17:04 freenas ntpd[2225]: ntpd 4.2.8p10-a (1): Starting
Nov 18 19:17:14 freenas root: /etc/rc: WARNING: failed precmd routine for minio
Nov 18 19:28:23 freenas GEOM_ELI: Device gptid/563b1c79-cce4-11e8-8936-0024219c327c.eli destroyed.
Nov 18 19:28:37 freenas GEOM_ELI: Device gptid/532c67ec-cce4-11e8-8936-0024219c327c.eli destroyed.
Nov 18 19:28:37 freenas GEOM_ELI: Device gptid/53f3775c-cce4-11e8-8936-0024219c327c.eli destroyed.
Nov 18 19:28:37 freenas GEOM_ELI: Device gptid/54ae6569-cce4-11e8-8936-0024219c327c.eli destroyed.
Nov 18 19:28:37 freenas GEOM_ELI: Device gptid/557470ca-cce4-11e8-8936-0024219c327c.eli destroyed.
Nov 18 19:28:37 freenas GEOM_ELI: Device gptid/570e06b8-cce4-11e8-8936-0024219c327c.eli destroyed.
Nov 18 19:31:03 freenas GEOM_ELI: Device gptid/532c67ec-cce4-11e8-8936-0024219c327c.eli created.
Nov 18 19:31:03 freenas GEOM_ELI: Encryption: AES-XTS 256
Nov 18 19:31:03 freenas GEOM_ELI:	 Crypto: software
Nov 18 19:31:03 freenas GEOM_ELI: Device gptid/53f3775c-cce4-11e8-8936-0024219c327c.eli created.
Nov 18 19:31:03 freenas GEOM_ELI: Encryption: AES-XTS 256
Nov 18 19:31:03 freenas GEOM_ELI:	 Crypto: software
Nov 18 19:31:03 freenas GEOM_ELI: Device gptid/54ae6569-cce4-11e8-8936-0024219c327c.eli created.
Nov 18 19:31:03 freenas GEOM_ELI: Encryption: AES-XTS 256
Nov 18 19:31:03 freenas GEOM_ELI:	 Crypto: software
Nov 18 19:31:03 freenas GEOM_ELI: Device gptid/557470ca-cce4-11e8-8936-0024219c327c.eli created.
Nov 18 19:31:03 freenas GEOM_ELI: Encryption: AES-XTS 256
Nov 18 19:31:03 freenas GEOM_ELI:	 Crypto: software
Nov 18 19:31:03 freenas GEOM_ELI: Device gptid/563b1c79-cce4-11e8-8936-0024219c327c.eli created.
Nov 18 19:31:03 freenas GEOM_ELI: Encryption: AES-XTS 256
Nov 18 19:31:03 freenas GEOM_ELI:	 Crypto: software
Nov 18 19:31:03 freenas GEOM_ELI: Device gptid/570e06b8-cce4-11e8-8936-0024219c327c.eli created.
Nov 18 19:31:03 freenas GEOM_ELI: Encryption: AES-XTS 256
Nov 18 19:31:03 freenas GEOM_ELI:	 Crypto: software
Nov 18 19:31:20 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=6101513576394797243
Nov 18 19:31:35 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=6264427186477707529
Nov 18 19:31:35 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=13357247756435181852
Nov 18 19:31:49 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=7129007276595544499
Nov 18 19:31:49 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=16763856345661737768
Nov 18 19:31:49 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=11672369870299984770
Nov 18 19:32:04 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=4865005178264087716
Nov 18 19:32:04 freenas ZFS: vdev state changed, pool_guid=16805045382313555006 vdev_guid=5440176513673927910
Nov 18 19:32:05 freenas uwsgi: [middleware.notifier:2527] Importing ROOT [16805045382313555006] failed with: cannot import 'ROOT': no such pool or dataset
 
P

P33444

Cadet
Joined
Nov 4, 2018
Messages
6
I am sorry, not to understand. What it is that would help analyze the problem? Even better what it is that would prevent it next time?

Yes, I do have a back up.
 
P

P33444

Cadet
Joined
Nov 4, 2018
Messages
6
So I gave up, and decided to start over, but now I have another problem creating trouble creating new volume.

Code:
Environment:

Software Version: FreeNAS-11.1-U6 (caffd76fa)
Request Method: POST
Request URL: http://192.168.1.6/storage/disks/wipe/ada0/


Traceback:
File "/usr/local/lib/python3.6/site-packages/django/core/handlers/exception.py" in inner
  42.			 response = get_response(request)
File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py" in _legacy_get_response
  249.			 response = self._get_response(request)
File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py" in _get_response
  178.			 response = middleware_method(request, callback, callback_args, callback_kwargs)
File "./freenasUI/freeadmin/middleware.py" in process_view
  162.		 return login_required(view_func)(request, *view_args, **view_kwargs)
File "/usr/local/lib/python3.6/site-packages/django/contrib/auth/decorators.py" in _wrapped_view
  23.				 return view_func(request, *args, **kwargs)
File "./freenasUI/storage/views.py" in disk_wipe
  864.				 notifier().disk_wipe(devname, form.cleaned_data['method'])
File "./freenasUI/middleware/notifier.py" in disk_wipe
  3610.				 self._do_disk_wipe_quick(part)
File "./freenasUI/middleware/notifier.py" in _do_disk_wipe_quick
  3587.				 "Failed to wipe %s: %s" % (devname, err)

Exception Type: MiddlewareError at /storage/disks/wipe/ada0/
Exception Value: [MiddlewareError: Failed to wipe ada0p1: dd: /dev/ada0p1: Operation not permitted
]
 
Status
Not open for further replies.

Important Announcement for the TrueNAS Community.

The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums.

Related topics on forums.truenas.com for thread: "The volume ROOT state is UNKNOWN"

Similar threads

cstanley
  • Locked
Unlock Pool Fails on First Attempt
Replies
1
Views
703
dlavigne
D
T
  • Locked
decryption problem after upgrade
Replies
7
Views
1K
tsf0x13
T
oRAirwolf
SOLVED I can unlock an encrypted pool with my passphrase, but not with geli.key
Replies
9
Views
4K
EsTaF
EsTaF
V
  • Locked
SOLVED Unusual Authentication Activity in Security Logs
Replies
13
Views
6K
Redcoat
Redcoat
P
SWAP partition encryption is AES-XTS 128
Replies
4
Views
1K
Phil1295
P
Top