help recover wrecked OMV 5.x system

1st Official Post

    I had a 9 year old mini ITX system based on Intel and OMV 5.x on ssd and 2 data drives in Raid 1 config. I think the power supply died on the system , so I hired a small local outfit to install a new one for me. They called me back the next day and said they had accidentally fried the motherboard while installing the new power supply. This place did not have my data, but the original OMV5 ssd was still in there, so I think it might be dead as well. But I have not verified this for myself. Fast forward a few weeks and I now have a new Raspberry Pi 5 running OMV 6.x. I managed to connect one of the old Raid 1 data drives using USB 3, and can see now that the USB 3 connected drive is recognized in OMV 6 and in good health.

    I also did the following per the instructions in an earlier post:

    Code
    mdadm --stop /dev/md127

pi@raspberrypi:~ $ sudo mdadm --verbose --assemble --force /dev/md127 /dev/sda
mdadm: looking for devices for /dev/md127
mdadm: /dev/sda is identified as a member of /dev/md127, slot 0.
mdadm: no uptodate device for slot 1 of /dev/md127
mdadm: added /dev/sda to /dev/md127 as 0
mdadm: /dev/md127 has been started with 1 drive (out of 2).

    Now I am seeking advice on how to move forward restoring my data from the old Raid 1 drive to OMV 6? I am afraid I do not have any of the information of the old system as far as file system names or configurations.

    Many thanks!

    Quote from paleraler

    I now have a new Raspberry Pi 5 running OMV 6.x.

    Pi5 only runs on Debian Bookworm so you should be on OMV7 unless you flashed the wrong RaspiOS image.


    Nonetheless, for now, the most important is to sort the RAID issue.

    Since you managed to, at least mount the FS even if degraded, you better make a full copy of the DATA to a secondary drive ASAP.

    OMV doesn't allow USB RAID and you only got away because you ran those CLI commands.


    I only hope that the USB adapter that you are using has it's own power supply.


    Use another drive of the same size or bigger via USB (with it's own power) and copy ALL DATA from the RAID1 drive to the other.

    A simple rsync on the CLI will be enough to do the job.


    After, just make sure that the DATA is intact on the new drive and then you can move from there, cleaning the old RAID drives and use them again on OMV/Pi as single drives. Just not on a RAID type.

    Quote from paleraler

    My bad! It is Sandworm. I followed the install process here

    No worries. At least you are using the proper arm64 img.


    The rest still applies, make sure you can get ALL DATA from that degraded RAID drive ASAP.


    You will hear a lot on this forum that:

    RAID is not a backup.

    OK I will acquire the new drive and get started on the USB rsync asap. My end goal is to use OMV to backup the data to cloud ( backblaze..)


    thanks again.

    • Official Post
    Quote from paleraler

    My bad! It is Sandworm. I followed the install process here

    That doc's specifies "Bullseye" (OMV6) not "Bookworm" (which installs OMV7). That statement has a Warning (in Bold Red).

    In any case, you'll be better off with OMV7 in the long run.

    Can I add a new file system in OMV 7 to a formerly RAID 1 mounted drive without damaging it?


    The new USB 3 drive was recognized without any problem. It showed up as NTFS. I don't know if the old RAID 1 drive file system should be created as ext3 or ext4 ?


    Quote from paleraler

    Can I add a new file system in OMV 7 to a formerly RAID 1 mounted drive without damaging it?

    Sorry but I don't know much about RAID mdadm.


    I'll poke geaves or Krisbee to see if they can give better pointer on how to proceed next.

    The run down is:


    Former RAID1 drive is plugged to the Pi5.

    OP wants to mount it degraded and copy ALL data to a second UDB drive that is already mounted (as NTFS if it matters)


    Known outputs are the one's above on post #7 and #1


    What's next to have the DATA seen and then be able to run a sudo rsync -a /<RAID1 degraded mountpath>/ /srv/dev-disk-by-uuid-34D4AFE2D4AFA498/

    ???

    paleraler


    1. To rsync degraded RAID1 to USB, the USB drive should be formatted as ext4, not ntfs.


    2. If /dev/md127 is currently inactive as shown in #7 above, you need to stop the array and re-assemble it as you did in #1 above.


    3. You then need to see if you can mount the filesystem that is on the degraded RAID1. ( Storage | Filesystems > mount existing )


    4. If the filesystem on /dev/md127 mounts and all files/folders are present & correct, then you can proceed with the rsync.

    These steps all worked beautifully! The only change I made was after executing step #3, I mounted the new USB drive file system which gave me this:

    Code
    pi@raspberrypi:~ $ blkid
/dev/mmcblk0p1: LABEL_FATBOOT="bootfs" LABEL="bootfs" UUID="5DF9-E225" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="def6fa19-01"
/dev/mmcblk0p2: LABEL="rootfs" UUID="3b614a3f-4a65-4480-876a-8a998e01ac9b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="def6fa19-02"
/dev/sda: UUID="b0a10962-c385-b6d2-184e-8e6b187102dc" UUID_SUB="c7fb30e3-6ca8-0db5-13f5-3d8ab1d1a0c3" LABEL="openmediavault:RAID1mirror" TYPE="linux_raid_member"
/dev/sdb1: UUID="79099c68-5444-459d-8420-39a089c55a98" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="77be5746-5101-43a4-b42c-c2ff0f897640"
/dev/md127: LABEL="hamptonFILEZ" UUID="b4c1e1f9-451c-4191-87e0-4fa0372511cb" BLOCK_SIZE="4096" TYPE="ext4"

    then for step #4


    Code
    pi@raspberrypi:~ $ sudo rsync -a /srv/dev-disk-by-uuid-b4c1e1f9-451c-4191-87e0-4fa0372511cb/ /srv/dev-disk-by-uuid-79099c68-5444-459d-8420-39a089c55a98/

    I am currently copying the terabyte of data to the new USB!. This command has been running for 3 hours now, with the USB 3 connected drives. Is this normal?


    Thank you so much! :)

    The rsync ran for over 3 hours while duplicating the data from degraded RAID1 to newly ext4 formatted USB.

    Code
    Then some strange stuff started going on....

