Description of problem: Once the installer tries to access my existing MBR partitions on an SATA drive, it gives this error: I cannot read the partition table of device sda, it's too corrupted for me :( I can try to go on, erasing over bad partitions (ALL DATA will be lost!!). The other solution is to not allow DrakX to modify the partition table. (the error is Can't locate Time/HiRes.pm in @INC (you may need to install the Time::HiRes module) (@INC contains: /usr/lib/libDrakX /usr/local/lib64/perl5/5.32 /usr/local/share/perl5/5.32 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5). ) Do you agree to lose all the partitions? < Yes > < No > This is a pretty dangerous failure mode as an inattentive user could easily erase all his data. Version-Release number of selected component (if applicable): md5sum of install iso: ade337db66b90e5307fc8bc6bba4a3ca Mageia-8-x86_64.iso How reproducible: It happened every time I tried to install on this machine. Steps to Reproduce: Unfortunately, I didn't file this bug right away so I've forgotten the exact details of how it got into this state. But, it was during the partitioning stage in the DVD installer, likely after going into advanced mode. In any case, the use of and missing Time/HiRes.pm in the install image should be pretty easy to verify.
> my existing MBR partitions on an SATA drive This needs more background information to pursue. Were you trying to install to a machine with a working system on it? If so, what system? Is it a BIOS (not EFI) machine? It looks as if you are using the 'Classic' installer. Can you try one of the 'Live' ISOs (Xfce is the smallest)? We shall want system details, either via the existing working system (if there is one), or from a Live session. What was your intention for the new installation: leave & use the existing partitions? Re-partition part of the disc? Re-partition it entirely?
CC: (none) => lewyssmith
It's an EFI machine with BIOS compatibility, and has an existing mga7 x86 installation on it. I was booting with EFI to install mga8 x86_64 onto a new NVM drive, so the existing partitions on the SATA drive weren't even that relevant to the install (except for dual-booting). I was able to complete the installation eventually (the details on how I did so are now hazy after a few weeks) but since I captured this error message with a (presumably) simple fix I figured I'd report it. If it helps, I could try to reproduce it on the installed system.
The module is located at /usr/lib64/perl5/Time/HiRes.pm $ rpm -q -f /usr/lib64/perl5/Time/HiRes.pm perl-5.32.1-1.mga8 $ md5sum Mageia-8-x86_64.iso ade337db66b90e5307fc8bc6bba4a3ca Mageia-8-x86_64.iso So there is no obvious cause for the error and others have not reported it that I've noticed. The question becomes why did it fail to read that perl module on that system. Without being able to recreate it, I don't see a way to debug it. If you can recreate it, as soon as the error shows up, use Ctrl+Alt+F2 to switch to a terminal. Mount a writable partition (or find one that's already mounted) and save the output and enter the command "bug" (without the quotes) to create a text file to attach to this bug report.
CC: (none) => davidwhodgins
CC: (none) => ouaurelienStatus: NEW => NEEDINFO
(In reply to Dan Fandrich from comment #2) > It's an EFI machine with BIOS compatibility, and has an existing mga7 x86 > installation on it. I was booting with EFI to install mga8 x86_64 onto a new > NVM drive, so the existing partitions on the SATA drive weren't even that > relevant to the install (except for dual-booting) Thank you for these notes. I would not be surprised if the problem did not come from here: "with BIOS compatibility". Does this mean that you you have/had so-called 'compatibility mode' set in the Firmware? If you have still, booting must be from the MBR disc. If you want to install Mageia 8 as a proper EFI setup on the NVM device, and boot to that, the Firmare must be set to EFI. Were you using BIOS/MBR mode for Mageia 7, but are aiming for EFI/GPT for the new NVM drive? It is never a good idea to mix these; and as for booting from one to the other, I am unsure. Do you want to be able to dual boot between M8 on the NVM (GPT?) drive, and M7 on the MBR disc? Whichever one actually does the initial boot must be able to boot the other; an interesting exercise for Grub2. And I wonder whether an MBR installed Linux can be booted by rEFInd. To tell us about the system, please post the O/P of: $ inxi -MSpoDxx plus #fdisk -l /dev/sd... for both discs.
Please remember that a bios system can use either mbr or gpt partitioned drives or a mix of both, provided the bios recognizes the drive (old systems will not recognize nvme drives). Their are some uefi systems with broken firmware that can only boot from a gpt drive, but can still have mbr partitioned drives used in addition to the gpt boot drive. Other then that, any uefi system can use either mbr or gpt partitioned drives or a mix of both. There is false info circulating that uefi requires gpt. That is not true. Mixing uefi and bios installs on the same system is the only thing that is not recommended. It may work or may not depending on the uefi firmware, and is hard to debug when problems do show up. Dan, the inxi and fdisk may help in figuring out why it isn't working on that system and help us to provide an update so future versions of the installer do work. Please provide the requested info.
@Dan Is this still an issue, or can we close it?
@Dan Is this still an issue, or can we close it? If you do not reply within 7 days, we will assume the issue no longer troubles you, and close the bug. Also, note that Mageia 9 is newly released, and what this should be about if the issue persists.
Closing.
Status: NEEDINFO => RESOLVEDResolution: (none) => OLD