Bug 11601 - critical install fail - can't mount ext3 partitions
Summary: critical install fail - can't mount ext3 partitions
Status: RESOLVED DUPLICATE of bug 11600
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 4beta1
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-06 11:18 CET by Tony Blackwell
Modified: 2013-11-06 14:17 CET (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Tony Blackwell 2013-11-06 11:18:38 CET
Description of problem:
hardware: UEFI laptop, GPT disk.  Previous successful M3A4 install on /dev/sda4 after gdisk partitioning. Attempted to overwrite this now with M4B1 round 3 x86_64 install, classic DVD.

Install failed immediately after custom disk partitioning, when I selected /dev/sda4 again, the next stage formatting this gave no increment in the formatting progress bar.  'mount' failed, couldn't recognise ext3 partition type.  I went to the F2 # prompt, ran 'mke2fs -j /dev/sda4' which completed normally.  Tried to mount it from the hash prompt; 'mount -t ext3 /dev/sda4 /mnt -o acl,noatime' but this failed.'mount: unknown filesystem type 'ext3'

The only other error I can see, (possibly unrelated) behind Ctrl-Alt-F4, is some systemd stuff:
systemd-udevd[427]: failed to execute '/sbin/initqueue'  '/sbin/initqueue --onetime --unique --name console_init_tty0- /lib/udev/console_init /dev/tty0': no such file or directory


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


How reproducible: always


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Tony Blackwell 2013-11-06 12:33:53 CET

Whiteboard: (none) => M4B1 x86_64 round 3

Comment 1 claire robinson 2013-11-06 12:42:32 CET
Confirming this with DVD 64 (3rd build Nov 5th).

The installer (DVD 64) doesn't offer to upgrade mga3 64
which still have ext3 partitions on a dual booting system, only a
previous install from the same DVD which has ext4.

Looking in the log on tty3 it finds the partitions and tries to mount
them as ext3 read only on /tmp/inspect_tmp_dir. It does modprobe ext3
then modprobe -n ext3 before mounting each ext3 partition.

It doesn't show any error message there.

When it tests the ext4 partitions it doesn't modprobe and says ext4
already loaded.

Seems likely the modprobe is failing and the mounts for ext3 fail.
Looking n the dmesg log on tty4 it shows EXT4-fs (sda7) mounted and then
EXT4-fs (sda8) mounted but there is nothing showing for the previous
ext3 mounts (sda1,sda5 i think).

Whiteboard: M4B1 x86_64 round 3 => 4beta1

claire robinson 2013-11-06 12:42:45 CET

Summary: critical install fail - can't mount partition => critical install fail - can't mount ext3 partitions

Comment 2 claire robinson 2013-11-06 12:45:02 CET
Also in the partitioning stage, selecting to use existing partitions usually defaults to the first two on the drive but currently is defaulting to the ext4 partitions at the end of the drive.

I'll attach report.bug.xz when done.
Comment 3 claire robinson 2013-11-06 12:46:36 CET
Not sure if this is also true of live isos, i'll try one on this machine next install.

CC: (none) => ennael1, mageia, thierry.vignaud, tmb

Comment 4 Colin Guthrie 2013-11-06 12:57:47 CET
Sounds similar to #11600 in that the module is no longer automatically loaded and it's not pulled in magically. If you do a "modprobe ext3" first does it work OK? See the instructions on the other bug for how to do that.
Comment 5 Colin Guthrie 2013-11-06 13:12:16 CET
I think I see the problem:

https://bugs.mageia.org/show_bug.cgi?id=11600#c12
Comment 6 Tony Blackwell 2013-11-06 13:45:08 CET
FWIW 'modprobe ext3' doesn't then enable mounting of the ext3 target partition
Comment 7 Colin Guthrie 2013-11-06 13:48:49 CET
(In reply to Tony Blackwell from comment #6)
> FWIW 'modprobe ext3' doesn't then enable mounting of the ext3 target
> partition

When did you run that? If you run it during stage2 it's too late - it has to be done in combination with rd.break=pre-pivot command line option as detailed on the other bug and mentioned above.
Comment 8 Colin Guthrie 2013-11-06 14:03:23 CET
OK, so this problem should be fixed in the new drakx-installer-binaries I've just committed. Thomas can you push and rebuild -images after?
Comment 9 Thierry Vignaud 2013-11-06 14:17:30 CET
It's a dup then (stage2 not being able to load modules with new stage1)

*** This bug has been marked as a duplicate of bug 11600 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


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