Read the statement by Michael Teeuw here.
Everything was going so well
-
@sdetweil Wow, that was a bit to take in but makes sense (I think).
So if I unmount it how do I get the information off it?
what are the steps here? -
@JMac
unmount it
run fsck against it
remount it (hopefully fixed)then copy your data first thing, DO NOT WRITE TO THE SD CARD
config.js
custom.css
and a list of all the modules in modules (ls *)if u WANT to try in each module folder do
git remote -v ```⁷ so we know where it came from quickest way in each module folder git remote -v | tail -a ~/module_list this will list to github source (git remote -v) and append that info (tail -a) to a known file in your home folder (~ = home) this is what my backup script does IF you have any modules that require authentication (run an auth script) ls *.json while you are there, you could also run my backup script, from the web page copy/paste with -s pointing to the mounted folder MagicMirror https://github.com/sdetweil/MagicMirror-backup-restore ...MM_backup -s /media/??????/MagicMirror some gobbleygoop name (tab key will fill it in after the 1st letter) this will create the MM_backup folder in your logged on user home folder.. and do all the work described above (after the mount) https://github.com/sdetweil/MagicMirror-backup-restore
-
had a little crack at this again, the Mrs is bugging me to get “her” mirror back up and running.
So I’ve run sudo umount /dev/sda1
sudo umount /dev/sda2Both drive folders from the mounted (old) SD disappeared from the home screen on the pi as expected.
then run, (and got)
sudo e2fsck -f -v /dev/sda2
e2fsck 1.46.2 (28-feb-2021)
rootfs: recovering journal
superblock needs_recovery flag is clear but journal has data.
Run journal anyway ? YES
e2fsck: unable to set superblock flags on rootfsrootfs: *********** WARNING: filesytem still has errors *********
-
@JMac bummer
from search
https://unix.stackexchange.com/questions/327863/fsck-wont-fsck-unable-to-set-superblock-flags/386886#386886was the card readable at all? if so
take it out and put it back in to get mounted
and copy the old config.js, custom.css and dols >~/savedlist.txt
in the MagicMirror/modules folder
to some file on your booted cardthen we can help you rebuild a new sd card
-
@sdetweil hey Sam, I can still see the old list of modules on the old SD card.
If that’s the case can the old card still be used?
the new card is just a completely empty Pi OS, nothing to do with MM on there yet.
Do I need in run the basic install for MM on the new SD to get that running?
-
@JMac yes, you need to install MM on the new sd.
use my script…
see https://github.com/sdetweil/MagicMirror_scripts
but you should extract your MM config from the sd card.use my backup script to point to the mounted sd card
see https://github.com/sdetweil/MagicMirror-backup-restorethen install MM
and then restore the config saved to the new sdcard (~/MM_backup folder) -
@sdetweil So install the base of MM on the new SD then follow the steps in your previous post?
I have a feeling it definitely won’t be that easy.
-
@JMac back is copy/paste from the github, add -s/media/{user}/mountname/MagicMirror
then install MagicMirror
copy/paste from the github linkthen restore, copy/paste from the github link. no parms required
-
@sdetweil right so when I copy those 2 file’s am I literally just dragging a copy to the new SD’s home screen (just so they’re on the new card) or do they need to go into a MM specific folder on the new card.
I can find both of those files on the old SD but I’m not understanding from
ls >~savedlist.txt.
am I doing that after I’ve installed a fresh MM on the new SD card once that MagicMirror/modules folder exists because running the above command won’t work as the new SD has no reference to MM’s existence.
-
@JMac copy ?
you go to the web page, and click copy for the command
then to terminal window or ssh window, paste command, hit enter (install and restore, add -s parm on backup)
you are executing the command directly from the web