Description of problem: Upgrading Mageia 2 to Mageia 3 via DVD fails with mount error Version-Release number of selected component (if applicable): Mageia 2 x64 with all updates installed, up-to-date Mageia 3 x64 DVD installer How reproducible: Boot from DVD, choose upgrade Mageia 2 Error Message: mounting partition UUID=[my-sda1-UUID] in directory /mount/boot failed at /usr/lib/libDrakX/fs/mount.pm line 87. sda1 is my explicit /boot partition. The UUID is correct, and it's clean. The / partition on sda6 gets mounted correctly. Reproducible: Steps to Reproduce:
I presume you mean /mnt/boot in the error message? Can you check to see if an appropriate symlink exists in /dev/disk/by-uuid/ for [my-sda1-UUID] ? If so, can you double check that you do not have two disks with the same UUID (which would be possible if you'd used e.g. dd to copy a partition). If you temporarily edit the /mnt/etc/fstab to change from UUID to e.g. /dev/sda1 does it allow you to upgrade?
CC: (none) => mageia
(In reply to Colin Guthrie from comment #1) > I presume you mean /mnt/boot in the error message? yes, sorry. > Can you check to see if an appropriate symlink exists in /dev/disk/by-uuid/ > for [my-sda1-UUID] ? If so, can you double check that you do not have two > disks with the same UUID (which would be possible if you'd used e.g. dd to > copy a partition). The symlink is correct, I can mount the partition via UUID or /dev/sda1 if I run simply 'mount [UUID=x or /dev/sda1] /mnt/boot'. But if I run the complete mount command which ist used by the installer, 'mount -t ext4 [UUID=x or /dev/sda1] /mnt/boot -o umask=0,acl,noatime' it fails with 'wrong filesystem, bad superblock etc.' > If you temporarily edit the /mnt/etc/fstab to change from UUID to e.g. > /dev/sda1 does it allow you to upgrade? no, same error.
(In reply to Christian Müller from comment #2) > run simply 'mount [UUID=x or /dev/sda1] /mnt/boot'. But if I run the > complete mount command which ist used by the installer, 'mount -t ext4 > [UUID=x or /dev/sda1] /mnt/boot -o umask=0,acl,noatime' it fails with 'wrong > filesystem, bad superblock etc.' umask=0 seems to cause the problem.
Interesting. Not sure why the installer would add that in to be honest :s What does the fstab contain verbatim. Thierry, any idea where the umask could be coming from (mga3 installer)
CC: (none) => thierry.vignaud
See fs/mount_options.pm. For new vfat & ntfs mountpoints, we put: - 'umask=0' for low security level - 'umask=0022' for high security level (only for NTFS) It's documented: - 'umask=0' => N("Give write access to ordinary users"), - 'umask=0022' => N("Give read-only access to ordinary users") For an upgrade, we use use values from /etc/fstab. Please: 1) retry your upgrade up to this error, 2) attach an USB key, 3) then go to console #2 (alt+ctrl+f2) 4) run the "bug" command 5) attach the report.bug.xz file you'll found on your USB key to this bug report
I'm gonna guess that the upgrade is probably not possible to retry now, so not sure we'll be able to get the info out of it... If so I think we may have to resolve this one as old unless anyone else turns up who can reproduce the problem.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD