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
@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. -
RE: Everything was going so well
@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?
-
RE: Everything was going so well
@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?
-
RE: Everything was going so well
@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? -
RE: Everything was going so well
@mumblebaj that’s worked.
I’m now presented with
/dev/mmcblk0p1
/dev/mmcblk0p2so follow @sdetweil step above and go with the second option?
-
RE: Everything was going so well
I get the same issue. Sudo fdisk -i returns
fdisk: invalid option - - ‘i’
try 'fdisk - - help fro more informationany thoughts?
-
RE: Everything was going so well
@OldSunGuy well that was a great start :man_facepalming_light_skin_tone:
if I can get the steps above to work, can I get the original SD card to work again? It’s a samsung evo micro sd and way better than the unbranded one I’ve found to try and recover the original setup.
-
RE: Everything was going so well
@sdetweil managed to find an old SD card and put a fresh Pi OS on it.
Mounted the old one in an adapter, when I run your sudo fdisk -1, I get
fdisk:invalid option–‘1’
Try ‘fdisk --help’ for more information.I guess I don’t try you recovery command until this one is happy?
Edit to add, I do have - on the home screen - a boot file and a rootfs file from the old SD card.
-
RE: Everything was going so well
@sdetweil my apologies for the very very late reply. To be honest I haven’t wanted to get into it for fear I’ll have to start again.
is this an SD card failure (would it be better to run the MM from a USB drive? I don’t know how easy that is to do.
Going to try and get this looked at now. -
Everything was going so well
Hi folks, I’m fearing the worst at this point.
My magicmirror has been running really nicely on the whole for like a year.
Because computers aren’t really my thing I’ve avoided doing too many updates when the notifications have popped up.Earlier this week I noticed the screen had completely frozen and the pi was no longer responsive to keyboard inputs, so I felt I didn’t have a choice but to pull the power and try to restart the pi.
now I’m stuck with a screen has a long list of processes, the the bottom one reads,
[ 3.399958] —[ end Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(179,2) ]—is this game over and start again or can any of the previous setup be rescued.
I genuinely don’t think I know how I did it first time round and got it working as well as it did.Any help appreciated.