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/008164.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/008164.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/2012-July/008164.html | 212 |
1 files changed, 212 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/2012-July/008164.html b/zarb-ml/mageia-discuss/2012-July/008164.html new file mode 100644 index 000000000..53ef26f05 --- /dev/null +++ b/zarb-ml/mageia-discuss/2012-July/008164.html @@ -0,0 +1,212 @@ +<!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=%3C4FF94CBA.4060000%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="008161.html"> + <LINK REL="Next" HREF="008187.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=%3C4FF94CBA.4060000%40laposte.net%3E" + TITLE="[Mageia-discuss] partitioning bug">andre999mga at laposte.net + </A><BR> + <I>Sun Jul 8 11:02:50 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="008161.html">[Mageia-discuss] partitioning bug +</A></li> + <LI>Next message: <A HREF="008187.html">[Mageia-discuss] partitioning bug +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8164">[ date ]</a> + <a href="thread.html#8164">[ thread ]</a> + <a href="subject.html#8164">[ subject ]</a> + <a href="author.html#8164">[ 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> David W. Hodgins wrote: +</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> Morgan Leijström wrote: +</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> 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> 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> [<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> 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> 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 would say very mature, even when I started using it (under mdv 2010.0 +or 2010.1) +The developer says the "hybid" option which simulates MBR for Msw is +risky, but even that I found very stable and predictable +><i> +</I>><i> Grub? +</I>><i> +</I>Yes, since 1.97 patched for GPT, as used in mdv and fedora (at least) +when I started using GPT. +Mageia has always used this version. +><i> Grub2? +</I>><i> +</I>Definitely + +><i> Lilo? +</I>><i> +</I>Not sure. I think newer versions do. + +><i> The Mageia installer? +</I>><i> +</I>I didn't have a problem. I did an upgrade install from mdv2010.2 to +mga1, and could read the other partitions to set up fstab. +Sometime before mga1 was available, I had a problem which corrupted my +system, and made it unbootable. It took me a while to get around that, +as I didn't want to loose my uncorrupted partitions. I ended up fixing +it with SystemRescueCD (it contains a partition recovery tool called +testdisk.) I was able to reinstall mdv. I may have formatted / with +SystemRescueCD. At that point I had a "hybrid" format simulating MBR +for systems not aware of GPT. + +><i> Other installers? +</I>><i> +</I>><i> Other operating systems? +</I>><i> +</I>According to what I have read, most other major distros handle GPT +nicely. The Linux kernel does. +Msw 32-bit does not, but can work with gdisks' "hybrid" format, which +puts an MBR table at the end of the first sector (a space not used by +GPT). It is a little tricky to set up, but initially I had it working. +Recently I haven't been bothered to get it working again. +Msw 64-bit is GPT-aware, but I have read that it works only on EFT +hardware, which has a special BIOS. (Incompatible with Msw 32-bit.) It +may be just that it is the default installation. +MacOS handles GPT, but I'm not sure of the restrictions if any. Is was +an early adopter. +*BSD systems should handle GPT just like Linux. +>><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 drive. +</I>>><i> 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>>><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 work. +</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 installed mga1 from DVD. This upgrade went very smoothly. + +I did have a problem changing partition parameters with diskdrake under +mga1, not long after installing it, shortly after mga1 was released. +Luckily I was testing things, so I didn't loose anything important. But +everything was lost on the partition in question. I then tried +reformatting the partition with diskdrake, and it wouldn't work. I had +to use SystemRescueCD (with gparted). +I strongly suspect it was due to my having a "hybrid" format. I think +that at least at that point, diskdrake (or whatever it uses) would see +the MBR table, and classify the disk as MBR. While still getting the +partition location parameters from the GPT table. (The simulated MBR +table puts most partitions in a large "foreign" partition. The +corrupted partition was not in the MBR table. And no other partition +was affected.) + +Note that I have never had a problem simply accessing (read or write) a +GPT partition on mdv or mga. + +Also, initially I used gdisk to format usb drives (but no hybrid MBR +table), and have never had a problem on those disks with diskdrake or +any other mdv or mga tools. + +BTW, I installed gdisk from upstream on mdv, and first imported gdisk to +Mageia. +>><i> Just in case you might be interested +</I>>><i> +</I>><i> I'm interested. +</I> +You will probably find this interesting :) +<A HREF="http://en.wikipedia.org/wiki/GUID_Partition_Table">http://en.wikipedia.org/wiki/GUID_Partition_Table</A> + +-- +André + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="008161.html">[Mageia-discuss] partitioning bug +</A></li> + <LI>Next message: <A HREF="008187.html">[Mageia-discuss] partitioning bug +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8164">[ date ]</a> + <a href="thread.html#8164">[ thread ]</a> + <a href="subject.html#8164">[ subject ]</a> + <a href="author.html#8164">[ 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> |