| Summary: | Installation Mageia 6 RC failed with 'unpack' errors | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Gerald <g.sprik> |
| Component: | Installer | Assignee: | Mageia tools maintainers <mageiatools> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | yvesbrungard |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | report.bug | ||
|
Description
Gerald
2017-06-09 14:12:54 CEST
Created attachment 9396 [details]
report.bug
A second installation attempt failed too, again an 'unpack' error, but now on another package.
Do you have enough available disk space on the partition you chose for / ?
Rémi Verschelde
2017-06-09 15:49:22 CEST
Assignee:
bugsquad =>
mageiatools (In reply to Rémi Verschelde from comment #2) > Do you have enough available disk space on the partition you chose for / ? The partition is 19 GB (I chose for Plasma as DE). In earlier releases of Mageia this was more than enough disk space for /. (In reply to Gerald from comment #3) > (In reply to Rémi Verschelde from comment #2) > > > Do you have enough available disk space on the partition you chose for / ? > > The partition is 19 GB > (I chose for Plasma as DE). > > In earlier releases of Mageia this was more than enough disk space for /. That still does not answer the question. How about providing the output from df -h / (In reply to Bit Twister from comment #4) The output from df -h / (when I see the 'unpack' ERROR messages) is: Filesystem Size Used Avail Use Mounted on /dev/loop0 66 66 0 100% /usr /dev/sda1 39999 65 39934 0% /mnt/media/windows /dev/sdb11 19923 1143 18779 5% /mnt /dev/sdb8 495376 376608 118768 76% /mnt/mnt/data1 /dev/sdc 3908 3908 0 100% /tmp/media devtmpfs 3953 0 3953 0% /mnt/dev none 3967 0 3967 0% /mnt/tmp/.X11-unix rootfs 3953 111 3841 2% / tmpfs 3967 1 3966 0% /mnt/run I use partition sdb11 to install Mageia 6. This is rather suspicious, as these days RPM usually catches the kind of things that cause unpack errors before they happen. Did you verify the checksum of your ISO? (In reply to David Walser from comment #6) > This is rather suspicious, as these days RPM usually catches the kind of > things that cause unpack errors before they happen. Did you verify the > checksum of your ISO? Yes, i verified. All checksums matched (md5sum, sha1sum and sha512sum). I use IsoDumper in Mageia 5 to write the ISO image on an USB stick. The IsoDumper log shows that it has been done successfully, but the SHA1-sum and MD5-sum in the log are different from the md5sum and sha1sum of the ISO itself. Should they match? Yes, Isodumper reports that it encounters no error, but it doesn't check the sums against source sums. CC:
(none) =>
yves.brungard_mageia The conclusion is that these unpack errors were caused by an incorrect 'isodump'. It's not an installer issue. Status:
NEW =>
RESOLVED |