News:

Server migration complete, Welcome to version 2.1.1

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 15231
Latest: Manuelpereyra78
New This Month: 20
New This Week: 4
New Today: 2
Stats
Total Posts: 124533
Total Topics: 15147
Most Online Today: 58
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 3
Guests: 30
Total: 33

fpp error when writing to emmc on BBB

Started by neilric99, June 30, 2022, 03:55:57 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

neilric99

I attempted to update my emmc with the 6.0 master branch (latest) 6.x-master-451-gbae3eb01 and came up with this error. Not sure what to do with it or how to report it.

Command: sudo TERM=vt100 env 2>&1
----------------------------------------------------------------------------------
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=C
MAIL=/var/mail/root
LOGNAME=root
USER=root
HOME=/root
SHELL=/bin/bash
TERM=vt100
SUDO_COMMAND=/usr/bin/env
SUDO_USER=fpp
SUDO_UID=500
SUDO_GID=500
==================================================================================
Command: sudo TERM=vt100 /opt/fpp/SD/BBB-FlashMMC.sh btrfs 2>&1
----------------------------------------------------------------------------------
---------------------------------------
Installing bootloader

dd if=/opt/fpp/bin.bbb/bootloader/MLO of=/dev/mmcblk0 count=1 seek=1 bs=128k
0+1 records in
0+1 records out
92256 bytes (92 kB, 90 KiB) copied, 0.0322101 s, 2.9 MB/s
dd if=/opt/fpp/bin.bbb/bootloader/u-boot.img of=/dev/mmcblk0 count=2 seek=1 bs=384k
1+1 records in
1+1 records out
472872 bytes (473 kB, 462 KiB) copied, 0.0386698 s, 12.2 MB/s
dd if=/opt/fpp/bin.bbb/bootloader/MLO of=/dev/mmcblk1 count=1 seek=1 bs=128k
0+1 records in
0+1 records out
92256 bytes (92 kB, 90 KiB) copied, 0.525052 s, 176 kB/s
dd if=/opt/fpp/bin.bbb/bootloader/u-boot.img of=/dev/mmcblk1 count=2 seek=1 bs=384k
1+1 records in
1+1 records out
472872 bytes (473 kB, 462 KiB) copied, 0.141716 s, 3.3 MB/s
---------------------------------------
Creating partitions

Checking that no-one is using this disk right now ... OK

Disk /dev/mmcblk1: 3.66 GiB, 3925868544 bytes, 7667712 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x70c83afe

Old situation:

Device         Boot Start     End Sectors  Size Id Type
/dev/mmcblk1p1       8192 7667711 7659520  3.7G 83 Linux

>>> Created a new DOS disklabel with disk identifier 0xd1f34561.
/dev/mmcblk1p1: Created a new partition 1 of type 'Linux' and of size 96 MiB.
Partition #1 contains a ext4 signature.
/dev/mmcblk1p2: Created a new partition 2 of type 'Linux' and of size 3.6 GiB.
/dev/mmcblk1p3: Done.

New situation:
Disklabel type: dos
Disk identifier: 0xd1f34561

Device         Boot  Start     End Sectors  Size Id Type
/dev/mmcblk1p1 *      8192  204799  196608   96M 83 Linux
/dev/mmcblk1p2      204800 7667711 7462912  3.6G 83 Linux

The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Device or resource busy
The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or partx(8).
Syncing disks.
blockdev: ioctl error on BLKRRPART: Device or resource busy
Disk /dev/mmcblk1: 3.66 GiB, 3925868544 bytes, 7667712 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd1f34561

Device         Boot  Start     End Sectors  Size Id Type
/dev/mmcblk1p1 *      8192  204799  196608   96M 83 Linux
/dev/mmcblk1p2      204800 7667711 7462912  3.6G 83 Linux
---------------------------------------
Formating partitions

mke2fs 1.46.2 (28-Feb-2021)
Discarding device blocks:   4096/957440␈␈␈␈␈␈␈␈␈␈␈␈␈528384/957440␈␈␈␈␈␈␈␈␈␈␈␈␈             ␈␈␈␈␈␈␈␈␈␈␈␈␈done                           
Creating filesystem with 957440 4k blocks and 239520 inodes
Filesystem UUID: 5c6bf440-dc89-4fab-a91d-c8efc24cfbfe
Superblock backups stored on blocks:
   32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables:  0/30␈␈␈␈␈     ␈␈␈␈␈done                           
Writing inode tables:  0/30␈␈␈␈␈ 1/30␈␈␈␈␈ 2/30␈␈␈␈␈ 3/30␈␈␈␈␈ 6/30␈␈␈␈␈ 9/30␈␈␈␈␈12/30␈␈␈␈␈16/30␈␈␈␈␈17/30␈␈␈␈␈19/30␈␈␈␈␈22/30␈␈␈␈␈26/30␈␈␈␈␈29/30␈␈␈␈␈     ␈␈␈␈␈done                           
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information:  0/30␈␈␈␈␈     ␈␈␈␈␈done

ERROR: mount check: cannot open /dev/mmcblk1p2: No such file or directory
ERROR: cannot check mount status of /dev/mmcblk1p2: No such file or directory
btrfs-progs v5.10.1
See http://btrfs.wiki.kernel.org for more information.

Poporacer

Are you trying to manually update your emmc or using the web UI? And is there a reason that you need to update the emmc? If you have an SD card with the FPP image on it, then FPP will be running off of the SD card and not the emmc. The developers have ran across reliability issues running FPP from the emmc and because of that, they recommend to run FPP from the SD card. 
If to err is human, I am more human than most people.

dkulp

You are also flashing with btrfs, but the original was ext4.   That requires changing from one partition to two partitions which SOMETIMES requires an extra reboot.   I'm willing to bet if you reboot and re-run the flash as btrfs, it would get further.   That said, is there a particular reason you are using btrfs?    It hasn't been extensively tested in quite a while.  It will definitely boot a bit slower, but once booted up it should be fine.
Daniel Kulp - https://kulplights.com

neilric99

For some reason I thought that I needed to load the emmc , if I don't need to sorry about that I will continue to run for the SD. I did have a problem with the SD extender and it was booting from emmc which was running 3.5. my SD I was already on 6.0 master. I put the SD card into the slot directly and got it back to reading the SD


Support FPP

+- Recent Topics

FPP CANT REACH CONTROLLER THROUGH ETHERNET IP ADDRESS by k6ccc
Today at 12:33:42 PM

Testing RGB's by ecbrum
Today at 12:09:32 PM

Beagle Board x36 networking issues. by rayster
Today at 11:40:19 AM

Touchscreen by Poporacer
Today at 10:46:45 AM

BBB Display by TracyDockter
Today at 07:13:26 AM

Customizable Virtual Matrix to Drive Video Screens by CaptainMurdoch
August 18, 2022, 02:38:11 PM

Pi Top on sale by CaptainMurdoch
August 18, 2022, 11:49:33 AM

PiCap abnormal conditions: Disabling my IP address by CeP
August 18, 2022, 08:00:16 AM

FPP 6.0 Released! by Poporacer
August 17, 2022, 05:17:25 PM

Just putting this out for research? by Poporacer
August 17, 2022, 10:53:09 AM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod