1st aid check list:
1. try confirm the installmedia is not corrupted (md5 sum against the shipped one - there is a "recipe" somewhere in doc wiki or shipped HOWTOs)
2. try read-write test the receiving storage carrier (format with bad block checking)
3. try skew the partitions for few MB back or forth just to avoid the sector if not detected
4. try any other storage media at hand?
5. try test RAM somehow (format an RAM disk with bad blocks check?)

there can be only few culprits:
1. Bad install media (bad copy) or bad USB contacts
2. bad storage media (bad "disk") or bad SD-card contacts
3. bad RAM
less likely:
4. bad CPU/memory controller

It goes without saying, no overclock, stock voltages and clocks all over the system

HTH?

Are you installing headless and do you have an Internet connection already configured before you install?

The easiest thing is to look what is in /mnt
/mnt also probably is not mounted against the device (e.g. /dev/sdaX) - it's probably just a directory on the installer RAM file system (which it should be until that directory becomes a mount point for your root file system).

Your installation probably failed entirely either because the installer could not mount the device, or it was not formatted or something like that.

I am not installing headless. Internet connection is always available, but I only get ip during NFS install.

Ja, I'm simply trying to emulate what you're doing to reproduce the same error, but it's just not happening here. I've tried installing locally and remotely, using USB stick (with and without Internet connection) and http/ftp server as source - every thing seems to be working as expected each time, following the instructions on sarpi.fatdog.eu website.

However, I have a couple of Samsung EVO 32GB microSD cards that have given me some headaches with Slackware ARM in the past on the RPi3, but the same cards work flawlessly on the RPi1 with the occasional/frequent hiccup on the RPi2. Have you taken heed of my previous advice and tried installing on a different microSD card using the same SARPi image?

Other than what has already been suggested and pointed out in this thread, there has to be something that's causing your problem. I've wasted quite a few hours making sure the SARPi installer isn't failing by some means or methods that hasn't previously been tested and it seems to be working 100% based on my own results.

Kirk Douglas was 100 years old yesterday!

Seems the sd cards I am using are ok, as I have successfully install Raspbian using them.

If using -current, there is a chance You found a bug, but note, we too installed it to Pi3, so it has to be a recent one?
Outside that, only an error_on_copy would be explaining the observed?
Try "pause" the setup right before the critical moment and compare: /proc/mtab vs mount output?
also then inspect dmesg?
Ctrl+z can suspend setup in between inputs
makes it go on

Ah, this is where it gets foggy.

The Samsung EVO 32GB microSD cards of mine which I know to be problematic with Slackware ARM on the RPi3, seem to work perfectly with Raspbian. I once had a Sandisk full size SD card that worked great with Slackware ARM but wasn't too happy running Raspbian. A few years ago I did a lot of testing with different cards and in the end I gave up trying to solve these kinds of problem because it really didn't make sense. Over time, I've found which SD/microSD cards work best and just stuck with them.

The only way to find out if your storage media is affected in the same way is to try different microSD cards and compare results. See this page for some idea on which cards are better suited than others: http://elinux.org/RPi_SD_cards

1 members found this post helpful.

Will there be any problem if my Raspberry is made in China? The key string is different.

If memory serves me correct, I think Louigi has such a device that he has issues with using the SARPi installer and packages. The only RPis I own which are "made in China" are all RPi1, so I cannot offer you much advice here I'm afraid.

<edit> Having said that, I don't have any problems with SARPi installers or packages on the RPis which are made in China.

I think mine B1's are china made?

No problem either FWIW.

I tried the new images with 4.9 kernel and everything works fine now. Thanks.

That's good news. As far as your issues go, my guess is that it had something to do with the RPi firmware. Nothing that I'm aware of in the Slackware ARM tree has changed, or the SARPi installers/packages, which would contribute to the problems you were experiencing. As I've stated, it's *just* a guess that it was a firmware issue.