Controller Nimble AF40 reboot loop and cannot join arrray.

[phuongnv]

Controller Nimble AF40 reboot loop and cannot join arrray.

decriptions: Controller A reboot loop and cannot join arrray.

please help to troubleshooting ,bellow the log when booting

"md_d10: ro 0 raid10 0 bitmap 1

Setting up memory for system partition quick-rebuild

Starting system partition quick-rebuild on md_d10

md_d12: ro 0 raid10 0 bitmap 1

Starting system partition quick-rebuild on md_d12

md_d14: ro 0 raid10 1 bitmap 1

md_d16: ro 0 raid10 0 bitmap 1

Starting system partition quick-rebuild on md_d16

Enabling first expansion shelf phys: 0 1 2 3

Enabling first expansion shelf phys on right port: 36 37 38 39

sleeping for 10 seconds to discover ES expanders

Check for required controller specific firmware upgrades...

//tmp/fud.sh: line 203: echo: write error: No space left on device

//tmp/fud.sh: line 204: echo: write error: No space left on device

cat: write error: No space left on device

cat: write error: No space left on device

//tmp/fud.sh: line 203: echo: write error: No space left on device

//tmp/fud.sh: line 204: echo: write error: No space left on device

cat: write error: No space left on device

//tmp/fud.sh: line 203: echo: write error: No space left on device

//tmp/fud.sh: line 204: echo: write error: No space left on device

cat: write error: No space left on device

//tmp/fud.sh: line 203: echo: write error: No space left on device

//tmp/fud.sh: line 204: echo: write error: No space left on device

cat: write error: No space left on device

//tmp/fud.sh: line 203: echo: write error: No space left on device

//tmp/fud.sh: line 204: echo: write error: No space left on device

cat: write error: No space left on device

//tmp/fud.sh: line 203: echo: write error: No space left on device

//tmp/fud.sh: line 204: echo: write error: No space left on device

cat: write error: No space left on device

Verifying Intel BIOS settings

WARNING: Skipping Intel BIOS settings restore (previous restore failed)

Verifying PCI slot speeds"

[buzzsubash]

Hi, we need root access to the system to see which file system is full, the logs are complaining about "No space left on device".

Please do create a support ticket referencing array serial number

[controles]

Hi,

Based on the logs, the key issue here seems to be:

"No space left on device"

This typically indicates that an internal filesystem (often related to system partitions or logs) is full, which can prevent normal boot processes and lead to a reboot loop.

A few things to consider:

1. Internal filesystem saturation
During boot, the system is attempting operations (fud.sh, rebuild processes), but fails due to lack of space. This can block firmware checks or system services.

2. System partition rebuild behavior
The md_d10/md_d12/md_d16 rebuild messages suggest the system is trying to recover internal RAID partitions. If space is exhausted, these processes may not complete properly.

3. Possible causes
- Excessive log accumulation
- Incomplete upgrade or firmware process
- Corruption or abnormal growth in system partitions

4. Next steps
As mentioned, opening a support case is the right approach, since root-level access is required.

However, if console/root access is available, it may be useful to:
- Check filesystem usage (df -h)
- Identify large files under /var or tmp
- Review if any upgrade or patch process was interrupted

In similar cases, cleanup or repair of internal partitions was required, which is typically handled by HPE support.

Regards,
Carlos Parra Solano
HPE Master ASE Storage