Bug 12647 - Upgrade to mageia 4 from internet gives problems at reboot
Summary: Upgrade to mageia 4 from internet gives problems at reboot
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Low minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-07 10:14 CET by Alberto Girlando
Modified: 2014-02-10 08:50 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Alberto Girlando 2014-02-07 10:14:36 CET
Description of problem: I upgraded from Mageia 3 to Mageia trough internet. I used the cli command since the applet did not work (never told me there was a new distro). At the end I rebooted. Initially told me could not open file us-intl, and could not found the resume device (which was there...), stopping at the dracut level. I entered manually resume=/dev/sda... and the boot recovered after the error, then stuck at the moment of Starting Hostname service. I inserted failsafe, and once at the recovery console I made dracut -f, but this did not changed things. 




Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. Boot
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Florian Hubold 2014-02-07 23:09:50 CET
For your first issue with resume partition, please have a look at https://wiki.mageia.org/en/Mageia_4_Errata#Upgrade_Issues and https://bugs.mageia.org/show_bug.cgi?id=12305

CC: (none) => doktor5000

Comment 2 Alberto Girlando 2014-02-10 08:49:39 CET
The secondo problem (unable to get the login screen) has been solved once I made a reistall from dvd. All the other trials that I made in between from the recovery screen failed, so I do not know what the origini of the preoblem was.

Still at boot tells me it does not find us-intl. Anyway, I thing the bug can be considered closed.

Priority: Normal => Low

Comment 3 Alberto Girlando 2014-02-10 08:50:39 CET
Still at boot tells me it does not find us-intl. Anyway, I thing the bug can be considered closed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Severity: critical => minor


Note You need to log in before you can comment on or make changes to this bug.