As discussed on the qa discuss mailing list, systems installed from Mageia 5.1 iso images on a root partition with the file system type xfs are not bootable using grub, or grub2. Works with lilo. This is a regression from the original Mageia 5 iso images.
Summary: System installed from live iso fails to boot (grub/grub2) if root file system type is xfs => System installed from 5.1 live iso fails to boot (grub/grub2) if root file system type is xfs
Assignee: bugsquad => isobuild
Also affects Mageia-5.1-x86_64-DVD
Summary: System installed from 5.1 live iso fails to boot (grub/grub2) if root file system type is xfs => System installed from any 5.1 iso fails to boot (grub/grub2) if root file system type is xfs
Keywords: (none) => 5.1
Is it valid for original mga5 too? I think it was possible to install grub2 on / xfs w/o a non xfs /boot b/c of: http://gitweb.mageia.org/software/drakx/commit/?id=0fe6821e92a6a5b0b5c1c2b1bb0955899d998135
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaud
Also, on mga6, grub legacy doesn't support new xfs metadata... Sadly, xfsprogs (& kernel) was(were) updated on mga5, so I fear that now the installer will format XFS with the new format, which will make grub legacy to fail... (which is one of the reason we switched from lilo/grub to grub2 on mga6...) (with the fact that they're no more maintained thus the above xfs issue...) At least e2fsprogs wasn't backported so new ext4 format isn't an issue for grub legacy... We can alter the installer so that it forbid xfs / w/o a separate non-xfs /boot...
CC: (none) => tmb
Which brings the issue that grub2 support in mga5's drakboot isn't as complete as in mga6...
I tested an install using, Mageia-5-LiveDVD-KDE4-x86_64-DVD.iso with only one xfs partition on the hard drive (under vb), using grub (not grub2), and it worked. The partition was formatted during the install.
(In reply to Thierry Vignaud from comment #3) > Also, on mga6, grub legacy doesn't support new xfs metadata... > Sadly, xfsprogs (& kernel) was(were) updated on mga5, so I fear that now the > installer will format XFS with the new format, which will make grub legacy > to fail... Not sadly :) we need it to be able to install on recent hw. > (which is one of the reason we switched from lilo/grub to grub2 on mga6...) > (with the fact that they're no more maintained thus the above xfs issue...) > > At least e2fsprogs wasn't backported so new ext4 format isn't an issue for > grub legacy... > > We can alter the installer so that it forbid xfs / w/o a separate non-xfs > /boot... Or just stick it on errata that if you want xfs on / you need a separate ext /boot... meaning I dont think the pain vs gain is worth redoing more drakx stuff at this point given mga5 lifetime and mga6 eta
Keywords: (none) => FOR_ERRATA5
of course if someone want to try a fix... boot a live iso, do a manual mkfs.xfs -m crc=0 /dev/<target_partition> and try to install on it... is grub/grub2 happy then ?
(In reply to Thomas Backlund from comment #7) > of course if someone want to try a fix... > > boot a live iso, do a manual mkfs.xfs -m crc=0 /dev/<target_partition> > > and try to install on it... is grub/grub2 happy then ? without formatting it again that is...
(In reply to Thomas Backlund from comment #7) > of course if someone want to try a fix... > > boot a live iso, do a manual mkfs.xfs -m crc=0 /dev/<target_partition> > > and try to install on it... is grub/grub2 happy then ? grub installs, but fails to boot. grub2 won't even install, with the error: grub2-install: error: hostdisk//dev/sda appears to contain a xfs filesystem which isn't known to reserve space for DOS-style boot. Installing GRUB there could result in FILESYSTEM DESTRUCTION if valuable data is overwritten by grub-setup (--skip-fs-probe disables this check, use at your own risk).
CC: (none) => mageia
ok, second test... try this instead: mkfs.xfs -m spinodes=0 /dev/<target_partition>
[root@localhost live]# mkfs.xfs -m spinodes=0 /dev/sda1 unknown option -m spinodes=0 ...
Sorry, that would be mkfs.xfs -m sparse=0 /dev/<target_partition>
That option isn't recognised either. The version of mkfs.xfs (4.3.0) on the Live ISOs only supports: Usage: mkfs.xfs /* blocksize */ [-b log=n|size=num] /* metadata */ [-m crc=0|1,finobt=0|1,uuid=xxx] /* data subvol */ [-d agcount=n,agsize=n,file,name=xxx,size=num, (sunit=value,swidth=value|su=num,sw=num|noalign), sectlog=n|sectsize=num /* force overwrite */ [-f] /* inode size */ [-i log=n|perblock=n|size=num,maxpct=n,attr=0|1|2, projid32bit=0|1,sparse=0|1] /* no discard */ [-K] /* log subvol */ [-l agnum=n,internal,size=num,logdev=xxx,version=n sunit=value|su=num,sectlog=n|sectsize=num, lazy-count=0|1] /* label */ [-L label (maximum 12 characters)] /* naming */ [-n log=n|size=num,version=2|ci,ftype=0|1] /* no-op info only */ [-N] /* prototype file */ [-p fname] /* quiet */ [-q] /* realtime subvol */ [-r extsize=num,size=num,rtdev=xxx] /* sectorsize */ [-s log=n|size=num] /* version */ [-V] devicename
Keywords: FOR_ERRATA5 => IN_ERRATA5CC: (none) => yves.brungard_mageia
*** Bug 19957 has been marked as a duplicate of this bug. ***
CC: (none) => alex_q_2000
Closing as OLD because Mageia 5* is no longer officially supported and because there is no mention that this affected Mageia 6
Status: NEW => RESOLVEDResolution: (none) => OLDCC: (none) => marja11