Firmware update error: Cannot UBI create volume

[rgrs]

Hi Adriana,

Was this bug fixed recently after 2.7.0 release?
My codebase is aligned with 2.7.0 and I'm hitting this issue often.

Thanks,
Raj


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, December 18, 2019 1:56 PM, rgrs <rgrs at protonmail.com> wrote:

> Thanks :)
> I am able to flash new images now.
>
> ~Raj
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Tuesday, December 17, 2019 10:30 PM, Adriana Kobylak anoo at linux.ibm.com wrote:
>
> > 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 at 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.