Data rebuild stuck with second drive failing on dual parity

[tazman]

Hi,

 

My disk 15 got disabled, so I  started a rebuild. The rebuild is stuck at 1.8% and does not progress. Probably at the same time, disk 12 got write errors and also got disabled.

 

I tried to pause, then cancel the rebuild to use another drive to rebuild to, but the commands do not do anything.

 

The GUI is responsive but the CPU Meter on Dashboard does not repaint. The log does not show anything new since 45min. With the following two errors at the end:

 

Jun  1 15:46:40 SS emhttpd: error: hotplug_devices, 1709: No such file or directory (2): tagged device WDC_WD40EFAX-68JH4N1_WD-WX22DC1RNJP0 was (sds) is now (sdah)
...
Jun  1 15:46:40 SS kernel: emhttpd[9837]: segfault at 67c ip 0000000000418359 sp 00007fff0d396560 error 4 in emhttpd[404000+1a4000] likely on CPU 3 (core 1, socket 0)

 

Disk 12 is NJP0 mentioned in the first error. 

 

Diags attached. 

 

What do you advise?

 

Wait? Reboot and retry?

 

Thanks!

 

Tomss-diagnostics-20240601-1625.zip

[JorgeB]

emhttp segfaulted, type reboot in the CLI, if it doesn't reboot after 5 minutes you will need to force it, then post new diags after array start.

[tazman]

I rebooted. No events logged in the bios, memtest passed.

 

The first rebuild completed at the usual speeds. The second is running now.

 

Another dual failure hopefully averted. I have 22 data disks which is stretching it.

 

I am really waiting for the multiple-arrays to be ready in Unraid 7. 

[tazman]

4 minutes ago, JorgeB said:

emhttp

Thanks, so is the assumption that the segfault destabilized the system, causing the write error on the second drive and the stalling of the rebuild?

 

So it's basically bad luck?

[JorgeB]

42 minutes ago, tazman said:

Thanks, so is the assumption that the segfault destabilized the system

Not really destabilized, but after the that the GUI commands won't work, so you need to reboot.

[tazman]

17 minutes ago, JorgeB said:

Not really destabilized, but after the that the GUI commands won't work, so you need to reboot.

Thanks, JorgeB!