SanDisk storage only reading 30.6 MB capacity after board reset

jon
jon New Member Posts: 3 ✭
in UP Board Linux

Hello, we have a few UP-CHT01-A20-0432-A11 boards that accidentally had the reset button pressed, and it wiped the Sandisk eMMC storage. When we went to reinstall Ubuntu Linux on mmcblk0, the capacity only reads as 30.6 MB now instead of 32 GB as expected. Does anyone know why this happens and how to fix it? We have tried updating the BIOS to UPC1DM23 but it didn't change this behavior.

I've attached a log from Ubuntu's boot-repair tool below in case it is helpful. Thanks in advance for your assistance!

boot-repair-4ppa130                                              [20210921_1938]

============================== Boot Info Summary ===============================

 => No boot loader is installed in the MBR of /dev/mmcblk0.

sda: ___________________________________________________________________________

    File system:       iso9660
    Boot sector type:  Unknown
    Boot sector info: 
    Operating System:  
    Boot files:        /boot/grub/grub.cfg


================================ 0 OS detected =================================


============================ Architecture/Host Info ============================

CPU architecture: 64-bit
Live-session OS is Ubuntu 64-bit (Ubuntu 18.04.5 LTS, bionic, x86_64)


===================================== UEFI =====================================

BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.

efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001
Boot0001* UEFI: Memorex USB Flash Drive PMAP, Partition 1   PciRoot(0x0)/Pci(0x14,0x0)/USB(6,0)/USB(0,0)/HD(1,MBR,0x483122d5,0x35d8,0x1340)..BO
This session has been detected as 'live' because /proc/cmdline contains (boot=casper)
This session has been detected as 'live' because df -Th / contains overlay



============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________


Partitions info (1/3): _________________________________________________________


Partitions info (2/3): _________________________________________________________


Partitions info (3/3): _________________________________________________________


fdisk -l (filtered): ___________________________________________________________

Disk mmcblk0: 30.6 MiB, 32096256 bytes, 62688 sectors
Disk sda: 29.3 GiB, 31457280000 bytes, 61440000 sectors
Disk identifier: 0x483122d5
      Boot Start     End Sectors  Size Id Type
sda1  *        0 4284223 4284224    2G  0 Empty
sda2       13784   18711    4928  2.4M ef EFI (FAT-12/16/32)

parted -lm (filtered): _________________________________________________________

sda:31.5GB:scsi:512:512:unknown:Memorex USB Flash Drive:;
mmcblk0:32.1MB:sd/mmc:512:512:unknown:MMC SDM032:;

blkid (filtered): ______________________________________________________________

NAME    FSTYPE   UUID                                 PARTUUID                             LABEL                    PARTLABEL
sda     iso9660  2020-08-06-22-59-01-00                                                    Ubuntu 18.04.5 LTS amd64 
├─sda1  iso9660  2020-08-06-22-59-01-00               483122d5-01                          Ubuntu 18.04.5 LTS amd64 
└─sda2  vfat     EC34-71CF                            483122d5-02                          Ubuntu 18.04.5 LTS amd64 
mmcblk0                                                                                                             

df (filtered): _________________________________________________________________

       Avail Use% Mounted on
sda         0 100% /cdrom

Mount options: __________________________________________________________________

sda    ro,noatime,nojoliet,check=s,map=n,blocksize=2048

====================== sda/boot/grub/grub.cfg (filtered) =======================

Try Ubuntu without installing
Install Ubuntu
OEM install (for manufacturers)
Check disc for defects

==================== sda: Location of files loaded by Grub =====================

           GiB - GB             File                                 Fragment(s)
            ?? = ??             boot/grub/grub.cfg                             1


======================== Unknown MBRs/Boot Sectors/etc =========================

Unknown BootLoader on sda

00000000  45 52 08 00 00 00 90 90  00 00 00 00 00 00 00 00  |ER..............|
00000010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000020  33 ed fa 8e d5 bc 00 7c  fb fc 66 31 db 66 31 c9  |3......|..f1.f1.|
00000030  66 53 66 51 06 57 8e dd  8e c5 52 be 00 7c bf 00  |fSfQ.W....R..|..|
00000040  06 b9 00 01 f3 a5 ea 4b  06 00 00 52 b4 41 bb aa  |.......K...R.A..|
00000050  55 31 c9 30 f6 f9 cd 13  72 16 81 fb 55 aa 75 10  |U1.0....r...U.u.|
00000060  83 e1 01 74 0b 66 c7 06  f3 06 b4 42 eb 15 eb 02  |...t.f.....B....|
00000070  31 c9 5a 51 b4 08 cd 13  5b 0f b6 c6 40 50 83 e1  |1.ZQ....[...@P..|
00000080  3f 51 f7 e1 53 52 50 bb  00 7c b9 04 00 66 a1 b0  |?Q..SRP..|...f..|
00000090  07 e8 44 00 0f 82 80 00  66 40 80 c7 02 e2 f2 66  |..D.....f@.....f|
000000a0  81 3e 40 7c fb c0 78 70  75 09 fa bc ec 7b ea 44  |.>@|..xpu....{.D|
000000b0  7c 00 00 e8 83 00 69 73  6f 6c 69 6e 75 78 2e 62  ||.....isolinux.b|
000000c0  69 6e 20 6d 69 73 73 69  6e 67 20 6f 72 20 63 6f  |in missing or co|
000000d0  72 72 75 70 74 2e 0d 0a  66 60 66 31 d2 66 03 06  |rrupt...f`f1.f..|
000000e0  f8 7b 66 13 16 fc 7b 66  52 66 50 06 53 6a 01 6a  |.{f...{fRfP.Sj.j|
000000f0  10 89 e6 66 f7 36 e8 7b  c0 e4 06 88 e1 88 c5 92  |...f.6.{........|
00000100  f6 36 ee 7b 88 c6 08 e1  41 b8 01 02 8a 16 f2 7b  |.6.{....A......{|
00000110  cd 13 8d 64 10 66 61 c3  e8 1e 00 4f 70 65 72 61  |...d.fa....Opera|
00000120  74 69 6e 67 20 73 79 73  74 65 6d 20 6c 6f 61 64  |ting system load|
00000130  20 65 72 72 6f 72 2e 0d  0a 5e ac b4 0e 8a 3e 62  | error...^....>b|
00000140  04 b3 07 cd 10 3c 0a 75  f1 cd 18 f4 eb fd 00 00  |.....<.u........|
00000150  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001b0  94 80 00 00 00 00 00 00  d5 22 31 48 00 00 80 00  |........."1H....|
000001c0  01 00 00 82 e0 fd 00 00  00 00 40 5f 41 00 00 fe  |..........@_A...|
000001d0  ff ff ef fe ff ff d8 35  00 00 40 13 00 00 00 00  |.......5..@.....|
000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200


=============================== StdErr Messages ================================

File descriptor 63 (pipe:[80550]) leaked on lvs invocation. Parent PID 7838: /bin/bash

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the boot.
· Share on FacebookShare on Twitter

Comments

  • camillus
    camillus Administrator, Moderator, AAEON Posts: 188 admin

    Hi @jon,

    I am not sure how the button on the UP board will wipe the eMMC storage. Please follow this steps to wipe the eMMC:

    • Flash Ubuntu OS on USB
    • Plug in USB on UP board and power on
    • Select "Try Ubuntu"
    • When system boots, open terminal and type 'sudo gparted'
    • On the gparted GUI you will find a wide box with /dev/mmcblk0 and the storage capacity written under
    • Right click on the box and select unmount
    • Right click on it and select delete for all partitions (/dev/mmcblk0p1 and /dev/mmcblk0p2)
    • All partitions should be 'unallocated'

    The partitions will be deleted and you will have an empty eMMC. Power off and the storage capacity should be correct.

    Best Regards,

    · Share on FacebookShare on Twitter
  • jon
    jon New Member Posts: 3 ✭

    Hi @camillus,

    Even after rebooting and using Ubuntu on a USB drive, the mmcblk0 partition only shows as 30.6 MB in capacity. There are no partitions on the device anymore. Please let me know if there is anything else to potentially try. Is there another issue that could have caused this to happen, such as a power fluctuation? Thanks again.

    · Share on FacebookShare on Twitter
  • camillus
    camillus Administrator, Moderator, AAEON Posts: 188 admin

    Hi @jon ,

    Can you boot into BIOS menu, Go to Chipset > North Bridge and make a screenshot of the memory information shown there.

    Best Regards,

    · Share on FacebookShare on Twitter
  • pranav_khekare
    pranav_khekare New Member Posts: 1 ✭

    Hello, @camillus,

    I work with @jon, and I have the screenshot of the information you requested from the North Bridge tab in the BIOS settings.

    · Share on FacebookShare on Twitter
  • jon
    jon New Member Posts: 3 ✭

    Hi @camillus, any ideas on what might be causing this?

    Thanks,
    Jon

    · Share on FacebookShare on Twitter
  • camillus
    camillus Administrator, Moderator, AAEON Posts: 188 admin

    Can you please also show the output of df -h from the terminal.

    · Share on FacebookShare on Twitter
  • e_50
    e_50 New Member Posts: 1 ✭

    Sorry if this is a reply to a very old thread but maybe it would help someone who is facing the same issue again. 30.6MB recognition for Sandisk memory card capacity shows that the controller inside does not see the NAND (physically). In another word, the card is defective and needs to be replaced. However, if you lost some important information on it, there is a proper way to restore that data.

    · Share on FacebookShare on Twitter

Categories

Privacy Policy