| Summary: | drakboot crashed | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jorge Neto <jnt277> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | isobuild, mageia, mageiatools, marja11, zen25000 |
| Version: | 6 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakxtools-17.88-1.mga6 | CVE: | |
| Status comment: | |||
|
Description
Jorge Neto
2018-09-13 04:22:22 CEST
I meant to say Halted the PC - Boot the PC to grub and - no, grub did not install any partitioon table it can't. Don't know what more to say, explain. Good Luck and nice code time Hi Jorge, Thanks for the bug report and sorry to read about the trouble you ran into. You tried to install from a Live iso, right? Do you mind telling which exact Live iso? Do you still have Mageia installed on a partition, or did you overwrite it with another distribution? If you do still have it, then it would be fabulous if you could use the Live iso in Live mode to mount the root partition you installed to. There's a directory with a very long hexadecimal name in /that/partition's/var/log/journal/ please run, as root: journalctl -D /path/into/that/hexadecimal/directory/ > log.txt and attach log.txt to this bug report. If the log.txt is too large to attach, then do first run: xz log.txt and attach log.txt.xz I'll CC the persons with the most knowled about grub, drakboot and live isos, even if we don't have the needed logs, yet. Oh, one more question: You didn't mention that, but you did also try booting into your fresh install *without* the USB-key attached, right? CC:
(none) =>
isobuild, mageiatools, marja11, zen25000 If you attempt to set up the bootloader in MCC when booted into the live system, that will attempt to configure the bootloader for the live system, not for your installed system. I would expect that to fail. We should try to disable drakboot when running in live mode, to avoid users making that mistake. The bootloader for your installed system should have been configured and installed at the end of the installation process. To find out why that didn't work, we need the information Marja has asked for. CC:
(none) =>
mageia No reply :-( So closing as OLD. Status:
NEW =>
RESOLVED |