Read the statement by Michael Teeuw here.
Everything was going so well
-
@JMac you cant whack on a file system if its mounted for access,do
df -k
will show u the devices and where they are mounted then sudo umount /dev/… what you were using
df -k should show it gone
then the fsck… commands should work w sudo -
@JMac if u can get the config, custom
css and and listing of the modules ( ls command) we can build the backup/restore files -
@sdetweil sorry to be dense how do I know what I’m unmounting?
am I unmounting /dev/mmcblk0p1?? it says thats mounted on /boot.edit to add,
after re running sudo fdisk -l it would appear the old memory card (with my previous MM setup on) is on Disk /dev/sdathats classed as Disk Model: storage device (as it’s mounted in the usb drive atm) does this seem correct? is this the one which needs unmounting?
-
@JMac well mounted means accessible by the filesystem
so it’s /dev/sda
the usb installed sd cardso
sudo unmount /dev/sda
and then run fsck on that -
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?
-
@JMac correct… you had to find the disk name
-
@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. -
@JMac yes, you must use sudo on both commands unmount and fsck
sorry I was unclear
normal users should not be able to mess with hardware, so one must act as root
-
@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. -
@JMac hm… wonder what is using it?
can you open the disks app on the pi from the dedktop menu
