From: Adriana Kobylak <anoo@linux.ibm.com>
To: rgrs <rgrs@protonmail.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: Firmware update error: Cannot UBI create volume
Date: Tue, 17 Dec 2019 11:01:06 -0600 [thread overview]
Message-ID: <0bedefae291dc69d048fd5806d17d385@linux.vnet.ibm.com> (raw)
In-Reply-To: <1i6T-_CIXkSAHAqGbzb3IZW6jbo0mDc2nF7amahFYZ_d-4bMaTTMJeG2rb-1wE6J0OPb7NZRJ0Zx80eTDA5ukPs9CknlPBlw6IGMfHTwedI=@protonmail.com>
On 2019-12-17 03:52, rgrs wrote:
> Hi All,
>
> I have a strange behavior where only one image is visible in webUI.
> I get UBI "no space left" errors when I try to update/flash new image.
> I dont have steps to reproduce and dont know how my BMC ended up in
> this state.
>
> How do I recover from this error? /proc/mtd shows all
> partitions/volumes properly.
> Is there any way to recover alternate partition without erasing SPI
> from uboot?
Seems there's an 'orphan' volume which you can manually delete to make
space. A while back there was an issue at some point where not all the
volumes were deleted during a firmware update.
>
> root@obmc:~# ubinfo -d 4 -n 1
> Volume ID: 1 (on ubi4)
> Type: static
> Alignment: 1
> Size: 43 LEBs (2812544 bytes, 2.6 MiB)
> Data bytes: 2767008 bytes (2.6 MiB)
> State: OK
> Name: kernel-7e7e1530
This seems to be the 'orphan' since there's not a corresponding
'rofs-7e7e1530' volume, you can manually delete it with "ubirmvol
/dev/ubi4 -n 1". You can also list all the volumes of a device with
"ubinfo -a -d 0" for example.
next prev parent reply other threads:[~2019-12-17 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 9:52 Firmware update error: Cannot UBI create volume rgrs
2019-12-17 17:01 ` Adriana Kobylak [this message]
2019-12-18 8:26 ` rgrs
2020-01-02 6:32 ` rgrs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0bedefae291dc69d048fd5806d17d385@linux.vnet.ibm.com \
--to=anoo@linux.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=rgrs@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.