openwifi/doc/known_issue/notter.md
Jiao Xianjun a4916c0701
Add solution to known issue:
No space left on device
2023-06-07 11:22:18 +02:00

1.9 KiB

Known issue

Network issue in quick star

If can't ssh to the board via Ethernet for the 1st time, you might need to delete /etc/network/interfaces.new on SD card (on your computer).

If still can't ssh the board via Ethernet, you should use UART console (/dev/ttyUSBx, /dev/ttyCH341USBx, etc.) to monitor what happened during booting.

EXT4 fs error rootfs issue

Sometimes, the 1st booting after flashing SD card might encounter "EXT4-fs error (device mmcblk0p2): ..." error on neptunesdr, changing SD card flashing tool might solve this issue. Some tool candidates:

  • gnome-disks
  • Startup Disk Creator
  • win32diskimager

antsdr e200 UART console

If can't see the UART console in Linux (/dev/ttyUSB0 or /dev/ttyCH341USB0), according to https://github.com/juliagoda/CH341SER, you might need to do sudo apt remove brltty

Client can not get IP

If the client can not get IP from the openwifi AP, just re-run "service isc-dhcp-server restart" on board and do re-connect from the client.

No space left on device

It might be due to too many dmesg/log/journal, disk becomes full.

systemd-journald[5694]: Failed to open system journal: No space left on device

You can try following operations.

systemd-tmpfiles --clean
sudo systemd-tmpfiles --remove
rm /var/log/* -rf
apt --autoremove purge rsyslog

Add followings into /etc/systemd/journald.conf

SystemMaxUse=64M
Storage=volatile
RuntimeMaxUse=64M
ForwardToConsole=no
ForwardToWall=no