Project

General

Profile

Bug #54027

Updating from 11.1u6 to 11.2 RC1

Added by Matt Johnson 9 months ago. Updated 9 months ago.

Status:
Closed
Priority:
No priority
Assignee:
Release Council
Category:
Console
Target version:
Seen in:
Severity:
New
Reason for Closing:
Not Applicable
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

No virtual machines, no jails.
It is joined to my domain.
Services: SMB NFS and iSCSI

Changed to 11.2 Stable which indicated 11.2 RC1 was to be updated. After rebooting I see a 2 line error message with "root : user NOT in suboders" for multiple commands such as "COMMAND=/etc/find_alias_for_smtplib.sh -t"

This has currently been scrolling for about an hour.

https://imgur.com/a/PqnaffL

Capture.PNG (38 KB) Capture.PNG Screenshot Matt Johnson, 10/25/2018 08:44 PM
36873

History

#1 Updated by Dru Lavigne 9 months ago

  • Status changed from Unscreened to Blocked
  • Reason for Blocked set to Need additional information from Author

Matt: did the update ever finish? It is possible that the boot device is failing. Does a fresh install of RC1 on a different stick result in the same behavior?

#2 Updated by Matt Johnson 9 months ago

Dru Lavigne wrote:

Matt: did the update ever finish? It is possible that the boot device is failing. Does a fresh install of RC1 on a different stick result in the same behavior?

It never did, I ended up rebooting it and rolling back to U6. I was going to disable SMTP/mail alerts to see if that made any change, but being the main storage for my virtual servers I just haven't done so yet. I will give it another try tomorrow (Sunday 28th).

#3 Updated by Matt Johnson 9 months ago

No sure if it made any real difference, went into mail settings and just changed the "from" address and saved hoping it would auto-fix any settings related. Deleted the RC1 boot snapshot and ran the update gain. Now it appears to be happily running RC1. Case solved?

#4 Updated by Dru Lavigne 9 months ago

  • Status changed from Blocked to Closed
  • Target version changed from Backlog to N/A
  • Reason for Closing set to Not Applicable
  • Reason for Blocked deleted (Need additional information from Author)

Thanks for the update Matt. It sounds like the original update failed. Glad to hear the next attempt worked out.

Also available in: Atom PDF