nas collectd[26057]: processes plugin: Cannot open kvm interface: /dev/null: No such file

[Crispin]

Hi folks,

I think I've broken my FreeNAS somehow.

I can no longer ssh into it (after a reboot the ssh service is running but if you stop it you cannot start it)
Jails are not showing up (but they are running - I can still see Plex (a jail) and my dev web server (a different jail))
CIFS is still working

If I look in the footer console I see screens and screens of the following:

Code:

Oct 21 19:23:11 nas collectd[26057]: processes plugin: Cannot open kvm interface: /dev/null: No such file or dire

What did I do?
I put in as a cache SSD this morning and worked fined. I've been ssh'd in all day on it without hassle. zpool status tank showed the disk just fine.
I then tried doing a read / write speed test using rsync and rsynced this :

Code:

rsync --progress /mnt/tank/Dump/bigiso.iso /dev/null

Did I break it? If so, what did I break and how can I fix it? :(

System:

See my uptime is blank too...

I cannot upgrade to U2 - it says something about U1 boot not being available.


Help :)

Thanks.
C

 

[Crispin]

I see other messages in the console too

Code:

Oct 21 19:48:08 nas notifier: /etc/rc.conf.local: cannot create /dev/null: Operation not supported
Oct 21 19:48:08 nas notifier: /etc/rc.conf.local: cannot create /dev/null: Operation not supported
Oct 21 19:48:09 nas notifier: /etc/rc.conf.local: cannot create /dev/null: Operation not supported
Oct 21 19:48:09 nas notifier: /etc/rc.conf.local: cannot create /dev/null: Operation not supported
Oct 21 19:48:09 nas notifier: /etc/rc.conf.local: cannot create /dev/null: Operation not supported
Oct 21 19:48:09 nas notifier: eval: cannot create /dev/null: Operation not supported

 

[Crispin]

well, not really sure what's happened but after the third reboot it seems to be ok.

I had added in a HDD controller which mucked up the boot-order. Not sure if that stopped the upgrade.


Oh well - it works now..