diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-discuss/2012-July/008199.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-discuss/2012-July/008199.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/2012-July/008199.html | 313 |
1 files changed, 313 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/2012-July/008199.html b/zarb-ml/mageia-discuss/2012-July/008199.html new file mode 100644 index 000000000..46ea2b88b --- /dev/null +++ b/zarb-ml/mageia-discuss/2012-July/008199.html @@ -0,0 +1,313 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] partitioning bug + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20partitioning%20bug&In-Reply-To=%3C4FFF5FB4.4010500%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="008187.html"> + <LINK REL="Next" HREF="008203.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] partitioning bug</H1> + <B>andre999</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20partitioning%20bug&In-Reply-To=%3C4FFF5FB4.4010500%40laposte.net%3E" + TITLE="[Mageia-discuss] partitioning bug">andre999mga at laposte.net + </A><BR> + <I>Fri Jul 13 01:37:24 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="008187.html">[Mageia-discuss] partitioning bug +</A></li> + <LI>Next message: <A HREF="008203.html">[Mageia-discuss] partitioning bug +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8199">[ date ]</a> + <a href="thread.html#8199">[ thread ]</a> + <a href="subject.html#8199">[ subject ]</a> + <a href="author.html#8199">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>blind Pete a écrit : +><i> andre999 wrote: +</I>><i> +</I>><i> +</I>>><i> blind Pete a écrit : +</I>>><i> +</I>>>><i> andre999 wrote: +</I>>>><i> +</I>>>><i> +</I>>>><i> +</I>>>>><i> blind Pete a écrit : +</I>>>>><i> +</I>>>>><i> +</I>>>>>><i> David W. Hodgins wrote: +</I>>>>>><i> +</I>>>>>><i> +</I>>>>>><i> +</I>>>>>><i> +</I>>>>>>><i> On Fri, 06 Jul 2012 04:03:34 -0400, blind Pete +</I>>>>>>><i> <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">0123peter at gmail.com</A>> wrote: +</I>>>>>>><i> +</I>>>>>>><i> +</I>>>>>>><i> +</I>>>>>>><i> +</I>>>>>>>><i> Morgan Leijström wrote: +</I>>>>>>>><i> +</I>>>>>>>><i> +</I>>>>>>>><i> +</I>>>>>>>>><i> It would also be interesting to know what other tools say. +</I>>>>>>>>><i> gparted? +</I>>>>>>>>><i> +</I>>>>>>>>><i> +</I>>>>>>>>><i> +</I>>>>>>><i> +</I>>>>>>><i> +</I>>>>>>>><i> Gparted looks pretty. As far as I can see, gparted agrees +</I>>>>>>>><i> with what I think things should look like. Gparted and +</I>>>>>>>><i> fdisk agree about the number of sectors. (More than you +</I>>>>>>>><i> get by multiplying CxHxS.) +</I>>>>>>>><i> +</I>>>>>>>><i> +</I>>>>>>>><i> +</I>>>>>>><i> Interesting. I guess it would be best to use 'hdparm -i /dev/sda|grep +</I>>>>>>><i> LBAsects" to find out the number of sectors. +</I>>>>>>><i> +</I>>>>>>><i> Regards, Dave Hodgins +</I>>>>>>><i> +</I>>>>>>><i> +</I>>>>>>><i> +</I>>>>>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">root at live</A> ~]# hdparm -i /dev/sda | grep LBA +</I>>>>>><i> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=1953523055 +</I>>>>>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">root at live</A> ~]# +</I>>>>>><i> +</I>>>>>><i> Same number of sectors as gparted and fdisk report. Number of heads +</I>>>>>><i> and sectors per cylinder are just, "it's a big disk". _Posssibly_ +</I>>>>>><i> number of cylinders gives a clue about how big. H can be 63 or 255, +</I>>>>>><i> depending on mood, and CxHxS should be a little less than max LBA. +</I>>>>>><i> +</I>>>>>><i> The situation just got worse. The latest work arround is to lie +</I>>>>>><i> about how big a sector is. That is called "advanced" formatting. +</I>>>>>><i> +</I>>>>>><i> +</I>>>>>><i> +</I>>><i> +</I>>>>><i> BTW, with all those partitions, I would convert your disk to GPT tables +</I>>>>><i> instead of MBR, using gdisk. +</I>>>>><i> (gdisk is in core.) +</I>>>>><i> +</I>>>>><i> +</I>>>><i> OK I have installed gdisk and will look at it. How would you rate +</I>>>><i> it for maturity? And what else can recognize a gpt disk? +</I>>>><i> +</I>>><i> I would say very mature, even when I started using it (under mdv 2010.0 +</I>>><i> or 2010.1) +</I>>><i> The developer says the "hybid" option which simulates MBR for Msw is +</I>>><i> risky, but even that I found very stable and predictable +</I>>><i> +</I>><i> I let it loose on my test machine. It has Lilo on the mbr. Mageia 1 +</I>><i> with Grub in its root partition, Mageia 2 with Grub in its root +</I>><i> partition, and Ubuntu 10.04.4 with Grub 2 in its root partition. +</I>><i> +</I>><i> Converting to gpt confused Ubuntu's Grub 2. +</I>><i> +</I>><i> Experimenting with a hybrid system, converting a primary +</I>><i> to a logical, adding a new primary, and renumbering confused +</I>><i> lots of things. +</I>><i> +</I>><i> It was only the test computer. +</I>><i> +</I>><i> +</I>>>><i> Grub? +</I>>>><i> +</I>>>><i> +</I>>><i> Yes, since 1.97 patched for GPT, as used in mdv and fedora (at least) +</I>>><i> when I started using GPT. +</I>>><i> Mageia has always used this version. +</I>>><i> +</I>>>><i> Grub2? +</I>>>><i> +</I>>>><i> +</I>>><i> Definitely +</I>>><i> +</I>><i> I managed to confuse it. Posibly by having it installed in the +</I>><i> root partition. +</I> +It might be because you had your "extended" partition at the beginning +of the disk, and MBR disk partitions are numbered with the "primary" +partions 1-4 and "extended" 5+. +Gdisk would normally number in disk order, but I'm not sure because I +have always numbered in disk order with the "extended" partition at the +end of the disk. With gdisk it is easy to extend an extended partition +to the end of disk with gparted (using a live cd such as systemrescueCD). +You can easily check what partition ordering is with gdisk. (From +systemrescueCD if necessary.) +In any case, both grub and grub2 can get confused sometimes when +partition numbering changes. +It is only necessary to go into rescue mode on boot (from any Mageia +boot cd/dvd, or systemrescueCD), and invoke grub to find the designated +boot partition. +It gives you a grub prompt. grub has somewhat cryptic but useful help. +(This may have changed under grub2, but I don't think so.) +><i> +</I>><i> +</I>>>><i> Lilo? +</I>>>><i> +</I>>>><i> +</I>>><i> Not sure. I think newer versions do. +</I>>><i> +</I>><i> Mostly works. The mbr code just jumps to a hardcoded sector +</I>><i> address and loads the real code from what is normally /etc/map. +</I>><i> +</I> +Good to know. +><i> +</I>>>><i> The Mageia installer? +</I>>>><i> +</I>>>><i> +</I>>><i> I didn't have a problem. I did an upgrade install from mdv2010.2 to +</I>>><i> mga1, and could read the other partitions to set up fstab. +</I>>><i> Sometime before mga1 was available, I had a problem which corrupted my +</I>>><i> system, and made it unbootable. It took me a while to get around that, +</I>>><i> as I didn't want to loose my uncorrupted partitions. I ended up fixing +</I>>><i> it with SystemRescueCD (it contains a partition recovery tool called +</I>>><i> testdisk.) I was able to reinstall mdv. I may have formatted / with +</I>>><i> SystemRescueCD. At that point I had a "hybrid" format simulating MBR +</I>>><i> for systems not aware of GPT. +</I>>><i> +</I>><i> Is there any option in the installer to turn the disk into a gpt disk? +</I> +I highly doubt it, if you mean converting an MBR disk to gpt. +I think gdisk must be used. (or some other similar application.) +And a live cd or dvd, since you can't be using the disk during conversion. + +If you're talking about completely reformatting the disk during +installation, it might work. +When I first tried gpt, I was able to newly format empty usb drives as +gpt, but I don't remember if I used the systemrescueCD or Mandriva. (If +Mandriva, then that should still work with Mageia.) +But working with secondary drives after installation doesn't mean it +would necessarily work with the boot drive during installation. (But it +would be nice if someone tested ;) ) + +>>><i> Other installers? +</I>>>><i> +</I>>>><i> Other operating systems? +</I>>>><i> +</I>>>><i> +</I>>><i> According to what I have read, most other major distros handle GPT +</I>>><i> nicely. The Linux kernel does. +</I>>><i> Msw 32-bit does not, but can work with gdisks' "hybrid" format, which +</I>>><i> puts an MBR table at the end of the first sector (a space not used by +</I>>><i> GPT). It is a little tricky to set up, but initially I had it working. +</I>>><i> Recently I haven't been bothered to get it working again. +</I>>><i> Msw 64-bit is GPT-aware, but I have read that it works only on EFT +</I>>><i> hardware, which has a special BIOS. (Incompatible with Msw 32-bit.) It +</I>>><i> may be just that it is the default installation. +</I>>><i> MacOS handles GPT, but I'm not sure of the restrictions if any. Is was +</I>>><i> an early adopter. +</I>>><i> *BSD systems should handle GPT just like Linux. +</I>>><i> +</I>>>>><i> It will make your disk more stable. +</I>>>>><i> It uses a 128 partition table,with a backup table at the end of the +</I>>>>><i> drive. No such thing as "extended" partitions. +</I>>>>><i> It takes less space than the ms-compatible MBR partition tables. +</I>>>>><i> The only trick is that you need to leave space for the backup table (34 +</I>>>>><i> 512-byte sectors). +</I>>>>><i> If you change your mind, you can convert back painlessly. +</I>>>>><i> I've used GPT for over 2 years, including converting back and forth a +</I>>>>><i> few times at first. +</I>>>>><i> +</I> +Note that if a disk is first formatted as gpt, it can't be converted to +mbr unless it has 4 or less partitions, or every partition after +partition 3 (that is, any that would be in the extended partition) has +enough empty space before it. With the default config for mbr, that +means 63 unallocated sectors before each "logical" partition. +>>>><i> To convert, you'll have to boot to a live disk, preferably with gdisk. +</I>>>>><i> I use systemRescueCD for that. <A HREF="http://www.sysresccd.org/">http://www.sysresccd.org/</A> +</I>>>>><i> The latest stable version is 379 Mib, usable from CD or USB key. +</I>>>>><i> I don't know if a Mageia live cd, or Mageia DVD in rescue mode might +</I>>>>><i> work. +</I>>>>><i> +</I>>>>><i> +</I>>>><i> In Mageia 1 the installer pulled it from the net rather than from +</I>>>><i> the local iso, so it was not prepackaged. +</I>>>><i> +</I>>><i> I installed mga1 from DVD. This upgrade went very smoothly. +</I>>><i> +</I>>><i> I did have a problem changing partition parameters with diskdrake under +</I>>><i> mga1, not long after installing it, shortly after mga1 was released. +</I>>><i> Luckily I was testing things, so I didn't loose anything important. But +</I>>><i> everything was lost on the partition in question. I then tried +</I>>><i> reformatting the partition with diskdrake, and it wouldn't work. I had +</I>>><i> to use SystemRescueCD (with gparted). +</I>>><i> I strongly suspect it was due to my having a "hybrid" format. I think +</I>>><i> that at least at that point, diskdrake (or whatever it uses) would see +</I>>><i> the MBR table, and classify the disk as MBR. While still getting the +</I>>><i> partition location parameters from the GPT table. (The simulated MBR +</I>>><i> table puts most partitions in a large "foreign" partition. The +</I>>><i> corrupted partition was not in the MBR table. And no other partition +</I>>><i> was affected.) +</I>>><i> +</I>>><i> Note that I have never had a problem simply accessing (read or write) a +</I>>><i> GPT partition on mdv or mga. +</I>>><i> +</I>>><i> Also, initially I used gdisk to format usb drives (but no hybrid MBR +</I>>><i> table), and have never had a problem on those disks with diskdrake or +</I>>><i> any other mdv or mga tools. +</I>>><i> +</I>>><i> BTW, I installed gdisk from upstream on mdv, and first imported gdisk to +</I>>><i> Mageia. +</I>>><i> +</I>>>>><i> Just in case you might be interested +</I>>>>><i> +</I>>>>><i> +</I>>>><i> I'm interested. +</I>>>><i> +</I>>><i> You will probably find this interesting :) +</I>>><i> <A HREF="http://en.wikipedia.org/wiki/GUID_Partition_Table">http://en.wikipedia.org/wiki/GUID_Partition_Table</A> +</I>>><i> +</I>><i> Thanks. +</I>><i> +</I>><i> +</I>A further thought. If you don't need MBR access on a gpt disk (in other +words, don't have msw installed), it is better not to have a "hybrid" +format. +That is, use the default gdisk format which creates an mbr table with a +non-ms partition occupying the entire disk. (To discourage +non-gpt-aware systems from corrupting your disk.) +The gdisk site has some info for using non-linux gpt-aware partitions, +in case you have any. + +Regards :) + +-- +André + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="008187.html">[Mageia-discuss] partitioning bug +</A></li> + <LI>Next message: <A HREF="008203.html">[Mageia-discuss] partitioning bug +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8199">[ date ]</a> + <a href="thread.html#8199">[ thread ]</a> + <a href="subject.html#8199">[ subject ]</a> + <a href="author.html#8199">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss +mailing list</a><br> +</body></html> |