Need help with Error getting available space

Status
Not open for further replies.

3L3ET

Dabbler
Joined
May 29, 2018
Messages
11
Came in and Volume1 is stating, Error getting available space!!!

What does this error mean?

Let me add some detail.

Under volume 1 it added .system, .system/syslog , .system/rrd-ad , system/cores , /systemconfigs. with an error getting space.
 
Last edited:

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504

3L3ET

Dabbler
Joined
May 29, 2018
Messages
11
I'm running FreeNAS 9.2.0
I have one volume named volume1 with 8 disks.
Under volume1 in storage a .system directory appeared with (Used: Error) (Available: Error getting available space) (Size: Error getting total space).

It appears to be synthetic in nature because all my other directories and shares are working. I have no disk issues. I've restarted the NAS and it still appears under volume1.

Any ideas on what this is?
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
Any ideas on what this is?
You didn't answer @danb35 's question... Hardware details. Please review the Forum Rules:
https://forums.freenas.org/index.php?threads/updated-forum-rules-8-3-16.45124/

Have you made any changes to your system recently?

Why are you still stuck on version 9.2?

Please share with us the output of zpool status which should look something like:
Code:
zpool status.

pool: volume1																													
state: ONLINE																													
  scan: resilvered 948G in 9h17m with 0 errors on Fri Feb 23 17:31:47 2018														
config:																															
																																  
	   NAME											STATE	 READ WRITE CKSUM												
	   volume1										 ONLINE	   0	 0	 0												
		 raidz2-0									  ONLINE	   0	 0	 0												
		   gptid/ee5274a9-725d-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
		   gptid/eeb562af-725d-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
		   gptid/ef232a0b-725d-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
		   gptid/ef8e7c61-725d-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
		   gptid/e1f55661-18a3-11e8-972a-bc5ff4c9a41d  ONLINE	   0	 0	 0												
		   gptid/f05c82ae-725d-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
	   logs																														
		 mirror-1									  ONLINE	   0	 0	 0												
		   gptid/128fa8cc-725e-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
		   gptid/16ef5cd0-725e-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
																																  
errors: No known data errors	
 
Last edited:

3L3ET

Dabbler
Joined
May 29, 2018
Messages
11
I inherited this system. I've attempted to upgrade but had to revert because I could not get it to sync with my domain controller.

zpool status.
Code:
pool: volume1																													
 state: ONLINE																													
  scan: resilvered 948G in 9h17m with 0 errors on Fri Feb 23 17:31:47 2018														
config:																															
																																  
	   NAME											STATE	 READ WRITE CKSUM												
	   volume1										 ONLINE	   0	 0	 0												
		 raidz2-0									  ONLINE	   0	 0	 0												
		   gptid/ee5274a9-725d-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
		   gptid/eeb562af-725d-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
		   gptid/ef232a0b-725d-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
		   gptid/ef8e7c61-725d-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
		   gptid/e1f55661-18a3-11e8-972a-bc5ff4c9a41d  ONLINE	   0	 0	 0												
		   gptid/f05c82ae-725d-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
	   logs																														
		 mirror-1									  ONLINE	   0	 0	 0												
		   gptid/128fa8cc-725e-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
		   gptid/16ef5cd0-725e-11e3-b06d-bc5ff4c9a41d  ONLINE	   0	 0	 0												
																																  
errors: No known data errors

As far as hardware its a homemade box with Intel processor M1A1 motherboard, and ironwolf HDD.
 
Last edited by a moderator:

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
Here is a screenshot
That is not what it is supposed to look like at all... However, it would be better to upload your photo directly into the forum, so it is here years from now when someone else looks at this to try and answer their question.
Your's looks like this:

nas.png


When it should look more like this:

storage-volumes.png


