Project

General

Profile

Bug #15876

FreeNAS shows update available but will not update

Added by Mark Stega over 4 years ago. Updated almost 3 years ago.

Status:
Closed: User Config Issue
Priority:
No priority
Assignee:
Sean Fagan
Category:
OS
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

FreeNAS shows an available update but when I attempt to apply the update I see the "apply pending updates" dialog briefly and then a return to the updates page.

The update is identified as "base-os-9.10-STABLE-201605240427-b1814726769db6f75a5797438735378e -> base-os-9.10-STABLE-201606072003-56206375162121f339ddd0deef235daa"

History

#1 Updated by Sean Fagan over 4 years ago

  • Status changed from Unscreened to 15

Run

freenas-update -v update

and include the output.

#2 Updated by Mark Stega over 4 years ago

I believe the pertinent output is this (I couldn't figure out how to capture the complete trace):

Verify command = ['/usr/local/libexec/verify_signature', '-K', '/usr/local/share
/certs/freenas-update.pem', '-C', '/usr/local/share/certs/iX-CA.pem', '-S', u'oV
FoQp7O5KZZqxoW5rYiK69mfzU2FOgIeKZdjdOq7eQVkJx5wbCwKazZwQniyp+8OuucBrHXT9qKJ3Q6hB
Dfeb6S7bIsVYvopsBrmeVGu7fvyDSUeyB0ti35FaicDPnvO55l2UEzjqD2wfoyUn/1KLnqN65KpF19XL
RexmDsm27wbLu2nuJQvXzB0YXxJidGwejFAEeKrATRbtqAoP8dNX7Hkqlz+PelfpDmzTZK5Y3gkUnNYf
ke0CmO3GVixxl8Kq1N3kP6KuxWaepyd7iwY00+yBe4SkQfw5ay5a2odtlA+ev0X5nfP861ZQgANdQsWg
CIx4srYv0Logp9ZgaBMA==', '-R', '/tmp/tmpC_Fzja.pem']
Signature check succeeded
TryGetNetworkFile(['https://web.ixsystems.com/updates/ix_crl.pem'])
TryGetNetworkFile(['https://web.ixsystems.com/updates/ix_crl.pem']): Read 1028
bytes total
Verify command = ['/usr/local/libexec/verify_signature', '-K', '/usr/local/share
/certs/freenas-update.pem', '-C', '/usr/local/share/certs/iX-CA.pem', '-S', u'oV
FoQp7O5KZZqxoW5rYiK69mfzU2FOgIeKZdjdOq7eQVkJx5wbCwKazZwQniyp+8OuucBrHXT9qKJ3Q6hB
Dfeb6S7bIsVYvopsBrmeVGu7fvyDSUeyB0ti35FaicDPnvO55l2UEzjqD2wfoyUn/1KLnqN65KpF19XL
RexmDsm27wbLu2nuJQvXzB0YXxJidGwejFAEeKrATRbtqAoP8dNX7Hkqlz+PelfpDmzTZK5Y3gkUnNYf
ke0CmO3GVixxl8Kq1N3kP6KuxWaepyd7iwY00+yBe4SkQfw5ay5a2odtlA+ev0X5nfP861ZQgANdQsWg
CIx4srYv0Logp9ZgaBMA==', '-R', '/tmp/tmp0SDDZ2.pem']
Signature check succeeded
Upgrade package base-os-9.10-STABLE-201605240427-b1814726769db6f75a5797438735378
e to base-os-9.10-STABLE-201606072003-56206375162121f339ddd0deef235daa
Upgrade package docs-9.10-STABLE-201605240427-b1814726769db6f75a5797438735378e t
o docs-9.10-STABLE-201606072003-56206375162121f339ddd0deef235daa
Upgrade package freebsd-pkgdb-9.10-STABLE-201605240427-b1814726769db6f75a5797438
735378e to freebsd-pkgdb-9.10-STABLE-201606072003-56206375162121f339ddd0deef235d
aa
Upgrade package freenas-pkg-tools-9.10-STABLE-201605240427-b1814726769db6f75a579
7438735378e to freenas-pkg-tools-9.10-STABLE-201606072003-56206375162121f339ddd0
deef235daa
Upgrade package FreeNASUI-9.10-STABLE-201605240427-b1814726769db6f75a57974387353
78e to FreeNASUI-9.10-STABLE-201606072003-56206375162121f339ddd0deef235daa
new_boot_name = 9.10-STABLE-201606072003, reboot = True
RunCommand(/usr/local/sbin/beadm, ['create', u'9.10-STABLE-201606072003'])
cannot create 'freenas-boot/ROOT/9.10-STABLE-201606072003': dataset already exis
ts
Failed to create BE 9.10-STABLE-201606072003
Cannot destroy boot-environment selected for next reboot (9.10-STABLE-2016060720
03)
Unable to mount boot-environment 9.10-STABLE-201606072003
RunCommand(/usr/local/sbin/beadm, ['destroy', '-F', u'9.10-STABLE-201606072003']
)
ERROR: Cannot destroy active boot environment
Unable to apply update: Unable to mount boot-environment 9.10-STABLE-20160607200
3
[root@Beachfield-NAS ~]# ^C
[root@Beachfield-NAS ~]# ^C
[root@Beachfield-NAS ~]#

#3 Updated by Sean Fagan over 4 years ago

Okay, what happened is that you did an update from the Web UI, and for some reason it lost the connection, and didn't reboot.

You can safely reboot.

#4 Updated by Mark Stega over 4 years ago

I rebooted and now all seems to be OK. Thx for the help.

#5 Updated by Sean Fagan over 4 years ago

  • Status changed from 15 to Resolved

#6 Updated by Dru Lavigne almost 3 years ago

  • Status changed from Resolved to Closed: User Config Issue
  • Target version set to N/A

Also available in: Atom PDF