Read the statement by Michael Teeuw here.
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. -
@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.
-
@JMac that should be the letter (l) not a number (1) .
sudo fdisk -l
-
@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.
-
I get the same issue. Sudo fdisk -i returns
fdisk: invalid option - - ‘i’
try 'fdisk - - help fro more informationany thoughts?
-
@JMac That is not an i it is an l (small letter L)
-
@mumblebaj that’s worked.
I’m now presented with
/dev/mmcblk0p1
/dev/mmcblk0p2so follow @sdetweil step above and go with the second option?
-
@JMac Yeah, would suggest you follow his recommendations.
-
@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? -
@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?