Create another boot disk on a fresh SD card, boot it and then mount and fix the borked fstab entry on the other card. Requires a USB microSD card reader, which everyone using a Pi should have.Oh dear.
Now my brand new Pi 5 boots to the aforementioned error message ... and I can't seem to do anything more on the Pi ... press Enter doesn't let me do anything and much as I like to press the Enter key it isn't all that helpful.
I see via fstab it is trying to mount something it can't find, and it is not anything I can turn on, and its fstab entry should but does not have ',nofail' on it. Silly me.
I don't have a linux box so I thought: well, perhaps I could pop the SD card onto my Windows 11 PC and it'll mount the fat32 partition and then Bob's my uncle and I'll be able to edit fstab and pop it back into the Pi.
But no, life is harder than that, of course. I can see lots of fun config stuff on the fat32 partition but no fstab even with a search. Oh.
And, Micro$oft and Windows being what they are, years after ubiquitous files system such as ext4 have been around, they only support the likes of NTFS and FAT's but not anything linux out of the box. Of course.
It means I cannot natively mount what I need to mount in windows 11 in 2024 going on 2025.
Honestly ... really ? Decades later ?
So, a quick google yielded zero useful results that I could try. Crikey.
Anyway, suggestions welcomed ... I am guessing my only option is to start afresh with a new SD card image ?
Cheers
Statistics: Posted by bls — Thu Aug 01, 2024 2:19 pm