Hello all,

 

  I am receiving this error while building the image:

 

Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/loop0 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.

 

I am .

 

This happens in the partitioning phase (lib/functions/image/partitioning.sh line 229, using branch "v23.11" commit bba856bb57823556e12fa180284c7490fdd3708d😞

  run_host_command_logged partprobe "${LOOP}"

 

Investigated a lot, tried to unmont the image, losetup -d the loop device but nothing helped.

 

Can you please help me?

 

Kind regards,

 

   Andrea

 

 

 

Please share full log.

Hi @Werner,

 

  yes of course: https://paste.next.armbian.com/pakisigigu

 

Perhaps this ? https://github.com/armbian/build/issues/6132

 

Despite the fact the problem is very similar, I am not using WSL2 to build. I am using a Ubuntu VM :

 

Ubuntu 22.04.3 LTS (GNU/Linux 5.15.0-94-generic x86_64)

 

andrea@armbian:~$ uname -a
Linux armbian 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
 

User adeepn confirms that it happens also on Ubuntu w/kernel 5.15.

 

I will try to upgrade to 6.1 and let you know.

 

Thanks for the hint

I confirm that using an updated kernel (6.7.3) the build succeds.

 

Linux armbian 6.7.3-060703-generic #202401311935 SMP PREEMPT_DYNAMIC Thu Feb  1 00:46:47 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

 

Thank you very much!

 

 

 

12.02.2024 в 14:35, Andrea сказал:

Can you please help me?

partprobe /dev/loop2
   Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,........
...........

This is the result of incorrect processing of operations with the loop device in the assembly system itself.
Some versions of Linux kernels have a delay with these operations, and the BASH script continues without waiting

for the operation to complete. As a result, we see a lot of open loop devices.

 

@Igor

Are further explanations required?

27 minutes ago, going said:

Are further explanations required?

 

I don't know why / when this bug was introduced  but kernel upgrade workarounds it.

37 минут назад, Igor сказал:

I don't know why / when this bug was introduced  but kernel upgrade workarounds it.

Working with loop devices in BASH is similar to opening a file for reading and closing it after completing the operation in the C language.

In the build system, there is a code that remembers the open loop device and there is a code that should delete\close the loop device.
But for some reason this does not happen.
May it be necessary to wait for the operation to complete?
The problem is in the build system.

Perhaps the new kernel is faster?