SliTaz Forum
You are not logged in.
Please show us the output of /etc/fstab
The error occurs while there is no entry for /dev/sda1
The line should look like:
/dev/sda1 /boot vfat defaults 0 2
If there is another device for /boot, you can probably suffice by changing it.
Also: there is supposed to be a space between -F 32 and /dev/..
I cannot see that on your output.
/emgi
Offline
emgi you're right - no entry in /etc/fstab for /dev/sda1
space between -F and /dev/.. was missing
did it meanwhile again (with space between) and let install.sh run again
here the outcome together with the fstab information
[attachment=34734,1746]
Offline
Sorry to let you linger for so long. This is mainly because I'm not too intimate with the procedure myself and I had to make time to check it. ;-)
However, meanwhile I managed to get slitaz-arm booted and, like you I created the SD card manually on a slitaz machine.
Here are my findings:
Starting point: logged in as root in the directory containing install.sh. In my case, the SD reader showed up as sdb; this will probably be sda for you.
Step 1: You have to use fdisk to create the partitions. That already looks fine. All three MUST be primary partitions.
Then, you have to make the FAT32 partiton bootable using fdisk with the a-option (toggle bootflag).
Last entry before exiting fdisk is the w-option for writing the changes to the card.
Next step: format partitions 1 and 3:
mkfs.vfat -F 32 /dev/sdb1
mkfs.ext4 /dev/sdb3
You will notice that after this step, you are able to mount both partitions by hand when you specify the fs-type.
This will be vfat for /dev/sdb1 and ext4 for /dev/sdb3. Syntax:
mount /dev/sdb1 /media/rpi/boot -t vfat
mount /dev/sdb3 /media/rpi/rootfs -t ext4
If you still get error messages here, the partions may have been automounted and you have to unmount them first using: umount /dev/sdb1 /dev/sdb3
When the mount is successful you can execute the two copy commands from the script, without the status option:
cp -a boot/* /media/rpi/boot/
cp -a rootfs/* /media/rpi/rootfs/
You may verify the copy action with:
ls /media/rpi/boot/
ls /media/rpi/rootfs/
Both commands should show a familiar(?) output; at least there must be a bunch of files.
Then umount both partitions again, remove the SD card and test your work in a raspberry pi.
Due to some trial & error and the fact that I also attempted to use the script, it worked upon the second attempt.
The biggest issue probably was the proper formatting of the partitions.
In hindsight, the script might work as well if the SD card is fully prepared like described here.
Goodluck!
/emgi
Offline
@emgi
got that bloody ownership error again which I had in previous tests already by copying boot files - even if ls command shows the files in the SD card by booting into the raspi it goes [c]panic[/c] again...
also at the end was unable to umount both partitions - please see screenshots
I'm gonna try to do the partiton anew and try again for the nth time
[attachment=34743,1759] [attachment=34743,1760]
Offline
It will be hard to spell it out more explicit than I already did.
All I can say is this worked for me. Erase the card and format it properly.
umount before you start to remove automounts. Only write to an empty disk.
Take small steps and verify each step thoroughly. I did it, you will get there too!
Meanwhile I have also created a disk image from my 1G card.
It even boots under Qemu version 15.3 for windows.
I will try to get it uploaded (64MB .rar file). No luck!
/emgi
Offline
Hi tiziano,
One remark regarding the umount command:
You cannot umount two devices on one line.
I know this was in the example but I really meant it like
umount /dev/sda1
umount /dev/sda3
Automounting is a problem that I ran into myself while creating the image so it really makes sense to unmount the devices before starting the installation.
/emgi
Offline
Hi emgi,
thank you for additional hint - hope to be successful somehow
one more doubt concerning /boot folder in the slitaz-rpi-desktop-20140329.tar
in the cmdline.txt file it's following to read: `root=/dev/mmcblk0p3 rootwait quiet
` - the /dev/mmcblk0p3 is the SD card partition name I see in the debian environment
this is also the partition named when the rpi returns the booting error - same error message either if I use slitaz partition (sda) or debian (mmcblk0) -
does it matter?
Offline
This is correct. On the Pi, partions are named mmcblk0p.. and that's what the cmdline is referring to.
When creating the SD card, it is mounted as another device; the only thing that matters is the number of the partition, in both cases number three.
/emgi
Offline
Hello can You please help me!
1)I download sliTaz raspberry pi desktop 20140329.
2) Make 3 partitions on my SD card. For this i use GParted Partition Editor (I have sliTaz on my laptop)
- fat32 boot partition
- linux-swap partition
- ext4 root partition
copy in fat32 boot partition content of boot folder.
copy in ext4 partition content of rootfs folder.
Copy not folders, only content. I hope its correct.
Now i
put sd card in sliTaz laptop with partitions and files
copy "install.sh" in /install.sh directory
open terminal and enter
su
(password)
/install.sh
But in result i have nothing.
Help me please!!!
[attachment=35748,1845]
[attachment=35748,1844]
[attachment=35748,1843]
Offline
I see no period before the forward slant.
./install.sh
Offline
If i put ./install.sh with point
terminal answer install.sh not found
Mojo, are You installed the sliTaz on raspberry pi?
Someone from here made this?
I want to make sharp instruction if i do this. I spend too much time for the installation process and still not have result. I want to make it for eeveryone like me.
Guys who know how to do this please SHARE YOUR experience!!
Offline
Hi Dmitry
Looking at the README file in the slitaz-rpi-desktop-20140329 directory:
SliTaz Raspberry Pi - Cooking/Release - http://arm.slitaz.org/rpi
================================================================================
boot/ : Must be copied to a FAT32 partition
rootfs/ : Must be copied to an ext4 or btrfs partition
Installation script
-------------------
Be sure the SD card has got 3 partitions (boot,swap,root). Then you simply have
to run the install.sh script from this SliTaz Raspberry Pi release directory:
# ./install.sh
===============================================================================
It really means that you should format /boot to a FAT32 partition and root to a ext4 partition (which you've already done).
You don't need to copy any files over.
If you run the ./install.sh script from INSIDE the slitaz-rpi-desktop-20140329 directory it will copy the files over for you and you should see some messages when running the script.
Offline
Hi tiziano,
On a Debian system you've got the install.sh script for the variable dev pass the string
mmcblk0p
So in the end is not 0 but p then the script executed properly.
so long
Offline
Hi everyone! I now start the script. Files will be automatically added to partitions. I try make partitions by two ways:
by fdisk
by G parted
in both cases ill have in result this window after card installetion
[attachment=35769,1846]
Script working well without mistakes. Partition i also make well. What the problem?
Offline
Exact same error from April 2014 in slitaz-rpi-no-boot thread.
Try Pauls permissions solution from post 31165:
Boot into i486 slitaz,open terminal as root.
Assuming the sd card ext4 formated partition with slitaz pi rootfs installed is sdc3.
Mount the pi sd card ext4 formated partition sdc3 holding the rootfs.
mount /dev/sdc3 /media/rootfs
chown -R root:root /media/rootfs
Reference:
http://forum.slitaz.org/topic/still-wont-boot-pi-f2fs-message#post-31165
http://forum.slitaz.org/topic/slitaz-rpi-no-boot-pi
Offline
@Joerg & all interested Forum friends,
This is a very Long issue as you can see in this post history - this is also, as I could experience, a not-easy-to-solve hurdle - the Arm section of the forum shows in the end several open items on this issue - I can tell you my impression - please bear in mind that I'm kind of newby and even if I'm successfully using Slitaz with an old pc and I'm happy with it, I'm using different distribution on other pc/Laptops - I love Slitaz for instance run from a live USB - Found it essential, usefull and definitely brilliant.
Coming back to Arm for raspi - here my experience and Personal opinion:
▪️ Partitioning and preparing the SD Card is not an easy job - at least for newbies - best explained solution the one given by emgi in this post (see above)
▪️The install.sh suggested by Slitaz raspi section contains a bug in the script - see error mentioned by mojo
▪️Even with the correct script if the partition is not corret obviously it does not work
▪️Often It not works at the very first attempt even if anything seems to be ok
▪️The ones who succeeded please refer your experiences
▪️on the other hand The raspberry org official distros, such as Raspbian or Pidora are stable and easy-to-install (see NOOBS for reference)
It depends of course on what you would live to do with your raspi - find out what the best ditro for your needs
According to my experiences, after several attemps I lost my patience and moved to Raspbian - very easy and user-friendly with berryboot for instance - noobs is also easy but has some problems with double boots -
This is a pity indeed because I love Slitaz but also I hadn't the time to further try and test in order to have a working raspi in a relative short time
Some suggestions for Slitaz raspi developers.
1⃣ make it easier
2⃣ why don't you create an .img file to easely install into the raspi with the instruction given by any raspi manual? With berryboot loading an .img is a few minutes work
3⃣ you're risking to keep Slitaz in an unknown niche
4⃣ I was reading in the forum lately that Slitaz went down in the distowatch.... Losing visibility. Wonder why?
Sorry for this long post, probably not useful for anybody
Tiziano
Offline
I absolutely agree with Tiziano!!!
Dear, Developers
We spend a lot of time to install the operating system, in place of develop our Projects!!!
I hope you are read this post and pay your attention to our request!
Offline
Sorry,
I just wanted to say that it is so work on my debian system.
I just wanted to help.
I understand that many are upset when something does not work the same, especially if you take a lot of time. But you should also think about how much time and effort the developer and all here invest in the forum to make the system better (step by step).
There can be many reasons (different hardware), if something does not work the same.
so long
Offline
@tiziano
tazbian users can install slitaz dual boot easily without repartionning
see http://forum.slitaz.org/topic/pi-slitaz-together-with-raspbian#post-34710
and http://forum.slitaz.org/topic/pi-slitaz-together-with-raspbian#post-34748
Offline
[ Generated in 0.022 seconds, 8 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]