mx53qsb ERROR "cp: write error: No space left on device"

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

mx53qsb ERROR "cp: write error: No space left on device"

2,841 Views
omprak
Contributor I

MX53-LOCO u-boot and kernel image . Not able to boot till ROOT prompt(Username).

Please help me debug this issue.


On console I'm continuosly getting:

starting pid 2215, tty '': '/sbin/getty -L ttymxc0 115200 vt100'

process '/sbin/getty -L ttymxc0 115200 vt100' (pid 2215) exited. Scheduling for restart.


log obtained  uImage :

EXT3-fs: barriers not enabled

kjournald starting.  Commit interval 5 seconds

EXT3-fs (mmcblk0p1): using internal journal

EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode

VFS: Mounted root (ext3 filesystem) on device 179:1.

Freeing init memory: 172K

starting pid 1203, tty '': '/etc/rc.d/rcS'

Mounting /proc and /sys

Starting the hotplug events dispatcher udevd

Synthesizing initial hotplug events

Setting the hostname to freescale

Mounting filesystems

cp: write error: No space left on device

cp: write error: No space left on device

cp: write error: No space left on device

cp: write error: No space left on device

mount: mounting usbfs on /proc/bus/usb failed: No such file or directory

starting pid 2215, tty '': '/sbin/getty -L ttymxc0 115200 vt100'

process '/sbin/getty -L ttymxc0 115200 vt100' (pid 2215) exited. Scheduling for restart.

starting pid 2216, tty '': '/sbin/getty -L ttymxc0 115200 vt100'

process '/sbin/getty -L ttymxc0 115200 vt100' (pid 2216) exited. Scheduling for restart.

starting pid 2217, tty '': '/sbin/getty -L ttymxc0 115200 vt100'

------------------------------------------------------------------------------------

BOOTARGS:

Hit any key to stop autoboot:  3     2     0

MX53-LOCO U-Boot > printenv

bootdelay=3

baudrate=115200

loadaddr=0x70800000

netdev=eth0

ethprime=FEC0

uboot=u-boot.bin

kernel=uImage

nfsroot=/opt/eldk/arm

bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp

bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootm

bootcmd=run bootcmd_mmc

ethact=FEC0

bootcmd_mmc=run bootargs_base bootargs_mmc;mmc dev 0;mmc read ${loadaddr} 0x800 0x1800;bootm

bootargs_mmc=setenv bootargs ${bootargs} root=/dev/mmcblk0p1 rw rootwait

ethaddr=00:04:9f:01:32:e0

bootargs_base=setenv bootargs console=ttymxc0,115200

stdin=serial

stdout=serial

stderr=serial



Labels (2)
0 Kudos
6 Replies

1,156 Views
VladanJovanovic
NXP Employee
NXP Employee

That error sometimes happens due to too small TMPFS_SIZE in /etc/rc.d/rc.conf . Try increasing default size from 512k to 8192k and see if it fixes the problem.

1,156 Views
omprak
Contributor I

cp:write error no space left on device is solved.
changed TMPFS_SIZE = 8192k in etc/rc.d/rc.conf
--------------------------------------------------------

.But still facing Issue.
starting pid 2215, tty ':'/sbin/getty -L ttymxc0 115200 vt100
process '/sbin/getty -L ttymxc0 115200 vt100'(pid 2215)exited.Scheduling for restart.


0 Kudos

1,156 Views
abdulrazak
Contributor I

Hi omprakash,

Were you able to solve the issue. please let me know. I am also stuck at the same point.

Thanks.

0 Kudos

1,156 Views
Matteo
Contributor II

Hi,

I have the same issue?

Have you solved the problem?

Best regards,

Matteo.

0 Kudos

1,158 Views
jimmychan
NXP TechSupport
NXP TechSupport

which profile you used to build in LTIB? if possible, please tell me the details and the steps so I can try to reproduct the problem on my side.

0 Kudos

1,158 Views
BrilliantovKiri
Senior Contributor I

Hello, omprakash!

Please recheck you inittab, rcS and other scripts which run after starting system.

0 Kudos