SliTaz Forum
You are not logged in.
I tried to install slitaz according to the instructions in the manual with the option “Loop install” (https://doc.slitaz.org/en:guides:uncommoninst#loop-install), but had no success!
I used the slitaz-rolling-preinit.iso from here: https://mirror.slitaz.org/iso/rolling/
I notice that the slitaz.fs is not mounted at all, but I can't see any errors in the logs! My question: are further actions required?
Further details are given below.
Many thanks!
Regards,
Abru
boot setup (menu.lst)
title SliTaz slitaz-rolling-preinit.iso with slitaz.fs on sda10
uuid 53080857-0a57-4636-9aa5-7bde31d88a18
kernel /boot/bzImage mount=53080857-0a57-4636-9aa5-7bde31d88a18 loopfs=slitaz.fs
initrd /boot/rootfs.gz
root@slitaz:~# uname -a
Linux slitaz 3.16.55-slitaz #4 SMP Thu Jul 14 18:31:26 UTC 2022 i686 GNU/Linux
root@slitaz:~# blkid /dev/sda10
/dev/sda10: UUID="53080857-0a57-4636-9aa5-7bde31d88a18" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="fdc442ff-0a"
root@slitaz:~# cat /proc/cmdline
mount=53080857-0a57-4636-9aa5-7bde31d88a18 loopfs=slitaz.fs
root@slitaz:~# head -n20 /var/log/boot.log
Switching / to tmpfs...
Starting udev daemon...
Udevadm requesting events from the Kernel...
Udevadm waiting for the event queue to finish...
Remounting rootfs read/write...
Mounting filesystems in fstab...
Detecting PCI devices Kernel modules...
* Builtin module : ata_piix
* Builtin module : ehci_pci
* Builtin module : pcieport
* Builtin module : uhci_hcd
Detecting USB devices Kernel modules...
root@slitaz:~# mount
tmpfs on /run type tmpfs (rw,relatime)
tmpfs on / type tmpfs (rw,relatime,size=2791800k)
proc on /proc type proc (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=1534308k,nr_inodes=210518,mode=755)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,relatime)
tmpfs on /var/lock type tmpfs (rw,nosuid,noexec,relatime)
Offline
Hello,
Are [c]bzImage[/c] and [c]rootfs.gz[/c] the kernel and the rootfs of slitaz-rolling-preinit.iso that you copied in a [c]/boot[/c] directory on your hard disk?
Is 53080857-0a57-4636-9aa5-7bde31d88a18 mounted?
Offline
Hello Ceel
To your questions:
Are bzImage and rootfs.gz the kernel and the rootfs of slitaz-rolling-preinit.iso that you copied in a /boot directory on your hard disk?
Yes
Is 53080857-0a57-4636-9aa5-7bde31d88a18 mounted?
Yes, slitaz boot from this partition, but "mount=53080857-0a57-4636-9aa5-7bde31d88a18 loopfs=slitaz.fs" is not executed and there are no messages about it!
I think the problem lies with the init script.
Offline
I have just tested it, the variant with subroot (https://doc.slitaz.org/en:guides:uncommoninst#subdirectory-install-in-a-posix-filesystem) does not work either.
Offline
The guides are for the simple /dev/sdxx identifier.
With the uuid identifier,the mount command requires the prefix UUID=
mount UUID="53080857-0a57-4636-9aa5-7bde31d88a18”
or in case of partition only
mount PARTUUID="53080857-0a57-4636-9aa5-7bde31d88a18”
blkid in each case removes any doubt about which one to use.
----------------------------------------------------------------------------------------
Le guide sono per il semplice identificativo /dev/sdxx
Con l'identificativo uuid,il comando mount richiede il prefisso UUID=
mount UUID="53080857-0a57-4636-9aa5-7bde31d88a18"
oppure in caso di sola partizione
mount PARTUUID="53080857-0a57-4636-9aa5-7bde31d88a18"
blkid in ogni caso toglie ogni dubbio su quale usare.
Offline
Hello gibor,
the guide (https://doc.slitaz.org/en:guides:uncommoninst#loop-install) describes this syntax:
mount=53080857-0a57-4636-9aa5-7bde31d88a18
but I had already tested with UUID and PARTUUID, but checked it again and each time with the same result as described above.
kernel /boot/bzImage mount=/dev/sda10 loopfs=/slitaz.fs
kernel /boot/bzImage mount=UUID=53080857-0a57-4636-9aa5-7bde31d88a18 loopfs=/slitaz.fs
kernel /boot/bzImage mount=PARTUUID=fdc442ff-0a loopfs=/slitaz.fs
I think your syntax is not quite correct: mount UUID="53080857-0a57-4636-9aa5-7bde31d88a18”
I am pretty sure that the error is in the init script.
Offline
mount --help
Usage:
mount [-lhV]
mount -a [options]
mount [options] [--source] <source> | [--target] <directory>
mount [options] <source> <directory>
mount <operation> <mountpoint> [<target>]
Mount a filesystem.
Options:
-a, --all mount all filesystems mentioned in fstab
-c, --no-canonicalize don't canonicalize paths
-f, --fake dry run; skip the mount(2) syscall
-F, --fork fork off for each device (use with -a)
-T, --fstab <path> alternative file to /etc/fstab
-i, --internal-only don't call the mount.<type> helpers
-l, --show-labels show also filesystem labels
-n, --no-mtab don't write to /etc/mtab
--options-mode <mode>
what to do with options loaded from fstab
--options-source <source>
mount options source
--options-source-force
force use of options from fstab/mtab
-o, --options <list> comma-separated list of mount options
-O, --test-opts <list> limit the set of filesystems (use with -a)
-r, --read-only mount the filesystem read-only (same as -o ro)
-t, --types <list> limit the set of filesystem types
--source <src> explicitly specifies source (path, label, uuid)
--target <target> explicitly specifies mountpoint
--target-prefix <path>
specifies path use for all mountpoints
-v, --verbose say what is being done
-w, --rw, --read-write mount the filesystem read-write (default)
-N, --namespace <ns> perform mount in another namespace
-h, --help display this help
-V, --version display version
Source:
-L, --label <label> synonym for LABEL=<label>
-U, --uuid <uuid> synonym for UUID=<uuid>
LABEL=<label> specifies device by filesystem label
UUID=<uuid> specifies device by filesystem UUID
PARTLABEL=<label> specifies device by partition label
PARTUUID=<uuid> specifies device by partition UUID
ID=<id> specifies device by udev hardware ID
<device> specifies device by path
<directory> mountpoint for bind mounts (see --bind/rbind)
<file> regular file for loopdev setup
Operations:
-B, --bind mount a subtree somewhere else (same as -o bind)
-M, --move move a subtree to some other place
-R, --rbind mount a subtree and all submounts somewhere else
--make-shared mark a subtree as shared
--make-slave mark a subtree as slave
--make-private mark a subtree as private
--make-unbindable mark a subtree as unbindable
--make-rshared recur
Offline
You are absolutely right, but this is a slightly different case, here only the information is passed to the init script, the correct mount is done from there.
Offline
Hmmm, i figured out what the problem was and found that the developer had removed this function (variant). Too bad that this in the documentation was not noted.
Thank you for your support!
Regards,
Abru
Offline
Hello abru,
I gave it a try this weekend. As you I wasn't able to run an install neither from loopfs nor subroot. Seems it is an old problem
I tested with the preinit ISO 4.0; only the subroot configuration worked with preinit rootfs, kernel and subroot installed on hard disk partitions from where I boot. No chance when one of them is installed on an USB device.
I think the doc was written for SliTaz 3.0
Hmm, question: why SliTaz provides weekly an ISO that seems not working... ?
Offline
Hello Ceel
Thank you for your message!
I found what I was looking for here: https://www.slax.org/
Copied the folder slax from slax-64bit-debian-12.iso to my harddisk with existing ext4 partition sda6 and created a menu entry in my bootloader grub.
title Slaz 64 slax-64bit-debian-12.2.0
rootnoverify (hd0,5)
kernel /slax/boot/vmlinuz quiet vga=normal load_ramdisk=1 notsc prompt_ramdisk=0 rw printk.time=0 consoleblank=0 perchdir=resume
initrd /slax/boot/initrfs.img
Runs perfectly and saves the changes! The installation of deb-packages works fine, installed Firefox and others.
Regards,
Abru
Offline
[ Generated in 0.020 seconds, 7 queries executed - Memory usage: 1.56 MiB (Peak: 1.77 MiB) ]