sorry to sound extremely daft, but what should I be renaming it? Is there a preferred name or one which makes most sense?
Read the statement by Michael Teeuw here.
Best posts made by JMac
-
RE: pm2 no longer launching MM
-
RE: pm2 no longer launching MM
once a new name is picked can it later be changed back to magicmirror just to keep everything standard?
Also, when you say,
mv magicmirror newname, I’m guessing the newname bit is actually what I want to call it, or do I put the new name after?
I’ve got a terrible feeling I’ll have to start the whole thing again which I definitely won’t look forward to. -
RE: pm2 no longer launching MM
Sam, scratch my last message, I was just about to turn everything off as it’s getting pretty late here.
used ctrl c to stop the MM so I could shutdown the pi and attack it another day.
pm2 restarted the MM and hey presto the mirror seems by and large back to normal.I’m away with work for the next 3 days but will have a proper butchers (look) when I’m back home.
Thank you so much for both your patience and help.
I had genuine fears I’d have to start the entire build (modules bit) again and I was lucky I got it up and running like I did in the first place.thank you!
Latest posts made by JMac
-
RE: Everything was going so well
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 *********
-
RE: 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? -
RE: Everything was going so well
@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.
-
RE: Everything was going so well
@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?
-
RE: Everything was going so well
so should i also run sudo umount /dev/sda2 before running sudo e2fsck -f -v /dev/sda2?
-
RE: Everything was going so well
@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/mmcblk0p2Disk /dev/sda:59.69 GiB (I again assume this is the old SD with my original MM setup)
Device
/dev/sda1
/dev/sda/2end 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.
-
RE: Everything was going so well
@sdetweil on the home screen I have 2 drive icons under the wastebasket.
one is boot
the other is rootfsi then have the option to eject these in the file manager
-
RE: Everything was going so well
@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. -
RE: Everything was going so well
@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. -
RE: Everything was going so well
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?