cryk_ Posted December 12, 2022 Share Posted December 12, 2022 Hello everybody, i have installed the current Armbian version on my banana pi m5 (Image-data: Armbian_22.11.1_bananapim5_bullseye_edge_6.0.10.img). the system starts and the login works without problems, but I can't update and upgrade anything. When I used the command apt update && apt upgrade, I get the following error: https://ibb.co/jbRcJwk Is this problem already known and can anyone help me with it? 0 Quote Link to comment Share on other sites More sharing options...
Myron Posted December 12, 2022 Share Posted December 12, 2022 @cryk_ Provide diagnostic logs with ... armbianmonitor -u ... and post the link here. It'll may help others determine what the issue is. The diagnostic logs might reveal why your file system is read-only and not read-write. 1 Quote Link to comment Share on other sites More sharing options...
cryk_ Posted December 14, 2022 Author Share Posted December 14, 2022 @MyronHere is my diagnostic log https://paste.armbian.com/tediwanoqu I have tried to remount my file system with... mount -o remount,rw / ...but I can't change it. 0 Quote Link to comment Share on other sites More sharing options...
Myron Posted December 14, 2022 Share Posted December 14, 2022 @cryk_ Have you run a file system check and repair on the root file system? There are conditions where if the file system is not clean then the root file system is always mounted as read-only. Also check the /etc/fstab file and make sure there are no errors and/or inconsistencies in there. Also see: https://www.thegeekstuff.com/2016/03/forcefsck-on-reboot/. Should work on an Armbian built system. I believe it is safe to invoke e2fsck on a read-only root file system as nothing is getting written. It's dangerous to use e2fsck on a read-write root file system and I don't believe e2fsck will allow you to perform repair operations on a read-write enabled file system. 0 Quote Link to comment Share on other sites More sharing options...
RES Posted December 17, 2022 Share Posted December 17, 2022 Start sbc on new image on sdcard and run fsck on mcc0. 0 Quote Link to comment Share on other sites More sharing options...
Myron Posted December 18, 2022 Share Posted December 18, 2022 @RES ... except when I look at the diagnostic log there is no mmc0 device. There is an mmcblk0. Is this the one you're referring to? 0 Quote Link to comment Share on other sites More sharing options...
gene1934 Posted January 9, 2023 Share Posted January 9, 2023 among other possible things, you must be capable of becoming root, and prefacing those commands with a "sudo" apt update, giving your user pw to the requester for it that should pop up if you are in the sudoers file. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.