It might be helpful if you gave (in code tags) the output of the command mount so we can see where, or if, your pool is mounted.
It should look something like this:
Code:
root@freenas:~ # mount
freenas-boot/ROOT/11.1-U5 on / (zfs, local, noatime, nfsv4acls)
devfs on /dev (devfs, local, multilabel)
tmpfs on /etc (tmpfs, local)
tmpfs on /mnt (tmpfs, local)
tmpfs on /var (tmpfs, local)
freenas-boot/grub on /boot/grub (zfs, local, noatime, nfsv4acls)
fdescfs on /dev/fd (fdescfs)
megavolume on /mnt/megavolume (zfs, local, nfsv4acls)
megavolume/dataset1 on /mnt/megavolume/dataset1 (zfs, local, nfsv4acls)
megavolume/.system on /var/db/system (zfs, local, nfsv4acls)
megavolume/.system/cores on /var/db/system/cores (zfs, local, nfsv4acls)
megavolume/.system/samba4 on /var/db/system/samba4 (zfs, local, nfsv4acls)
megavolume/.system/syslog-839d4bf50898424ab2b76c72b7c93def on /var/db/system/syslog-839d4bf50898424ab2b76c72b7c93def (zfs, local, nfsv4acls)
megavolume/.system/rrd-839d4bf50898424ab2b76c72b7c93def on /var/db/system/rrd-839d4bf50898424ab2b76c72b7c93def (zfs, local, nfsv4acls)
megavolume/.system/configs-839d4bf50898424ab2b76c72b7c93def on /var/db/system/configs-839d4bf50898424ab2b76c72b7c93def (zfs, local, nfsv4acls)
tmpfs on /var/db/collectd/rrd (tmpfs, local)
 
Last edited:

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
Came in and Volume1 is stating, Error getting available space!!!
Are your shares offline also, because it looks like you might have a problem with your system configuration.
While you are connected by SSH and getting the output of mount, you probably aught to get a list from the command zfs list so we can see if there is anything else hanging out there.
Should look something like this:
Code:
root@freenas:/mnt/megavolume/dataset1 # zfs list
NAME														  USED  AVAIL  REFER  MOUNTPOINT
freenas-boot												 2.50G   213G	64K  none
freenas-boot/ROOT											2.48G   213G	29K  none
freenas-boot/ROOT/11.1-U4									 750K   213G   836M  /
freenas-boot/ROOT/11.1-U5									2.47G   213G   845M  /
freenas-boot/ROOT/Initial-Install							2.25M   213G   825M  legacy
freenas-boot/ROOT/Wizard-2018-03-08_11:05:13					1K   213G   835M  legacy
freenas-boot/ROOT/default									6.37M   213G   831M  legacy
freenas-boot/grub											7.02M   213G  7.02M  legacy
megavolume												   22.4T  47.9T   176K  /mnt/megavolume
megavolume/.system										   19.2M  47.9T  1.55M  legacy
megavolume/.system/configs-839d4bf50898424ab2b76c72b7c93def  16.0M  47.9T  16.0M  legacy
megavolume/.system/cores									  751K  47.9T   751K  legacy
megavolume/.system/rrd-839d4bf50898424ab2b76c72b7c93def	   176K  47.9T   176K  legacy
megavolume/.system/samba4									 559K  47.9T   559K  legacy
megavolume/.system/syslog-839d4bf50898424ab2b76c72b7c93def	176K  47.9T   176K  legacy
megavolume/dataset1										  22.4T  47.9T  22.4T  /mnt/megavolume/dataset1							

I inherited this system.
Have you been reading voraciously on the forum and through the documentation to get up to speed, so you can administer the storage?
I've attempted to upgrade but had to revert because I could not get it to sync with my domain controller.
Did the current problem happen later or as soon as you went back to the previous boot environment?

PS. Do you have snapshots setup?
 
Last edited:

3L3ET

Dabbler
Joined
May 29, 2018
Messages
11
When I attempted the upgrade I didn't touch this machine, I was going to stand up a new machine and do a migration. This happened much later.

