dpkg freezes on depmod

Asked by Noam

The update manager says:
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
when I run: sudo dpkg --configure -a
I get:
Setting up linux-image-2.6.24-19-generic (2.6.24-19.36) ...
Running depmod.

and then the system freezes completely, and only a "hard" boot works.
Thanks for your help,
Noam.

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Daniel Schwitzgebel (schwitzd) said :
#1

try to restart and start from recovery mode and run
sudo dpkg --configure -a

Revision history for this message
Noam (noam-ugiya) said :
#2

Thanks for the quick response.
I got stuck in an endless loop:
ata1.00: status {DRDY ERR}
ata1.00: error: {UNC}
ata1.00: exception Emask 0x0 SACT 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x45
ata1.00: cmd c8/00:08:ff:72:58/00:00:00:00:00/e1 tag 0 dma 4096 in
ata1.00: status {DRDY ERR}
ata1.00: error: {UNC}
ata1.00: exception Emask 0x0 SACT 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x45
ata1.00: cmd c8/00:08:ff:72:58/00:00:00:00:00/e1 tag 0 dma 4096 in
... and so on.
Any ideas?

Revision history for this message
Rajkumar.R (rraj-be) said :
#3

Try fsck to check your disk's and then try to install.

The command is "sudo fsck"

Revision history for this message
Noam (noam-ugiya) said :
#4

fsck 1.40.8 (13-Mar-2008)
e2fsck 1.40.8 (13-Mar-2008)
/dev/sda1 is mounted.

WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? yes

/dev/sda1: recovering journal
Clearing orphaned inode 66156 (uid=1000, gid=1000, mode=0100600, size=4100)
Clearing orphaned inode 32656 (uid=1000, gid=1000, mode=0140755, size=0)
/dev/sda1: clean, 182426/1175040 files, 849490/4696996 blocks (check in 3 mounts)

then when I try:
sudo dpkg --configure -a

it freezes again...
depmod still stuck...

Revision history for this message
Noam (noam-ugiya) said :
#5

after running: sudo fsck -c
it fixed a few bad sectors, and after resetting the system, it now says:
dpkg: failed to open package info file `/var/lib/dpkg/status' for reading: No such file or directory

What's the next step?

Revision history for this message
Launchpad Janitor (janitor) said :
#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.