Error getting available space

[Zeke99]

FreeNAS running perfect 2 years and then yesterday suddenly I wasn't able to mount the volume anymore.
Nothing done with freenas, no upgrades or so.

Get the yellow flashing light with: Warning the volume Volume1 (ZFS) status is unknown.
When checking Volumes/View Volumes:

Code:

Volume1  0(Error)  Error getting available space  Error getting total space  -  -  UNKNOWN

When clicking on Change Permission I get this traceback:

Code:

Software Version: FreeNAS-9.2.1.5-RELEASE-x64 (80c1d35)
Request Method: GET
Request URL: http://192.168.2.142/storage/mountpoint/permission/mnt/Volume1/

Traceback:
File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
  107.  response = middleware_method(request, callback, callback_args, callback_kwargs)
File "/usr/local/www/freenasUI/../freenasUI/freeadmin/middleware.py" in process_view
  158.  return login_required(view_func)(request, *view_args, **view_kwargs)
File "/usr/local/lib/python2.7/site-packages/django/contrib/auth/decorators.py" in _wrapped_view
  22.  return view_func(request, *args, **kwargs)
File "/usr/local/www/freenasUI/../freenasUI/storage/views.py" in mp_permission
  546.  form = forms.MountPointAccessForm(initial={'path': path})
File "/usr/local/www/freenasUI/../freenasUI/storage/forms.py" in __init__
  1672.  user, group = notifier().mp_get_owner(path)
File "/usr/local/www/freenasUI/../freenasUI/middleware/notifier.py" in mp_get_owner
  2384.  raise OSError('Invalid mountpoint %s' % (path, ))

Exception Type: OSError at /storage/mountpoint/permission/mnt/Volume1/
Exception Value: Invalid mountpoint /mnt/Volume1

If I run dmesg | more in shell the last rows is:

Code:

Trying to mount root from ufs:/dev/ufs/FreeNASs1a [ro]
mountroot: waiting for device /dev/ufs/FreeNASs1a ...
da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
da0: <SanDisk Cruzer Blade 1.26> Removable Direct Access SCSI-5 device
da0: Serial number 4C5...
da0: 40.000MB/s transfers
da0: 3819MB
da0: quirks=0x2<NO_6_BYTE>
GEOM_RAID5: Module loaded, version 1.1.20130907.44 (rev 5c6d2a159411)
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)

If I reboot the computer the two 1000GB Seagate Barracuda HDD is visible in BIOS.

Is there something I can do to pinpoint what the problem is? Can I test the HDD from BSD in some way?

 

[nojohnny101]

please post your hardware per forum rules

please post the output (in code tags) for 'zpool status'

 

[SweetAndLow]

Also check your smart test results

Sent from my Nexus 5X using Tapatalk

 

[Zeke99]

Test add SMART but there is no disk to choose from.
Test zpool scrub Volume1 but the answer is cannot open Volume1 : no such pool.
Test to put the 2 hdds and the usb-memory with the OS in another computer with the same result.

Hdd: Seagate Barracuda 1000GB ST1000DM003 (x2)
First computer Fujitsu Esprimo P5730, motherboard Fujitsu D2811-A13 GS1, memory 6GB , cpu Intel Celeron E1200 ,hdd connected to onboard SATA
Second computer FujistuSiemens Celsius M460, motherboard D2608-A11 GS2, memory 4Gb, cpu Intel Core 2 duo Q8300, hdd connected to onboard SATA

 

[Mirfster]

Ugh...

• Neither of you systems meet the Minimum Hardware Requirements for FreeNAS
• Highly doubt you were running any SMART Tests at all, I would love to be proven wrong...
• Do you know what vDev(s) you *were* using for the Pool... Hopefully it was at least Mirrors, but I am highly doubting it. More than likely it was Two Single Drive vDevs and one drive died causing loss of Pool.
• Post the output of zpool history (In Code Tags)

In all honesty, I am not thinking that this is going to turn out well for you. At the very least, take some time to read vital information about running FreeNAS (In these Forums and there are links in my sig).

 

[SweetAndLow]

What mirfster meant to say is this is not going to turn it well for you.

Sent from my Nexus 5X using Tapatalk

 

[Mirfster]

What mirfster meant to say is this is not going to turn it well for you.

I am Mirfster and I approve this TL;DR message. :P

 

[Zeke99]

Zpool history answer no pools available.

Because I can't explain why this error happened and no one else have any answers I solve this by scrap the freenas both at home and at work. Instead I build a cluster with simple Ubuntu servers (which I'm much more familiar with) and program my own backup software. This will prevent a fried hdd to destroy all data and even if the house burn down I will have servers on other sites.

 

[Mirfster]

Zpool history answer no pools available.

Because I can't explain why this error happened and no one else have any answers I solve this by scrap the freenas both at home and at work. Instead I build a cluster with simple Ubuntu servers (which I'm much more familiar with) and program my own backup software. This will prevent a fried hdd to destroy all data and even if the house burn down I will have servers on other sites.

I did have an answer, actually an educated guess since you did not really provide much info at all:

More than likely it was Two Single Drive vDevs and one drive died causing loss of Pool.