Project

General

Profile

Bug #25050

Update failed

Added by Bo Nielsen about 3 years ago. Updated about 3 years ago.

Status:
Closed: User Config Issue
Priority:
No priority
Assignee:
William Grzybowski
Category:
OS
Target version:
Seen in:
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:

Supermicro X10SL7-F, Xeon E3-1220 v3, 4x 8GB Crucial DDR3L 1600MHz CT2KIT102472BD160B, 2x Sandisk U100 16GB SSD in mirror for boot, and also mirrored onto to 2x Sandisk Cruiser 16GB USB drives.

ChangeLog Required:
No

Description

Using the WebGUI I clicked update to latest stable in the 9.10-STABLE branch, updating an older 9.10 (pretty sure it was the STABLE-20160325).
After reboot I got boot-looping with GRUB complaining:

---------
error: compression algorithm inherit not supported
---------

Then GRUB fills the screen once with gngngngngngngngngngngngngngngngngng.... you get the picture, and system then reboots. Rinse and repeat...

After installing FreeNAS (STABLE-20170627), where the installer mentions, that the previous config-file had been located and migrated to the newly installed system, the WebGUI complains by the red lantern:

---------
CRITICAL: July 7, 2017, 11:14 p.m. - Update failed. Check /data/update.failed for further details
---------

Although on first glance the entire system seems to be complete and functioning normally.

Peering into the /data/update.failed-file reveals this some interesting comments from a developer:


! I'm not trusting myself; either fix this yourself by fiddling
! with the south_migrationhistory table, or pass --delete-ghost-migrations
! to South to have it delete ALL of these records (this may not be good).


The file has been attached.

I will leave this system running as is, fr at least a month or so, should you wish to make inqueries.

History

#1 Updated by Bo Nielsen about 3 years ago

  • File update.failed added

The bug report engine in FreeNAS never completed task 4 of 4 "Uploading attachments from host to the ticket".
Thus, I have added it via the bugs.freenas.org site.

#2 Updated by Sean Fagan about 3 years ago

The complaint about compression algorithm means that there's a zfs pool with, well, a compression algorithm it doesn't know. If you did a "zpool upgrade freenas-boot" then you're pretty much hosed by it. But this could be that the wrong disk is chosen in the BIOS for booting. See if you can boot from the ISO and import the pool (go to shell, and do "zpool import -N freenas-boot"). You could also just try to do an install and create a new boot environment, rather than reformat the disk(s), perhaps. Oh, I see you already did that.

The fact that the update failed is something for William to comment on, I think, but I don't think it's related to the grub issue.

#3 Updated by Bo Nielsen about 3 years ago

  • Hardware Configuration updated (diff)

Thanks for taking the time to peer into it - there could very well be two errors in play here.

The grub-thing has me worried though. I mean, I wasn't swapping drives or nothing, just system update and then GRUB made a mess in its pants.
Perhaps a regular reboot would have enden in the same GRUB-error, and not be related to the update process. Correlation or causation. I do not know.

Anywho, the system is up again, and that is good.
But the reinstall (with migration of the previous configuration) that complains as well is also troublesome.

In a month or so, if you guys have nothing you want me to try, I'll properbly make a clean install and import a known good config-file.
That should be end of this side skirmish.

#4 Updated by Dru Lavigne about 3 years ago

  • Assignee changed from Release Council to Sean Fagan

#5 Updated by Sean Fagan about 3 years ago

Again, if it's booting, then it's a harmless message -- just means that grub found a pool or dataset with a compression algorithm it doesn't understand. As long as that pool isn't freenas-boot, it doesn't matter.

#6 Updated by Sean Fagan about 3 years ago

  • Assignee changed from Sean Fagan to William Grzybowski

#7 Updated by William Grzybowski about 3 years ago

  • Status changed from Unscreened to Closed: User Config Issue

It looks to me that you have run this configuration database in a newer version at some point and then tried to use 9.10-STABLE on it again.

Thats pretty much what update.failed is saying and there isn't much we can do about that. What you could do is try to upgrade to 11-STABLE.

#8 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Seen in changed from Unspecified to N/A

#9 Updated by Dru Lavigne about 3 years ago

  • File deleted (update.failed)

#10 Updated by Dru Lavigne about 3 years ago

  • Target version set to N/A
  • Private changed from Yes to No

Also available in: Atom PDF