Shares are not offline, they are functioning as needed .
Code:
[root@freenas ~]# mount																											
/dev/ufs/FreeNASs1a on / (ufs, local, read-only)																					
devfs on /dev (devfs, local, multilabel)																							
/dev/md0 on /etc (ufs, local)																									  
/dev/md1 on /mnt (ufs, local)																									  
/dev/md2 on /var (ufs, local)																									  
/dev/ufs/FreeNASs4 on /data (ufs, local, noatime, soft-updates)																	
volume1 on /mnt/volume1 (zfs, NFS exported, local, nfsv4acls)																	  
volume1/bsdset on /mnt/volume1/bsdset (zfs, NFS exported, local, nfsv4acls)														
volume1/VM_backup on /mnt/volume1/VM_backup (zfs, local, nfsv4acls)															  
volume1/document on /mnt/volume1/document (zfs, local, nfsv4acls)										  
volume1/bodyparts on /mnt/volume1/bodyparts (zfs, local, nfsv4acls)																		
volume1/cash on /mnt/volume1/cash (zfs, NFS exported, local, nfsv4acls)												
volume1/filemover on /mnt/volume1/filemover (zfs, NFS exported, local, nfsv4acls)															
volume1/shares on /mnt/volume1/shares (zfs, NFS exported, local, nfsv4acls)														
/dev/md3 on /var/tmp/.cache (ufs, local, soft-updates)







[root@freenas ~]# zfs list																										
NAME																	   USED  AVAIL  REFER  MOUNTPOINT										  
volume1																	 4.80T  5.85T   532G  /mnt/volume1										
volume1/.system														18.6M  5.85T   352K  legacy											  
volume1/.system/configs-ad40dcca3c864de290e96a9bf25a9d15   815K  5.85T   815K  legacy											  
volume1/.system/cores												12.0M  5.85T  12.0M  legacy											  
volume1/.system/rrd-ad40dcca3c864de290e96a9bf25a9d15	   272K  5.85T   272K  legacy											  
volume1/.system/samba4											 4.91M  5.85T  4.91M  legacy											  
volume1/.system/syslog-ad40dcca3c864de290e96a9bf25a9d15	272K  5.85T   272K  legacy											  
volume1/bsdset															1.47T  5.85T  1.05T  /mnt/volume1/bsdset								
volume1/VM_backup													 21.6G  5.85T  21.6G  /mnt/volume1/VM_backup							
volume1/document														792G  5.85T   787G  /mnt/volume1/document					
volume1/bodyparts													   304K  5.85T   288K  /mnt/volume1/bodyparts								  
volume1/cash																3.06G  5.85T   205M  /mnt/volume1/cash							
volume1/filemover														200G  5.85T   177G  /mnt/volume1/filemover									
volume1/shares															1.66T  5.85T  1.66T  /mnt/volume1/shares
 
Last edited by a moderator:

3L3ET

Dabbler
Joined
May 29, 2018
Messages
11
I do have snapshots setup but failing back to those is not an option do to the loss of today's DATA. I do have a nuclear option of restoring this NAS from a backup NAS, but I'd rather repair this one due to the other complications that could cause.
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080

3L3ET

Dabbler
Joined
May 29, 2018
Messages
11
No thats the whole story . . . . havn't made any config changes in over a month.
 

HoneyBadger

actually does care
Administrator
Moderator
iXsystems
Joined
Feb 6, 2014
Messages
5,112
As far as hardware its a homemade box with Intel processor M1A1 motherboard, and ironwolf HDD

The only "M1A1" I know of is the Springfield; as in the rifle.

From the rules:

Hardware information is extremely important when diagnosing problems. This includes:
  • motherboard make and model
  • CPU make and model
  • RAM quantity
  • hard drives, quantity, model numbers, and RAID configuration
  • hard disk controllers
  • network cards
Please provide this information so that we can see if there is a potential hardware incompatibility.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
The only "M1A1" I know of is the Springfield; as in the rifle.
Don't forget the Main Battle Tank.

Anyway, the pool looks fine. That doesn't mean much, though, because the last scrub was a resilver nearly six months ago! But it does look like the GUI simply crapped out, for whatever reason. The underlying data should be fine.
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
If you don't know what Hardware is in your server, it's time to shut it down and take it apart and figure it out, because that's the kind of thing you need to know to be able to support the server.
Also I think it's probably time to read the documentation.

Sent from my SAMSUNG-SGH-I537 using Tapatalk
 
Status
Not open for further replies.
Top