Apparently the cure for this is to fsck it, but that refuses to work saying
that I have a DOS partition - that's the boot partition.
The Raspberry Pi Foundation chose to make the SD Card file system FAT32 because
it is a standard format used by a lot of different types of removable drives
like flash drives and it can be read by just about every operating system. The
other*partition*, the one with the data on it, is EXT3, the standard*Linux*file
system format.
You should be able to fsck the /boot partition of the SD Card using fsck as
follows. On my system, I have one SSD drive and one spinning rust drive, so
the SD Card pops up as sdc with sdc1 being the FAT32 partition called /boot and
sdc2 being the ext3 partion containing /. First the ext3 partition:
terry@OptiPlex:~$ sudo fsck /dev/sdc2
fsck from util-linux 2.32
e2fsck 1.44.4 (18-Aug-2018)
/dev/sdc2: clean, 161128/446208 files, 1430961/1817600 blocks
On this Kubuntu 18.10 desktop, fsck invoked e2fsk to do the job.
Then the FAT32 partition.
terry@OptiPlex:~$ sudo fsck /dev/sdc1
fsck from util-linux 2.32
fsck.fat 4.1 (2017-01-24)
/dev/sdc1: 121 files, 2663/8057 clusters
This time, fsck invoked fsck.fat.
Thanks Terry,
I didn't know that you should do each partition individually.
The sdb1 partition gave me a 'dirty flag set' message and the sdb2 one had
lots of errors that I let it clean.
Now it boots to the fixed IP address, and then crashes.
I'm trying Deans suggestion to catch an image and clone it, but not
successfully so far.
Cheers.
Peter
--
Next meeting at *new* venue: Bournemouth, Tuesday, 2018-12-04 20:00
Check if you're replying to the list or the author
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