rsync: [receiver] chown "/srv/dev-disk-by-uuid-79099c68-5444-459d-8420-39a089c55a98/data/break/DESKTOP-0G6NQ99/Data/C/Users/break/AppData/Local/Microsoft/Windows/Explorer/.thumbcache_1280 (2022_05_23 18_08_30 UTC).db.QuQoQS" failed: Read-only file system (30)
    Code
    rsync: [receiver] mkstemp "/srv/dev-disk-by-uuid-79099c68-5444-459d-8420-39a089c55a98/data/.../DESKTOP-044432/Data/C/.../AppData/Local/Microsoft/Windows/Explorer/NotifyIcon/.Microsoft.Explorer.Notification.{2D246B3B-EBD6-4D58-BD30-68861102ADED} (2020_07_01 00_34_24 UTC).png.FmWTWP" failed: Input/output error (5)
    Code
    *** Skipping any contents from this failed directory ***
rsync: [generator] recv_generator: mkdir "/srv/dev-disk-by-uuid-79099c68-5444-459d-8420-39a089c55a98/virtualbox" failed: Input/output error (5)
*** Skipping any contents from this failed directory ***
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.2.7]

    before the rsync ended. Currently I still have 2 file systems mounted but....rsync does not appear to have completed its job...

    Code
    can I continue rsync command and tell it to ignore errors/bad disk sectors?

pi@raspberrypi:~ $ blkid
/dev/md127: LABEL="FILEZ" UUID="b4c1e1f9-451c-4191-87e0-4fa0372511cb" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdb1: UUID="79099c68-5444-459d-8420-39a089c55a98" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="77be5746-5101-43a4-b42c-c2ff0f897640"
/dev/mmcblk0p1: LABEL_FATBOOT="bootfs" LABEL="bootfs" UUID="5DF9-E225" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="def6fa19-01"
/dev/mmcblk0p2: LABEL="rootfs" UUID="3b614a3f-4a65-4480-876a-8a998e01ac9b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="def6fa19-02"
/dev/sda: UUID="b0a10962-c385-b6d2-184e-8e6b187102dc" UUID_SUB="c7fb30e3-6ca8-0db5-13f5-3d8ab1d1a0c3" LABEL="openmediavault:RAID1mirror" TYPE="linux_raid_member"

Participate now!

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

Register Yourself Login