Project

General

Profile

Bug #15000

This morning's update 2016.Apr.27 did not complete.

Added by Robert Dinah over 4 years ago. Updated almost 3 years ago.

Status:
Closed: User Config Issue
Priority:
Important
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:

HP Proliant Microserver N36L (Athlon II amd64)

ChangeLog Required:
No

Description

Apr 27 00:00:00 server syslog-ng1317: Configuration reload request received, reloading configuration;
Apr 27 09:57:30 server updated.py: [freenasOS.Installer:308] Sub procss exited with status 0x100
Apr 27 10:26:04 server updated.py: [freenasOS.Update:1160] Cannot destroy boot-environment selected for next reboot (9.10-STABLE-201604261518)
Apr 27 10:26:04 server updated.py: [freenasOS.Update:1169] Unable to mount boot-environment 9.10-STABLE-201604261518
Apr 27 10:26:12 server manage.py: [middleware.exceptions:37] [MiddlewareError: Unable to mount boot-environment 9.10-STABLE-201604261518]
Apr 27 10:34:55 server updated.py: [freenasOS.Update:1160] Cannot destroy boot-environment selected for next reboot (9.10-STABLE-201604261518)
Apr 27 10:34:55 server updated.py: [freenasOS.Update:1169] Unable to mount boot-environment 9.10-STABLE-201604261518
Apr 27 10:34:56 server manage.py: [middleware.exceptions:37] [MiddlewareError: Unable to mount boot-environment 9.10-STABLE-201604261518]
Apr 27 10:35:43 server updated.py: [freenasOS.Update:1160] Cannot destroy boot-environment selected for next reboot (9.10-STABLE-201604261518)
Apr 27 10:35:43 server updated.py: [freenasOS.Update:1169] Unable to mount boot-environment 9.10-STABLE-201604261518
Apr 27 10:35:44 server manage.py: [middleware.exceptions:37] [MiddlewareError: Unable to mount boot-environment 9.10-STABLE-201604261518]
Apr 27 10:36:21 server updated.py: [freenasOS.Update:1160] Cannot destroy boot-environment selected for next reboot (9.10-STABLE-201604261518)
Apr 27 10:36:21 server updated.py: [freenasOS.Update:1169] Unable to mount boot-environment 9.10-STABLE-201604261518
Apr 27 10:36:22 server manage.py: [middleware.exceptions:37] [MiddlewareError: Unable to mount boot-environment 9.10-STABLE-201604261518]

History

#1 Updated by Jakub Klama over 4 years ago

  • Project changed from 9 to FreeNAS
  • Category changed from 168 to 1
  • Assignee changed from Jakub Klama to Sean Fagan
  • Seen in changed from to 9.10-STABLE-201604261518

#2 Updated by Sean Fagan over 4 years ago

I presume this is a dup of 14985.

Please run "beadm list". There'll be more steps later, but that first.

#3 Updated by Sean Fagan over 4 years ago

  • Status changed from Unscreened to 15

#4 Updated by Robert Dinah over 4 years ago

[root@server ~]# beadm list
BE Active Mountpoint Space Created Nickname
default - - 7.4M 2015-06-28 11:44 default
Initial-Install - - 5.7M 2015-06-28 11:57 Initial-Install
FreeNAS-8863f903d550e9d8a1e9f8c73ae9b4f0 - - 159.7M 2016-04-09 16:16 FreeNAS-8863f903d550e9d8a1e9f8c73ae9b4f0
9.10-STABLE-201604111739 - - 155.6M 2016-04-12 08:30 9.10-STABLE-201604111739
9.10-STABLE-201604140622 - - 238.6M 2016-04-15 08:24 9.10-STABLE-201604140622
9.10-STABLE-201604181743 N / 284.9M 2016-04-23 15:07 9.10-STABLE-201604181743
9.10-STABLE-201604261518 R - 2.4G 2016-04-27 09:53 9.10-STABLE-201604261518
[root@server ~]#

