Project

General

Profile

Bug #9592

Nightlies are not booting the right BE

Added by Sean Fagan over 5 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Important
Assignee:
Xin Li
Category:
Middleware
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:
ChangeLog Required:
No

Description

See the attached grub.cfg -- the line is

set default="FreeNAS (FreeNAS-9.3-Nightlies-201505010630) - 2015-05-01 21:56"

but note the output of "beadm list":

BE Active Mountpoint Space Created Nickname
default - - 932.7M 2014-10-29 14:26 default
FreeNAS-9.3-STABLE-201503200528 - - 944.0M 2015-03-20 09:41 FreeNAS-9.3-STABLE-201503200528
FreeNAS-9.3-Nightlies-201504280630 - - 26.9M 2015-04-28 07:04 FreeNAS-9.3-Nightlies-201504280630
FreeNAS-9.3-Nightlies-201504290630 - - 26.6M 2015-04-29 08:43 FreeNAS-9.3-Nightlies-201504290630
FreeNAS-9.3-Nightlies-201505010630 N / 4.5M 2015-05-01 21:56 FreeNAS-9.3-Nightlies-201505010630
FreeNAS-9.3-Nightlies-201505030630 - - 284.1M 2015-05-03 10:17 FreeNAS-9.3-Nightlies-201505030630
FreeNAS-9.3-Nightlies-201505040631 - - 289.1M 2015-05-04 09:14 FreeNAS-9.3-Nightlies-201505040631
FreeNAS-9.3-Nightlies-201505050630 R - 3.8G 2015-05-05 07:25 FreeNAS-9.3-Nightlies-201505050630

None of the last three BEs are in the grub.cfg file, which of course makes it difficult for it to show up.

Did this happen concurrent with the switch to the latest ports? (My -STABLE system does not appear to have this issue, however.)

I'm marking this critical -- it is not possible to select the new boot environment, which means there is no way to get past this other than using an ISO install.

Running grub-mkconfig manually, I see:

/usr/local/etc/grub.d/30_os-prober: 132: Syntax error: "else" unexpected (expecting "done")

If I fix that error ("fi" followed by "else", looks like the "fi" should be undone), I get:

Generating grub configuration file ...
grub-probe: error: unknown filesystem.
grub-probe: error: unknown filesystem.
done

and while it still has

set default="FreeNAS (FreeNAS-9.3-Nightlies-201505050630) - 2015-05-05 07:25"

it still also doesn't have a submenu named "FreeNAS (FreeNAS-9.3-Nightlies-201505050630)"

I may have more as I investigate.

I'd really like me to be the only one affected by this.

History

#1 Updated by Josh Paetzel over 5 years ago

Jakub noticed this as a mismerge and fixed it this weekend.

#2 Updated by Sean Fagan over 5 years ago

Whew. That explains why it didn't affect my -STABLE system!

I -- somehow, I truly don't know -- got it to the state where it loaded the new BE in grub.cfg. But no other bE's. Booting that now.

#3 Updated by Sean Fagan over 5 years ago

  • Priority changed from Critical to Important

Okay. That seems to have improved, but:

  1. It now created a "Boot Environment Menu" submenu, behind which all the others are hidden.
  2. The hidden ones? Are named 'TrueOS' not 'FreeNAS'.

Something's not right here.

#4 Updated by Xin Li over 5 years ago

  • Status changed from Unscreened to Screened

#5 Updated by Sean Fagan over 5 years ago

Annnnnnnnnnnd my development system at work does not have the "Boot Environment Menu" (yet, anyway, I haven't updated it since yesterday), but it does have all of the BE's named TrueOS.

#6 Updated by Xin Li over 5 years ago

  • Status changed from Screened to 15

I think this should have been addressed in 2.02p_27?

#7 Updated by Jordan Hubbard over 5 years ago

  • Status changed from 15 to Resolved

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

  • Seen in changed from Unspecified to N/A

#9 Updated by Dru Lavigne almost 3 years ago

  • Target version set to Master - FreeNAS Nightlies

Also available in: Atom PDF