Hi, I'm hoping someone has encountered this before and can provide some guidance. I'm troubleshooting a BeagleBone Black system that has two partitions, a read-only rootfs partition and a writable partition for everything else. When it boots, U-Boot completes and hands control to the kernel, which runs an fsck on the rootfs successfully, but appears to fail to run fsck at all on the writable partition. At that point the system essentially fails to come up further - I can't seem to break to a console prompt (or login, obviously).
>From the U-Boot level, I've examined the writable partition and even a bunch of files in it using U-Boot commands like "mmc", "part", and "ls" - and everything I've seen so far actually looks OK. My question is, is there some way I can determine why the kernel won't run the fsck on the writable partition? I suspect what happened is that the power was abruptly turned off to the BBB and a corruption occurred; I'm just trying to determine the "footprint" if possible. In the past I've only seen corruptions occur within a file system, and was able to repair them using fsck. But this time fsck won't even run on the partition. Is there some way I can force it to? Below is the log of a boot attempt. Thanks very much for any light! Dave --------------------------------------- U-Boot SPL 2016.11-00002-gab8be1c (Dec 07 2016 - 12:54:09) Trying to boot from MMC2 U-Boot 2016.11-00002-gab8be1c (Dec 07 2016 - 12:54:09 -0600), Build: jenkins-github_Bootloader-Builder-490 CPU : AM335X-GP rev 2.1 I2C: ready DRAM: 512 MiB Reset Source: Power-on reset has occurred. MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment Board: BeagleBone Black <ethaddr> not set. Validating first E-fuse MAC Net: eth0: MII MODE cpsw Press SPACE to abort autoboot in 2 seconds board_name=[A335BNLT] ... board_rev=[AIA0] ... Card did not respond to voltage select! Card did not respond to voltage select! Card did not respond to voltage select! gpio: pin 56 (gpio 56) value is 0 gpio: pin 55 (gpio 55) value is 0 gpio: pin 54 (gpio 54) value is 0 gpio: pin 53 (gpio 53) value is 1 Card did not respond to voltage select! Card did not respond to voltage select! switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... gpio: pin 56 (gpio 56) value is 0 gpio: pin 55 (gpio 55) value is 0 gpio: pin 54 (gpio 54) value is 0 gpio: pin 53 (gpio 53) value is 1 switch to partitions #0, OK mmc1(part 0) is current device gpio: pin 54 (gpio 54) value is 1 Checking for: /uEnv.txt ... Checking for: /boot.scr ... Checking for: /boot/boot.scr ... Checking for: /boot/uEnv.txt ... gpio: pin 55 (gpio 55) value is 1 1388 bytes read in 28 ms (47.9 KiB/s) Loaded environment from /boot/uEnv.txt Checking if uname_r is set in /boot/uEnv.txt... gpio: pin 56 (gpio 56) value is 1 Running uname_boot ... loading /boot/vmlinuz-4.4.36-ti-r72 ... 8646448 bytes read in 589 ms (14 MiB/s) loading /boot/dtbs/4.4.36-ti-r72/am335x-abbbi.dtb ... 61725 bytes read in 39 ms (1.5 MiB/s) loading /boot/initrd.img-4.4.36-ti-r72 ... 5231183 bytes read in 369 ms (13.5 MiB/s) debug: [console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-UART5,BB-I2C1 root=UUID=936d3d70-c3c4-4d5b-bb06-2d6d680ae95d ro rootfstype=ext4 rootwait coherent_pool=1M quiet net.ifnames=0 cape_universal=enable] ... debug: [bootz 0x82000000 0x88080000:4fd24f 0x88000000] ... ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Ramdisk to 8fb02000, end 8ffff24f ... OK Loading Device Tree to 8faef000, end 8fb0111c ... OK Starting kernel ... [ 0.001350] clocksource_probe: no matching clocksources found [ 2.075156] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle [ 2.259213] omap_voltage_late_init: Voltage driver support not added [ 2.270746] PM: Cannot get wkup_m3_ipc handle [ 2.382235] bone_capemgr bone_capemgr: slot #0: No cape found [ 2.426233] bone_capemgr bone_capemgr: slot #1: No cape found [ 2.470229] bone_capemgr bone_capemgr: slot #2: No cape found [ 2.514227] bone_capemgr bone_capemgr: slot #3: No cape found Loading, please wait... rootfs: clean, 78785/98304 files, 384993/393216 blocks [ 12.471231] pinctrl-single 44e10800.pinmux: pin 44e108c0.0 already requested by 481aa000.serial; cannot claim for 0-0039 [ 12.482304] pinctrl-single 44e10800.pinmux: pin-48 (0-0039) status -22 [ 12.488911] pinctrl-single 44e10800.pinmux: could not request pin 48 (44e108c0.0) from group adi_hdmi_bbbi_pins on device pinctrl-single [ 12.501341] adv7511 0-0039: Error applying setting, reverse things back [ 12.928105] pinctrl-single 44e10800.pinmux: pin 44e108c0.0 already requested by 481aa000.serial; cannot claim for 0-0039 [ 12.939198] pinctrl-single 44e10800.pinmux: pin-48 (0-0039) status -22 [ 12.945814] pinctrl-single 44e10800.pinmux: could not request pin 48 (44e108c0.0) from group adi_hdmi_bbbi_pins on device pinctrl-single [ 12.958243] adihdmi 0-0039: Error applying setting, reverse things back [ 14.022183] EDID block is all zeroes [ 14.038732] adihdmi_encoder_get_modes - 788 - No EDID [ 14.279735] adihdmi_encoder_get_modes - 788 - No EDID [FAILED] Failed to start File System Check on /dev/mmcblk1p2. See 'systemctl status [email protected]' for details. [DEPEND] Dependency failed for /var. [DEPEND] Dependency failed for Load/Save Random Seed. [DEPEND] Dependency failed for Update UTMP about System Runlevel Changes. [DEPEND] Dependency failed for /root. [DEPEND] Dependency failed for Local File Systems. [DEPEND] Dependency failed for netfilter persistent configuration. [DEPEND] Dependency failed for Emergency Shell. [DEPEND] Dependency failed for Emergency Mode. [DEPEND] Dependency failed for Update UTMP about System Boot/Shutdown. [DEPEND] Dependency failed for Flush Journal to Persistent Storage. [DEPEND] Dependency failed for /srv. [DEPEND] Dependency failed for /media. [DEPEND] Dependency failed for /home. [DEPEND] Dependency failed for /var/local/swapfile. [DEPEND] Dependency failed for Swap. Starting Raise network interfaces... Starting File System Check on /dev/mmcblk1p2... [ OK ] Reached target Timers. [ OK ] Closed Syslog Socket. [ OK ] Reached target Login Prompts. Starting Create Volatile Files and Directories... [ OK ] Reached target Sockets. [FAILED] Failed to start Create Volatile Files and Directories. See 'systemctl status systemd-tmpfiles-setup.service' for details. [FAILED] Failed to start File System Check on /dev/mmcblk1p2. See 'systemctl status [email protected]' for details. [DEPEND] Dependency failed for /var. [DEPEND] Dependency failed for /root. [ OK ] Started Raise network interfaces. [ OK ] Reached target Network. [ OK ] Reached target Network is Online. (no further output, can't seem to break to any prompt, etc.) -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/914dd72a-467d-4f35-891d-0505a1c8b56e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
