Dpkg error unable to access dpkg status area read only file system

dpkg: unable to access dpkg status area: Read-only file system

I running Kubuntu Intrepid Ibex and I tried to do a routine upgrade with the adept installer.
During the upgrade I got an error that told me to either
sudo dpkg —configure -a
or
sudo apt-get -f install
in terminal

sudo apt-get -f install tells me to run sudo dpkg —configure -a and configure gives me the error
dpkg: unable to access dpkg status area: Read-only file system

when I try to run the adept installer again I get the error configuration file «home/david/ .kde/share/ config/ kdesudorc» not writable.
And am then prompted for my password.

I still have the update notifier on the system tray.

Question information

Please open a terminal from menu Applications→ Accessories→ Terminal and copy and paste here the result of:

command, thank you.

Sorry, you must have different menu to open terminal (you are using Kubuntu).

Please open a terminal from your kde kubuntu menu copy and paste here the result of:

command, thank you.

when I try to empty my trash I get the error «/home/ david/. kde/share/ config/ kio_trashrc» not writable

When I try to access my home folder with dolphin I get the error «The process for the file protocol died unexpectedly»

I have 2 harddrives in my computer, I had kubuntu on one and windows xp on the other. About 2 weeks ago the harddrive with xp on it, died. I heard a clicking noise and my computer wouldn’t recognize either drive. When I removed the bad drive I was able to use kubuntu again and I bought a new drive to replace the old one. I fear that if I were to restart my computer I would find that error with my other old hard drive.

# mount
/dev/sdb1 on / type ext3 (rw,errors= remount- ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid, mode=0755)
/proc on /proc type proc (rw,noexec, nosuid, nodev)
sysfs on /sys type sysfs (rw,noexec, nosuid, nodev)
varrun on /var/run type tmpfs (rw,nosuid, mode=0755)
varlock on /var/lock type tmpfs (rw,noexec, nosuid, nodev,mode= 1777)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec, nosuid, gid=5,mode= 620)
fusectl on /sys/fs/ fuse/connection s type fusectl (rw)
lrm on /lib/modules/ 2.6.27- 9-generic/ volatile type tmpfs (rw,mode=755)
/dev/sdg1 on /media/disk type fuseblk (rw,noexec, nosuid, nodev,allow_ other,blksize= 512)
securityfs on /sys/kernel/ security type securityfs (rw)
binfmt_misc on /proc/sys/ fs/binfmt_ misc type binfmt_misc (rw,noexec, nosuid, nodev)
/dev/sdh1 on /media/disk2 type fuseblk (rw,noexec, nosuid, nodev,allow_ other,blksize= 4096)

Might be your / filesystem mounted in read only mode because it contain error.

Do you have the Ubuntu live install cd.

You can boot from this cd and make a filesystem check from terminal

sudo fsck /dev/sdb1

Or using the gparted partition «check» option (right click on a partition), menu System→ Administration→ Partition editor

Select the /dev/sdb hard-disk from gparted top right list box.

Please note: your device name might be diffrent from what i used before in this answer.

Hope this helps

I don’t have a disk on me, and I don’t think I will be able to download anything.
I can probably ask one of my friends to do it for me.

The closest application I could find in my system menu was Disk management. When try to run it I get the error, there are no file systems which you are allowed to mount/unmount.

I’m not sure I’m in readonly mode. Before I started getting these errors I was downloading things to my desktop. I didn’t restart my computer but I did have to restart my x-server at one point. I’m fairly certain I did it before I was downloading things to my desktop. Now that I think about it, some error text flashed across the screen before the login screen reappeared.

This may be unrelated but I had to restart my x-server because there are rare occurrences where my mouse pointer stops working. I can move it around but clicking does nothing and the pointer graphic doesn’t change when I mouse over things where it normally would.

well I was right about restarting my computer. I wasn’t my choice to, I woke up and my screens were black. When I restarted it I got a lot of errors most containing the text
ata5.00: STATUS (DRDY ERR)
I/O error on sdb5 logical block 3

there were a lot of other errors but my cellphone doesnt want to email me the pictures.

I restarted my computer with my other partition, the one on sda, I got a ton of those errors again. More logical block errors 3 and more. But this one was able to boot up.

These are common partition hard disk errors. (i think hardware errors) please consider to reformat the failed disk or partition. and it is strongly suggested to replace the damaged device.

Hope this helps

Can you help with this problem?

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

Источник

Cannot install using Software Center — fix does not work

The Ubuntu Software Center no longer lets me install software (tried to install pdfsam, and Synaptic, both give the same error):

There seems to be a programming error in aptdaemon, the software that allows you to install/remove software and to perform other package management related tasks.

Details: Traceback (most recent call last):

File «/usr/lib/python3/dist-packages/aptdaemon/worker.py», line 325, in _process_transaction self._apply_changes(trans)

File «/usr/lib/python3/dist-packages/aptdaemon/pkcompat.py», line 3157, in _apply_changes install_range)

File «/usr/lib/python3/dist-packages/aptdaemon/worker.py», line 1151, in _apply_changes with self._frozen_status():

File «/usr/lib/python3.4/contextlib.py», line 59, in enter return next(self.gen)

