Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] install fails at grub2-install #1813

Closed
kkaempf opened this issue Jan 13, 2022 · 6 comments
Closed

[BUG] install fails at grub2-install #1813

kkaempf opened this issue Jan 13, 2022 · 6 comments
Assignees
Labels
area/installer kind/bug Issues that are defects reported by users or that we know have reached a real release

Comments

@kkaempf
Copy link

kkaempf commented Jan 13, 2022

Describe the bug

Fresh install on a dual-cpu, dual-ssd server. Installer chooses /dev/sdb (to my surprise) and stops after a while with

grub2-install: error: failed to get canonical path of '/run/cos/target/boot/efi'

To Reproduce
Steps to reproduce the behavior:

  • boot from iso image
  • accept defaults (only /dev/sdb was offered)
  • wait

Expected behavior

Installation to succeed 😉

Support bundle

Environment:

  • Harvester ISO version: harvester-v1.0.0-amd64.iso
  • Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):
    2x AMD EPYC 7282 (Zen-Rome) 16-Core CPU,
    2x SSD 1,9TB SAS3, 24x7, 1 DWPD, Samsung PM1643

Additional context
Add any other context about the problem here.

@kkaempf kkaempf added the kind/bug Issues that are defects reported by users or that we know have reached a real release label Jan 13, 2022
@kkaempf
Copy link
Author

kkaempf commented Jan 13, 2022

/cc @mudler - might be a cos problem ?!

@kkaempf
Copy link
Author

kkaempf commented Jan 13, 2022

CaptureScreen

screen capture of remote console

@bk201
Copy link
Member

bk201 commented Jan 14, 2022

@kkaempf Can you change to TTY2 and capture the output of sudo lsblk and sudo blkid? Thanks!

@kkaempf
Copy link
Author

kkaempf commented Jan 14, 2022

Sorry, the system has a broken serial console and (apparently) there's no other way to access it :-(
Will retry on a similar system 🤞🏻

@kkaempf
Copy link
Author

kkaempf commented Jan 26, 2022

Turns out that the problem probably was caused by a broken /dev/sda. As the drive was replaced meanwhile, I cannot reproduce the problem.
Closing for now. Will re-open if/when new logs are available,

@kkaempf kkaempf closed this as completed Jan 26, 2022
@patrickdk77
Copy link

I had this same issue, it seems if you already have an efi partition, it doesn't wipe it out correctly and the old label remains, in my case VMWARE label still existed. after doing a zero wipe of the first gig of the drive, reinstalling worked fine and blkid shows the name of the EFI partition as COS_GRUB instead of VMWARE.....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/installer kind/bug Issues that are defects reported by users or that we know have reached a real release
Projects
None yet
Development

No branches or pull requests

4 participants