[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: So much for a wheezy install, massive fail



On 20/01/2015 15:40, Gene Heskett wrote:
Greetings;

I just started to do a wheezy 2.8 install on a disk with 4k sectors, this
after researching and finding a partitioner utility that DOES know about
4k/sector disks.  That is gdisk. which found the gparted setup and fixed
it, all I had to do was write it to the disk., gparted, an old version is
not capable of aligning things correctly.

So the disk is all partitioned and formatted but empty.

Now I find I cannot bypass the disk partitioner in the installer, nor can
I force it to use these partitions on the hilited drive   This is using
the installer in "expert" mode.

   It will not let me change the "do not use" when I hilite a partition and
hit enter.  It doesn't even acknowledge the mount points "/boot" and "/"
already set.


I'm not sure I understand the latter sentence correctly but in doubt :
Mount points can't be already set, the logic comes once the installation is over (i.e. in grub and in /etc/fstab). And if your partitions aren't recognized you can't assign them some mount points but maybe that's what you meant!

This is less than a desirable thing.

How can I both bypass the broken partitioner, AND force it to use the
partitions it finds on the hilited drive?


Cheers, Gene Heskett


I remember I had a similar issue installing debian maybe one year ago.

If I get it right, some partitions created with some tool wasn't recognized by the debian installer partitioner (it had something to do with gpt & sorry for the lack of precision). What were important is that, as you were already advised by other contributors, using the debian partitioner had solve the problem.

A 4k/sector value shouldn't raise an issue, well I think fdisk, gdisk, parted ... would make their way out of it. If partitions aren't aligned (especially bad for SSD) you can do it manually e.g. create your 1st partition at sector 256 (x 4k = 1M) for example.

--
mrr


Reply to: