Kernel panic on booting OMV 6.x running off WD My Cloud Home

  • Hi there,


    There was a power outage two days ago when I wasn't home.

    The NAS is a Western Digital My Cloud Home running Debian 11+OMV 6 as per fox_exe's instructions (followed in 2021). Off the top of my head, it simply used the original Android partitioning and replaced essential bits with Debian's, which was acceptable at the time but by no means a "clean" install.


    Even though the NAS was on a UPS, I believe the cut was long enough to eventually deplete the battery and the NAS suffered a hard shutdown, although there was no active network transfer at the time, which should make things repairable.


    It would repeatedly spin down then up afterwards, along with a typical LED-light pattern and recognized it just failed to boot properly.


    Now I have connected a serial console and can see many issues right before it reboots:

    - Can't find partitions

    - Now unsure why a HDD partition would be formatted as f2fs

    I tried to interrupt boot process, but of course it didn't work as UBoot apparently has it disabled


    How do I repair the partition map, mound sda19 (mounted on /), all without killing sda21, the data partition?

  • An update: I was able to interrupt the booting process from the serial connection. I also found a "Rescue" image from fox_exe, but sadly no instructions are provided. As I don't want to ruin the data, I plugged in an unused 500GiB for the tests.


    The goal is to be able to:

    1. get a functioning and up-to-date OMV installation
    2. without reformatting.

    What I have:

    • FAT32 -formatted USB drive (MBR), loaded with the rescue image
    • FAT32-formatted USB drive (MBR), loaded with the install Debian image
    • LAN connection to the board
    • UART connection to the board
    • 500 GiB scratch HDD. Unknown partitioning.

    Both HDD and USB drive are properly detected by the board. The means I thought it would work would be either:

    • Write initial image from USB drive to HDD, much like most other SBCs boot SD cards are set up, but that wouldn't meet goal #2 OR
    • Recreate partitions and mountpoints without touching data, and somehow (for lack of more refined expertise) write core Debian utilities that will be able to "pull" the necessary software from repositories.


    Already tried:

    From the Realtek> (bootloader) prompt:

    called goru (goru - start rescue linux from usb)

    It starts, then fails when bootloader can't find partition 18 on the HDD


    From the USB drive:

    I get dumped on a BusyBox prompt with only the bare minimum set of tools.


    What should I do next?

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!