SDcard is dead?

hi everyone. i have a question.
i’m following this site.

but while rebooting. sdcard boot do not working & appearance emergencymode.

how can i fix it?


U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img

U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)

I2C: ready
DRAM: 512 MiB
*** Warning - readenv() failed, using default environment

Net: not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot: 0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
Failed to mount ext2 filesystem…
** Unrecognized filesystem type **
Checking if uenvcmd is set …

uenvcmd was not defined in uEnv.txt …
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 1
reading uEnv.txt
1699 bytes read in 7 ms (236.3 KiB/s)
gpio: pin 55 (gpio 55) value is 1
Loaded environment from uEnv.txt
Importing environment from mmc …
Checking if uenvcmd is set …
gpio: pin 56 (gpio 56) value is 1
Running uenvcmd …
reading zImage
4103240 bytes read in 280 ms (14 MiB/s)
reading initrd.img
2952586 bytes read in 169 ms (16.7 MiB/s)
reading /dtbs/am335x-boneblack.dtb
25926 bytes read in 11 ms (2.2 MiB/s)
Kernel image @ 0x82000000 [ 0x000000 - 0x3e9c48 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Using Device Tree in place at 88000000, end 88009545

Starting kernel …

Uncompressing Linux… done, booting the kernel.
[ 0.378192] omap2_mbox_probe: platform not supported
[ 0.532827] tps65217-bl tps65217-bl: no platform data provided
[ 0.596617] bone-capemgr bone_capemgr.9: slot #0: No cape found
[ 0.633725] bone-capemgr bone_capemgr.9: slot #1: No cape found
[ 0.670831] bone-capemgr bone_capemgr.9: slot #2: No cape found
[ 0.707941] bone-capemgr bone_capemgr.9: slot #3: No cape found
[ 0.722633] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[ 0.732256] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[ 0.739001] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.756546] omap_hsmmc mmc.5: of_parse_phandle_with_args of ‘reset’ failed
[ 0.819548] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[ 0.831226] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
[ 0.838513] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
Loading, please wait…
Scanning for Btrfs filesystems
systemd-fsck[212]: rootfs: clean, 15082/111104 files, 79776/444160 blocks
[ 6.125184] EXT2-fs (mmcblk0p1): error: can’t find an ext2 filesystem on dev mmcblk0p1.
[ 6.143156] EXT4-fs (mmcblk0p1): VFS: Can’t find ext4 filesystem
[ 6.158794] FAT-fs (mmcblk0p1): bogus number of reserved sectors
[ 6.172894] FAT-fs (mmcblk0p1): bogus number of reserved sectors
[ 6.189982] F2FS-fs (mmcblk0p1): Can’t find a valid F2FS filesystem
Welcome to emergency mode. Use “systemctl default” or ^D to enter default mode.
Press enter for maintenance(or type Control-D to continue):

Well, you can either contact the author of that page ^ and find out where
he messed up.

Or actually follow, the page I wrote that he half ass copied :wink:


Now, to fix your font size.

A bit of google-ing brings you to


Now that I’ve had my morning coffee( long time ago , heh ), and read that persons “instructions”. I have to say there are many points of interest.

Mostly, his / her instructions are all jacked up.

From the looks of it this person was copying Roberts instructions from last year, with many deviations from Roberts original instructions. The lack of use of parted to set the boot partition active ( yes I saw that in fdisk but afaik that does not work in our case). fstab is also completely whack. Then last but not least, there is no mention of sudo in those instructions, for which I have to assume these instructions were performed as root. Bad mojo . . .

Anyway, in your shoes I’d do as Robert suggests, follow his latest instructions, and you should not have any issues.

Oh, and should I have mentioned that a journaling file system on a sd card is not exactly the best idea ?