- All data removed due situation with Ukraine -
Does sanctions vs Russia works? Nope. Its like my “sanctions” vs whole world - it is worked? No, but who cares?
I installed OMV with Bullseye on my WD My Cloud Ex2 device.
I prepared a guide.
There is no need to flash the native UBoot; you can load the new kernel on demand or by default keeping the original fw as it is, for safety and rollback procedure.
Guide and repository is on github /gisab WDMC-Ex2
In reply to @Fox_exe 's first post: People are very judgemental these days. I don’t hate you. I live in a country where my government embarrasses me all the time too. It’s not your fault. Don’t let hate people make you bad.
No, please don’t say that.
You shouldn’t be pessimistic.
I just created an account on this site when I was just browsing for possible future things that I’d buy, and found your post and I got really sad.
Although personally I am 100% against any kind of military operation, it is never on countries or people in it. We can only blame the leader who makes a bad decision but not the people.
Please cheer up and just remember that your part in the community is really important and valuable and a lot of people (might) depend on you.
Clean Debian Install && OMV 3 Install
Firstly open the WD My Cloud box and unplug the HardDrive from the main board and then connect it to a linux computer.
Run parted on the WD drive
Remove all partitions on the drive (DATA LOSS)
rm 1 rm 2 rm 3 rm 4 rm 5 rm 6 rm 7 rm 8
Recreate all needed partitions
mklabel gpt mkpart primary 528M 2576M mkpart primary 2576M 4624M mkpart primary 16M 528M mkpart primary 4828M 100% mkpart primary 4624M 4724M mkpart primary 4724M 4824M mkpart primary 4824M 4826M mkpart primary 4826M 4828M set 1 raid on set 2 raid on
Format data partition
Note: -O ^metadata_csum is needed since new versions of mkfs insert this feature, wich its not supported on older systems.
mkfs -t ext4 -O ^metadata_csum /dev/sd*4
Create swap partition
Mound raid partions
mdadm --stop /dev/md* mdadm -A /dev/md0 /dev/sd*1 /dev/sd*2
Mound data partitions
mount -t ext4 /dev/sd*4 /mnt cd /mnt
Download the Clean Debian package and extract it
wget https://github.com/abskmj/wd-mycloud-gen1/releases/download/packages/clean-debian-jessie.tgz tar zxvf clean-debian-jessie.tgz
Copy images to partitions
dd if=kernel.img of=/dev/sd*5 dd if=kernel.img of=/dev/sd*6 dd if=config.img of=/dev/sd*7 dd if=config.img of=/dev/sd*8 dd if=rootfs.img of=/dev/md0
Reconnect WD drive to My Cloud board. Power it on and connect a LAN cable
Connect to it with:
The default password for the root user is
First change root password with
passwd and follow the prompt
Remove all lines in sources.list with
and paste this inside
deb http://ftp.us.debian.org/debian/ jessie main contrib non-free deb-src http://ftp.us.debian.org/debian/ jessie main contrib non-free deb http://packages.openmediavault.org/public erasmus main
Run the following commands. Ignore the warnings.
apt-get update apt-get install --force-yes openmediavault-keyring apt-get update apt-get upgrade apt-get install openmediavault
At the mdadm prompt choose none and leave the rest as is.
Finish the install with this command
Now we need to label the data partition, since OMV uses labels to identify storage devices.
e2label /dev/sd*4 DATA
Reboot the system
Once the system is up and running you can login to the web interface at port 80 with the credentials
openmediavault as password
Go to System > General Settings > Web Administrator Password and change the admin password
Now go to Storage > File Systems and check that the data partition (/dev/sd*4) has the previously given label.
If everything is all right we can move on to the creation of a Shared Folder and a new User under Access Rights Management.
Lastly choose your preferred protocol between the ones available and enjoi your newly updated NAS.
When I mount raid partitions appears:
superblock on /dev/sda2 doesn't match others - assembly aborted
OK, I dealt with it:
mdadm --assemble /dev/md0 /dev/sda1 mdadm --add /dev/md0 /dev/sda2
But unfortunately I can’t connect to board via SSH - no route to host. The led on the board is yellow, not blinking
Is this a way to go back to the old system when I already installed omv ?
Do I need to install anything after installation to connect via SSH? I did everything according to these instructions, but the device is not visible in the network, I cannot connect via SSH, the LED is green.
I have an error after installation of OMV:
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
/usr/sbin/omv-initsystem: 24: .: Can’t open /etc/default/openmediavault
Is it possible to install OMV or DSM on my cloud EX2 Ultra if so how do i do it?
I had same issue. Just change your hostname (in /etc/hosts and /etc/hostname), reboot and rerun apt-get upgrade. That solved my problem
@Fox_exe your post was a big help…more than once in rescuing my nas…and I am sure there were hundreds of others like me…maybe thousands…you responded on our comments when we needed help…and even that you have deleted your files now…I would still say many many thanks for being such a kind person…and rest all…is ugly politics!!
Thank you for this guide! I followed this 100% multiple times from a dedicated nix laptop and a VM and once everything was done I could not connect to the drive via SSH no matter what. I actually just went through the “unbricking” process and it’s up and running again. Really hoping I can get this working but not sure what else to try. LED was solid white and nothing else.
which kernel version would this be running on?