hey

i had ubuntu12.04 LTS (32 bit).how to check that ubuntu installed is corrupted or not?

with regards
ajay

Considering you give us no information whatsoever my first suggestion is to use it and see how it goes.
My second suggestion is to say can you tell us why you are asking this?
My third suggestion is to ask you to give us as much information as you possibly can because what you have said so far doesn't give us anything to go on.

Considering you give us no information whatsoever my first suggestion is to use it and see how it goes.
i want to setup android development environment first it not setting adt plugin then i reinstall eclipse and sdk then i check in eclipse there is no icon of sdk manager in window option on toolbar of eclipse then i deleted all opton of eclipse and sdk and redownload from eclipse with eclipse classic4.2.1,android sdk r21.0.1 and jdk 6 from respective official site then i setup jdk environment and extract sdk files then i check md5sum of eclipse the sum is not matching with the sum given on website. i might think it was the problem of ubuntu
My second suggestion is to say can you tell us why you are asking this?
when i download ubuntu first time it is not updating from terminal then after ten days i reinstall it again from same iso file then it is updating.
My third suggestion is to ask you to give us as much information as you possibly can because what you have said so far doesn't give us anything to go on

Did you check your sources.list? Did you choose Automatic updates? Where are you located? What server did you chosen to update from? It may have been user error.

I don't know enough about Android to offer any help with aspect of your post. I wonder how anyone was supposed to know that from your first post though. Also how was anyone supposed to know that your system wasn't updating from what you put in your first post.

Also please use quote boxes when quoting others and use them in a logical order. It is 5am here right now and I found it a little difficult to see where my sentences were and yours where considering they were all jumbled in together. The point I am trying to make here is if you want help you also need to help us.

I think I can help you with the MD5sum problem, but the others are a bit beyond me.

Checksumming is subtly deceptive. There are several ways to do it (even with just MD5), and if you use a different one from what the people publishing the "correct checksum" used, you'll get the wrong result.

Here are the methods I use. Since it's astronomically unlikely to get the same sum by ANY means if the data doesn't match, if you can get even one of these to give you the right number, you know the file is good.

1) md5sum <file>
This reads the file in "text mode."

2) md5sum -b <file>
This reads the file in "binary mode." (I suspect this is better for most common uses.)

3) dd if=<file> bs=<see below> count=<see below> conv=notrunc,noerror,sync | md5sum
This is especially good for CD images and such, but also works for other things. Notably, the "coaster-less CD-burning guide" specifies this method (last I checked). Explanation:
dd: "disk dump". dumps the content of a file to standard output (the terminal) unless you redirect it with a pipe, "|" or other means. By default, it dumps 512 bytes per "block."
bs: "block size". How much to grab at a time before sending the data to output. This is important for CDs/DVDs, formatted hard drives, and any process you want to speed up (i.e. use larger block sizes). For a typical file, you can omit this option. For some files, you need to specify (see below).
count: How many blocks to read, total. This means, (size of the file/device) / (block size). See below.
conv: "conversion". This is a "tweaking" option that allows you to get around some annoying pecularities with data reading and checksumming. Suffice to say it's too complicated to explain here, but you can find out more elsewhere. "sync" is VERY important to deal with "padding" on optical media. Play around with these options as you need to.
| md5sum: All output from dd is NOT printed in your terminal window (which would be quite ugly!), and is instead fed into md5sum. NOTE THAT THIS CHECKS IN TEXT MODE UNLESS YOU USE, "md5sum -b" INSTEAD OF JUST "md5sum"! Try it both ways!

If you need to check the block size and count of an optical medium, use (as root) "isoinfo -d -i /dev/whatever". I digress.

For a normal file, you might do it like this:

dd if=myfile.xyz conv=notrunc,noerror,sync | md5sum
OR
dd if=myfile.xyz conv=notrunc,noerror,sync |md5sum -b
(Also try without the "conv=blahblahblah".)

If you can get ANY of the above methods to produce the MD5sum you see on the web page, then the file is OK. If not, the file is bad.

Hope that helps.

--Dane

From what he has written he hasn't got an MD5sum problem, he used (as far as I can tell) the same disc both times. The first time didn't work the second time did.

Right. Just being overly-complete, I guess. :-)

actually my ubuntu is get hanged sometimes when i press some keys then i press power button to get rid of this.

The installation disk will check itself. Boot up from it and the moment you see a logo at the bottom of the screen, press a key and you get a menu. Choose "integrity check" and it will do a checksum test on every file on the disk.

If the disk was fine but the installed OS is not behaving properly, it might be that Ubuntu doesn't work well with your particular computer; that sort of thing can happen. Do an internet search for "Ubuntu" and the computer's model name, to see if anyone else has a similar problem. Sometimes there's a well-known problem and it actually has a solution.

On the other hand, it might just be a particular program. Does the computer hang when you're doing one particular thing?