On Thu, 27 Jun 2019 07:23:52 -0700 (PDT),
z.mome...@gmail.com declaimed the
following:
>I used 7-zip for uncompressed that downloaded file. I used Etcher for write
>downloaded file on uSD card on windows and on ubuntu but on both of them,
>it's failed. after write i gave error "You need to format ...". i connected
>my board to my lap top and every thing about board is ok, when it
>connected, it turned on and its 4 User LED and power LED turned on and its
>drive showed and a notification "beaglebone is ready" showed on desktop.
>but when i used uSD card with image written on it on board, error "You need
>to format..." appeared.
>
If using Balena Etcher (recent version) you do NOT have decompress the
.xz file. Using
bone-debian-9.5-lxqt-armhf-2018-10-07-4gb.img.xz
on a freshly formatted (whether it needed to be formatted or not, I wanted
to clear out a Raspberry-Pi installer that was on it first) I ran Etcher
and wrote to a 16GB SanDisk card.
I did have to kill the Acronis Active Protection process -- stupid
software kills any attempt to overwrite the MBR region of a "disk", and
doesn't seem to have any controls to exclude SD cards.
Once Etcher completes, Windows can not read the SD card, and would say
it needs to be formatted -- just EJECT the card. Ubuntu might complain if
it is expecting to see a FAT file system (it appears the new image creates
ext4 filesystem).
Put the newly written SD card into my BBB and booted. It took a while,
but eventually the "BeagleBone Getting Started" virtual drive appeared
(while I have a CAT-5 cable connecting the BBB to my router, I was powering
it from a USB cable -- so both USB and Ethernet are active).
Used PuTTY to SSH into the BBB (using the router assigned IP. not the
USB IP).
Then followed the sequence at
https://www.element14.com/community/community/designcenter/single-board-computers/next-gen_beaglebone/blog/2017/07/17/extending-micro-sd-card-space-for-beaglebone-black-use-windows-users
to resize the SD card partition to take up the entire card. Note: rather
than the "su - root", just use "sudo su" to get into root account; there is
no root password on modern images so one can't use the bare "su ... "
syntax. Also, once root, you do NOT need to preface the subsequent resizing
commands with "sudo".
The ext4 did trigger another step as the fdisk asked me if I wanted to
clear that setting -- I answered N; if new images are ext4 I wasn't going
to downgrade to ext3. "partprobe" also gave me a few error messages, but
they might have been warnings, as the resize appeared to complete and after
a reboot I got...
debian@beaglebone:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 215M 0 215M 0% /dev
tmpfs 49M 6.0M 43M 13% /run
/dev/mmcblk0p1 15G 2.9G 12G 21% / <<<<<<< lots of free space
tmpfs 242M 0 242M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 242M 0 242M 0% /sys/fs/cgroup
tmpfs 49M 0 49M 0% /run/user/1000
debian@beaglebone:~$