Installation on Rpi3B on usb-stick

Community Help With My Project Helped
7

Hi @brz25ac,

I suspect the installer is getting stuck on an unnecessary step related to disk expansion, yes. Here is what I’d try:

Run the installer again until it gets stopped where you pictured, then Ctrl+C to exit the script. If you run the command ls, there should be a folder called myDevices-1.0. Enter it with cd myDevices-1.0.

From there, run sudo nano setup.sh to open the setup script for editing. Locate the following code block (around line 137)

#make sure we have enough space before or after restart
availableSize=`df -k | head -2 | tail -1 | awk '{print $4}'`
if [ $availableSize -lt 200000 ]; then
    retVal=$(expandFileSystem)
    echo $retVal
    if [ $retVal = 1 ]; then
        updateProgress -2 -2 'Setup will continue after reboot!'
        #setup crontab to start at reboot time
        chmod 0755 $reboot_script          
        line="@reboot ${reboot_installer}"
        (sudo crontab -u root -l; echo "$line" ) | sudo crontab -u root -
        sleep 3
        sudo reboot
        exit 2
    fi
    updateProgress -1 -1 'Installing myDevices agent'
    echo "Setup requires at least 200Mb for install" && exit 1
else
    #just expand the file system to maximum
    expandFileSystem
fi

You’ll want to comment out all of those lines with # character, like so:

#make sure we have enough space before or after restart
#availableSize=`df -k | head -2 | tail -1 | awk '{print $4}'`
#if [ $availableSize -lt 200000 ]; then
#    retVal=$(expandFileSystem)
#    echo $retVal
#    if [ $retVal = 1 ]; then
#        updateProgress -2 -2 'Setup will continue after reboot!'
#        #setup crontab to start at reboot time
#        chmod 0755 $reboot_script          
#        line="@reboot ${reboot_installer}"
#        (sudo crontab -u root -l; echo "$line" ) | sudo crontab -u root -
#        sleep 3
#        sudo reboot
#        exit 2
#    fi
#    updateProgress -1 -1 'Installing myDevices agent'
#    echo "Setup requires at least 200Mb for install" && exit 1
#else
#    #just expand the file system to maximum
#    expandFileSystem
#fi

Now save your changes and exit your editor. To re-start the installer with these changes, you’ll need to know your invite code. That’s the mixed character part of the original script you downloaded from the Cayenne dashboard. So for example, if you downloaded the script rpi_iqzajvlmnm.sh your invite code is iqzajvlmnm

Now that you have this invite code, you can re-run your edited setup.sh script with the following command:

sudo bash setup.sh -code yourinvitecode -v (where yourinvitecode is replaced with your actual invite code).

I suspect this will work to un-stick the script and allow you to complete your installation. If it doesn’t, let me know and I’ll continue to help troubleshoot.

1 Like