Read-Only file system error : Faulty EMMC?

[adxv]

Hey all,

Apologies in advance if this is a newbie question, but has anyone had any read-only errors on their wifi pineapples?

About 10 minutes into testing a phishing page (with the "evil portal" module) the UI stopped showing all of the portals I had installed, along with their respective controls (despite they being visible in the shell), furthermore, all the other modules I installed, now show a pop up which says: chmod /path/to/modules.py: read-only file system 

Even in the shell, sure enough the 2GB EMMC mount has a read only flag.

In the logs I see this: EXT4-fs error (device mmcblk0): ext4_journal_check_start:61: Detected aborted journal

Factory reset doesn't do anything, and firmware recovery either still retrieves the original configuration somehow, or doesn't mount the EMMC (if I do an offline firmware update).

 

ANY assistance would be greatly appreciated.

Thanks

[cooper2k4]

Hi

Your topic is already a year old, but I have similar problems. Every now and then the EMMC is not recognized. After turning off the power and rebooting, the memory reappears. I do not know what is the cause of this.

The states of two subsequent boots:

 __          ___ ______ _   _____ _  oxl:::oOOo:::lxo,;0W:       _.O   KMk
 \ \        / (_|  ____(_) |  __ (_) MMWk:.;,.;kWMMMMKc;.       | |  .OX:
  \ \  /\  / / _| |__   _  | |__) _ _ __   ___  __ _ _ __  _ __ | | ___
   \ \/  \/ / | |  __| | | |  ___| | '_ \ / _ \/ _` | '_ \| '_ \| |/ _ \
    \  /\  /  | | |    | | | |   | | | | |  __| (_| | |_) | |_) | |  __/
     \/  \/   |_|_|    |_| |_|   |_|_| |_|\___|\__,_| .__/| .__/|_|\___|
----------------------------------------------------| |-- | |-----------------
 * Firmware Version: 1.1.1                          |_|   |_|  Mark VII
 * Documentation: https://docs.hak5.org
 * Community: https://community.hak5.org  * Interface: http://172.16.42.1:1471
------------------------------------------------------------------------------
Your JFFS2-partition seems full and overlayfs is mounted read-only.
Please try to remove files from /overlay/upper/... and reboot!
root@mk7:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                19.0M     19.0M         0 100% /rom
tmpfs                   124.5M    180.0K    124.3M   0% /tmp
/dev/mtdblock6           10.6M     10.4M    164.0K  98% /overlay
overlayfs:/overlay       10.6M     10.4M    164.0K  98% /
tmpfs                   512.0K         0    512.0K   0% /dev
root@mk7:~# fdisk -l
root@mk7:~#

----------------------------------------------------| |-- | |-----------------
 * Firmware Version: 1.1.1                          |_|   |_|  Mark VII
 * Documentation: https://docs.hak5.org
 * Community: https://community.hak5.org  * Interface: http://172.16.42.1:1471
------------------------------------------------------------------------------
root@mk7:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                19.0M     19.0M         0 100% /rom
tmpfs                   124.5M    184.0K    124.3M   0% /tmp
/dev/mmcblk0              1.8G     71.8M      1.6G   4% /overlay
overlayfs:/overlay        1.8G     71.8M      1.6G   4% /
tmpfs                   512.0K         0    512.0K   0% /dev
root@mk7:~# fdisk -l
Disk /dev/mmcblk0: 1876 MB, 1967128576 bytes, 3842048 sectors
60032 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk0 doesn't contain a valid partition table

root@mk7:~# dmesg |grep mmc
[    6.210979] mmc0: new high speed MMC card at address 0001
[    6.231510] mmcblk0: mmc0:0001 H2G1c 1.83 GiB 
[    9.502993] EXT4-fs (mmcblk0): recovery complete
[    9.515495] EXT4-fs (mmcblk0): mounted filesystem with ordered data mode. Opts: 

 

[Foxtrot]

This is definitely not intentional. I recommend trying to a firmware recovery and seeing if the issue is solved. If not, please seek a replacement.

 

[Gwozd]

Is this not malware that encrypts files? If so, then it’s bad, because I ran into this problem. I can restore access to files through EFS Recovery. But restoring the firmware didn't help.