LinuxQuestions.org - interrupted dpkg can't be fixed because of filesystem location issue?

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - interrupted dpkg can't be fixed because of filesystem location issue? (https://www.linuxquestions.org/questions/linux-general-1/interrupted-dpkg-cant-be-fixed-because-of-filesystem-location-issue-698913/)

interrupted dpkg can't be fixed because of filesystem location issue?

Somehow (I don't know for sure) when I was installing GIMP & Inkscape (last time I install two prgrams at the same time) via apt-get something went wrong and I got a message reading something-swap(space-I-think)-something (I won't lie, I was in a hurry so I just hit enter without reading throughly, now when I try to make an apt-get upgrade I get this:

Code:

debian:/home/oncozerov# apt-get upgrade

E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

Obviously I ran dpkg and this is what I get:

Code:

debian:/home/oncozerov# dpkg --configure -a

Setting up initramfs-tools (0.92o) ...

update-initramfs: deferring update (trigger activated)

Setting up linux-image-2.6.26-1-686 (2.6.26-13) ...

Running depmod.

Running mkinitramfs-kpkg.

mkinitramfs-kpkg failed to create initrd image.

Failed to create initrd image.

dpkg: error processing linux-image-2.6.26-1-686 (--configure):

 subprocess post-installation script returned error exit status 9

Processing triggers for initramfs-tools ...

update-initramfs: Generating /boot/initrd.img-2.6.26-1-686

mkinitramfs: missing sdb root /dev/sdb1 /sys entry

mkinitramfs: workaround is MODULES=most

mkinitramfs: Error please report the bug

update-initramfs: failed for /boot/initrd.img-2.6.26-1-686

dpkg: subprocess post-installation script returned error exit status 1

Now, I KNOW (sure everybody says the same thing) that the problem is the sdb/sdb1 part (which I have marked in red) because originally my machine didn't boot unless I hit 'e' during GRUB to alter the path (that's permanently modified now) otherwise I got a couldn't mount filesystem, my filesystem is in sda (a fact) but I think because I installed from an USB stick and I just have a few weeks playing with linux (I have Debian Lenny installed by the way) I probably did something wrong during the installation so I got that filesystem problem, I'm convinced that issue is totally related to this dpkg error and all I wish for is a pointer as of where is what I' suppoused to modify so that my machine will forever forget that sdb inexistant location.
I hope this goes here, and yes, I've tried reading about dpkg, and initramfs, mkinitramfs, pendriving linux, but still I can't find aomething that'll get my in the right direction.
I almost forgot, MODULES is already set to 'most'.
That's it, thank you.

dpkg is failing while trying to configure linux-image-2.6.26-1-686. Is this your current kernel or is it an old kernel package that you no longer use?

If you no longer use this kernel package then you could try deleting this package and then run configure again.

--------------------
Steve Stites

If my current kernel is the one that I get when I 'uname -r' then I'm afraid it is my current kernel, I'll keep trying to fix this but any other idea will be welcomed, thank you anyway for your attention.

Not sure if this is what you want, but you might check your /boot/grub/device.map file. That's the file that tells grub which device to consider hd0, etc. If there's an hdb entry there you might try removing it.

Well, there was indeed a sdb reference in that file, I've changed it already but I still get the exact same response from the dpkg, I'm beggining to belive there will be endless references to this location, guess I'll just have to keep looking for them, if you know any other filesystem location related files please tell me, but thank you anyway I'm convinced this got me a little bit closer to solve my problem.

Well people, for those of you interested, I've found what I've been looking for, my endless gratefulness to David the H. for it was using the file he suggested that I found the file I had to modify,

which was by the way /etc/fstab in case this is of any use to anyone,

well, that'll be it,

PROBLEM SOLVED.