|
Ok, so I'm running ssh via windows powershell.
so far, this is what it shows when I ran fdisk:
/mnt/secure # fdisk -l
Disk /dev/mmcblk0: 15 GB, 15634268160 bytes, 30535680 sectors
1908480 cylinders, 1 heads, 16 sectors/track
Units: cylinders of 16 * 512 = 8192 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk0p1 * 0,0,0 0,0,0 1683456 30633983 28950528 13.8G b Win95 FAT32
Partition 1 does not end on cylinder boundary
/dev/mmcblk0p2 0,0,0 0,0,0 73728 139263 65536 32.0M 6 FAT16
Partition 2 does not end on cylinder boundary
/dev/mmcblk0p3 0,0,0 0,0,0 1 1544192 1544192 754M 5 Extended
Partition 3 does not end on cylinder boundary
/dev/mmcblk0p5 0,0,0 0,0,0 139264 172031 32768 16.0M 83 Linux
/dev/mmcblk0p6 0,0,0 0,0,0 172032 241663 69632 34.0M 83 Linux
/dev/mmcblk0p7 0,0,0 0,0,0 241664 372735 131072 64.0M 83 Linux
/dev/mmcblk0p8 0,0,0 0,0,0 372736 1421311 1048576 512M 83 Linux
/dev/mmcblk0p9 0,0,0 0,0,0 1421312 1683455 262144 128M 83 Linux
It's layout reminds me of some android devices, but with different labels. So the fat32 partition is "/dev/mmcblk0p1". I run with fsck -N, and this is what I get:
/mnt/secure # fsck -N /dev/mmcblk0p1
fsck (busybox 1.26.2, 2020-08-06 18:11:11 EEST)
[fsck.auto (1) -- ] fsck.auto /dev/mmcblk0p1
Not certain what it's doing, so I run it again with the -A option and I get:
/mnt/secure # fsck -A /dev/mmcblk0p1
fsck (busybox 1.26.2, 2020-08-06 18:11:11 EEST)
I may have to use a linux machine to get this to work.
|