Bug 20263 - Draklive installer fails to do copies on new root when a USB stick is present.
Summary: Draklive installer fails to do copies on new root when a USB stick is present.
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-11 10:52 CET by André DESMOTTES
Modified: 2019-02-20 17:38 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
journalctl -ab > journal.txt (541.12 KB, text/plain)
2017-02-11 16:51 CET, André DESMOTTES
Details
output of df and fdisk (7.91 KB, text/plain)
2017-02-11 16:53 CET, André DESMOTTES
Details

Description André DESMOTTES 2017-02-11 10:52:36 CET
Description of problem:
Needing Live installation screenshots, I plugged an extra USB stick and mounted it on /mnt just before launching the installation. Then the behaviour became strange:
- First error message to complain that Windows is hibernating and can't mount sda4 on /root/..../windows, whereas just before the Classical installer said nothing. Workaround by removing the sda4 mount point. (sda4 being the Windows partition)
- second error message later on: "Unable to copy files to new root" and the installation is cancelled.

Same thing if mounted on /media

Without the extra USB stick, this second error message doesn't exist.
Strange behaviour also, if I save the screenshots into /home/live/Documents during the installation, after the first reboot some of these screenshots are still there (one to 3 over about 6) but many are missing. I succeeded at the end by doing the installation until the prompt to reboot, then mounting the extra USB stick and doing the copies.

Version-Release number of selected component (if applicable):
Mageia 6 sta2 Live DVD x86_64 Plasma on real UEFI/GPT hardware


Steps to Reproduce:
1.Boot on the Live USB stick
2.Plug an extra USB stick formatted vfat
3.Open a console and mount the stick on /mnt (or /media)
4.Click on the icon to start the installation
5.Do screenshots with Gimp and export then in .png format on the USB stick
6.The error massages pop up
Comment 1 Marja Van Waes 2017-02-11 13:41:12 CET
Would it be possible to reproduce this while doing the following:


* Before you plugged and mounted the USB stick, run, as root:

   echo ==BEFORE > 1.txt && df >> 1.txt && fdisk -l | grep sd >> 1.txt

* Right after you plugged and mounted the USB stick, run, as root: 

   echo ==KEY_ADDED >> 1.txt && df >> 1.txt && fdisk -l | grep sd >> 1.txt


* Right after you get the first error message, before removing the windows mount
  point:

   echo ==ERROR_1 >> 1.txt && df >> 1.txt && fdisk -l | grep sd >> 1.txt

* after removing the Windows mountpoint, but before continuing:

   echo ==WIN_GONE >> 1.txt && df >> 1.txt && fdisk -l | grep sd >> 1.txt

* Right after you get the second error message:

   echo ==ERROR_2 >> 1.txt && df >> 1.txt && fdisk -l | grep sd >> 1.txt

  and

   journalctl -ab > journal.txt


and then attach 1.txt and journal.txt to this bug report?

Btw, which screenshots had gotten lost? The ones from the beginning of install?

CC: (none) => marja11
Component: Installer => RPM Packages
Assignee: bugsquad => mageiatools
Severity: minor => normal

Comment 2 André DESMOTTES 2017-02-11 15:25:13 CET
I begin by your last question.
At a first try, I got only the first made screenshot, and at a second try I got the 3 firsts screenshots.
Comment 3 André DESMOTTES 2017-02-11 16:51:15 CET
Created attachment 8949 [details]
journalctl -ab > journal.txt

asked file
Comment 4 André DESMOTTES 2017-02-11 16:53:17 CET
Created attachment 8950 [details]
output of df and fdisk

asked file
Comment 5 Marja Van Waes 2017-02-12 11:05:34 CET
About the message that windows is hibernating: was "fast boot" or "fast startup" enabled in windows?

About install failing with the "Unable to copy files to new root" message: at that point, according to the df output, only the new home partition is mounted, but the new / partition (/dev/sda5) isn't. I fail to see why.
Comment 6 André DESMOTTES 2017-02-12 18:31:59 CET
(In reply to Marja van Waes from comment #5)
> About the message that windows is hibernating: was "fast boot" or "fast
> startup" enabled in windows?

I can't check in Windows because it is in fact a former Win10 Technical Review that doesn't boot any more and that I keep to have the Windows partition in the partitioning screenshots.
However, in the firmware, "fast boot" is disabled and I could install Linux Mint, Fedora and Mageia Classical with no complaint. 

> 
> About install failing with the "Unable to copy files to new root" message:
> at that point, according to the df output, only the new home partition is
> mounted, but the new / partition (/dev/sda5) isn't. I fail to see why.

What is sure is that without the USB key, it works and if the key is mounted on /mnt or /media, I get the error message.
Comment 7 Martin Whitaker 2017-02-15 22:35:55 CET
I've tried to replicate the problem with the USB stick mounted on /mnt, but had no success - the install completes without error for me. Note that the installer mounts the partition it is installing to on /mnt/install, so if you already have a USB stick mounted on /mnt, an 'install' directory gets created on the USB stick.

Actually the installer is supposed to unmount all drives/partitions before proceeding to the partitioning step, and on the next Live ISO build it will (see bug 20268). So saving the screenshots to /home/live is your best option. Whether these get copied to the installed system would depend whether you saved the screenshots before or after that part of the filesystem was copied.

CC: (none) => mageia

Comment 8 André DESMOTTES 2019-02-20 17:38:03 CET
I can't check this bug with Mga7beta2 because I have no more Windows. Sorry.

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