Project

General

Profile

Bug #14341

Error during Upgrade vom 9.3.1 to 9.10 rebooting into Single User Mode

Added by René Keller over 4 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Important
Assignee:
Sean Fagan
Category:
OS
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

I have tried to upgrade my freenas 9.3.1 System to FreeNASA 9.10.

After successful install through webgui the system reboots and show me the following errors on the console:

linker_load_file: Unsupported file type
kldload: an error occurred while loading the module. please check dmesg(8) for more details.
/etc/rc: WARNING: Unable to load kernel module geom_gate
link_elf_obj: symbol _sx_assert_undefined
linker_load_file: Unsupported file type
kldload: an error occurred while loading the module. please check dmesg(8) for more details.
/etc/rc: WARNING: Unable to load kernel module geom_multipath
em0: link state changed to UP
em1: link state changed to UP
Setting hostuuid: c8129b61-f068-11e5-91af-001517b21d68
Setting hostid: 0x5fd72849
No suitable dump device was found.
Entropy harvesting: interrupts ethernet point_to_point swi.
Starting file system checks:
Mounting local file systems: link_elf_obj: symbol kassert_panic undefined
linker_load_file: Unsupported file type
mount: fdescfs: Operation not supported by device
.
Mounting /etc/fstab filesystems failed, startup aborted
ERROR: ABORTING BOOT (sending SIGTERM to parent)!
Mar 29 16:25:41 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode
Enter full pathname of shell or RETURN for /bin/sh:

History

#1 Updated by Sean Fagan over 4 years ago

  • Status changed from Unscreened to 15

Not quite sure what's going on. But please try this:

  1. Boot to single user mode. (From the GRUB menu, press enter for the highlighted one, then select Single User Mode.)
  2. When it prompts for a shell, press enter.
  3. Do "mount -u /" and "mount /boot/grub"
  4. Then do "beadm list"
  5. Take note of the one that is currently mounted (it'll have "/" as one of the fields, instead of "-").
  6. Do "beadm activate ${that one}"
  7. Then "shutdown -r now"

Let me know if any of those steps fail, or if the whole process succeeds.

#2 Updated by René Keller over 4 years ago

  • File logging.txt added
  • Priority changed from No priority to Important

Hey I have tried what you wrote.
at point 3 (mount /boot/grub) I got a device is busy so I first unmounted it.

I have appended the output of dmesg and the beadm commands. Maybe it can help in this case.

#3 Updated by Sean Fagan over 4 years ago

My mistake. Replace step 6 with:

  1. beadm activate default
  2. beadm activate FreeNAS-8863f903d550e9d8a1e9f8c73ae9b4f0
  3. shutdown -r now

#4 Updated by René Keller over 4 years ago

it worked, thank you!

#5 Updated by Sean Fagan over 4 years ago

  • Status changed from 15 to Resolved

Okay, so that was due to having the wrong version of beadm. It should be fixed now. If it happens again, try doing this again to get the boot files rebuilt.

#6 Updated by Dru Lavigne almost 3 years ago

  • Target version set to Master - FreeNAS Nightlies

#7 Updated by Dru Lavigne almost 3 years ago

  • File deleted (logging.txt)

Also available in: Atom PDF