Re: [Astlinux-devel] Not enough free space for new firmware on the RUNNIX partition.

[Lonnie A. <li...@lo...>]

Hi David,

Great you got things going again.

> Worse, it looks like I cannot boot into "shell" from initial boot, whatever I select it just boots the main system.

I just tested both a VMware Fusion VM and Proxmox VM and both were able to boot into "shell".  Both had the latest runnix-0.6.3, though one had the old syslinux 3.x and the other had the newer syslinux 6.x ... on one I typed "shell" the other I arrowed down to "shell".  Both worked for me.

Being a VM gives you a lot of repair/recovery options.

Lonnie



> On Jun 28, 2021, at 3:44 PM, David Kerr <Da...@Ke...> wrote:
> 
> Answering my own question... thanks to the magic of VMware I was able to attach my test vmdk image to another running astlinux VM and inside that run fsck.fat -a /dev/sdb1 (where it was attached) and that cleaned up the "dirty bit".  Then I could delete 150MB of "recovered" files and now I am back in business.
> 
> David
> 
> On Mon, Jun 28, 2021 at 4:08 PM David Kerr <da...@ke...> wrote:
> One of my test systems has got into a state where I cannot upgrade the firmware anymore... "Not enough free space for new firmware on the RUNNIX partition."  I have tried everything I can think of to fix it.  I'm having problems unmounting /dev/sda1 (device is busy) so have not been able to run fsck on it.  Worse, it looks like I cannot boot into "shell" from initial boot, whatever I select it just boots the main system.
> 
> I may just have to rebuild my test system (not a huge issue, it is afterall just a VM test system), but any suggestions on how to fix this?  
> 
> Thanks,
> David
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel