TRY THIS Raspbx - No Boot After Removing Net Persistence Rules

[phonehome]

Need help to reboot Incredible Pi system.

Incredible PBXed Raspbx running on Beaglebone Black.

Looking to test cloned backup with a different BBB(worked before), I first entered:
rm /etc/udev/rules.d/70*

And rebooted.

Upon reboot, Raspbx does not boot and the heartbeat, removable memory, and network lights are lit solid and does not process boot sequence - checked with monitor directly connected as well.

Could this be because of static IP set through /network/interfaces?

Removed microSD, rebooted to stock BBB/Angstrom and tried to mount microSD - cannot seem to mount it for editing.

Learning linux101 while trying out Raspbx.... Any life preserver would be appreciated.

 

[Rrrr]

I am doing the same: cloning a working BBB and encountered your problem too: no boot, but with no lights.

I can only share what worked for me.
I think that the image made with raspbx-backup as in here and copied back to the eMMC let to problem of not being able to boot from it.

I solved it by copying back to eMMC this image I made before, like this:

dd bs=1M if=/mnt/emmc_orig_contents.img of=/dev/mmcblk1

(you can also copy from USB stick to eMMC)
(you can also make an image after installing incrediblepbx and use that in case you need a clean system)

I do not think it has to do with the other problem of not getting network, due to reserved MAC, which allows booting, but not getting network.
You deleted the file /etc/udev/rules.d/70*, I edited it as in here, but only after I copied back the good image.

If you have problems with mounting, then you need to describe what is the problem?
Note that BBB/Angstrom is a different OS and needs different commands.
Better to start with a clean RASPBX image copied from USB stick to eMMC.

Try the commands:
df -a to see which devices are available to mount
mount to see your current mounted folders
sudo apt-get install nfs-common to make mounting to an nfs file system possible

 

[phonehome]

Thanks for the response Rrrr! I believe that my uSD card was corrupt, thus the failed boot issues.

Although I have different BBBs with working Incredible Pi[maybe we should name ours now Incredible B³(alt+0179) or Beagle or BBB] I have rebuilt this one for practice - plus, this really drove home the lesson to have a warm or hot standby system ready.

Couple responses to your advice:

1. You're correct that the issue did not have anything to do with static IP settings, as I tried on the new one again like this:
   1. Set static IP
   2. "rm /etc/udev/rules.d/70*"
   3. shutdown
   4. install uSD in second BBB
   5. Perfect boot, access via html and ssh via static IP worked fine
2. I did try df -l to see what was mounted by "mount /dev/sda1 /mnt" but could not mount to the folders I needed to edit

I am going to try some different strategies on backup within a couple of weeks, and will let you know what works for me.

Have you been experimenting with warm/hot standby system?
Did you custom install different Ubuntu/Asterisk/FreePBX on your BBBs?

 

[Rrrr]

2x no I am afraid

I did find out that sometimes connecting power to the BBB will not let SDcard boot.
Simply removing power and reconnecting after 10 sec, will let it boot as normal.

 

[wardmundy]

You're supposed to hold down the Boot button when you plug in power to boot from the microSD card. See step #3 here.

 

[phonehome]

2x no I am afraid

I did find out that sometimes connecting power to the BBB will not let SDcard boot.
Simply removing power and reconnecting after 10 sec, will let it boot as normal.

Will keep you posted then.

I have not had this issue from connecting to power yet, and hope it never appears.

 

[phonehome]

You're supposed to hold down the Boot button when you plug in power to boot from the microSD card. See step #3 here.

Yes, for the first boot from uSD only - I learned that from you, Yoda.

Then the board remembers boot sequence to check for uSD card on future boots.