Solved Error during Diversion installation: "Not enough free space available on /mnt/[NAME_OF_ENTWARE_PARTITION]"

[papypaprika]

Hi all,

I'm a longtime user and fan of Diversion. I noticed I had issues with certs yesterday, and decided to remove and reinstall Diversion.

When I now try to install Diversion, I'm greeted with the following error:
"Not enough free space available on /mnt/[NAME_OF_ENTWARE_PARTITION]"

My entware set-up is fine, and my USB key has plenty of free room (3-4 GB).
When looking at the install script, I see that there is a disk size test, but I'm wondering if the command (df) used for such test is correct:
df -h /mnt/[NAME_OF_ENTWARE_PARTITION] reports the wrong size (43mb) of my Entware USB stick, and the wrong usage (20.5mb).
du -hs /mnt/[NAME_OF_ENTWARE_PARTITION] reports the right size of usage my Entware USB stick (3.3Gb).

I thought that my USB stick may be failing, formated it, but I still have the same error message and weird df -h output showing wrong disk size and disk usage.

I'm on RT-ACC66u, FW 374.43_44EAj9527, amtm 3.1.8 FW

Any ideas?
Otherwise, where can I manually comment the disk size check in the Diversion script / modules?

Thank you !!

 

[ColinTaylor]

Your disk partitioning may be wrong or corrupted. I suggest that you use amtm's fd option to re-partition and reformat the drive.

How big is the drive?

 

[papypaprika]

Your disk partitioning may be wrong or corrupted. I suggest that you use amtm's fd option to re-partition and reformat the drive.

How big is the drive?

Thank you Colin. Will try and report. Drive is 7-8GB.

 

[ColinTaylor]

Drive is 7-8GB.

OK. Make sure you only create 1 partition that covers the whole drive, rather then choosing the option to split the drive into multiple partitions.

 

[papypaprika]

Ok, formatting and re-installing from scratch did the trick.
When I restore (rsync -a) my previous entware back-up, I have again the same problem... Oh well, I guess I'll have to set-up everything from scratch...

Thank you for helping me pinpoint the issue.

 

[thelonelycoder]

Any ideas?
Otherwise, where can I manually comment the disk size check in the Diversion script / modules?

This would have been a bad idea anyway, right?

 

[papypaprika]

Indeed, it would have postponed data corruption for later.

I suspect that my usb stick got corrupted because the swap partition didn't unmount properly.

May I suggest an improvement to the way swapoff is added by amtm/diversion to the services-stop script?

What about appending the swapoff command at the end rather than the top of the script?

My swap refuses to unmount until mysql/mariadb is stopped, and the current addition of the swapoff command amtm/diversion does not append it necessarily at the end of the script unless mistaken.