#5 Updated by Sean Fagan over 4 years ago

Okay, this is a duplicate of it. Before I mark it as such, please do:

beadm destroy -F 9.10-STABLE-201604261518
freenas-update -v update

and paste the output of everything.

Before you do that, however: this looks like the update already completed. Did you do an update and not reboot, and then try an update again?

#6 Updated by Robert Dinah over 4 years ago

Okay, I will do that ... I did an update and the system did not automatically reboot. The system just sat there with a pending update displayed. I tried a few times again and just got a waiting dialog that just went away without a reason why. I did not do a reboot as I wanted to keep the system in a state that some debugging information may be extracted that a reboot might overwrite. Right now the server is very busy. When it frees up I will perform your steps and post the output. I assume I can safely reboot afterwards ... unless of course it reboots automatically after the update completes. Thank you!

p.s. I was really concerned by the 2.4G extent that 201604261518 was showing.
p.p.s. Off subject: Any news on clearing up that security issue that gets posted nightly? I thought a previous update was supposed to resolve this.

Checking for packages with security vulnerabilities:
libtasn1-4.7
samba43-4.3.6_100313
proftpd-1.3.5a_2

-- End of security output --

#7 Updated by Sean Fagan over 4 years ago

The 2.4g in use is normal, that's how ZFS works.

#8 Updated by Sean Fagan over 4 years ago

Also, okay so it sounds like you did the update process, but it didn't reboot. Then you tried to do the update again, and things complained. This is mostly expected, I think. (Although the not rebooting may not be.)

#9 Updated by Jordan Hubbard over 4 years ago

Depends on whether or not he checked the reboot flag. If he didn't, then this would be the expected behavior (I wonder if we should detect a "pending reboot" scenario and not attempt to double-apply the update).

#10 Updated by Robert Dinah over 4 years ago

This didn't get very far ... :-)

[root@server ~]# beadm destroy -F 9.10-STABLE-201604261518
ERROR: Cannot destroy active boot environment
[root@server ~]#

#11 Updated by Robert Dinah over 4 years ago

Okay, I've rebooted the server and it came up live with no clear problems. Thanks for the assistance!

#12 Updated by Jordan Hubbard over 4 years ago

  • Status changed from 15 to Resolved

#13 Updated by Benjamin Carr over 4 years ago

  • File debug-freenas-20160609005226.tgz added
  • File beamd_list.txt added
  • File F_U_Update.txt added
  • File F_U_Check.txt added
  • File F_U_Update_Error.txt added
  • Priority changed from No priority to Important
  • Seen in changed from 9.10-STABLE-201604261518 to 9.10-STABLE-201605240427
  • Hardware Configuration updated (diff)

Basically looking for permission to reboot (hopefully safely.....

encountered mDNS chatty bug in https://bugs.freenas.org/issues/15495 repulled with webgui, download, verify apply. received e "Unable to mount boot-environment"

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 exists
Failed to create BE 9.10-STABLE-201606072003
Cannot destroy boot-environment selected for next reboot (9.10-STABLE-201606072003)
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-201606072003

Ran "freenas-update -v check" and then "freenas-update -v update" with tee and errors (attached)

-check suggests:
Reboot is (conditionally) required
Sequence d55ab9177fa7bbcd849b9f0687646c3d -> 56206375162121f339ddd0deef235daa

Terrified to reboot (though do have db backup)

#14 Updated by Dru Lavigne almost 3 years ago

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

#15 Updated by Dru Lavigne almost 3 years ago

  • File deleted (debug-freenas-20160609005226.tgz)

#16 Updated by Dru Lavigne over 2 years ago

  • File deleted (beamd_list.txt)

#17 Updated by Dru Lavigne over 2 years ago

  • File deleted (F_U_Update.txt)

#18 Updated by Dru Lavigne over 2 years ago

  • File deleted (F_U_Check.txt)

#19 Updated by Dru Lavigne over 2 years ago

  • File deleted (F_U_Update_Error.txt)

Also available in: Atom PDF