On Tue, Jun 19, 2012 at 9:15 PM, Geoffrey Leach <geoff@hughes.net> wrote:

So, I'm doing a fresh install of Fedora 17 from DVD. I get to the disk

layout and select custom partitioning.



Partition size: default 500 (MB)



Here's where I have trouble. I need 100 GB. So, 1 GB = 1000MB, so I

should enter 100x1000, no?



Anaconda crashes.



I can't believe that Anaconda is so broken, so it must be me.


Hi Geoffrey,

500mb should be for your boot partition (Perhaps 1gb would be better).* Next allocate the 100gb for /


Good luck with your install.

/s

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 19.06.2012 15:15, Geoffrey Leach wrote:
> So, I'm doing a fresh install of Fedora 17 from DVD. I get to the disk
> layout and select custom partitioning.
>
> Partition size: default 500 (MB)
>
> Here's where I have trouble. I need 100 GB. So, 1 GB = 1000MB, so I
> should enter 100x1000, no?
>
> Anaconda crashes.
>
> I can't believe that Anaconda is so broken, so it must be me.

It is broken very badly! When I was trying to setup a custom partition
layout with LVM on RAID and I made a mistake and wanted to correct it,
installer simply crashed. I had to create disk partitions step by step
without doing any changes. On error installation was finished and had to
be started again!

So it's all about Anaconda stability! If you value your time you'd
better go with default options or don't change anything once it was done.


Mateusz Marzantowicz

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/19/2012 06:15 AM, Geoffrey Leach wrote:

Here's where I have trouble. I need 100 GB. So, 1 GB = 1000MB, so I
should enter 100x1000, no?


No. 1GB = 1024 MB. Not that that should make Anaconda crash, but you
should at least get the numbers right.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Do what thou wilt
shall be the whole of the Law.


On Tue, Jun 19, 2012 at 1:44 PM, Joe Zeff <joe@zeff.us> wrote:
> On 06/19/2012 06:15 AM, Geoffrey Leach wrote:
>>
>> Here's where I have trouble. I need 100 GB. So, 1 GB = 1000MB, so I
>> should enter 100x1000, no?
>
>
> No. *1GB = 1024 MB. *Not that that should make Anaconda crash, but you
> should at least get the numbers right.
>

1GB = 1000 MB. 1GiB = 1024 MiB.
does Anaconda use MB or MiB?

charles zeitler
--




Love is the law, love under will.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/19/2012 07:08:41 PM, Charles Zeitler wrote:
> Do what thou wilt
> shall be the whole of the Law.
>
>
> On Tue, Jun 19, 2012 at 1:44 PM, Joe Zeff <joe@zeff.us> wrote:
> > On 06/19/2012 06:15 AM, Geoffrey Leach wrote:
> >>
> >> Here's where I have trouble. I need 100 GB. So, 1 GB = 1000MB, so
> I
> >> should enter 100x1000, no?
> >
> >
> > No. *1GB = 1024 MB. *Not that that should make Anaconda crash, but
> you
> > should at least get the numbers right.
> >
>
> 1GB = 1000 MB. 1GiB = 1024 MiB.
> does Anaconda use MB or MiB?

Hmmm ... would that that was the problem. AFAIK Anaconda takes input
only in MB. (By whatever definition, the darn thing still crashes.)
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/20/2012 11:43 AM, Geoffrey Leach wrote:
> Hmmm ... would that that was the problem. AFAIK Anaconda takes input
> only in MB. (By whatever definition, the darn thing still crashes.)

FWIW, I just installed a test system in a VM. I have a 137GB virtual disk.

I modified the partitions by deleting the configuration and creating my own. I
created a /boot using 105000 which would be 105GB give or take. I defined the
remaining as an LVM Physical partition and then put swap in an LVM Logical Volume
with a size of 1GB and the rest gave to /.

No crash....

