Trying to salvage data from dead Helios4 nas + Openmediavault

Louis_F · 4. Juni 2022

Hello,

I have been using a Helios 4 raid array with Openmediavault for several years without issue but it died on me yesterday (lightning struck close to our house yesterday).

I thought maybe only the SD card was dead so I flashed a new one but the device still will not boot (full boot log from the serial console in case someone can make something out of it).

From what I could see, the hard drives themselves should be still alive.

Is there a way I could access my raid array on a different system (even just temporarily) ? What kind of system should I put together ?

I built it so long ago and I never touched it since, so I am ashamed to report that I even forgot whether I selected Raid 5, 6 or 10. Will that be an issue ?

Thank you in advance for any help or pointers,

Louis.

Helios 4 boot log:

---

U-Boot SPL 2019.04-armbian (May 30 2020 - 13:48:54 +0200)

High speed PHY - Version: 2.0

Detected Device ID 6828

board SerDes lanes topology details:

| Lane # | Speed | Type |

--------------------------------

| 0 | 6 | SATA0 |

| 1 | 5 | USB3 HOST0 |

| 2 | 6 | SATA1 |

| 3 | 6 | SATA3 |

| 4 | 6 | SATA2 |

| 5 | 5 | USB3 HOST1 |

--------------------------------

High speed PHY - Ended Successfully

mv_ddr: mv_ddr-armada-18.09.2

DDR3 Training Sequence - Switching XBAR Window to FastPath Window

DDR Training Sequence - Start scrubbing

DDR3 Training Sequence - End scrubbing

mv_ddr: completed successfully

Trying to boot from MMC1

U-Boot 2019.04-armbian (May 30 2020 - 13:48:54 +0200)

SoC: MV88F6828-A0 at 1600 MHz

DRAM: 2 GiB (800 MHz, 32-bit, ECC enabled)

MMC: mv_sdh: 0

Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **

Model: Helios4

Board: Helios4

SCSI: MVEBU SATA INIT

Target spinup took 0 ms.

AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode

flags: 64bit ncq led only pmp fbss pio slum part sxs

Net:

Warning: ethernet@70000 (eth1) using random MAC address - 5e:2a:fa:ee:8e:36

eth1: ethernet@70000

Hit any key to stop autoboot: 0

switch to partitions #0, OK

mmc0 is current device

Scanning mmc 0:1...

Found U-Boot script /boot/boot.scr

2967 bytes read in 209 ms (13.7 KiB/s)

## Executing script at 03000000

Boot script loaded from mmc

158 bytes read in 169 ms (0 Bytes/s)

26333 bytes read in 469 ms (54.7 KiB/s)

9052983 bytes read in 1761 ms (4.9 MiB/s)

6165728 bytes read in 1306 ms (4.5 MiB/s)

## Loading init Ramdisk from Legacy Image at 02880000 ...

Image Name: uInitrd

Created: 2020-05-30 19:42:35 UTC

Image Type: ARM Linux RAMDisk Image (gzip compressed)

Data Size: 9052919 Bytes = 8.6 MiB

Load Address: 00000000

Entry Point: 00000000

Verifying Checksum ... OK

## Flattened Device Tree blob at 02040000

Booting using the fdt blob at 0x2040000

Loading Ramdisk to 0f75d000, end 0ffff2f7 ... OK

ERROR: reserving fdt memory region failed (addr=2040000 size=6c000)

Loading Device Tree to 0f6ee000, end 0f75cfff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Loading, please wait...

Starting version 241

Begin: Loading essential drivers ... done.

Begin: Running /scripts/init-premount ... done.

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.

Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems

done.

Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: Found some drive for an array that is already active: /dev/md/helios4:LostArk

mdadm: giving up.