Jump to content

Recommended Posts

Posted

Clean Installation of Armbian Stretch mainline kernel 4.14.y to the internal memory of the Orange PI

 

   2018-05-10 09:38:51: (mod_accesslog.c.180) writing access log entry failed: /var/log/lighttpd/access.log No space left on device

   2018-05-10 09:39:21: (mod_accesslog.c.180) writing access log entry failed: /var/log/lighttpd/access.log No space left on device

   2018-05-10 09:39:22: (mod_accesslog.c.180) writing access log entry failed: /var/log/lighttpd/access.log No space left on device

   2018-05-10 09:39:52: (mod_accesslog.c.180) writing access log entry failed: /var/log/lighttpd/access.log No space left on device

   2018-05-10 09:39:53: (mod_accesslog.c.180) writing access log entry failed: /var/log/lighttpd/access.log No space left on device

pi@orangepiplus2e:~$ sudo fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mmcblk1: 14.6 GiB, 15634268160 bytes, 30535680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6ea0214e

Device         Boot Start     End Sectors Size Id Type
/dev/mmcblk1p1       8192 30230303 30222112 14.4G 83 Linux


Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 7.6 GiB, 8103395328 bytes, 15826944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start     End Sectors Size Id Type
/dev/sda1  *        2 15826943 15826942  7.6G  7 HPFS/NTFS/exFAT

 

Screenshot 2018-05-10 10.20.21.png

Posted

Check power....check to ensure you have a good quality SD card...I too just went round and round...turns out I had a sd card that was wearing out

Posted
On 5/10/2018 at 6:24 PM, Carlos_Tico said:

Clean Installation of Armbian Stretch mainline kernel 4.14.y to the internal memory of the Orange PI

   2018-05-10 09:38:51: (mod_accesslog.c.180) writing access log entry failed: /var/log/lighttpd/access.log No space left on device

   2018-05-10 09:39:21: (mod_accesslog.c.180) writing access log entry failed: /var/log/lighttpd/access.log No space left on device

 

 

I dont think you have to check the card, because most likely its caused by log2ram whcih is used ba armbian.

I also got "no space" in /var/log with my Pihole, because log2ram was set to 50MB in /etc/default/log2ram (50MB Ram-Disk)

 

@Igor is working with some other developers on a ZRAM option to replace this.

 

By now I have extended (on systems with >= 5122MB of Ram) the log2ram size to 150-250MB (depending on the System Ram).
Now my Pihole is working fine without getting "out of space" :)

root@bpi-a20(192.168.6.3):~# more /etc/default/log2ram
# configuration values for the log2ram service
#
# enable the log2ram service?
ENABLED=true
#
# size of the tmpfs mount
SIZE=250M
#
# use rsync instead of cp -r
# requires rsync installed, may provide better performance
# due to copying only new and changed files
USE_RSYNC=true
#

 

 

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines