Install of 2010 Main fails

[edday]

I have installed the new KDE Main version on VirtualBox. 

When I try to install on the computer, however, the install fails.

Click on the install icon, asks for password (root), opens the initial install wizard screen.  Click on "next" and nothing happens.

Shut down machine and brought back up from cold hardware.  Same result.

2009.2 works just fine.


Processor:  Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz
Video Card:  G92 (GEForce 9800 GT)
Memory:  12 GB

[qbrick]

Seems to be a similar problem I had. The partitioner of the installation program didn't work.
From your live cd try to set up your partitions with System > Administration > GParted, then launch the installer and select to install on existing partition table.
Maybe that works (it did for me).

[menotu]

Hi edday

Couple of quick questions if I may:

Did you run the VM from the ISO or from a burned CD?

If it was from the ISO (which obviously ran fine in VBox) did you do a CD media check after the burn and/or an md5sum check?

See if we can isolate those as problems.

PS, I can see have PLENTY of memory    

[Texstar]

Unable to duplicate. I've installed every version of 2010 in Virtualbox without issue. How much memory/disk space are you giving the system? I have a 8 gig vharddrive and 640 mb of memory in my setup.

[Old-Polack]

Unable to duplicate. I've installed every version of 2010 in Virtualbox without issue. How much memory/disk space are you giving the system? I have a 8 gig vharddrive and 640 mb of memory in my setup.

As I read this, his VBox installation was fine; it's the install on the hardware that's giving him problems.

[Texstar]

Unable to duplicate. I've installed every version of 2010 in Virtualbox without issue. How much memory/disk space are you giving the system? I have a 8 gig vharddrive and 640 mb of memory in my setup.

As I read this, his VBox installation was fine; it's the install on the hardware that's giving him problems.

Ah ok.

[gandy]

I had a similar problem.

Live CD booted on Compq Presario 5000 series 1200 AMD Athlon 384MB old geforce video(test machine). Went to install, it asked for root pass. entered root, box disappeared, then X restarted.

Opened a console, typed draklive-install the installer started and I chose "Use Existing Partitions" got the message "cannot format hda1, ext3 error".

Tried "Use Custom Partitioning" with the same result.

Opened PCC, tried to format partition, got the message that it couldn't unmount the root partition.

Haven't tried GParted yet.

[edday]

running draklive-install from a terminal as root seemed like a good idea.  Produced the following output, but no install.  I have no idea what this means, but here it is.

/media/ user
Warning: /dev/sdb contains GPT signatures, indicating that it has a GPT table.  However, it does not have a valid fake msdos partition table, as it should.  Perhaps it was corrupted -- possibly by a program that doesn't understand GPT partition tables.  Or perhaps you deleted the GPT table, and are now using an msdos partition table.  Is this a GPT partition table?
Warning: /dev/sdb contains GPT signatures, indicating that it has a GPT table.  However, it does not have a valid fake msdos partition table, as it should.  Perhaps it was corrupted -- possibly by a program that doesn't understand GPT partition tables.  Or perhaps you deleted the GPT table, and are now using an msdos partition table.  Is this a GPT partition table?
1 /dev/sdb1 fat32 normal (40,409639,409600)2 /dev/sdb2  normal (409640,2930014983,2929605344)$VAR1 = {
          'part_number' => '1',
          'fs_type' => 'fat32',
          'pt_type' => 186,
          'size' => '409600',
          'start' => '40',
          'real_device' => '/dev/sdb1'
        };
$VAR2 = {
          'part_number' => '2',
          'fs_type' => '',
          'pt_type' => 186,
          'size' => '2929605344',
          'start' => '409640',
          'real_device' => '/dev/sdb2'
        };
INTERNAL ERROR: unknown device sdb2
MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/devices.pm:176
devices::entry() called from /usr/lib/libDrakX/devices.pm:191
devices::make() called from /usr/lib/libDrakX/fs/type.pm:277
fs::type::call_blkid() called from /usr/lib/libDrakX/fs/type.pm:285
fs::type::type_subpart_from_magic() called from /usr/lib/libDrakX/fsedit.pm:271
fsedit::get_hds() called from /usr/sbin/draklive-install:116
main::umount_first_pass() called from /usr/sbin/draklive-install:135
main::init_hds() called from /usr/sbin/draklive-install:68
main::install_live() called from /usr/sbin/draklive-install:42

