Thanks, I got that all done. I don't get those few error lines any more. But still apt-get -f install gives errors and seg fault.

(see post #15 for screen dump)

Well at least we seem to have peeled back a layer of the problem onion.

A quick search shows that the seg fault could be related to a faulty dpkg package itself. You have a search around, and I will too, and we'll see what we can do about it.

Just a note that problems like this are a perfect example of why it is a good idea to image your partitions on a regular basis. If I had come across it on my system, and realised how it doesn't just have a simple solution, I would have rolled back to my most recent weekly image, checked the package management situation, and then worked carefully through the update process step by step.

To see if this is purely dpkg related, can you post the output from:

Did you try to do fsck to repair file system? Also, if seg fault is caused by dying card, it would be better to backup what you can from it, while you still can. Further playing with dying card could just speed up process, so it is better to save what you can, while you are still able to.

I think I did. I ran the command that should have caused it to run one at next reboot and then rebooted. I'm remote from the machine so I don't know for sure what it found.

I'm trying to get the card pulled so I can attempt to clone it to a new one. Any suggestions on a good process for that? I'm open to suggestions!

$ sudo dpkg --audit
The following packages have been unpacked but not yet configured.
They must be configured using dpkg --configure or the configure
menu option in dselect for them to work:
libc-dev-bin GNU C Library: Development binaries
libc6-dbg:armhf GNU C Library: detached debugging symbols
libc6-dev:armhf GNU C Library: Development Libraries and Header Files
libtirpc1:armhf transport-independent RPC library
rpcbind converts RPC program numbers into universal addresses

Have you tried configuring them as suggested? (although I suspect that dpkg will barf again)

Okay, I imaged the SD and copied it onto a new SD card and installed it. I then did:
sudo touch /forcefsck

hoping that would fix up the new drive. Nothing seems to have changed, all the commands in this thread fail with the same errors. Any ideas what I can do to fix up this drive?


Thanks!

Why imaged it? Why not simply making back up of important data, install fresh system on new SD card and then restore what is important from backup? If you imaged damaged filesystem, then it is looks logical to me that your new SD card will get same errors.

I guess I was thinking the new file system would only have logical errors (if any) whereas the old drive possibly had hardware errors? Seems like it should be fixable.

Anyone have a backup tutorial they recommend? took me awhile to get this system built and configured so kinda hate to start over again.

The Maildir folders would be some of the most important to me.

https://wiki.archlinux.org/index.php...kup_with_rsync

https://opensource.com/article/17/1/rsync-backup-linux

https://www.linux.com/news/back-expert-rsync

Those are rsync options. There are few more ways to do it, but this should be good enough. Also, in case of read errors on your drive, you might use gddrescue. Guess that what you really want is to be sure to backup your home and your config files. Rest is, more or less, replaceable.