Everything was going so well

[mumblebaj]

@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

[sdetweil]

@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

[sdetweil]

@JMac if u can get the config, custom
css and and listing of the modules ( ls command) we can build the backup/restore files

[JMac]

@sdetweil sorry to be dense how do I know what I’m unmounting?
am I unmounting /dev/mmcblk0p1?? it says thats mounted on /boot.

edit to add,
after re running sudo fdisk -l it would appear the old memory card (with my previous MM setup on) is on Disk /dev/sda

thats classed as Disk Model: storage device (as it’s mounted in the usb drive atm) does this seem correct? is this the one which needs unmounting?

[sdetweil]

@JMac well mounted means accessible by the filesystem

so it’s /dev/sda
the usb installed sd card

so

sudo unmount /dev/sda
and then run fsck on that

[JMac]

so I run the command sudo umount /dev/sda
and get
umount: /dev/sda: not mounted.

so should now go,
e2fsck -f -v /dev/sda
not the original
e2fsck -f -v mmcblk0p2

?

[sdetweil]

@JMac correct… you had to find the disk name

[JMac]

@sdetweil when i run e2fsck…
I get
e2fsck: permission denied while trying to open /dev/sda
you must have r/w access to the filesystem or be root.

[sdetweil]

@JMac yes, you must use sudo on both commands unmount and fsck

sorry I was unclear

normal users should not be able to mess with hardware, so one must act as root

[JMac]

@sdetweil I run sudo umount…
and get
umount:… not mounted,

then run
sudo e2fsck -f -v /dev/sda
and get
e2fsck 1.46.2 (28-feb-2021)
/dev/sda is in use
efsck: connot continue, aborting.

[sdetweil]

@JMac hm… wonder what is using it?

can you open the disks app on the pi from the dedktop menu

[JMac]

@sdetweil on the home screen I have 2 drive icons under the wastebasket.
one is boot
the other is rootfs

i then have the option to eject these in the file manager

[sdetweil]

@JMac there should be that drive on /dev/sda too

[JMac]

@sdetweil I’m a little confused (I’d imagine thats pretty clear at this point).

i run sudo fdisk -1
and get
Disk /dev/ram0 through to Disk /dev/ram15
the list then has
Disk/dev/mmcblk0: 7.4GiB (my thinking is this is the current/new sd card)

Device
/dev/mmcblk0p1
/dev/mmcblk0p2

Disk /dev/sda:59.69 GiB (I again assume this is the old SD with my original MM setup)

Device
/dev/sda1
/dev/sda/2

end of the list.

does any of that make sense/ is any of it what I’m looking for? I’ve obviously taken out several lines under each of those headers just for space and time typing.

[sdetweil]

@JMac yes sda has two partitions boot and rootfs

but you need to run e2fsck on /dev/sda2
e2fsck mean extended version 2, file system check

[JMac]

so should i also run sudo umount /dev/sda2 before running sudo e2fsck -f -v /dev/sda2?

[sdetweil]

@JMac yes

[JMac]

@sdetweil so I’ve run sudo umount /dev/sda1 and the same for sda2 and both folders have disappeared off the home screen.

which e2fsck do I run if i had to unmount 2 drives?

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