daemon is being inhibited

Asked by Diego Lluna on 2010-08-04

Hi,
I am trying to install ubuntu 10.04 from a boot CD. A fresh install.
System has one IDE 120GB disk. AMD x32 processor.

I can't install it from the CD. It gives an error and sends me to an emulated RAM session.
There, I can see the disk, a partition just made for a Windows XP system, and a 90 GB empty space.

When I try to partition this space from Linux (ext3 or ext4), I get the error:
"error creating partition"
An error occurred while performing an operation on "120 GB Hard Disk" (AT Maxtor ...):
The daemon is being inhibited

any ideas how can I solve this?

I discard a hardware problem, since I just installed a fresh Windows XP with no problem. Linux simply will not access the disk. Cannot format the existing partition, or create a new one.

many thanks,
Diego

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2010-08-04
Last reply:
2011-02-22

Did you MD5 test the ISO you burned?
Did you burn the CD as SLOWLY as you could?
Did you check the CD for defects?
Have you tested your RAM?

Diego Lluna (diego-lluna) said : #2

I just downloaded again the file, directly from
http://www.ubuntu.com/desktop/get-ubuntu/download

It has exactly same name and size, I can burn another CD to try, though I hardly believe that would be the issue. If there was a problem with the CD, why not give a simple I/O error?

no, I haven't tested the RAM, but Windows is working fine.

There used to be a linux server on this machine. It was using a RAID 1 on two disks. RAID is now disabled, and I have disconnected one of the disks to avoid confussion.
Ubuntu detects the single drive fine, so I really can't find the explanation.

best

Diego Lluna (diego-lluna) said : #3

Again... when I try the installation from the RAM emulated ubuntu, i can get up to step 4, where it is asking to prepare the partitions, and does not find any.

However, in the Disk utility, ubuntu is seeing the disk, and saying that it is healthy.

The name and size are moot, you can have single bit errors all through the data, the name and size will match but the data will be garbage. It is also moot where you get it from. As long as the hashes generated when you MD5 match these then you could have got the image from ANYWHERE but you know it is an Ubuntu image and is complete and consistant:
https://help.ubuntu.com/community/UbuntuHashes

Check your ISO. If the file is bad then it will explain the bad install experience.

Jitter errors and downright crappy burners can cause even MD5 passed images to fail. The CD is a moving object in the drive so bad burns can happen. Once you see the stickman screen, press space and select "Check CD for defects"

Windows can mark ram as "bad" and will not use it, a few are ok but many are dangerous, The CD has a slick memory checker which you can stop after 5 or 10 mins and assume all is well

Prety much all through the install procedure you have assumed all to be well when infact it may not be the case, you have no concrete way of knowing what you are dealing with is right or good or error free and have failed to test anything. There are ways though and you should use them every time you install so you know the media and hardware are not at fault.

rory edwards (r-l-edwards) said : #5

I have the same problem am just running the checkers and have burned the disk on super slow and checked for errors.

no errors on the disk and ram is ok

any other ideas,

i'm trying to install on toshiba portege pentiumIII 1GHz , 512K ram

any help is great thanks

rory edwards (r-l-edwards) said : #6

I have the same problem am just running the checkers and have burned the disk on super slow and checked for errors.

no errors on the disk and ram is ok

any other ideas,

i'm trying to install on toshiba portege pentiumIII 1GHz , 512K ram

any help is great thanks

Can you help with this problem?

Provide an answer of your own, or ask Diego Lluna for more information if necessary.

To post a message you must log in.