Read the statement by Michael Teeuw here.
Everything was going so well
-
@JMac Yeah, would suggest you follow his recommendations.
-
@mumblebaj cool. Do you have any idea why the initial SD card would be failing to launch when the pi is turned on?
as mentioned above it’s a good quality SD card so am I daft to consider (providing I can recover a copy of my old setup) copying it back onto to the original SD card, am I asking for trouble in the future? -
@sdetweil so I ran e2fsck -f -v /dev/mmcblk0p2
got a warning about SEVERE filesystem damage.
went yes and got ]e2fsck : permission denied while trying to open /dev/mmcblk0p2
you must have r/w access to the filesystem or be root.How do I get around this?
-
@JMac I am sure Sam is probably still sleeping, but you can try
sudo e2fsck -f -v /dev/mmcblk0p2
. This should run as root user. -
@mumblebaj when I run that in terminal I get,
e2fsck 1.46.2 (28-Feb-2021)
/dev/mmcblk0p2 is mounted.
e2fsck: cannot continue, aborting.Any thoughts, is that image/setup a goner?
-
@JMac You could try
systemctl stop udev
and then try running it again. My knowledge of these linux things are not that great. Orservice udev stop
might work. I am leaning towards the card being a goner thought. -
@mumblebaj It would be way easier if I could recover the previous setup but I’m starting to feel like it might be worth starting the entire MM install again, but for me that’s the least interesting parts of Pi builds.
The files are still available on the old SD card so the card itself isn’t completely kaput.
edit to add I ran the systemctl stop udev command.
put in the password of the MM to allow this.
re ran sudo e2fsck -f -v /dev/mmcblk0p2
and get the same e2fcsk: cannot continue, aborting error. -
@JMac You can use the scripts from Sam to install MM. You can find them here. Always do a backup of your install with one of Sam’s script as this would save tears in the end. I have been there before and the backup and restore process saved me a few times.
Scripts can be located here:
https://github.com/sdetweil/MagicMirror_scripts -
@JMac you cant whack on a file system if its mounted for access,do
df -k
will show u the devices and where they are mounted then sudo umount /dev/… what you were using
df -k should show it gone
then the fsck… commands should work w sudo -
@JMac if u can get the config, custom
css and and listing of the modules ( ls command) we can build the backup/restore files