Description of problem: Bonjour, le 01mars2021 Je suis en charge d' une dizaine de PC , principalement DELL Optiplex 9010 7010 3090 +... + Portable etc ... Sur ces PC j' ai installé , MAGEIA 7.1 avec quelques PBs , mais à la fin j' ai réussis ...et l' utilisation + Mise à jour se passe sans probleme ... J' ai téléchargé la version MAGEIA 8 32b PLASMA disponible , hier ( j' ai vérifié la validé des fichiers téléchargés ...) ... J' ai procédé à une 1ere installation MAGEIA 8 32B sur un PC DELL OPTIPLEX 9010 / I5/ 4G ram / 2x2To dsk et je dois dire que j' ai un peu galéré ( plusieurs installations de suite qui donnent les mèmes résultats ): -> avec le lecteur de DVD du PC et un Lecteur DVD USB Externe ( que je sais OK ) ... -> contrairement à la MAGEIA 7.1 l' installation semble devoir se faire en 2 etapes : 1ere étape : installation classique ... qui se termine au bout d' un temps assez long par un arret ; dans un état non fonctionnel ... 2eme étape : relecture du DVD Installation + reparamétrage puis set "Mise à jour Mageia" -> l' installation se terminant alors , de façon classique comme pour la 7.1 ... puis demande de reboot Etc ... En revanche au reboot : l' interface graphique de LogIn n' est pas accessible ... seulement un login dans une fenètre simple genre Bash est possible dans ce cas ... Si on lance , après login "startx" , l' interface graphique se lance correctement ... ( mais avec crash de /usr/bin/kwin_x11 ) -> puis Mageia 8 semble fonctionner correctement ... -> à chaque nouveau boot ; mème probleme : pas de fenetre login graphique -> j' ai essayé plusieurs solutions ... j' en ai trouvé une qui semble marcher sans problème ?? : après startx puis démarrage interface graphique : sous interface graphique standard (centre de controle de Mageia -> Démarrage ->Configurer le Gestionnire de connexion -> changer SDDM par XDM ... puis Reboot puis login avec le nouvel interface puis quelques commandes montrant que celà fonctionne .... puis restaurer SDDM : sous interface graphique standard (centre de controle de Mageia -> Démarrage ->Configurer le Gestionnire de connexion -> changer XDMS par XDM SDDM puis reboot et là miracle ?? l' interface graphique de Login est correcte comme dans la 7.1 et fonctionnel et Mageia 8 fonctionnent apparemment correctement et sans probleme ?? ... Conclusion : cette méthode d' installation marche ... mais fait un peu bidouillage ... contrairement à la 7.1 ... Tous commentaires sont les bienvenus ... Et merci à tous encore pour tout le travail complexe effectué pour Mageia ... Amicalement Rebonjour, Je vous ai dejà signalé les problèmes que j' ai eu hier avec l' installation de la version 8 32b ... J'ai recréé un DVD Install pour Mageia 8 32b , avec un autre lecteur de DVD USB Externe ... J' ai refait une installation avec le mème lecteur de DVD USB externe puis avec le lecteur de DVD interne du PC et obtenu les memes résultats ( pbs d' installation identiques ) ... En revanche , aujourd'hui , j' ai testé la version actuelle Mageia 8 LIVE 64b sur le mème PC avec le mème lecteur de DVD USB externe puis avec le lecteur de DVD interne du PC et sur un autre PC DELL Optiplex ... et elle est OK sur les deux PC , et marche sans probleme en mode live ( je n' ai testé que les fonctions de base de cette version .. Tous commentaires sont les bienvenus ... Et merci à tous encore pour tout le travail complexe effectué pour Mageia ... Amicalement Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Severity: normal => criticalKeywords: (none) => 8finalPriority: Normal => High
Thank you. I will just translate it in english for our installer developper. March 01, 2021 I am in charge of ten PCs, mainly DELL Optiplex 9010 7010 3090 + ... + Laptop etc ... On these PCs I installed, MAGEIA 7.1 with some PBs, but at the end I succeeded ... and the use + Update goes without problem ... I downloaded the MAGEIA 8 32b PLASMA version available yesterday (I checked the validation of the downloaded files ...) ... I carried out a first MAGEIA 8 32B installation on a DELL OPTIPLEX 9010 / I5 / 4G ram / 2x2TB dsk PC and I must say that I had a bit of trouble (several installations in a row which give the same results): -> with the DVD drive of the PC and an External USB DVD Drive (which I know is OK) ... -> unlike the MAGEIA 7.1 the installation seems to have to be done in 2 steps: 1st step: classic installation ... which ends after a rather long time with a stop; in a non-functional condition ... 2nd step: rereading the DVD Installation + reconfiguration then set "Mageia update" -> the installation then ending, in a classic way as for 7.1 ... then reboot request Etc ... On the other hand during reboot: the graphical interface of LogIn is not accessible ... only a login in a simple window like Bash is possible in this case ... If we launch, after login "startx", the graphical interface is launched correctly ... (but with crash of / usr / bin / kwin_x11) -> then Mageia 8 seems to work correctly ... -> at each new boot; same problem: no graphical login window -> I tried several solutions ... I found one that seems to work fine ?? : after startx then start the graphical interface: under standard graphical interface (Mageia control center -> Startup -> Configure Connection Manager -> change SDDM to XDM ... then reboot then login with the new interface then a few commands showing that it works .... then restore SDDM: under standard graphical interface (Mageia control center -> Startup -> Configure Connection Manager -> change XDMS to XDM SDDM then reboot and there miracle ?? Login GUI is correct as in 7.1 and functional and Mageia 8 apparently works fine and without problem ?? ... Conclusion: this installation method works ... but does a bit of hacking ... unlike 7.1 ... All comments are welcome ... And thank you all again for all the complex work done for Mageia ... Kindly Hello again, I have already reported to you the problems I had yesterday with the installation of version 8 32b ... I recreated an Install DVD for Mageia 8 32b, with another External USB DVD drive ... I remade an installation with the same external USB DVD drive then with the internal DVD drive of the PC and obtained the same ones results (identical installation pbs) ... On the other hand, today I tested the current version Mageia 8 LIVE 64b on the same PC with the same external USB DVD drive then with the internal DVD drive of the PC and on another DELL Optiplex PC ... and it is OK on both PCs, and works without problem in live mode (I only tested the basic functions of this version .. All comments are welcome ... And thank you all again for all the complex work done for Mageia ... Kindly
CC: (none) => mageia
Désolé d'apprendre vos problèmes. Soyez rassuré que nous teston les ISOs 32-bit. Je doute que pour l'instant votre situation est critique, parce-que M7 va continuer quelque temps encore. [Sorry for probs. Be assured we test 32-b ISOs. I doubt that your situation is at present critical because M7 will be around for some time] Pourquoi voulez-vous installer Mageia 32-b sur un système qui est sûrement 64 ?Et utiliser un DVD plutôt qu'une clé USB est curieux. Accepte que tout doit marcher quand même. [Why install a 32-b ISO on a 64-b system? Odd also to use DVD rather than USB. It should work, however] Quelque confusion : vous parler de "MAGEIA 8 32b PLASMA", ensuite "installation classique ... relecture du DVD Installation + reparamétrage puis set "Mise à jour Mageia" " qui suggère l'ISO Classic. Précisez lequel SVP. [Some confusion: talk of the Plasma 32-b ISO, then a 'classic' installation with 'update Mageia', which suggest the Classic ISO. Which one?] Vous dites que l'installation du Plasma [Live] 32-b a donné les problèmes ; a-t-il marché en mode Live ? Aussi, avez vous fait l'installation depuis le menu 'boot', ou le bureau 'live' ? [The problems came with installing Plasma [Live] 32-b: did it work in Live mode? Also, did you do the installation from the boot menu, or live desktop?] Par contre, vous dites que le Plasma 64-b marche OK en mode Live ; avez-vous essayé de l'installer ? [OTOH Plasma 64-b works OK in Live mode; have you tried installing it?] On va vous demander de fournir quelques logs d'installation, mais je dépende sur un collègue plus affuté pour préciser exactement lesquels. [We shall ask for installation logs, but depend on a more expert colleague to specify exactly which]
Severity: critical => majorCC: (none) => lewyssmith
Forgot to CC Aurélien & Martin.
CC: (none) => mageia, ouaurelien
I'm also confused by the reference to a 32-bit Plasma version, which does not exist. But from the description I think this was an install from the classical installer ISO, selecting Plasma as the DE. To know what goes wrong with the initial install, we need the log from that install. At the point at which the initial install stops, is it possible to switch to the debug console using Ctrl=Alt-F2? If so, insert a formatted USB stick and enter the command "bug" at the command prompt. That should write a file named "report.bug" to the USB stick. Compress the file (xz is best, but gzip or zip will do) and attach it to this bug report.
You are rigtht : From https://www.mageia.org/fr/downloads/ I choose : "Installation Classique" / "Architecture supportée" / 32 bit / Méthode de téléchargement : "Lien Direct" That give : .....Le téléchargement de Mageia 8 32bit .... Mageia-8-i586.iso https://www.mageia.org/fr/downloads/get/?q=Mageia-8-i586.iso then write this iso on a DVD on another Mageia 7.1 DELL OPTIPLEX PC ... Then install from the classical installer ISO (DVD), selecting Plasma as the DE. Be assured we test 32-b ISOs. I doubt that your situation is at present critical because M7 will be around for some time] OK I will stay On 7.1 Mageia ... Why Critical ? : For people who like and want mageia 8 , it is critical to be unable to do install ... [Why install a 32-b ISO on a 64-b system? Odd also to use DVD rather than USB. It should work, however] Why DVD ? : Because I have habit do do it ... Why 32b ? : Because I am developing Software for 32b ... Why Mageia Live 64b : Because Mageia Live 32b is not available ... For the time being , I have not tried to install Mageia 8 64b either from classic iso or from live 64b ... All my install are from classic iso from DVD ... I am sorry , but I did already at least 10 installs of Mageia 8 32b , and for the time being I have no more time to do another one to generate a new bug report. may be next week , if I have some spare time ... may be next week also , if I have some spare time , I will try an 32b install from this Mageia-8-i586.iso from USB Key ... But anyway the install problem is reproductible at each time ... easy to do for you ... try an 32b install from this Mageia-8-i586.iso from DVD ... regards
CC: (none) => fri
Lewis Smith 2021-03-03 20:11:46 CET [Sorry for probs. Be assured we test 32-b ISOs. I doubt that your situation is at present critical because M7 will be around for some time] Are you really sure that you have recently do an install with the last available Mageia-8-i586.iso ?? Could you che checks please and confirm ... Many thancks in advance .... regards
(In reply to Jean Claude PERRAUD from comment #6) > Lewis Smith 2021-03-03 20:11:46 CET > [Sorry for probs. Be assured we test 32-b ISOs. I doubt that your situation > is at present critical because M7 will be around for some time] > > Are you really sure that you have recently do an install with the last > available Mageia-8-i586.iso ?? Could you che checks please and confirm > ... Absolutely sure. QA test all ISOs before they are released. Many people have spent many hours doing this. We frequently get this complaint from users: it didn't work on my hardware so you can't have tested it. Do you realise how many variants of hardware are out there and how impossible it is to test that something will work everywhere? How many different machines have you tested and reproduced this fault on before making this accusation? But as you clearly won't believe us, I've just done a test with the final Mageia-8-i586.iso, burnt onto a DVD-R, and installed on real hardware, selecting the default Plasma DE install. It completed with no errors and rebooted straight to SDDM from where I could log into a working Plasma desktop. So, to have any chance of finding out why it is not working on your hardware, we need you to provide the requested information.
Status: NEW => NEEDINFO
i confirm that QA have tested all isos ( w/o any doubt ). Please do what martin ask because the bug is not reproducible by every one so he needs the debug infos to understand what can go wrong.
Hello , Sorry but I wonder if I didn't make noise about anything ... you convinced me to try again with a USB key and start the whole installation again from the USB key: here is exactly what I did again: 1- reload a new version of Mageia-8-i586.iso with Ktorrent ... 2 - check this new version with Mageia-8-i586.iso.md5 and Mageia-8-i586.iso.sha512 .... Result: OK compare this new file with the previous one with "cmp": identical 3- Copy Mageia-8-i586.iso onto a USB key (almost new + 16GB) with "dd" 4- redo the installation with this USB key on the PC ... 5- this 1st installation gives the same results as the previous ones with the DVD 6- I start a new installation with this USB key by writing the bug report: that is to say by writing at each step and noting the options chosen (a little time) and then the installation goes well until the end ... 7- I start a new installation with the DVD and then the installation goes well until the end ... 8- I start a new installation with the DVD and then the installation goes well again until the end ... I am very puzzled ... apparently I have random results with this PC ... This means that : -> mageia 8 32b is not involved ... -> and that I must expect a Hardware failure on an element of this PC ... I continue my tests, but I have the impression of having made a lot of noise for nothing ... I'm really really sorry to have wasted your time ... Thank you again for your support friendly
@Jean Claude, You're welcomed. Don't be sorry, sometimes, in french, we say: "L'erreur est humaine..." (English: Make errors is human). But, in this case, this seems some hardware failure. Feel free to repoen this, if you do see a bug somewhere, notably in Installer by doing this: - provide the file /root/drakx/report.bug.xz as an attachment? If you don't have the file, in Installer, you can switch to console 2 (by pressing 'Ctrl-Alt-F2') during installation, plug a USB key/stick and type: 'bug' then press Enter. It will put report.bug on the key.
Status: NEEDINFO => RESOLVEDKeywords: (none) => NEEDINFOResolution: (none) => WORKSFORMEPriority: High => NormalSeverity: major => normal
Jean, it is very good you report problems - thank you. You may one day find something we can improve. Especially susceptible is that it failed on several of your systems. The installer do write an install log, and i have learned it is good to save it per instructions in comment 4 before rebooting - even when it looks like everything went well it may not boot ;) and then it is good to see in that file what happened during install, for you and for bug hunters. And of course do so in case where it looks like problems during install. The install log is also reachable when the installed system is running. In the installer boot menu you have the option to start memory test. You may like to run that over night. For me it have also found CPU fault. You may also want to check hard disk S.M.A.R.T status. If you want to check compatibility without installing, try a Live ISO.
(Mid air collision)
Also keep in mind that even if the downloaded iso is correct and correctly burnt to a dvd, the dvd reader may not work correctly all of the time. Being a heavy smoker, a dvd reader in my system would typically last at most 18 months before it would have random read errors on a dvd that worked ok in other systems. Optical media and hardware should not be considered reliable. Because of that I only use usb drives for real hardware installs, and only use the dvd functionality of the iso images when testing them under virtualbox.
CC: (none) => davidwhodgins
@Jean Claude > Je suis en charge d' une dizaine de PC > j' ai installé MAGEIA 7.1 avec quelques PBs, mais à la fin j'ai réussis Perhaps when we get to testing Mageia 9, you might like to join the ISO testing group. Your experience - especially the 32-bit aspect, and use of DVD - would be helpful.
Why not ? I am not a expert of everything on Mageia ... mainly , I was developing Electronic cad software using Mageia ( previously Mandrake ...) What I could do is only to test installing progress and compatibility ... Etc ... I have time because I am retired ... "join the ISO testing group" ?? Why not ? Wat I have to do and when ??
You are much welcome :) Next ISO testing, for Mageia 9, is a year ahead though, but you may like to be in QA team, using mailing list "qa-discuss", where it will be announced and discussed, more info at https://wiki.mageia.org/en/QA_ISO_testers Also see: https://wiki.mageia.org/en/Contributing https://wiki.mageia.org/en/Mailing_lists https://wiki.mageia.org/en/Mageia_IRC_Channels You may join more than one team or only lists of course - i work in QA but also "listen to" and sometimes input to dev and doc lists.
> Why not ? > I have time because I am retired Idéal. Certes, pourquoi pas ? > What I have to do > What I could do is only to test installing progress and compatibility https://wiki.mageia.org/en/Pre-release_ISO_testing https://wiki.mageia.org/en/Pre-release_ISO_testing:_Part_2 You do not have to be expert in anything. The main aim is to ensure the different ISOs install and then work OK. Si vous trouvez de problèmes en route, ils doivent être corrigé en route.
CC: lewyssmith => (none)
Sorry to come back to my previous message , but in in fact I did some other install of Mageia 8 32b on other PC's On some , it was OK ... but on one other : a PC Tower ACER I7 4Go ram , 2To Dsk ( Dual Boot : Windows 10 + Mageia 8 32b ) I found exaxtly the same results but in thes new install I used an USB Key instead of DVD Reader as source for Mageia 8 standard iso ... I did , for the time being , 2 install on this PC Tower ACER giving exactly the same result... (install is done using french ...) You ask me : "At the point at which the initial install stops, is it possible to switch to the debug console using Ctrl=Alt-F2? If so, insert a formatted USB stick and enter the command "bug" at the command prompt. That should write a file named "report.bug" to the USB stick. Compress the file (xz is best, but gzip or zip will do) and attach it to this bug report" but in fact it looks not possible , because it stop , only after automatic rebooting , after end of installing process... Every thing looks OK before : Page that set : Pass Root .......... set Users Icone nom et prénom Id de connexion passwd advanced then some time loop Skiping all other standard steps ... some messages displayed whithout stoping ...Looks to be the standard message of install ... then automatic reboot and failed with the following messages when rebooting : "error: ../../grub-core/fs/fhelp.c:257:file '/boot/grub2/i386-pc/normal.mod' not found/ Entering rescue mode... grub rescue> Then what I do is to as I mentionned previously, I Reinstall Mageia 8 (option 32b iso) with Update option... As I describe it previously ... untill that works ... for your info , in this case the user's name is "perraud" /home/perraud (group users 800Mo used/ on 1.2To partition) So I restart another Install with the same USB Key : same options but other user name ( new one's not existing on /home ...) But I choose to create a new users "atelecad" instad of "perraud" ( new directory created by install on /home ...) and in this case All step of Install works OK ... Rebooting is OK too ... And , then I am able to complete the install for other users "perraud" etc ... Aparently , Install bug com's from existing user's or existing Directory ?? Any comment are welcome
Resolution: WORKSFORME => (none)Status: RESOLVED => REOPENED
Existing user should be imported as long as they have the same short name. Do these PC are UEFI or BIOS-only? What about partitions-mode: GUID or MBR? (In reply to Jean Claude PERRAUD from comment #19) > > "error: ../../grub-core/fs/fhelp.c:257:file '/boot/grub2/i386-pc/normal.mod' > not found/ > Entering rescue mode... > grub rescue> This is unrelated to using pre-existing user account.
Keywords: 8final, NEEDINFO => (none)
(In reply to Jean Claude PERRAUD from comment #19) > then automatic reboot and failed with the following messages when > rebooting : > "error: ../../grub-core/fs/fhelp.c:257:file '/boot/grub2/i386-pc/normal.mod' > not found/ > Entering rescue mode... > grub rescue> As /usr/lib/grub/i386-pc/normal.mod is copied to /boot/grub2/i386-pc/ during grub install, is the filesystem used for /boot full?
"Do these PC are UEFI or BIOS-only?" ************************************ PC's with bugs are almost old DELL OPTIPLEX and are BIOS-only , I presume ... "What about partitions-mode: GUID or MBR?" ****************************************** I am not sure ... How to answer ??As /usr/lib/grub/i386-pc/normal.mod is copied "to /boot/grub2/i386-pc/ during ******************************* grub install, is the filesystem used for /boot full?" **************************************************** How to answer ?? I am not sure ?? What I know is that I use rather big partition for "/" , around 40Go and they is a lot of room left ... Please give me the ways ( Unix command to answer your questions and I will do ... Sorry , I am not an System expert ... Mainly , I am only developing CAD Software ...
(In reply to Jean Claude PERRAUD from comment #22) > "Do these PC are UEFI or BIOS-only?" > *********************************** Under Linux, $ ls /sys/firmware/efi If it exists and non-empty, this is a Booted UEFI system. On Windows, “System Information” in Start panel and under BIOS Mode, you can find the boot mode. If it says Legacy, your system has BIOS. If it says UEFI, well it’s UEFI. > "What about partitions-mode: GUID or MBR?" > ****************************************** Become root and do: # gdisk -l /dev/sda If the output of the above command shows like this,then you have MBR disk, Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present If the output shows like this then you have GPT disk, Partition table scan: MBR: protective BSD: not present APM: not present GPT: present > "to /boot/grub2/i386-pc/ during > ******************************* > grub install, is the filesystem used for /boot full?" > **************************************************** > > How to answer ?? I am not sure ?? > What I know is that I use rather big partition for "/" , around 40Go and > they is a lot of room left ... To tell if /boot folder is in a separate partition from "/" root: $ df -h Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur devtmpfs 7,8G 76K 7,8G 1% /dev tmpfs 7,8G 145M 7,7G 2% /dev/shm tmpfs 7,8G 1,4M 7,8G 1% /run /dev/nvme0n1p3 174G 9,4G 156G 6% / /dev/nvme0n1p2 4,9G 168M 4,5G 4% /boot /dev/nvme0n1p1 299M 1,7M 297M 1% /boot/EFI tmpfs 7,8G 12K 7,8G 1% /tmp /dev/sda2 1,3T 1,1T 211G 84% /home /dev/sda4 384G 6,3G 358G 2% /var tmpfs 1,6G 972K 1,6G 1% /run/user/1000 This displays registered partitions and filesystems necessary to boot your Linux OS, usage and left empty space. In the above example, you can see /, /boot, /boot/EFI and /home separated partitions. > Sorry , I am not an System expert ... Mainly , I am only developing CAD > Software ... Don't worries, you're welcomed.
(In reply to Aurelien Oudelet from comment #23) > (In reply to Jean Claude PERRAUD from comment #22) > > "Do these PC are UEFI or BIOS-only?" > > *********************************** > Under Linux, > $ ls /sys/firmware/efi > If it exists and non-empty, this is a Booted UEFI system. To determine if the system has been booted in bios firmware mode but is capable of booting in uefi mode ... /sys/firmware/efi must not exist, i.e. booted in bios firmware mode. Use the command "lshw -class memory". In the *-firmware section, the capabilities: tag shows what the system firmware can do. If it includes the string "uefi", then it is capable of booting in uefi mode. On one of my systems ... # lshw -class memory|head -n 9 *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 1604 date: 10/16/2012 size: 64KiB capacity: 4032KiB capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi So this 9 year old system can boot it uefi mode. # ls -l /sys/firmware total 0 drwxr-xr-x 5 root root 0 Mar 16 03:46 acpi/ drwxr-xr-x 3 root root 0 Mar 16 06:42 dmi/ drwxr-xr-x 8 root root 0 Mar 16 03:54 edd/ drwxr-xr-x 27 root root 0 Mar 17 17:21 memmap/ but has been started in bios firmware mode. I don't use uefi mode as it requires manual intervention at every boot to select uefi firmware mode, with no way (that I've been able to find) to have it default to uefi firmware mode.
Hello , In fact, on my 10 pc, I have 5 Dell Optiplex 3090, 7010, 9010, 3010 ... Some with 4GB, or 6GB or 8GB RAM ... All with 2 discs ( almost new ) ... some 1to + 2TB, or some 2x2to ... While using the "legacy" option in the BIOS of all these PCs ... 2 out of 5 have this bug ... In Mageia 7.1 "perraud" user is defined and /home/perraud is mount on the 2nd disk 2To sdb ( around 800 Mo used on 1.2To ) / partition is pretty large around 40 Go in 1rst disk sda , because I have pretty room on this disk ... Windows + Mageia ... But despite the bug, I always succeed to install Mageia 8 ( when this bug previously happened ) with the following new install method : During Mageia 8 installation process using "perraud" user : I only use and set the first dsk ( sda ) , custom partitions ... So "perraud" user is NEW in this case , and defined on 1rst disk , so a new /home/perraud is created on sda This way work all the time ... and Mageia 8 is installed OK completly .. Then when rebooting , I may complete the Mageia 8 installation , using graphical standard interface : setting the /home/perraud on this real place ( on sdb dsk ) and saving this in /etc/fstab ... reset all users etc... and with "chown -R xxx" set the rigths on dir etc... Now cmd results to answer your questions on the 1rst Bugged PC's ( now OK ) using Mageia 8 32b : # ls /sys/firmware/efi ls: impossible d'accéder à '/sys/firmware/efi': Aucun fichier ou dossier de ce type # gdisk -l /dev/sda GPT fdisk (gdisk) version 1.0.6 Warning: Partition table header claims that the size of partition table entries is 12255407 bytes, but this program supports only 128-byte entries. Adjusting accordingly, but partition table may be garbage. Warning: Partition table header claims that the size of partition table entries is 0 bytes, but this program supports only 128-byte entries. Adjusting accordingly, but partition table may be garbage. Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. *************************************************************** Disk /dev/sda: 3907029168 sectors, 1.8 TiB Model: WDC WD20EZRZ-00Z Sector size (logical/physical): 512/4096 bytes Disk identifier (GUID): A0DF9630-51E4-4045-8ADE-68D9E254F910 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 3907029134 Partitions will be aligned on 2048-sector boundaries Total free space is 21110 sectors (10.3 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 206847 100.0 MiB 0700 Microsoft basic data 2 206848 1023012698 487.7 GiB 0700 Microsoft basic data 3 1023012864 1023997951 481.0 MiB 2700 Windows RE 5 1024002048 1136839724 53.8 GiB 8300 Linux filesystem 6 1136842752 1164278744 13.1 GiB 8200 Linux swap 7 1164281856 1990855124 394.1 GiB 8300 Linux filesystem 8 1990858752 3907024064 913.7 GiB 8300 Linux filesystem # df -h Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur devtmpfs 2,0G 0 2,0G 0% /dev tmpfs 2,0G 95M 1,9G 5% /dev/shm tmpfs 2,0G 1020K 2,0G 1% /run /dev/sda5 53G 6,7G 44G 14% / tmpfs 2,0G 56K 2,0G 1% /tmp /dev/sda1 100M 32M 69M 32% /media/win_c /dev/sdb6 1,7T 974G 734G 58% /home /dev/sdb1 115G 61M 109G 1% /work1 /dev/sda3 481M 407M 75M 85% /media/win_ /dev/sda8 899G 77M 853G 1% /local_users1 /dev/sda7 387G 61G 308G 17% /users /dev/sda2 488G 52G 437G 11% /media/win_d tmpfs 394M 132K 394M 1% /run/user/1000 # lshw bash: lshw : commande introuvable # ls -l /sys/firmware total 0 drwxr-xr-x 5 root root 0 mars 18 12:53 acpi/ drwxr-xr-x 2 root root 0 mars 18 12:53 devicetree/ drwxr-xr-x 3 root root 0 mars 18 12:53 dmi/ drwxr-xr-x 4 root root 0 mars 18 12:53 edd/ drwxr-xr-x 24 root root 0 mars 18 12:53 memmap/ any comments are welcomed ... you're welcomed.
Hello , I have some comments + questions : 1- this bug happen only when we install using existing users ( with existing groups ) in /home/UserName No bug when using new users and new group for this users are used ... 2 - what happen with existing dir and files with their existing owner and right ( RWX ) not compatible with the ways of installation script ?? If not compatible there is a Error code that is generated ?? ... what happen then ?? ... part of the scirpt does not go complete all installation ?? 3- I am quasi sure that a command such as "chown -R /home/UserName" is not done !! from my poiny of view this command should be done in order that everything is consistant for user "UserName" ... 4- For a NEW user the groups "GroupName" are created by the PERL script for "UserName" And so it easy to add in the script a new command such as " : chown -R UserName:GroupName /home/UserName" 5-for an already existing user : "UserName" , so "/home/UserName" exists already , whith group : 5-1 if new group is created "UserName" : echo $UserName -> "UserName" chown -R $UserName:$UserName /home/$UserName" has to be done ... 5-2 or you may detect the existing group Id with such commands as : GroupId=` grep -i $UserName /etc/group | awk -F ":" '{print $3}' ` or GroupId=`id -u $UserName ` or GroupName= `id -ng $UserName ` and then executes a new command such as " : chown -R $UserName:$GroupName /home/UserName" Then all use and copy of files in "/home/UserName" will be normaly consistant an normaly no error codes will be generated ... any comments are welcomed ... you're welcomed.
OK. Mageia 8 can install itself without error with an empty /home directory. That's fine. There is errors if there is a user directory named "perraud" in /home like /home/perraud That's ugly. Hum. These computers should be installed in past with a Mageia version when the first userID had a number 500. Currently we ship Mageia with a first user ID at 1000. Perhaps Installer can't handle such situation. Do you make an upgrade or a new installation in Installer?
Hello, to try to understand a little more I would like to umcompress the stag2 perl script in a directory ... I try to follows : "https://wiki.mageia.org/en/Drakx-installer_tips_and_tricks" but as I already said : Sorry , I am not an System expert ... So I try the following command and I did not succeed : (some other commands are probably missing ??) ( I try first to get the script of the 7.1 version to understand on my prefer PC's that is still using Mageia 7.1 version ) So my list of commands that I have executed : # su ..... # mkdir /export # mount -o loop /home/perraud/Dir-Mageia/Mageia-7.1/Mageia-7.1-i586.iso /exportmount: /export: /home/perraud/Dir-Mageia/Mageia-7.1/Mageia-7.1-i586.iso est déjà monté. # cd /export # ll total 11 -rw-r--r-- 1 501 501 80 mai 27 2011 autorun.inf drwxr-xr-x 1 501 501 2048 juil. 12 2019 boot/ -r--r--r-- 1 501 501 2048 juil. 12 2019 boot.catalog -rw-r--r-- 1 501 501 30 juil. 12 2019 DATE.txt drwxr-xr-x 1 501 501 2048 mai 27 2011 dosutils/ drwxr-xr-x 1 501 501 2048 juil. 12 2019 EFI/ drwxr-xr-x 1 501 501 2048 juil. 12 2019 i586/ # cd i586 ll total 310 drwxrwxr-x 1 501 501 2048 mars 14 2012 doc/ drwxr-xr-x 1 501 501 2048 juil. 12 2019 install/ drwxr-xr-x 1 501 501 2048 juil. 12 2019 media/ drwxr-xr-x 1 501 501 2048 juin 23 2019 misc/ -rw-r--r-- 1 501 501 211006 juil. 12 2019 package.idx -rw-r--r-- 1 501 501 113 juil. 12 2019 product.id -rw-r--r-- 1 501 501 58627 juil. 12 2019 release-notes.html -rw-r--r-- 1 501 501 37819 juil. 12 2019 release-notes.txt -rw-r--r-- 1 501 501 47 juil. 12 2019 VERSION # misc/mdkinst_stage2_tool --uncompress install/stage2 Creating install/stage2/live from install/stage2/mdkinst.sqfs Parallel unsquashfs: Using 4 processors 3543 inodes (5022 blocks) to write dir_scan: failed to make directory install/stage2/live, because Read-only file system [| ] 0/5022 0% created 0 files created 0 directories created 0 symlinks created 0 devices created 0 fifos So is there somebody that may help me ?? any comments are welcomed ... you're welcomed.
(In reply to Aurelien Oudelet from comment #27) > OK. > > Mageia 8 can install itself without error with an empty /home directory. > That's fine. > > There is errors if there is a user directory named "perraud" in /home like > /home/perraud > That's ugly. > > Hum. These computers should be installed in past with a Mageia version when > the first userID had a number 500. > > Currently we ship Mageia with a first user ID at 1000. Perhaps Installer > can't handle such situation. Do you make an upgrade or a new installation in > Installer? as I already said : "Sorry , I am not an System expert" your question "Do you make an upgrade or a new installation in Installer?" what do you means ?? does you means ?? : does you make any change or update in the available in the Mageia-8-i586.iso ?? Off course not ... I am not enouch competent to do that ?? see my previous message ... I would like to understand more on Install script of stage2 , but now I does not know how to get and see this perl script .. any comments are welcomed ... you're welcomed.
(In reply to Jean Claude PERRAUD from comment #28) > Hello, > > to try to understand a little more I would like to umcompress the stag2 perl > script in a directory ... > > I try to follows : > > "https://wiki.mageia.org/en/Drakx-installer_tips_and_tricks" > > but as I already said : Sorry , I am not an System expert ... > > So I try the following command and I did not succeed : > (some other commands are probably missing ??) > > ( I try first to get the script of the 7.1 version to understand on my > prefer PC's that is still using Mageia 7.1 version ) > > So my list of commands that I have executed : > > > # su > ..... > > # mkdir /export > > # mount -o loop /home/perraud/Dir-Mageia/Mageia-7.1/Mageia-7.1-i586.iso > /exportmount: /export: > /home/perraud/Dir-Mageia/Mageia-7.1/Mageia-7.1-i586.iso est déjà monté. > > # cd /export > # ll > total 11 > -rw-r--r-- 1 501 501 80 mai 27 2011 autorun.inf > drwxr-xr-x 1 501 501 2048 juil. 12 2019 boot/ > -r--r--r-- 1 501 501 2048 juil. 12 2019 boot.catalog > -rw-r--r-- 1 501 501 30 juil. 12 2019 DATE.txt > drwxr-xr-x 1 501 501 2048 mai 27 2011 dosutils/ > drwxr-xr-x 1 501 501 2048 juil. 12 2019 EFI/ > drwxr-xr-x 1 501 501 2048 juil. 12 2019 i586/ > > # cd i586 > ll > total 310 > drwxrwxr-x 1 501 501 2048 mars 14 2012 doc/ > drwxr-xr-x 1 501 501 2048 juil. 12 2019 install/ > drwxr-xr-x 1 501 501 2048 juil. 12 2019 media/ > drwxr-xr-x 1 501 501 2048 juin 23 2019 misc/ > -rw-r--r-- 1 501 501 211006 juil. 12 2019 package.idx > -rw-r--r-- 1 501 501 113 juil. 12 2019 product.id > -rw-r--r-- 1 501 501 58627 juil. 12 2019 release-notes.html > -rw-r--r-- 1 501 501 37819 juil. 12 2019 release-notes.txt > -rw-r--r-- 1 501 501 47 juil. 12 2019 VERSION > > # misc/mdkinst_stage2_tool --uncompress install/stage2 > Creating install/stage2/live from install/stage2/mdkinst.sqfs > Parallel unsquashfs: Using 4 processors > 3543 inodes (5022 blocks) to write > > > dir_scan: failed to make directory install/stage2/live, because Read-only > file system > [| > ] 0/5022 0% > > created 0 files > created 0 directories > created 0 symlinks > created 0 devices > created 0 fifos > > > > > So is there somebody that may help me ?? > > > any comments are welcomed ... > > > you're welcomed. In fact , I just found how to get the Installation Perl file that I want to see : # mkdir /export # mount -o loop /home/$UserName/Dir-Mageia/Mageia-7.1/Mageia-7.1-i586.iso /export # cd /export/i586/misc ll total 16 drwxr-xr-x 1 501 501 2048 juin 23 2019 . drwxr-xr-x 1 501 501 2048 juil. 12 2019 .. -rwxr-xr-x 1 501 501 9696 juil. 12 2019 drakx-in-chroot -rwxr-xr-x 1 501 501 1591 juil. 12 2019 mdkinst_stage2_tool # Perl file of Installation ########################## # nedit drakx-in-chroot & # Auxiliary Perl file of Installation ##################################### # nedit mdkinst_stage2_tool any comments are welcomed ... you're welcomed.
(In reply to Jean Claude PERRAUD from comment #29) > "Do you make an upgrade or a new installation in Installer?" The installer probably asked early in the process if it should upgrade the present Mageia 7 installation, or do a fresh install. (I dont remember the wording). Which did you choose? Please keep your posts a bit shorter where possible, i.e you can type " Referring to comment 26 " Instead of copying all that text. :)
(In reply to Aurelien Oudelet from comment #27) > OK. > > Mageia 8 can install itself without error with an empty /home directory. > That's fine. > > There is errors if there is a user directory named "perraud" in /home like > /home/perraud > That's ugly. > > Hum. These computers should be installed in past with a Mageia version when > the first userID had a number 500. > > Currently we ship Mageia with a first user ID at 1000. Perhaps Installer > can't handle such situation. Do you make an upgrade or a new installation in > Installer? Always I start by a new installation ... as the 1rst step ... I do an upgrade only when there is the bug as a second step , after rebooting , to complete Mageia 8 installation ... By the way I got the Source of Stage 1 ... And probably the bug is in a perl scripts part of Stage1 ... I believe I saw some parts where Users and Group are processed ... but very big and too complicate for knowledge ... Good luck ...
Stage 1 is a very minimal system whose sole purpose is to locate and mount the compressed stage 2 root file system contained in the mdkinst.sqfs file. Stage 1 is written in C, not Perl. It only mounts the file system on the install media (DVD or USB stick), so can't be affected by your existing home directory. To unpack the stage 2 file system, copy the mdkinst.sqfs file to a writable location first, e.g. mkdir -p ~/tmp cp /export/i586/install/stage2/mdkinst.sqfs ~/tmp /export/i586/misc/mdkinst_stage2_tool --uncompress ~/tmp which will unpack the stage 2 file system into ~/tmp/live. That is a complete Linux root filesystem. The installer Perl scripts can be found in ~/tmp/live/usr/lib/libDrakX/install. Alternatively you can browse the installer source files here: https://gitweb.mageia.org/software/drakx Select the "tree" tab and navigate to perl-install/install. If I understand you correctly. the installer is failing after you leave the User Management dialogue but before you reach the next dialogue (which would normally be either the graphics card or monitor selection). First, can you capture the installer logs (as described in comment 4) before leaving the User Management dialogue and attach them here, so we at least have some information to go on. Second, after leaving the User Management dialogue, immediately press Ctl-Alt-F3, and you should see the installer debug messages. Try to spot what is the last message before the machine reboots (a camera helps here). Note that on my machines I always do a clean install whilst reusing my existing home directory, and I know at least one of the QA team does the same. Neither of us has hit this bug. And I have just done a test using the Mageia-8-i586 ISO with / and /home on different disks, and again failed to reproduce this bug.
Created attachment 12483 [details] report-Mageia8-32b-DVD-Bug28517-2021-03-03--17-26-Jean-Claude-PERRAUD-done-21mars20121 Command "bug" done after Install page Interactive step : Set Root password ( 2 x ) Set User's Data : Complete Name + Surname Connexion name Connexion Password ( 2 x ) Cntrl+ Alt+ F2 then typed : " # bug "
To sum up: - Mageia 8 32bits installs well with / and /home formatted. - Mageia 8 32bits does not want to install while keeping /home with a /home/perraud directory AND user want a new install (format /) rather upgrading existing installation. I suspect an old userID involved (500 or 501...). On such systems, it should be useful to have the content of /etc/passwd to see the userID of the first user... - I can't reproduce with a /home with whatever I left here owned by a user with a userid >1000. Modifying title. Assigning to Mageia Tools maintainers. Thanks @Jean Claude for files in Comment 34.
Assignee: bugsquad => mageiatoolsStatus: REOPENED => NEW
Summary: Mageia-8-i586.iso 32b probleme Installation => Mageia-8-i586.iso Bogus handling of existing folder with a userid of 500 instead of 1000 in /home
I tested with an existing user/group ID of 500/500 and couldn't reproduce the fault. Reading the attached bug file, I find this comment at the end: ============================================================== I make this install today 2 times again : ( be aware that I start now from an Mageia 8 32b completly , and correctly installed ?? Ram 4Go 2 disks : 2 x 2To ( almost new ) Video Card : GK 2088 ( Geforce GT 710 ) Driver : Geforce 420 to 630 -> "nvidia" user : "perraud" id 1000 group of "perraud" id 100 1rst- New install using an USB key : so 2 keys in 2 USB inputs: -> Install : key sdc1 -> Bug key : key sdc2 -> it was impossible to generate the bug file : ( on sdc2 ) when executing "# bug" it write an error "file system unknown" and after I got the same bug as mentionned in "Comment 1 " New install using an DVD standard Reader : so 1 keys in 1 USB inputs: -> Bug key : key sdc1 -> it was now possible to generate the bug file : ( on sdc1 ) when executing "# bug" it write NO error but bug file on key ... and after in this case the install go on correctly untill the end ( All OK with all correct interactive step of install ... ) So I would say : in the 1rst New Install (using USB key ) -> BUG !!! in the 2nd New Install (using DVD ) -> NO BUG !!! with the same hardware ... same conditions , same options ... ============================================================== So a) The existing user ID is 1000. It says the group ID is 100, but I suspect that is a typo. b) This is an intermittent fault. So I still suspect it's a hardware problem. Without having a way to reproduce this or knowing exactly where the installer is failing, there's little more I can do. BTW, /dev/sdc2 was the second partition on the installer USB stick (the ESP, for UEFI boot), which is why the "bug" command couldn't write to it. The second USB stick should have appeared as /dev/sdd.
Summary: Mageia-8-i586.iso Bogus handling of existing folder with a userid of 500 instead of 1000 in /home => Mageia-8-i586.iso intermittent installer failure causing machine to reboot
(In reply to Martin Whitaker from comment #36) > So > > a) The existing user ID is 1000. It says the group ID is 100, but I suspect > that is a typo. NO it was not a typo : In my last 2 new Installation , I start from a Mageia 8 installed system ... looking correctly installed ?? then I have check before , and I confirm The existing user ID was 1000. It says the group ID was 100 ... I Just check again on another Dell OPTIPLEX 3010 PC's and I exec the following commands : ( still using an full updated Mageia 7.1 version ...) id -u perraud 1000 id -g perraud 100 id -G perraud 100 id -nu perraud perraud id -ng perraud users > b) This is an intermittent fault. So I still suspect it's a hardware problem. > Why not ?? But , strange : 1- I did a lot of new installations and NEVER this bug happen when no existing "perraud" users exists already before all the new installations ( /home/perraud is not mounted as option inthis case when setting the Installations partitions ...So , then a new "perraud" users is created that uses a new /home/perraud ...) on the 1rst Bugged PC's and on the other Bugged PC's (starting from Mageia 7.1 and Mageia 8 ... ?? ) 2- this exactly same bug happen , exactly the same behaviour all the time , when bug ang No bug , with some other PC's ... strange for hardware problem ?? I am sorry , but I do not believe that ... Remember that I have already more than 30 new Mageia8 Installation, for testing ... > BTW, /dev/sdc2 was the second partition on the installer USB stick (the ESP, > for UEFI boot), which is why the "bug" command couldn't write to it. The > second USB stick should have appeared as /dev/sdd. I allways use "Legacy" on this PC's , and not UEFI ... For the 1rst new Bugged Installation : IN the list of /dev/xx : sdc1 and sdc2 was listed but not sdd ... when "bug" command was executed ... For the next 2nd OK new Installation : "bug" command was executed without problem , and that give the file report.bug that I have posted ...
A group ID of 100 for a user is unusual. AFAIK IDs below 500 have always been reserved for system groups. I know you use legacy boot, but that doesn't remove the second partition from the installer USB stick, so the Linux kernel will detect it and assign it to /dev/sdc2 (assuming the USB stick has been assigned to /dev/sdc). The Linux kernel will *never* assign one device to /dev/sdc1 and another device to /dev/sdc2. If there was no /dev/sdd1, your second USB stick wasn't detected. You say "this exactly same bug happen , exactly the same behaviour all the time" and yet you have just reported one failed install and one successful install on the same machine with the same ISO and with the existing "perraud" user - the only difference being using a DVD instead of a USB stick. Yet you have previously reported the same failure when using a DVD. And you report it only occurs on some machines, not all. Unless you can find a way to reliably reproduce this fault on any machine, we are reliant on you to do further detective work. As suggested in comment 33, watching the messages output on VT3 (seen when you press Ctrl-Alt-F3) might give some clues. If your phone can record video, that is the best way to capture the messages. I can't do this for you - I can't reproduce the fault.
Hello , Again , I did more 30 new installations of Mageia 8 , for 10 PC's ... I have found a way that work all the time ... My Test program shows that Mageia 8 is OK and work well ... For me that is finish ... That is Suffisant ... I made a lot of test , and I have let you a Bug report ... If somebody else got the same bug , you may inform them the workaround ... Again , many thancks for all the work done by mageia team ... kind regards