Just out of curiosity, could you let us know why do you need to use run level 1? Is there something specific you need to do in this mode?
we are encountering many problems making the backup of edison with dd command and restoring it on another edison.
For this reason we think that entering in runlevel 1 to make this backup (and restore) can resolve the issues.
Errors we got are like:
- EXT4-fs error (device mmcblk0p8): ext4_mb_generate_buddy:755: group 2, 14512 clusters in bitmap, 65529 in gd
- EXT4-fs error (device mmcblk0p8): ext4_lookup:1437: inode #15418: comm systemd: deleted inode referenced: 15457
Could you check the partition size of the source Edison (backup) and the target Edison (restore) by using the command df –h /dev/mmcblk0p8? What is the output on each Edison?
Hi, sorry, I can't verify that.
I remember that the partition size are correct.
The problem is surely that is strange to make a DD over a mounted partition. In addition I think that journaling also make errors.
I solve the problem doing the boot from a microsd, than, make a dd over the root and the home partitions unmounted. Then, in the new edison, booting from the microsd I do the restore, with DD, over partitions. All works, without any errror.
1 of 1 people found this helpful
using the command "init 1", to access to runlevel 1 in my edison, the system ask me the root password, but, when I insert it, it says me that's wrong.
However if I leave the system with no password (default), I'm able to enter into runlevel 1.
Do you know why?
please note: the default OS on Edison is Yocto with systemd. Systemd doesn't have the concept of runlevels any longer but just "emulates" runlevels by loading only specific services which are defined for those "runlevels"