[egreshko@f17t ~]$ uname -r
3.3.4-5.fc17.i686
[egreshko@f17t ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 29G 3.7G 24G 14% /
devtmpfs 494M 0 494M 0% /dev
tmpfs 502M 96K 502M 1% /dev/shm
tmpfs 502M 1.3M 501M 1% /run
/dev/mapper/vg_f17t-lv01 29G 3.7G 24G 14% /
tmpfs 502M 0 502M 0% /sys/fs/cgroup
tmpfs 502M 0 502M 0% /media
/dev/sda1 103G 1.7G 96G 2% /boot

Is that what you're trying to do?

--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/19/2012 09:44:39 PM, Ed Greshko wrote:
> On 06/20/2012 11:43 AM, Geoffrey Leach wrote:
> > Hmmm ... would that that was the problem. AFAIK Anaconda takes
> input
>
> > only in MB. (By whatever definition, the darn thing still crashes.)
>
> FWIW, I just installed a test system in a VM. I have a 137GB virtual
> disk.
>
> I modified the partitions by deleting the configuration and creating
> my own. I
> created a /boot using 105000 which would be 105GB give or take. I
> defined the
> remaining as an LVM Physical partition and then put swap in an LVM
> Logical Volume
> with a size of 1GB and the rest gave to /.
>
> No crash....
>
> [egreshko@f17t ~]$ uname -r
> 3.3.4-5.fc17.i686
> [egreshko@f17t ~]$ df -h
> Filesystem Size Used Avail Use% Mounted on
> rootfs 29G 3.7G 24G 14% /
> devtmpfs 494M 0 494M 0% /dev
> tmpfs 502M 96K 502M 1% /dev/shm
> tmpfs 502M 1.3M 501M 1% /run
> /dev/mapper/vg_f17t-lv01 29G 3.7G 24G 14% /
> tmpfs 502M 0 502M 0% /sys/fs/cgroup
> tmpfs 502M 0 502M 0% /media
> /dev/sda1 103G 1.7G 96G 2% /boot
>
> Is that what you're trying to do?

No. What I'm dealing with is a naked, never-before-seeing-fedora disk.
(there are a couple of ntfs partitions put there by the manufacturer.
I'm allocating the remaining space.) I've done this with earlier
Fedoras without any problems.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Geoffrey Leach <geoff@hughes.net> wrote:

>On 06/19/2012 09:44:39 PM, Ed Greshko wrote:
>> On 06/20/2012 11:43 AM, Geoffrey Leach wrote:
>> > Hmmm ... would that that was the problem. AFAIK Anaconda takes
>> input
>>
>> > only in MB. (By whatever definition, the darn thing still crashes.)
>>
>> FWIW, I just installed a test system in a VM. I have a 137GB virtual
>> disk.
>>
>> I modified the partitions by deleting the configuration and creating
>> my own. I
>> created a /boot using 105000 which would be 105GB give or take. I
>> defined the
>> remaining as an LVM Physical partition and then put swap in an LVM
>> Logical Volume
>> with a size of 1GB and the rest gave to /.
>>
>> No crash....
>>
>> [egreshko@f17t ~]$ uname -r
>> 3.3.4-5.fc17.i686
>> [egreshko@f17t ~]$ df -h
>> Filesystem Size Used Avail Use% Mounted on
>> rootfs 29G 3.7G 24G 14% /
>> devtmpfs 494M 0 494M 0% /dev
>> tmpfs 502M 96K 502M 1% /dev/shm
>> tmpfs 502M 1.3M 501M 1% /run
>> /dev/mapper/vg_f17t-lv01 29G 3.7G 24G 14% /
>> tmpfs 502M 0 502M 0% /sys/fs/cgroup
>> tmpfs 502M 0 502M 0% /media
>> /dev/sda1 103G 1.7G 96G 2% /boot
>>
>> Is that what you're trying to do?
>
>No. What I'm dealing with is a naked, never-before-seeing-fedora disk.
>(there are a couple of ntfs partitions put there by the manufacturer.
>I'm allocating the remaining space.) I've done this with earlier
>Fedoras without any problems.

Well what you seemed to be saying is that you were unable to create a 100GB boot partition.
Maybe you need to be more precise about the current disk content / configuration.
It seems it already must have a label and partition layout.

If you try installing F16 do you get the same crash.


--
Sent from my Android tablet with K-9 Mail.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/20/2012 06:06:38 AM, Ed Greshko wrote:
> Geoffrey Leach <geoff@hughes.net> wrote:
>
> >On 06/19/2012 09:44:39 PM, Ed Greshko wrote:
> >> On 06/20/2012 11:43 AM, Geoffrey Leach wrote:
> >> > Hmmm ... would that that was the problem. AFAIK Anaconda takes
> >> input
> >>
> >> > only in MB. (By whatever definition, the darn thing still
> crashes.)
> >>
> >> FWIW, I just installed a test system in a VM. I have a 137GB
> virtual
> >> disk.
> >>
> >> I modified the partitions by deleting the configuration and
> creating
> >> my own. I
> >> created a /boot using 105000 which would be 105GB give or take. I
> >> defined the
> >> remaining as an LVM Physical partition and then put swap in an LVM
> >> Logical Volume
> >> with a size of 1GB and the rest gave to /.
> >>
> >> No crash....
> >>
> >> [egreshko@f17t ~]$ uname -r
> >> 3.3.4-5.fc17.i686
> >> [egreshko@f17t ~]$ df -h
> >> Filesystem Size Used Avail Use% Mounted on
> >> rootfs 29G 3.7G 24G 14% /
> >> devtmpfs 494M 0 494M 0% /dev
> >> tmpfs 502M 96K 502M 1% /dev/shm
> >> tmpfs 502M 1.3M 501M 1% /run
> >> /dev/mapper/vg_f17t-lv01 29G 3.7G 24G 14% /
> >> tmpfs 502M 0 502M 0% /sys/fs/cgroup
> >> tmpfs 502M 0 502M 0% /media
> >> /dev/sda1 103G 1.7G 96G 2% /boot
> >>
> >> Is that what you're trying to do?
> >
> >No. What I'm dealing with is a naked, never-before-seeing-fedora
> disk.
> >(there are a couple of ntfs partitions put there by the
> manufacturer.
>
> >I'm allocating the remaining space.) I've done this with earlier
> >Fedoras without any problems.
>
> Well what you seemed to be saying is that you were unable to create a
> 100GB boot partition.
> Maybe you need to be more precise about the current disk content /
> configuration.
> It seems it already must have a label and partition layout.
>
> If you try installing F16 do you get the same crash.

The disk has two NTFS partitions, placed there by the mfg. Windows 7,
FWIW. The rest of the disk is empty. t has not been partitioned or
formatted, at least as far as Anaconda is concerned. Windows 7 does not
see anything there, for that matter. Actually, I was attempting to
create a 100GB / partition, but I don't believe that the name of the
partition is significant.

What I'm going to try (after I finish re-wiring my solar panel array)
is to start with a 500MB boot partition, that being the default offered
by Anaconda. Perhaps if we get it started, it will play nice. If that
doesn't work, I'll try a Fedora 16 dsk. That worked in a similar
situation on another box.

The person who got stuck with the bug report on Bugzilla (https://
bugzilla.redhat.com/show_bug.cgi?id=833239, no additional info) tells
me that I should be able to save the crash to a thumb drive. The box in
question has only WiFi via a dongle, and it seems its too early in the
process for that to be used.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On Wed, 2012-06-20 at 07:58 -0700, Geoffrey Leach wrote:

> > Geoffrey Leach <geoff@hughes.net> wrote:

> > >No. What I'm dealing with is a naked, never-before-seeing-fedora
> > disk.
> > >(there are a couple of ntfs partitions put there by the
> > manufacturer.

Most manufacturer-delivered disks that I have seen allocate the entire
disk to Windows. Are you sure there is actually free space left on the
disk to allocate? Once anaconda has started, you can press CTRL-ALT-F2
and get to a shell. Then you can run something like "fdisk -l /dev/sda"
to see how the disk is partitioned.

What I had to do in a similar situation was run "gparted" (from a
bootable live CD; I actually used an Ubuntu live CD even though I was
preparing to install Fedora, just because the Ubuntu CD comes with
gparted ready to go). Using gparted, I could shrink down the main
windows partition to make room for some Linux partitions. That allowed
me to preserve the manufacturer-installed Windows system and also
install Fedora.

--Greg


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org