summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/2012-July/008187.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-discuss/2012-July/008187.html')
-rw-r--r--zarb-ml/mageia-discuss/2012-July/008187.html238
1 files changed, 238 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/2012-July/008187.html b/zarb-ml/mageia-discuss/2012-July/008187.html
new file mode 100644
index 000000000..48aff40c6
--- /dev/null
+++ b/zarb-ml/mageia-discuss/2012-July/008187.html
@@ -0,0 +1,238 @@
+<!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=%3Ca1r2d9-2eg.ln1%40psd.motzarella.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="008164.html">
+ <LINK REL="Next" HREF="008199.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-discuss] partitioning bug</H1>
+ <B>blind Pete</B>
+ <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20partitioning%20bug&In-Reply-To=%3Ca1r2d9-2eg.ln1%40psd.motzarella.org%3E"
+ TITLE="[Mageia-discuss] partitioning bug">0123peter at gmail.com
+ </A><BR>
+ <I>Thu Jul 12 14:03:21 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="008164.html">[Mageia-discuss] partitioning bug
+</A></li>
+ <LI>Next message: <A HREF="008199.html">[Mageia-discuss] partitioning bug
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#8187">[ date ]</a>
+ <a href="thread.html#8187">[ thread ]</a>
+ <a href="subject.html#8187">[ subject ]</a>
+ <a href="author.html#8187">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>andre999 wrote:
+
+&gt;<i> blind Pete a &#233;crit :
+</I>&gt;&gt;<i> andre999 wrote:
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> blind Pete a &#233;crit :
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> David W. Hodgins wrote:
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;<i> On Fri, 06 Jul 2012 04:03:34 -0400, blind Pete
+</I>&gt;&gt;&gt;&gt;&gt;<i> &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">0123peter at gmail.com</A>&gt; wrote:
+</I>&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> Morgan Leijstr&#246;m wrote:
+</I>&gt;&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<i> It would also be interesting to know what other tools say.
+</I>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<i> gparted?
+</I>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> Gparted looks pretty. As far as I can see, gparted agrees
+</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> with what I think things should look like. Gparted and
+</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> fdisk agree about the number of sectors. (More than you
+</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> get by multiplying CxHxS.)
+</I>&gt;&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;<i> Interesting. I guess it would be best to use 'hdparm -i /dev/sda|grep
+</I>&gt;&gt;&gt;&gt;&gt;<i> LBAsects&quot; to find out the number of sectors.
+</I>&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;<i> Regards, Dave Hodgins
+</I>&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">root at live</A> ~]# hdparm -i /dev/sda | grep LBA
+</I>&gt;&gt;&gt;&gt;<i> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=1953523055
+</I>&gt;&gt;&gt;&gt;<i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">root at live</A> ~]#
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> Same number of sectors as gparted and fdisk report. Number of heads
+</I>&gt;&gt;&gt;&gt;<i> and sectors per cylinder are just, &quot;it's a big disk&quot;. _Posssibly_
+</I>&gt;&gt;&gt;&gt;<i> number of cylinders gives a clue about how big. H can be 63 or 255,
+</I>&gt;&gt;&gt;&gt;<i> depending on mood, and CxHxS should be a little less than max LBA.
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> The situation just got worse. The latest work arround is to lie
+</I>&gt;&gt;&gt;&gt;<i> about how big a sector is. That is called &quot;advanced&quot; formatting.
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;<i>
+</I>&gt;&gt;&gt;<i> BTW, with all those partitions, I would convert your disk to GPT tables
+</I>&gt;&gt;&gt;<i> instead of MBR, using gdisk.
+</I>&gt;&gt;&gt;<i> (gdisk is in core.)
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;<i> OK I have installed gdisk and will look at it. How would you rate
+</I>&gt;&gt;<i> it for maturity? And what else can recognize a gpt disk?
+</I>&gt;<i>
+</I>&gt;<i> I would say very mature, even when I started using it (under mdv 2010.0
+</I>&gt;<i> or 2010.1)
+</I>&gt;<i> The developer says the &quot;hybid&quot; option which simulates MBR for Msw is
+</I>&gt;<i> risky, but even that I found very stable and predictable
+</I>
+I let it loose on my test machine. It has Lilo on the mbr. Mageia 1
+with Grub in its root partition, Mageia 2 with Grub in its root
+partition, and Ubuntu 10.04.4 with Grub 2 in its root partition.
+
+Converting to gpt confused Ubuntu's Grub 2.
+
+Experimenting with a hybrid system, converting a primary
+to a logical, adding a new primary, and renumbering confused
+lots of things.
+
+It was only the test computer.
+
+&gt;&gt;<i> Grub?
+</I>&gt;&gt;<i>
+</I>&gt;<i> Yes, since 1.97 patched for GPT, as used in mdv and fedora (at least)
+</I>&gt;<i> when I started using GPT.
+</I>&gt;<i> Mageia has always used this version.
+</I>&gt;&gt;<i> Grub2?
+</I>&gt;&gt;<i>
+</I>&gt;<i> Definitely
+</I>
+I managed to confuse it. Posibly by having it installed in the
+root partition.
+
+&gt;&gt;<i> Lilo?
+</I>&gt;&gt;<i>
+</I>&gt;<i> Not sure. I think newer versions do.
+</I>
+Mostly works. The mbr code just jumps to a hardcoded sector
+address and loads the real code from what is normally /etc/map.
+
+&gt;&gt;<i> The Mageia installer?
+</I>&gt;&gt;<i>
+</I>&gt;<i> I didn't have a problem. I did an upgrade install from mdv2010.2 to
+</I>&gt;<i> mga1, and could read the other partitions to set up fstab.
+</I>&gt;<i> Sometime before mga1 was available, I had a problem which corrupted my
+</I>&gt;<i> system, and made it unbootable. It took me a while to get around that,
+</I>&gt;<i> as I didn't want to loose my uncorrupted partitions. I ended up fixing
+</I>&gt;<i> it with SystemRescueCD (it contains a partition recovery tool called
+</I>&gt;<i> testdisk.) I was able to reinstall mdv. I may have formatted / with
+</I>&gt;<i> SystemRescueCD. At that point I had a &quot;hybrid&quot; format simulating MBR
+</I>&gt;<i> for systems not aware of GPT.
+</I>
+Is there any option in the installer to turn the disk into a gpt disk?
+
+&gt;&gt;<i> Other installers?
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Other operating systems?
+</I>&gt;&gt;<i>
+</I>&gt;<i> According to what I have read, most other major distros handle GPT
+</I>&gt;<i> nicely. The Linux kernel does.
+</I>&gt;<i> Msw 32-bit does not, but can work with gdisks' &quot;hybrid&quot; format, which
+</I>&gt;<i> puts an MBR table at the end of the first sector (a space not used by
+</I>&gt;<i> GPT). It is a little tricky to set up, but initially I had it working.
+</I>&gt;<i> Recently I haven't been bothered to get it working again.
+</I>&gt;<i> Msw 64-bit is GPT-aware, but I have read that it works only on EFT
+</I>&gt;<i> hardware, which has a special BIOS. (Incompatible with Msw 32-bit.) It
+</I>&gt;<i> may be just that it is the default installation.
+</I>&gt;<i> MacOS handles GPT, but I'm not sure of the restrictions if any. Is was
+</I>&gt;<i> an early adopter.
+</I>&gt;<i> *BSD systems should handle GPT just like Linux.
+</I>&gt;&gt;&gt;<i> It will make your disk more stable.
+</I>&gt;&gt;&gt;<i> It uses a 128 partition table,with a backup table at the end of the
+</I>&gt;&gt;&gt;<i> drive. No such thing as &quot;extended&quot; partitions.
+</I>&gt;&gt;&gt;<i> It takes less space than the ms-compatible MBR partition tables.
+</I>&gt;&gt;&gt;<i> The only trick is that you need to leave space for the backup table (34
+</I>&gt;&gt;&gt;<i> 512-byte sectors).
+</I>&gt;&gt;&gt;<i> If you change your mind, you can convert back painlessly.
+</I>&gt;&gt;&gt;<i> I've used GPT for over 2 years, including converting back and forth a
+</I>&gt;&gt;&gt;<i> few times at first.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> To convert, you'll have to boot to a live disk, preferably with gdisk.
+</I>&gt;&gt;&gt;<i> I use systemRescueCD for that. <A HREF="http://www.sysresccd.org/">http://www.sysresccd.org/</A>
+</I>&gt;&gt;&gt;<i> The latest stable version is 379 Mib, usable from CD or USB key.
+</I>&gt;&gt;&gt;<i> I don't know if a Mageia live cd, or Mageia DVD in rescue mode might
+</I>&gt;&gt;&gt;<i> work.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;<i> In Mageia 1 the installer pulled it from the net rather than from
+</I>&gt;&gt;<i> the local iso, so it was not prepackaged.
+</I>&gt;<i>
+</I>&gt;<i> I installed mga1 from DVD. This upgrade went very smoothly.
+</I>&gt;<i>
+</I>&gt;<i> I did have a problem changing partition parameters with diskdrake under
+</I>&gt;<i> mga1, not long after installing it, shortly after mga1 was released.
+</I>&gt;<i> Luckily I was testing things, so I didn't loose anything important. But
+</I>&gt;<i> everything was lost on the partition in question. I then tried
+</I>&gt;<i> reformatting the partition with diskdrake, and it wouldn't work. I had
+</I>&gt;<i> to use SystemRescueCD (with gparted).
+</I>&gt;<i> I strongly suspect it was due to my having a &quot;hybrid&quot; format. I think
+</I>&gt;<i> that at least at that point, diskdrake (or whatever it uses) would see
+</I>&gt;<i> the MBR table, and classify the disk as MBR. While still getting the
+</I>&gt;<i> partition location parameters from the GPT table. (The simulated MBR
+</I>&gt;<i> table puts most partitions in a large &quot;foreign&quot; partition. The
+</I>&gt;<i> corrupted partition was not in the MBR table. And no other partition
+</I>&gt;<i> was affected.)
+</I>&gt;<i>
+</I>&gt;<i> Note that I have never had a problem simply accessing (read or write) a
+</I>&gt;<i> GPT partition on mdv or mga.
+</I>&gt;<i>
+</I>&gt;<i> Also, initially I used gdisk to format usb drives (but no hybrid MBR
+</I>&gt;<i> table), and have never had a problem on those disks with diskdrake or
+</I>&gt;<i> any other mdv or mga tools.
+</I>&gt;<i>
+</I>&gt;<i> BTW, I installed gdisk from upstream on mdv, and first imported gdisk to
+</I>&gt;<i> Mageia.
+</I>&gt;&gt;&gt;<i> Just in case you might be interested
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;<i> I'm interested.
+</I>&gt;<i>
+</I>&gt;<i> You will probably find this interesting :)
+</I>&gt;<i> <A HREF="http://en.wikipedia.org/wiki/GUID_Partition_Table">http://en.wikipedia.org/wiki/GUID_Partition_Table</A>
+</I>
+Thanks.
+
+--
+blind Pete
+Sig goes here...
+
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="008164.html">[Mageia-discuss] partitioning bug
+</A></li>
+ <LI>Next message: <A HREF="008199.html">[Mageia-discuss] partitioning bug
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#8187">[ date ]</a>
+ <a href="thread.html#8187">[ thread ]</a>
+ <a href="subject.html#8187">[ subject ]</a>
+ <a href="author.html#8187">[ 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>