Hi Tarmo, Thanks for the reply! And we are considering doing something like you're suggesting - adding fsck options to the kernel to do automatic repairs during startup when possible. Thanks for that.
/etc/fstab just has a few entries. Two partitions and then directories bound within the second writable partition (/var): # /etc/fstab: static file system information. # UUID=fe3a62a1-b2ea-45d3-afcb-f1f66161ef0d / ext4 ro,noatime,errors=remount-ro 0 1 debugfs /sys/kernel/debug debugfs defaults 0 0 tmpfs /tmp tmpfs defaults,noatime,nodev,nosuid,noexec 0 2 /dev/mmcblk1p2 /var auto defaults,noatime,errors=remount-ro 0 2 /var/local/home /home none bind 0 0 /var/local/media /media none bind 0 0 /var/local/root /root none bind 0 0 /var/local/srv /srv none bind 0 0 /var/local/swapfile none swap sw 0 0 /boot/uEnv.txt is as follows - we enable a couple pins but that's it: #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 uname_r=4.4.36-ti-r72 #uuid= #dtb= ##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..) ##BeagleBone Black: HDMI (Audio/Video) disabled: #dtb=am335x-boneblack-emmc-overlay.dtb ##BeagleBone Black: eMMC disabled: #dtb=am335x-boneblack-hdmi-overlay.dtb ##BeagleBone Black: HDMI Audio/eMMC disabled: #dtb=am335x-boneblack-nhdmi-overlay.dtb ##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled: #dtb=am335x-boneblack-overlay.dtb ##BeagleBone Black: wl1835 #dtb=am335x-boneblack-wl1835mod.dtb ##BeagleBone Green: eMMC disabled #dtb=am335x-bonegreen-overlay.dtb cmdline=coherent_pool=1M quiet net.ifnames=0 cape_universal=enable #In the event of edid real failures, uncomment this next line: #cmdline=coherent_pool=1M quiet net.ifnames=0 cape_universal=enable video=HDMI-A-1:1024x768@60e ##Example v3.8.x #cape_disable=capemgr.disable_partno= #cape_enable=capemgr.enable_partno= ##Example v4.1.x #cape_disable=bone_capemgr.disable_partno= #cape_enable=bone_capemgr.enable_partno= ##Changes to enable serial port /dev/ttyO5 and I2C bus 1 cape_enable=bone_capemgr.enable_partno=BB-UART5,BB-I2C1 ##enable Generic eMMC Flasher: ##make sure, these tools are installed: dosfstools rsync #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh uuid=fe3a62a1-b2ea-45d3-afcb-f1f66161ef0d --------------------------------- Does anything there look strange to you? Dave On Wednesday, December 6, 2017 at 9:33:09 AM UTC-5, ta...@thinnect.com wrote: > > On Monday, December 4, 2017 at 11:30:32 PM UTC+2, Dave Barndt wrote: >> >> Hi, >> >> I'm hoping that someone has come across this problem before and can point >> me in the right direction. >> >> I'm trying to troubleshoot a BeagleBone Black with Debian 8 that appears >> to have a filesystem corruption. The system has two partitions, a read-only >> rootfs partition and a writable partition for essentially everything else. >> When the system boots, U-Boot completes and hands control to the kernel, >> which runs an fsck on the rootfs successfully, but then fails to run an >> fsck on the writable parition. At that point the startup process appears to >> simply hang. I cannot seem to break to a console prompt (or get to a login >> prompt, obviously). >> >> The best hypothesis I have so far is that some sort of power failure >> caused a corruption, but I'd like to see if I can examine the "footprint" >> at all. I've never seen a corruption where fsck can't be run at all. >> Usually fsck can be run and the corruption can be examined and hopefully >> repaired. >> >> My question is, why can't fsck be run on the partition at all? Can I >> somehow break to the console prompt when the startup process hangs up? >> Earlier in the process, I can interrupt U-Boot and run "mmc", "part", and >> "ls" types of U-Boot commands to look at the partition in question - at >> that level things appear to look OK. But obviously it can't tell why fsck >> won't run on the partition. >> >> Could there be anything else going on that I'm not thinking of? >> >> Below is a log of the boot/startup process. Any light anyone can shed >> would be very helpful. >> >> Thanks for any help, >> 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 systemd-fsck@dev-mmcblk1p2.service' 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 systemd-fsck@dev-mmcblk1p2.service' 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. >> >> (nothing appears after this; unable to break to a console prompt, etc.) >> > > Hi Dave, > > Although I have seen a few corrupt file systems, I haven't stumbled on a > case where fsck fails to run. With vanilla config fsck usually is started > on boot and, in case of errors, patiently waits for you to manually confirm > each fix by pressing "y". This can be worked around by adding to the kernel > command line "fsck.mode=force fsck.repair=yes". > > What's in your /etc/fstab and /boot/uEnv.txt? > > -- > Kind regards, > Tarmo Kuuse > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/33187695-706a-4111-ba59-e23ecf88fb7c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
