balena os configure fails on 3.2.7

Product support
1

Using balena device: raspberrypi4-64
OS version: v3.2.7

Balena CLI: balena-cli-v17.0.0

Trying to configure that image to our fleet fails:
balena os configure balena-raspberrypi4-64-v3.2.7.img --fleet alpha_fleet --debug

[debug] new argv=[/home/ben/balena/balena-cli/balena,/snapshot/balena-cli/bin/balena,os:configure,balena-raspberrypi4-64-v3.2.7.img,–fleet,alpha_fleet] length=6
[debug] Deprecation check: 0.00680 days since last npm registry query for next major version release date.
[debug] Will not query the registry again until at least 7 days have passed.
[debug] Event tracking error: Timeout awaiting ‘response’ for 0ms
? Network Connection ethernet
Configuring operating system image
IO: Input/output error

Error: Input/output error
at Object.IO (/snapshot/balena-cli/node_modules/fatfs/structs.js:251:17)
at /snapshot/balena-cli/node_modules/fatfs/chains.js:122:69
at /snapshot/balena-cli/node_modules/fatfs/vol.js:102:44
at Object. (/snapshot/balena-cli/node_modules/fatfs/chains.js:55:34)
at Immediate._onImmediate (/snapshot/balena-cli/node_modules/fatfs/helpers.js:168:12)
at process.processImmediate (node:internal/timers:471:21)
From previous event:
at /snapshot/balena-cli/node_modules/balena-device-init/build/network.js:125:14
at _finish (/snapshot/balena-cli/node_modules/fifolock/index.js:31:13)
at /snapshot/balena-cli/node_modules/fifolock/index.js:36:20
From previous event:
at /snapshot/balena-cli/node_modules/balena-device-init/build/network.js:117:25
at runInFat (/snapshot/balena-cli/node_modules/balena-image-fs/build/index.js:62:18)
at async tryInteract (/snapshot/balena-cli/node_modules/balena-image-fs/build/index.js:81:16)
at async diskInteract (/snapshot/balena-cli/node_modules/balena-image-fs/build/index.js:109:12)
at async /snapshot/balena-cli/node_modules/balena-image-fs/build/index.js:126:20
at async withOpenFile (/snapshot/balena-cli/node_modules/file-disk/build/index.js:106:16)
at async Object.interact (/snapshot/balena-cli/node_modules/balena-image-fs/build/index.js:124:16)

For further help or support, visit:

2

I would to correct myself -
balena os configure works correctly.

It just fails if i try to configure an image that i have already did balena os configure on.
In this case i need to download the OS image again, and run balena os configure.

3

Hello,
Thanks for reaching out. This happens to me as well sometimes. The second OS configure somehow always fails.
At the moment, I don’t understand why this happens and it’s a known documented error: Running `balena os configure` twice will fail the second time and then a subsequent `balena preload` will also fail · Issue #2487 · balena-io/balena-cli · GitHub
Be sure to document the issue you are facing over for the team to get as much context as possible.

It could be expected even to not configure an already configured image twice but that remains to be investigated.