Everything was going so well

sdetweil

@JMac unmount means remove them from normal file system access

the device names still exist

as e2fsck could modify the file system blocks on the drive, you don’t want to do that while you could still copy a file there

so you are passing the hardware name to e2fsck

JMac

@sdetweil so do I run e2fsck -f -v /dev/sda1 or e2fsck -f -v /dev/sda2
or does it not matter?

I’m struggling here to the bigger picture so can’t see the logic of the steps.

sdetweil

@JMac ok bigger picture, in Linux

hardware devices are named. see the output of ls /dev

disk devices are usually named sd??? where xxx is a letter, and partition number
letter a is the first device b the second etc

sometime in the past the type of storage device was also used as part of the name, scsi, atapi …
for this case they are named sd (storage device)

sda is the first storage device
sda1 is the first partition on the sda device

on those partitions are a logical way of storing data. most linux and all windows devices store file data in sectors, 512 byte chunks called sectors. and then the file system (way of organizing those sectors)
applies some data structure on top. it’s a directory or a file. tables in other sectors build trees of data to describe the entire partition.

there are different layouts depending on vendor and intended use
FAT, exFAT, NTFS EXT3, EXT4, and a host of others.

all is wonderful until some sector or more gets damaged… machine was powered off during write, a hardware failure…

now the filesystem code is confused… says read sector 853, and the bits there will tell it where the next sector is for this file. but the bits don’t point to the right place… Oops

some file systems include a duplicate set of bits do there is an alternative way . some use them only for recovery.

sd card hardware is known for being fragile. it was designed for lots of reads,with few writes. camera picture music file. NOT an os that is waiting logs and other stuff constantly.

anyhow.
to check and correct these kinds of problems with the Linux ext file system we need to run thr fsck program on the raw partition. and make sure that moone else is using it.

unmount takes it out of circulation. no users files open

fsck and e2fsck need to read the raw sectors on the partition, but we just unmounted it.
so we need to provide the hardware name for the program to use.

JMac

@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?

sdetweil

@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

JMac

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/sda2

Both 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 rootfs

rootfs: *********** WARNING: filesytem still has errors *********

sdetweil

@JMac bummer

from search
https://unix.stackexchange.com/questions/327863/fsck-wont-fsck-unable-to-set-superblock-flags/386886#386886

was 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 do

ls >~/savedlist.txt

in the MagicMirror/modules folder
to some file on your booted card

then we can help you rebuild a new sd card

JMac

@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?

sdetweil

@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-restore

then install MM
and then restore the config saved to the new sdcard (~/MM_backup folder)

JMac

@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.