read-only boot partition?
#1
Hi all,
I'm not sure if this is really a linux / debian / whatever issue, or what, but it seems my /boot partition is read only. (let me know, or mods, feel free to move me).

I installed the original Debian version (not the "unofficial installer"), which installs Debian 9 or so, then upgraded that to Debian Sid (via the usual "update the releases file and apt-get update , apt-get update", and resolving some dependency issues). Then only recently, I realized that apt-get dist-upgrade doesn't actually upgrade the kernel like it does in ubuntu (been using xuubuntu for 12 years or so now, and not much else), so I went along with this to upgrade the kernel, but ran into an error where apt-get / dpkg said /boot was read-only. indeed, "cd /boot; sudo touch 'testing.txt'" shows it's read only, even to root, despite "sudo ls -l" from "/" telling me root ought to have read permissions. strange. This is linux installed on the eMMC module, which /boot and / (which includes home which i've been freely writing to for a while now) are partitions on.

it shouldn't be device dependent (both home (which I can write to) and boot (which I can't) are on the same device). it shouldn't be OS / mount dependent (nothing in fstab aside from swap, and "ls -l" says root is allowed to write to it). so what's up?

I did find this thread, but it appears to not really be resolved.

I'm also not exactly sure where else to look (what system logs, etc, and where?). (un)fortunately, xubuntu has served me extraordinarily well over the years and I spend more of my time doing daily computerly things than i do looking through logs files and troubleshooting things (so I may be a bit out of the loop, please bear with me).

EDIT: interesting. I was able to unmount /boot via gparted, then remount it (idk, an icon showed up on my desktop and i clicked on it), and then I was able to write to it, and "sudo apt-get install linux-image05.8...". I did see a few warnings appear, regarding drivers not found though. rebooting, I appear to still be in linux 4.4.207, per uname.

google tells me I'd want to update grub if i were on a more typical system which used grub, but otherwise i'm not sure how to get into the newer kernel which is supposedly installed. (also unsure if i even want to get into the newer kernel, given those driver errors it showed....)
#2
4.4.207?? You didn't get most up to date on git,, 4.4.210,, and the (mrfixit) updates to 4.4.213
(ls /lib/modules)
That update is an icon just left of clock, bottom right (logged in as root)
If you added a user, it (icon) may not be there (also updates & writes u-boot)
/usr/bin/mrfixit_update.sh (as root,, it will modify extlinux.conf too)
BTW, extlinux has NOTHING to do with syslinux, just the same name
I don't think you want (or should) use a stock debian kernel,
it lacks pbp specific patches
You know kernel is 64 bit,, userland armhf (32 bit)?? (mrfixit distro)
#3
(09-16-2020, 10:06 PM)wdt Wrote: 4.4.207?? You didn't get most up to date on git,, 4.4.210,, and the (mrfixit) updates to 4.4.213
(ls /lib/modules)
That update is an icon just left of clock, bottom right (logged in as root)
If you added a user, it (icon) may not be there (also updates & writes u-boot)
/usr/bin/mrfixit_update.sh (as root,, it will modify extlinux.conf too)
BTW, extlinux has NOTHING to do with syslinux, just the same name
I don't think you want (or should) use a stock debian kernel,
it lacks pbp specific patches
You know kernel is 64 bit,, userland armhf (32 bit)?? (mrfixit distro)

yup, 4.4.207. only updating I ever did here was the "standard" routes (apt-get update / upgrade / dist-upgrade), so i guess I missed that. (and I made a new user right away so I guess i never saw the updates icon, thanks for pointing that out).

ls /lib/modules:
4.4.207  5.8.0-1-armmp 5.8.0-1-armmp-lpae
(5.8.0-1 is what I apt-get installed manually per here, but clearly i'm not using it)

I found mrfixit_update.sh in /usr/bin just now, thank you! I was looking for it before but I never found it so i thought "hey maybe there's something different about the stock vs unofficial etc". i'll give that a poke and post back.

thanks for your help!


Possibly Related Threads…
Thread Author Replies Views Last Post
  Pinebook pro won't boot after bootloader installation jwensouls 4 705 08-21-2024, 04:17 AM
Last Post: KC9UDX
  Need Help Recovering Manjaro /boot Contents on Pinebook Pro calinb 6 3,300 12-11-2023, 03:47 AM
Last Post: calinb
  Boot Order in Pinebook Pro food 8 2,455 11-23-2023, 07:37 AM
Last Post: KC9UDX
  [Manjaro] u-boot won't boot from eMMC with (unbootable) SD card present zackw 1 2,374 08-21-2023, 09:08 PM
Last Post: vanessadonald
  Emergency Mode Boot Hotkey? jiacovelli 20 7,132 06-02-2023, 01:32 PM
Last Post: wdt
  Tow Boot install help Paulie420 7 4,726 11-24-2022, 10:24 AM
Last Post: myself600
  Resume from suspend not working after flashing Tow-Boot to SPI xp19375 3 2,436 10-31-2022, 10:14 AM
Last Post: wdt
  Bootloader: SD card boot quirks crazyquark 1 1,338 10-04-2022, 12:27 PM
Last Post: elitegamercody
  Fresh Manjaro does not boot from eMMC pentamassiv 7 5,408 08-18-2022, 11:47 AM
Last Post: Bemo
  PBP won’t boot from eMMC after Debian update / Tow-Boot installer won’t boot from SD Pino64 21 12,703 05-12-2022, 05:00 AM
Last Post: Pino64

Forum Jump:


Users browsing this thread: 1 Guest(s)