LinuxQuestions.org - [SOLVED] Failure when attempting to update the kernel

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Failure when attempting to update the kernel (https://www.linuxquestions.org/questions/linux-newbie-8/failure-when-attempting-to-update-the-kernel-4175614692/)

Failure when attempting to update the kernel

I never had a problem before, including the same OS (Linux Mint 18) on other computers. This is after a fresh install on a Lenovo Thinkpad T470. I am trying to update from kernel 4.10.0-32 to 4.10.0-35. My configuration is that I have Centos 7 installed on partitions 1 & 2 (GRUB here is used to select OS), and Linux Mint 18 installed on partition 4. Windows is out of the picture installed on a separate hard drive. Uninstalling the kernel and cleaning the update caches/etc. and then reinstalling the kernel results in the same error. Running various broken link or other fixes within the update Manager or from within apt does not solve the problem. I have also tried installing from both the Update Manager as well as apt from the command line. Regular non-kernel updates work fine, and the OS works fine as well.

The following is the kernel install attempt messages and error messages:

Code:



Selecting previouslyunselected package linux-headers-4.10.0-35.

(Reading database... 235675 files and directories currently installed.)

Preparing to unpack.../linux-headers-4.10.0-35_4.10.0-35.39~16.04.1_all.deb ...

Unpackinglinux-headers-4.10.0-35 (4.10.0-35.39~16.04.1) ...

dpkg: errorprocessing archive/var/cache/apt/archives/linux-headers-4.10.0-35_4.10.0-35.39~16.04.1_all.deb(--unpack):

 unable to open'/usr/src/linux-headers-4.10.0-35/arch/score/kernel/Makefile.dpkg-new':Operation not permitted

Selecting previouslyunselected package linux-headers-4.10.0-35-generic.

Preparing to unpack.../linux-headers-4.10.0-35-generic_4.10.0-35.39~16.04.1_amd64.deb...

Unpackinglinux-headers-4.10.0-35-generic (4.10.0-35.39~16.04.1) ...

Selecting previouslyunselected package linux-image-4.10.0-35-generic.

Preparing to unpack.../linux-image-4.10.0-35-generic_4.10.0-35.39~16.04.1_amd64.deb ...

Done.

Unpackinglinux-image-4.10.0-35-generic (4.10.0-35.39~16.04.1) ...

dpkg: errorprocessing archive/var/cache/apt/archives/linux-image-4.10.0-35-generic_4.10.0-35.39~16.04.1_amd64.deb(--unpack):

 unable to createnew file '/var/lib/dpkg/info/linux-image-4.10.0-35-generic.list-new':Operation not permitted

Selecting previouslyunselected package linux-image-extra-4.10.0-35-generic.

Preparing to unpack.../linux-image-extra-4.10.0-35-generic_4.10.0-35.39~16.04.1_amd64.deb...

Unpackinglinux-image-extra-4.10.0-35-generic (4.10.0-35.39~16.04.1) ...

dpkg: errorprocessing archive/var/cache/apt/archives/linux-image-extra-4.10.0-35-generic_4.10.0-35.39~16.04.1_amd64.deb(--unpack):

 unable to open'/lib/modules/4.10.0-35-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko.dpkg-new':Operation not permitted

Errors wereencountered while processing:

/var/cache/apt/archives/linux-headers-4.10.0-35_4.10.0-35.39~16.04.1_all.deb

/var/cache/apt/archives/linux-image-4.10.0-35-generic_4.10.0-35.39~16.04.1_amd64.deb

/var/cache/apt/archives/linux-image-extra-4.10.0-35-generic_4.10.0-35.39~16.04.1_amd64.deb

E: Sub-process/usr/bin/dpkg returned an error code (1)

A package failed toinstall.  Trying to recover:

dpkg: dependencyproblems prevent configuration of linux-headers-4.10.0-35-generic:

linux-headers-4.10.0-35-generic depends on linux-headers-4.10.0-35;however:

  Packagelinux-headers-4.10.0-35 is not installed.





dpkg: errorprocessing package linux-headers-4.10.0-35-generic (--configure):

 dependency problems- leaving unconfigured

Just guessing, out of inodes perhaps?

Quote:

Originally Posted by Emerson (Post 5764122)

Just guessing, out of inodes perhaps?

It is a brand new install. In any event I checked and it is at only 10% usage.

Quote:

Operation not permitted

Presuming you are manually doing this through the terminal, use sudo.

Quote:

Originally Posted by syg00 (Post 5764224)

Presuming you are manually doing this through the terminal, use sudo.

No, I did not do the update manually (If you meant the command line). Those messages are from the details screen of the Update Manager program.

Hmmm - let me check the logs on another machine. I did a selective kernel update on someone elses' machine a few days back.

Can't see anything odd in the logs. But the system in question has zero files containing dpkg-new - I don't know enough about apt/dpkg, but I'm guessing temporary filename until install.
Everything under /usr/src/... are owned root:root - with the Makefile (note, not Makefile.dpkg-new) world readable, and writable by root.

Hopefully somebody with more apt knowledge will be able to help.

I fear I am going to have to reinstall everything. Maybe the install is corrupted for some reason (I did do a crc check on the download), or Mint doesn't like my hardware. I dread reinstalling all my programs and changing settings everywhere again, but oh well.

Create a /home partition and copy everything over. Select that during install as /home and don't format it. Create the same users and passwords (optional).
You'll have to re-install the packages, but they'll come up customised as at present.

SOLVED: Found a post with the identical error. Sophos Anti-Virus was preventing the install of the new kernel so I removed it.

Ugh.
But you gotta expect things like that if you run anti-virus I guess.

I run Sophus on 4 other different distros without an issue. So, I switched to Clam o n Linux Mint. Linux is becoming more and more a target, but my main reason is that I often transfer files to/from Windows computers.