Project

General

Profile

Bug #8133

bootadm: is_ramdisk test is not functional

Added by Michal Nowak over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
cmd - userland programs
Start date:
2017-05-01
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Difficulty:
Bite-size
Tags:

Description

When I restart after OpenIndiana text installation (20160431, 20161030 up to my own yesterday's snapshot from current code) I see following line in console:

bootadm: failed to open file: //platform/i86pc/kernel/unix: No such file or directory

It happens only on x86_64, i386 is fine (as expected). The error is probably harmless, the system reboots fine, boots fine as well. Screenshot attached.


Files

bootadm.png (14 KB) bootadm.png Michal Nowak, 2017-05-01 07:29 AM
bootloader_textmode-dmesg.txt (17.3 KB) bootloader_textmode-dmesg.txt Michal Nowak, 2017-05-01 07:40 AM
bootloader_textmode-install_log.txt (4.47 KB) bootloader_textmode-install_log.txt Michal Nowak, 2017-05-01 07:40 AM
bootloader_textmode-svc_logs.txz (3.62 KB) bootloader_textmode-svc_logs.txz Michal Nowak, 2017-05-01 07:40 AM

Subtasks

Bug #8142: bootadm: get_boot_cap() should test for both 32-bit and 64-bit kernelClosedToomas Soome

Actions

History

#2

Updated by Toomas Soome over 2 years ago

Michal Nowak wrote:

When I restart after OpenIndiana text installation (20160431, 20161030 up to my own yesterday's snapshot from current code) I see following line in console:

[...]

It happens only on x86_64, i386 is fine (as expected). The error is probably harmless, the system reboots fine, boots fine as well. Screenshot attached.

Yes it is harmless, it is a bit unfortunate combination of how the install media is built; the system state on startup does change - as this is boot from "clean" media, and on reboot the bootadm is called to update the boot_archive with this new state for install media. And bootadm is built to expect both 32 and 64 bit kernels are present - which is not the case with install media.

#3

Updated by Toomas Soome over 2 years ago

  • Subject changed from "bootadm: failed to open file: //platform/i86pc/kernel/unix: No such file or directory" on AMD64 to bootadm: is_ramdisk test is not functional
#4

Updated by Toomas Soome over 2 years ago

  • Category set to cmd - userland programs
  • Status changed from New to In Progress
  • Assignee set to Toomas Soome
  • % Done changed from 0 to 90
  • Difficulty changed from Medium to Bite-size
  • Tags deleted (needs-triage)
#5

Updated by Toomas Soome over 2 years ago

  • Description updated (diff)

The actual reason for this message is issue #8142 - the bootadm is checking for the 32-bit kernel and is failing if the system is 64-bit.

However, it is not enough to fix just that check for the kernel, because the ramdisk check is still broken. so those two issues are actually related and happen when system is run from the boot media and is using boot_archive as ramdisk for root file system.

#6

Updated by Electric Monk over 2 years ago

  • Status changed from In Progress to Closed

git commit 1a96bf60a6b9227444199581bdccccf87e84b308

commit  1a96bf60a6b9227444199581bdccccf87e84b308
Author: Toomas Soome <tsoome@me.com>
Date:   2017-05-03T15:18:11.000Z

    8133 bootadm: is_ramdisk test is not functional
    Reviewed by: Peter Tribble <peter.tribble@gmail.com>
    Reviewed by: Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org>
    Approved by: Robert Mustacchi <rm@joyent.com>

Also available in: Atom PDF