SliTaz rolling: tazusb fails to create full rootfs.gz after cook setup

SliTaz Forum » English Support » Live and installation

SliTaz rolling: tazusb fails to create full rootfs.gz after cook setup

(3 posts) (2 voices)

Started 9 years ago by slo.sleuth
Latest reply from slo.sleuth
This topic is resolved

Tags:

No tags yet.

slo.sleuth

offline
Member

I am unable to create a proper rootfs.gz after executing cook setup. The problem can be reproduced as follows

Starting with a clean slitaz-rolling-core.iso and create a live usb install (tazusb format --> tazusb gen-liveusb --> reboot). Boot from the usb and do the following:

$ su
Password:
# cook setup
...
# tazusb writefs lzma

Write filesystem
================================================================================
The command writefs will write all the current filesystem into a suitable
cpio archive (rootfs.gz) usable on a bootable LiveUSB media.

Archive compression: lzma

Do you wish to remove the sound card and screen configs ?
Press ENTER to keep or answer (No|yes|exit): yes
Removing current sound card and screen configurations... [ Done ]

Do you wish to remove local/keymap settings ?
Press ENTER to keep or answer (No|yes|exit): yes
Removing current locale/keymap settings... [ Done ]
Creating rootfs.gz with lzma compression... Killed
Moving rootfs.gz to media. Remember to unmount for delayed writes!
================================================================================
Root filesystem size: 2.0M
`

Posted 9 years ago #
az_ua

offline
Moderator

My topic about tazusb is even on first page, i had not exactly same problem(size was normal), but also after cooksetup, so after you ran tazusb open /tmp/list in any text editor with possibility of showing line numbers, and tell me how many lines=files+dirs is there. 65K is limit for rootfs. Cooksetup creates too many little files, each with own dir. Remember, that dir is also "file".

Edit post: wait, now I see "Creating rootfs.gz with lzma compression... Killed", this means - no enough RAM. Do you have 512 or even 256 Mb? Use swap or linux-zram module with editing its size in tazpanel.

Posted 9 years ago #

slo.sleuth

offline

Member

Good call @az_ua! I did not know the significance of the "killed" message. I booted in a VM with 1gb of RAM and repeated the process:

# tazusb writefs lzma

Write filesystem
================================================================================
The command writefs will write all the current filesystem into a suitable
cpio archive (rootfs.gz) usable on a bootable LiveUSB media.

Archive compression: lzma

Do you wish to remove the sound card and screen configs ?
Press ENTER to keep or answer (No|yes|exit): yes
Removing current sound card and screen configurations...             [ Done ]

Do you wish to remove local/keymap settings ?
Press ENTER to keep or answer (No|yes|exit): yes
Removing current locale/keymap settings...                           [ Done ]
Creating rootfs.gz with lzma compression... Moving rootfs.gz to media. Remember to unmount for delayed writes!
================================================================================
Root filesystem size: 80.0M

----
ENTER to continue...
#

Increasing the RAM allowed the successful completion of the operation. Also, thanks for the tip on linux-zram module.

Posted 9 years ago #

RSS feed for this topic

Reply

You must log in to post.