Read the statement by Michael Teeuw here.
Everything was going so well
-
@JMac hm… wonder what is using it?
can you open the disks app on the pi from the dedktop menu
-
@sdetweil on the home screen I have 2 drive icons under the wastebasket.
one is boot
the other is rootfsi then have the option to eject these in the file manager
-
@JMac there should be that drive on /dev/sda too
-
@sdetweil I’m a little confused (I’d imagine thats pretty clear at this point).
i run sudo fdisk -1
and get
Disk /dev/ram0 through to Disk /dev/ram15
the list then has
Disk/dev/mmcblk0: 7.4GiB (my thinking is this is the current/new sd card)Device
/dev/mmcblk0p1
/dev/mmcblk0p2Disk /dev/sda:59.69 GiB (I again assume this is the old SD with my original MM setup)
Device
/dev/sda1
/dev/sda/2end of the list.
does any of that make sense/ is any of it what I’m looking for? I’ve obviously taken out several lines under each of those headers just for space and time typing.
-
@JMac yes sda has two partitions boot and rootfs
but you need to run e2fsck on /dev/sda2
e2fsck mean extended version 2, file system check -
so should i also run sudo umount /dev/sda2 before running sudo e2fsck -f -v /dev/sda2?
-
@JMac yes
-
@sdetweil so I’ve run sudo umount /dev/sda1 and the same for sda2 and both folders have disappeared off the home screen.
which e2fsck do I run if i had to unmount 2 drives?
-
@JMac unmount means remove them from normal file system access
the device names still exist
as e2fsck could modify the file system blocks on the drive, you don’t want to do that while you could still copy a file there
so you are passing the hardware name to e2fsck
-
@sdetweil so do I run e2fsck -f -v /dev/sda1 or e2fsck -f -v /dev/sda2
or does it not matter?I’m struggling here to the bigger picture so can’t see the logic of the steps.