thanks for your reply one last question
Ubiattach command is not available on DSM version any idea how to get it on DSM
also when i try to mount the ubifs i get the following error
mount: unknown filesystem type ‘ubifs’
is it possible to use this revert method
======== REVERT =========
dd if=/dev/zero of=/dev/mtdblock1
reboot -f
After this WDMC runs in “Rescue” mode. Go to webgui and upload original firmware file (.bin)
Hi Jack
My Box is EX2 not EX2 Ultra
I am not sure if the copy from it will work on your box they have deferent HW
my recommendations is to get the correct image for your Box EX2 Ultra HW Specifications
Thanks again for your help, I really appreciate that.
I have now dd’ed uImage.bin to mtdblock1, uRamdisk.bin to mtdblock2, rootfs.cfs to mtdblock3, and executed the following commands on mtdblock5:
ubiformat on /dev/mtd5, then i have created an ubifs volume with the name config, that fills the whole device, and extracted config.tgz onto it.
Cool. I analyse this file and get some interesting info:
Header contains same data as Firmware file (model code, version, build version, something like CRC32)
And two files: uImage + uRamdisk
If i’m right - we can write this two files in mtd1 and mtd2 and device will boot into recovery (Force recovery mode)
All files and some info here: https://fox-exe.ru/WDMyCloud/WDMyCloud-Mirror-Gen2/Dev/WD-Recovery/
I’ve OMV working flawless, but I would like to change the harddrives for higher capacity. Is there any way to migrate the OS to the new drives? I can replicate the data inside, is not too much.
It is no longer md0, md1, md2 - is this my problem now?
I corrected this by doing
/ # mdadm -S /dev/md126
mdadm: stopped /dev/md126
/ # mdadm --assemble --verbose /dev/md0 /dev/sda1 /dev/sdb1
mdadm: looking for devices for /dev/md0
mdadm: /dev/sda1 is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 1.
mdadm: added /dev/sdb1 to /dev/md0 as 1
mdadm: added /dev/sda1 to /dev/md0 as 0
mdadm: /dev/md0 has been started with 2 drives.
/ # mdadm --assemble --verbose /dev/md1 /dev/sda2 /dev/sdb2
mdadm: looking for devices for /dev/md1
mdadm: /dev/sda2 is identified as a member of /dev/md1, slot 0.
mdadm: /dev/sdb2 is identified as a member of /dev/md1, slot 1.
mdadm: added /dev/sdb2 to /dev/md1 as 1
mdadm: added /dev/sda2 to /dev/md1 as 0
mdadm: /dev/md1 has been started with 2 drives.
but after reboot the device names are changed again.
So I cannot get further:
/ # init 2
# Loading, please wait...
# Mounting filesystems...
mount: mounting sysfs on /sys failed: Device or resource busy
mount: mounting proc on /proc failed: Device or resource busy
# Check disk and init
### Press any key to stop and run shell... (2)mdadm: No arrays found in config file or automatically
# /dev/md1 not exist!
# Runing a shell...
ifup: interface lo already configured
ifup: interface eth0 already configured