*HEADS UP* - careful with upgrades - zf kernel load unexpected EOF

phil.davis

Just to report that nanoBSD is OK. I upgraded from:

2.2-BETA (i386)
built on Fri Nov 14 18:48:42 CST 2014
FreeBSD 10.1-RELEASE

to

2.2-BETA (i386)
built on Sat Nov 15 03:49:56 CST 2014
FreeBSD 10.1-RELEASE

without problem.

falumas

Same here. Things have gone so well with this Alpha/Beta that I didn't check the forums before upgrading.

This version should be revoked.

Pertan

Safe to update to amd64 built on Sat Nov 15 10:08:19 CST 2014?

falumas

I do not know, I updated to a 15th version can't remember the time.

cmb

I deleted all snapshot auto-updates. It's definitely a problem on both 32 and 64 bit full version. I probably should have left the nano images there, but they'll get re-populated.

There is another build running right now that will probably have the same problem but I'm letting it run. I'll check that at some point after it comes out.

Until someone says otherwise, don't upgrade anything other than test systems.

cmb

@Pertan:

What can I do to rescue this install?

Reinstall and restore backup. Rescue config in installer should work too, though I haven't tried that in a bit.

kejianshi

Smart advice that applies to lots of problems… haha
I usually get scolded for saying that.

cmb

There is a new snapshot up that doesn't seem to have that problem. I've upgraded upwards of a half dozen different full installs, mix of 32 and 64 bit, to the most recent snapshot at the time of this writing and they all went fine. I'm not sure what the issue was, and probably won't know until we can discuss on Monday. Take care when upgrading in the mean time.

robvanhooren

@cmb:

There is a new snapshot up that doesn't seem to have that problem.

New version: Sun Nov 16 04:06:10 CST 2014

"This image is not digitally signed."

:(

cmb

Snapshots aren't signed, that's normal.

BeerCan

Sun Nov 16 04:06:10 CST 2014

Installed and worked fine for me.

hansrotec

worked when upgraded this time, there was an error synching user profiles on first boot next boot no such error, took a third boot to check still was fine, checked config and users all seem to be fine, will be checking IPsec when remote in just over an hour. do not expect and issues

tested IPsec works… seems everything is good now

cmb

I've upgraded about 10 systems to the 3 snapshots out since the run I deleted and haven't had any issues since, seems this is fine now.

charliem

@cmb:

I'm not sure what the issue was, and probably won't know until we can discuss on Monday.

Any further info on what the problem was?