#20617: trunk ar71xx: dropbear inactive because filesystem read-only
----------------------------------------------+----------------------------
Reporter: doddel | Owner: developers
Type: defect | Status: new
Priority: high | Milestone: Chaos Calmer
Component: base system | (trunk)
Keywords: file system read-only after boot | Version: Trunk
----------------------------------------------+----------------------------
checked out revision 47062 (27/9/2015) for Ubiquiti RouterStation, ar71xx
based.
After flashing can only reach the board via serial console.
Problem: the entire filesystem, including //etc/dropbear and //tmp is read
only so the key generation process cannot write anything and dropbear
cannot start. At least that is the error given when trying to write
anything: 'read-only filesystem'.
Something seriously defective in the creation over the filesystem
overlays.
Output of cat //proc/mounts:
/dev/root / squashfs ro,relatime 0 0
proc /proc proc rw,noatime 0 0
sysfs /sys sysfs rw,noatime 0 0
tmpfs /tmp tmpfs rw,nosuid,nodev,noatime 0 0
tmpfs /dev tmpfs rw,relatime,size=512k,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
debugfs /sys/kernel/debug debugfs rw,noatime 0 0
--
Ticket URL: <https://dev.openwrt.org/ticket/20617>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
