Hi Gabriel,
Gabriel Wicki <[email protected]> writes: > (file-systems (cons (file-system > (device "/dev/mmcblk2p1") So here you have mmcblk2. > --8<---------------cut here---------------start------------->8--- > Welcome, this is GNU's early boot Guile. > Use 'gnu.repl' for an initrd REPL. > > loading kernel modules... > e2fsck: No such file or directory while trying to open /dev/mmcblk1p1 Here you have mmcblk1. > Possibly non-existent device? > File system check on /dev/mmcblk1p1 failed > Spawning Bourne-like REPL. > --8<---------------cut here---------------end--------------->8--- > >/dev/mmcblk1p1 does exist, or at least it is listed when i Here also mmcblk1. > > ls /dev/ Did you rewrite this from the screen? Which one is correct, are you sure the config is the same as what you're expecting? > > is there a major difference between creating an image and reconfiguring > the system with the same operating-system definition? what am i > missing? The most major difference is in the file systems / partitions. The root file system definition is commonly ignored and replaced with a custom one. But it all depends on the image type you used. Then, commonly the root file system is replaced with a uuid rather than pointing to /dev/device directly, because it's unknown on what device it will go. So in case the device is incorrect in the config, this will happen. On the other hand you still get the original configuration.scm in /run/current-system, so it can be confusing, because then the reconfiguration leads to a change of the file-systems. Rutherther > > thanks as usual for any and all pointers in advance! > g