[menotu]

I had a similar problem.

Live CD booted on Compq Presario 5000 series 1200 AMD Athlon 384MB old geforce video(test machine). Went to install, it asked for root pass. entered root, box disappeared, then X restarted.

Opened a console, typed draklive-install the installer started and I chose "Use Existing Partitions" got the message "cannot format hda1, ext3 error".

Tried "Use Custom Partitioning" with the same result.

Opened PCC, tried to format partition, got the message that it couldn't unmount the root partition.

Haven't tried GParted yet.

You could try formatting your partitions before you install PCLOS.

You mentioned Gparted, which I think is a very good tool -  I would suggest you download the Gparted LiveCD version and do it that way, then do your PCLOS install

[edday]

Thanks.  I have 2009.2 installed and I am just trying to upgrade essentially.  Does the information in my last post indicate a partition problem?

I did the BIG UPGRADE last year on this machine without difficulty. 

It is true that while I have been using PCLOS for some time, I still don't know the "innards" of this distribution.  I don't want to mess with my home partition.

[sling-shot]

Try and wait for at least half hour or more. Better still leave it overnight.
My 2010 Beta 2 installation used to do something like this. I aborted first 5 - 6 times until it dawned on me that due to some unknown reason it is taking a lot of time to just read the partition table or something.

Have not yet installed 2010 final though.

[edday]

Thanks, but running the install from the command line shows that the program exits after producing the output above.  This looks like a problem with one of the drives, but I don't know which one or how to fix  what's wrong.

[Old-Polack]

Thanks, but running the install from the command line shows that the program exits after producing the output above.  This looks like a problem with one of the drives, but I don't know which one or how to fix  what's wrong.

From a root terminal:

[root@localhost ~]# fdisk -l            <Enter>    <-- That's a lower case L not a number 1

Post your results.

Also, read the link below.

http://en.wikipedia.org/wiki/GUID_Partition_Table

Just how large is the drive in question?

[edday]

Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000237f5

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       23873   191759841   83  Linux
/dev/sda2           23874      182401  1273376160    5  Extended
/dev/sda5           23874       24680     6482196   82  Linux swap / Solaris
/dev/sda6           24681      182401  1266893901   83  Linux

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1      182401  1465136001   83  Linux

[Old-Polack]

Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000237f5

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       23873   191759841   83  Linux
/dev/sda2           23874      182401  1273376160    5  Extended
/dev/sda5           23874       24680     6482196   82  Linux swap / Solaris
/dev/sda6           24681      182401  1266893901   83  Linux

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1      182401  1465136001   83  Linux

Did you read the link I posted? The GUID partition table is strictly an Intel thing, and said to be needed for drives greater than 2 TB in size. Your drive is not that large, so the question I have is, how did that partition table come to be? If this is the original drive from your system, there may be a reason for this, but I really can't think of one. The other drive of the same size seems to be working fine, with a normal DOS partition table.

I see two choices;

1. Leave things as is, and repartition using parted, as the fdisk message suggests.

2. Wipe the partition table and create a new DOS partition table with fdisk, partitioning the drive as you wish.

Were the drive mine, I'd go with the second choice, as the messages indicate that the GUID partition table is corrupt, or incomplete, as is. The GPT signatures could in fact be spurious, and not intentionally put there at all. What's seen as a signature could in fact be a curious corruption of some sort. Even if the GPT partition table was correct in every way, the size of the drive does not warrant it's use. I'd go with the DOS partition table just because of the flexibility of being able to use your choice of standard partitioning tools.

The other thought that occurs to me; is this by chance, one of those new "green" drives with 4096 blocks? I thought they were only available in 2 TB+ sizes. Just asking. Looking at the two drive's output from fdisk, they look like twins, so what works with one should work on the other.