Ubuntu This forum is for the discussion of Ubuntu Linux. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
12-20-2006, 10:31 AM
|
#1
|
Member
Registered: Nov 2005
Distribution: Mint 14 Nadia
Posts: 189
Rep:
|
Dapper install stalls at 70%
I've lost count of the number of times I've now DLed tried to install Dapper from ther GUI CD and it stalls at 70%, with 14:43 remaining. When I've run the "check CD for errors" I keep coming up with one checksum error, and the one time I DLed the alternate CD, and ran an MD5 utility, it gave one checksum error also, and identified it as bein in one of the Open Office files. This has been very consistent...at least 5 attempts to install from at least 3 independently DLed ISOs, including both GHUI and alternate.
This is a dual boot install with Win2K, and is trying to install over a previous install of Dapper, into the same partitions.
Any suggestions?
Thanks!
Optiker
|
|
|
12-21-2006, 03:37 AM
|
#2
|
LQ Guru
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211
Rep: 
|
Reinstall dapper - you know this goes.
(Though it sounds like your CD drive is starting to break.)
Then "upgrade" dapper to edgy.
alt-F2
gksu "update-manager -c"
This is remarkably reliable these days.
https://wiki.ubuntu.com/EdgyReleaseN...0c683c77e56cd0
|
|
|
12-21-2006, 03:49 AM
|
#3
|
LQ Guru
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733
|
Is it possible not to install Open Office until later?
|
|
|
12-21-2006, 12:40 PM
|
#4
|
Member
Registered: Nov 2005
Distribution: Mint 14 Nadia
Posts: 189
Original Poster
Rep:
|
Quote:
Originally Posted by Simon Bridge
|
This IS an attempt to install Dapper - not Edgy. It's the Dapper install that's hanging up. I know there are known issues with the Edgy installation that hang up at 77%, but this is Dapper, not Edgy.
The CD drive appears OK, in fact, have two CD drives in that computer, and get the same behavior on both.
Optiker
Last edited by Optiker; 12-21-2006 at 12:42 PM.
|
|
|
12-21-2006, 12:41 PM
|
#5
|
Member
Registered: Nov 2005
Distribution: Mint 14 Nadia
Posts: 189
Original Poster
Rep:
|
Quote:
Originally Posted by jschiwal
Is it possible not to install Open Office until later?
|
Not that I know of. Prior to the step where it hangs, there are no options that allow not installing.
Thanks!
Optiker
|
|
|
12-21-2006, 02:46 PM
|
#6
|
LQ Newbie
Registered: Sep 2005
Distribution: SuSE first, now Ubuntu
Posts: 14
Rep:
|
If another computer is not available to download and burn a fresh copy of the CD, there is always the free Ship-it service.
Have you tried the Alternate CD? That's another tack.
|
|
|
12-21-2006, 06:09 PM
|
#7
|
LQ Guru
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211
Rep: 
|
Quote:
This IS an attempt to install Dapper - not Edgy. It's the Dapper install that's hanging up. I know there are known issues with the Edgy installation that hang up at 77%, but this is Dapper, not Edgy.
|
Sorry - for some reason I thought you had already installed dapper ... hmmm
Quote:
The CD drive appears OK, in fact, have two CD drives in that computer, and get the same behavior on both.
|
However, you keep getting checksum errors after burning the install CD.
This will be because of;
1. bad internet connection
2. bad CD hardware
3. bad (i.e. cheap) CD media
4. bad CD burning software
5. bad source of ISO's
Consistently failed checksums usually mean the hardware is not up to the task.
Quote:
The CD drive appears OK, in fact, have two CD drives in that computer, and get the same behavior on both.
|
How do you know the drives "appear" OK? (The only way to check is to burn, repeatedly, a large file and run a checksum.)
Mind you - you may want to check those cables.
So: you do the process of elimination and get back to me with the details OK?
Quote:
previous install of Dapper
|
... I take it this installation is now useless? I take it the disk you used for this previous install is not available?
If you are really stuck, and bloody minded - you could try the server installation, then install the GUI packages by hand using apt.
|
|
|
12-22-2006, 06:16 AM
|
#8
|
LQ Newbie
Registered: Sep 2005
Distribution: SuSE first, now Ubuntu
Posts: 14
Rep:
|
Quote:
Originally Posted by Simon Bridge
How do you know the drives "appear" OK? (The only way to check is to burn, repeatedly, a large file and run a checksum.)
|
You can check the checksum before burning. Actually, once you have burned the ISO the checksum is useless, because the original file has now been converted to the files used during the install.
|
|
|
12-22-2006, 06:59 AM
|
#9
|
LQ Guru
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211
Rep: 
|
Really? After I've burned an ISO, I still have the ISO - the iso can be mounted and browsed ... how is it different. Anyway - Ubuntu has a media checker which I was thinking of I guess. (Similarily with Optiker - how can a checksum fail on a particular package if it is the ISO checksum being used? Again, I just figured it was the media check which failed.)
I maintain - if the media is bad consistently over many burnings, this is a hardware problem.
|
|
|
12-22-2006, 07:42 AM
|
#10
|
LQ Newbie
Registered: Sep 2005
Distribution: SuSE first, now Ubuntu
Posts: 14
Rep:
|
Quote:
Originally Posted by Simon Bridge
Really? After I've burned an ISO, I still have the ISO - the iso can be mounted and browsed ... how is it different.
|
Checksums are for checking the download to ensure the integrity of the file. Checksums have nothing to do with burning at all. Burning an ISO to CD will have no effect on the ISO no matter how many copies you burn.
If you are mounting the ISO then there is no need to burn anything in the first place.
|
|
|
12-27-2006, 03:26 PM
|
#11
|
Member
Registered: Nov 2005
Distribution: Mint 14 Nadia
Posts: 189
Original Poster
Rep:
|
Quote:
Originally Posted by jhenager
If another computer is not available to download and burn a fresh copy of the CD, there is always the free Ship-it service.
Have you tried the Alternate CD? That's another tack.
|
It WAS DLed with another computer - twice, with two different computers, tied to two totally independent connections.
I'm considering the free CD, but having DLed with different computers, can't see how that could make a difference.
I have tried the alternate CD - got the same "one checksum error" message - but at least on this dual boot setup, the partition step is sufficiently ambiguous that I'm not sure enough of what I'm doing to take that step. It's OK up to the last "continue" before actual partitioning.
Optiker
|
|
|
12-27-2006, 03:42 PM
|
#12
|
Member
Registered: Nov 2005
Distribution: Mint 14 Nadia
Posts: 189
Original Poster
Rep:
|
Quote:
Originally Posted by Simon Bridge
Sorry - for some reason I thought you had already installed dapper ... hmmmHowever, you keep getting checksum errors after burning the install CD.
This will be because of;
1. bad internet connection
2. bad CD hardware
3. bad (i.e. cheap) CD media
4. bad CD burning software
5. bad source of ISO's
Consistently failed checksums usually mean the hardware is not up to the task.
How do you know the drives "appear" OK? (The only way to check is to burn, repeatedly, a large file and run a checksum.)
Mind you - you may want to check those cables.
So: you do the process of elimination and get back to me with the details OK?
... I take it this installation is now useless? I take it the disk you used for this previous install is not available?
If you are really stuck, and bloody minded - you could try the server installation, then install the GUI packages by hand using apt.
|
DLed over two different independent internet connections (T1 at work and wireless broadband at home) to two different computers (both much newer than the system I'm trying to install on). That would appear to answer your #1 and #2. Two different packages of media bought at widely different tiems and places - answers #3 other than low probability coincidence.
Same burning software installed on differenct machines - CD Bruner XP Pro3 (freeware). However, running an MD5 checksum utility on the ISO gave a one checksum error (in one Open Office file), so that existed before burning.
DL was from different mirrors from the Kubuntu site list.
Regarding the burning drives appearing OK - it's true I've not done rigorous testing. However, CDs burned on two different computers, with two different drives have the same problem and have shown no problem in any other use.
Cables...would you expect such a consistent error from loose or defective cables? Doesn't make sense, but easy enough to at least check for tight cables. But, again, I go back to ISOs DLed and burned with two independent systems, and I've tried installing from two separate drives on the target computer.
At this point, I've all but given up. I've tossed the previous numerous copies of the ISOs including one Edgy, several Dappers (including both desktop and alternate). I am really stuck, but too inexperienced to try a server install. This is my secondary home computer, and since I have other pressing issues on the primary - installing a new drive and trying to mix SATA and PATA drives so I can mirror the system - the Kubuntu install is on the back burner for now. Just answering these replies to close the loop and out of general courtesy.
Thanks for taking the time for an extended reply.
Optiker
|
|
|
12-27-2006, 03:44 PM
|
#13
|
Member
Registered: Nov 2005
Distribution: Mint 14 Nadia
Posts: 189
Original Poster
Rep:
|
Quote:
Originally Posted by jhenager
You can check the checksum before burning. Actually, once you have burned the ISO the checksum is useless, because the original file has now been converted to the files used during the install.
|
Agreed! In the one instance where I checked the checksum before burning, got the "one checksum error" in an Open Office file. I only went ahead and tried to install from it because I had hopes it might be a negligible problem with Open Office that could be solved later, not a fatal install error.
Optiker
Last edited by Optiker; 12-27-2006 at 03:46 PM.
|
|
|
12-27-2006, 05:55 PM
|
#14
|
Registered User
Registered: Dec 2006
Posts: 1,454
Rep:
|
Optiker,
In your original post, you stated that you were trying to install Dapper over a previous install of Dapper, into the same partitions. Why would you need to do that in the first place? Are you having problems with the original installation? And under which OS are you checking the checksums?
Just trying to help...
|
|
|
12-28-2006, 10:17 AM
|
#15
|
Member
Registered: Nov 2005
Distribution: Mint 14 Nadia
Posts: 189
Original Poster
Rep:
|
Quote:
Originally Posted by dragonslayer48dx
Optiker,
In your original post, you stated that you were trying to install Dapper over a previous install of Dapper, into the same partitions. Why would you need to do that in the first place? Are you having problems with the original installation? And under which OS are you checking the checksums?
|
Looooong story, so will try to abbreviate it. Some of detail and sequence may be inaccurate...I think I've probably mentally buried it as some of the details are already fading! Senior moment, or just avoiding recalling the facts?
* Dual booted, Win2000Pro (Win2k) and Kubuntu Breezy (maybe it was even Hoary), on an old MIcron P2/300 MHz machine. All working well.
* Windows update badly messed up Windows...wouldn't even boot
* tried to find a solution short of reinstalling Win2k from scratch
* Weeks of trying to find the problem...possible solution included replacing some Win2k files, but c-drive was NTFS and had problems doing it from Kubuntu. Even tried using Knoppix.
* tried installing Edgy, then Xubuntu over Breezy...messed up that installation and finally reinstalled Win2k from scratch
* somewhere along the line, managed to cleanly install Dapper - great...now I had updated Win2k and updated Kubuntu!
* used Automatix to try to install Wine, nVidia driver, new KDE and a few other things...disaster!
* lost boot into GUI, only got commandline boot and manual startX; no shutdown option, just logoff to commandline.
* spent weeks trying to get that fixed...finally gave up and tried to reinstall Kubuntu Dapper
* multiple failed attempts to install Dapper (desktop and alternate) resulting in this thread.
* even tried giving up on Kubuntu and trying Mepis instead, but Mepis CD booted to commandline in grub directory, so was lost woth what to do next, and no help from Mepis forum.
* bottom line as of last night - Dapper installed clean from a new ISO DL and burn. Will NOT try using Automatix!
CD checked using option on the install CD, then also using manual checksum using an MD5 utility on WinXP.
Finally...see my next post that I will be adding to this thread after I submit this one for details of successful installation.
Thanks for the reply!
Optiker
|
|
|
All times are GMT -5. The time now is 12:28 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|