File «/usr/lib/python3/dist-packages/aptdaemon/worker.py», line 1175, in _frozen_status frozen_dir = tempfile.mkdtemp(prefix=»aptdaemon-frozen-status»)

File «/usr/lib/python3.4/tempfile.py», line 426, in mkdtemp dir = gettempdir()

File «/usr/lib/python3.4/tempfile.py», line 370, in gettempdir tempdir = _get_default_tempdir()

File «/usr/lib/python3.4/tempfile.py», line 312, in _get_default_tempdir dirlist)

FileNotFoundError: [Errno 2] No usable temporary directory found in [‘/tmp’, ‘/var/tmp’, ‘/usr/tmp’, ‘/’]

I found and tried this fix, which is featured in all the threads I could find on this problem: Cannot install any software from the Software Center due to ttf-mscorefonts-installer package error

The command sudo dpkg —configure -a does not work. Output:

sudo: unable to open /var/lib/sudo/andreas/5: No such file or directory

dpkg: error: unable to access dpkg status area: Read-only file system

Now, I am a Linux-newbie. Before Ubuntu I have used Linux Mint 15, then 16. There the system frequently froze, in particular during installation of new software via apt-get or the software center, which, upon restart, somehow screwed up my user rights (what seems to be the case here, too?) and file system. To fix it I had to reinstall Mint (repeatedly).

Some more background: A few days ago Ubuntu froze, and over lots of waiting (it didn’t recover) I found the solution online: What should I do when Ubuntu freezes?

If it locks up completely, you can REISUB it, which is a safer alternative to just cold rebooting the computer.

Could this have caused the problem? Before that, Software Center worked just fine.

I switched from Mint to Ubuntu under the impression that Ubuntu is more stable and less «tinkery» than Mint. I really really don’t want to switch back to Windows, but I need my laptop to work, and work reliably; thesis deadline is coming closer.

Источник

Fixing failed upgrade to 13.10 [duplicate]

When I start Ubuntu after it froze during an upgrade to 13.10, it says:

When I use sudo apt-get update it eventually says:

E: dpkg was interrupted, you must manually run «sudo dpkg —configure -a» to correct the problem

When I run that command, it says:

dpkg: error: unable to access dpkg status area: Read-only file system

And then gives me the root prompt again. Please help! I’m a VERY basic user of Ubuntu.

2 Answers 2

Try remounting your file systems read/write, as described here and here, and then rerunning dkpg . I.e., do

See the linked answers for more info if this does not work.

Ubuntu usually remounts a file system as read-only if it detects an error with said system (this is done to prevent further file-system errors). To fix this, I would suggest you reboot your system. When the bootloader comes up, select the «Advanced options for Ubuntu» option. Select a kernel in Recovery Mode (generally, the newest one on the list should do). Select the option to boot into a root shell. Once in the root shell, run fsck -f -y / , and and restart the system using either reboot , or shutdown -r now . If after this, you still get the same above error, you may have a failing hard drive.

Linked

Hot Network Questions

Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.1.14.43159

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник

Snappy 15.04: How to install deb file? nano deb

On Snappy Ubuntu 15.04 : Linux localhost.localdomain 3.19.0-51-generic #57-Ubuntu SMP Fri Feb 19 14:05:05 UTC 2016 x86_64 x86_64 x86_64 GNU/Linu

With much pain, using curl.curl and moving of file, I was able to download the nano deb file.

However, when I tried to run sudo dpkg -i nano_2.2.6-3_amd64.deb it failed with error message dpkg: error: unable to access dpkg status area: Read-only file system

1 Answer 1

Snappy Ubuntu Core is a read-only file system. It’s based on snap and not on debs. It means that you can’t install them on your system on purpose.

You can make a «nano» snap that you will install on your system. For more information on how to create snaps, here is the tour (do not hesitate to explore the developer website): https://developer.ubuntu.com/en/snappy/build-apps/

Hot Network Questions

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.1.14.43159

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник

Ubuntu shut down while updating?

Last night I was updating my Ubuntu 10.04 to either 11.04 or 12.04 (I’m not entirely sure which one it was, but I think it was 11.04) and I left it overnight to finish. When I came down in the morning, I noticed that the computer hadn’t barely begun installing the updates! The update thing said that my computer was on the installation step, but it was still preparing the libc bin (or whatever its called) . It’s like the first part of the step installing the upgrades. So, I stupidly restarted the computer, and when it rebooted, I got five options on a purple screen:

Long story short, not matter which way I enter Ubuntu to try and reinstall the updates using the root thing (it’s like terminal) after I enter sudo apt-get update it basically said it failed to fetch every url link, and it then says:

So, I entered sudo dpkg —configure -a , and it says:

I’m left like wtf, and I really just some guidance here. I just got this laptop, and I can not afford a new one if I broke this one.

1 Answer 1

I think you cannot upgrade from an EOL version to another EOL version. 10.04 and 11.04 are both reached EOL and not supported anymore.

The best option you have now IMO , is to download the .iso of a supported version eg: Ubuntu 12.04 LTS , create a bootable DVD or USB and upgrade Ubuntu through the installer window. You will see the option «upgrade 10.04 to 12.04»

Following links will help you in case you don’t know how to create a Live DVD or USB and how to install Ubuntu.

Источник

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх