Failed to create mountpoint

[Zurlox]

I upgraded FreeNAS from v9.2 to v9.3.

When attempting to import the original volume I receive an error:



In the system log it shows that it 'failed to create mountpoint'.

I have scoured the forum for similar issues but I have been unsuccessful so far.

The zpool status shows the volume as online:



The hardware is as follows:

HP Proliant Microserver N36L
10GB Kingston ECC RAM
FreeNAS is installed on a 16GB Sandisk Fit USB
Vault volume is across 5x3TB drives

Should I be performing a zpool scrum of the volume and retry the import process?

What is actually happening when the system is trying to import the volume?
What system resources are need for this process to happen?

Should I be expanding the FreeNAS install disk space from 16GB?

Any help would be greatly appreciated.

Thank you.

 

[dlavigne]

Is the volume not showing at all in Storage -> Volume Manager? Anything related in /var/log/messages?

 

[Zurlox]

The volume shows up in System -> Import Volume

Once I attempt the import and it fails it doesn't show up in the Volume Manager, nor does it show up in the Import Volume section

I would have no idea what to be looking for in the messages log file. I can attach it if it would help.

Thanks.

 

[dlavigne]

Yes, it would help to attach it (assuming you haven't figured this out yet).

 

[Zurlox]

I still have not found a solution to this issue.

I have uploaded the messages file from the boot drive.

I have also tried with dual 32GB USB flash drives with the same result.

Not sure where to go from here...

Thank you for your continued assistance.

 

[dlavigne]

Are you sure this is the correct file? it seems to be from a Linux system.

 

[Zurlox]

Oops

Perhaps this is the correct log file

Sorry

 

[Zurlox]

I have updated the system with 16GB of ECC ram and the boot drive is a 300GB mechanical. The results are the same.

Would my next step be to scrub the volume for errors?

 

[SweetAndLow]

Doing a scrub won't help anything. What happens if you put the old build on a usb stick and upload your configuration file. Does it work?

 

[Zurlox]

The ZFS pool has been updated and is no longer compatible with 9.2.

Every instance of config file backups seem to fail and destroy the freenas install, for whatever reason, even the 9.3 saved configs don't like to be uploaded and applied.

 

[SweetAndLow]

Why in earth would you update zfs when it doesn't even work!

If you do a fresh install and don't upload configuration file, what happens? Just go to storage->auto import in the GUI.

 

[Zurlox]

Who knows why I updated the ZFS pool... crazy idea in hindsight.

I have attached the output for update.failed which may provide useful.

I will try and install the original Freenas version which I got the config from and see if it will accept the config upload.

 

[SweetAndLow]

Since you upgraded the pool you have to use 9.3

Also there isn't anything in your logs. Just boot logs. What does zfs list, ls -l /mnt and zpool status show you?

 

[Zurlox]

Installing 9.2 and uploading the config successfully may allow me to fix and save the config to work with 9.3?

 

[SweetAndLow]

No

 

[Zurlox]

zfs list and ls -l /mnt output



Also zpool status

 

[rogerh]

Is the problem that the pool is completely full? As I understand it, 9.3 is more conservative and requires slightly more working space on a nearly full pool than did 9.2. That might be why it won't import properly. There are ways of deleting a (expendable) large file from the CLI to regain space for further file operations. I am not sure what would be a good search string for the forum search, but others may remember.

 

[cyberjock]

Is the problem that the pool is completely full? As I understand it, 9.3 is more conservative and requires slightly more working space on a nearly full pool than did 9.2. That might be why it won't import properly. There are ways of deleting a (expendable) large file from the CLI to regain space for further file operations. I am not sure what would be a good search string for the forum search, but others may remember.

That would be precisely why you are having problems. 0 bytes of free space is bad!

 

[Zurlox]

Ok thanks! Now at least I know what the problem is.

If there is a way, as rogerh mentioned, of removing data then the entire /vault/misc/ mountpoint can go.

That would remove 490GB, might that be enough?

 

[cyberjock]

Well, you need to fee up at least 100MB or so before you can do anything with mountpoints, datasets, etc.

So first you need to delete something so the zpool isn't locked up like it currently is. ;)