I read in Install Debian on WD My Cloud home - #170 by juniornerd "The easiest way is to download OMV from Fox_exe file archive (fox-exe.ru) 13. Extract it to a USB stick (FAT formatted, format with windows, not linux). Then you put that into the USB port and reset. After some Minutes you should be able to access http://wdnas 9 Then you can log in via SSH and follow the guide at Lötzimmer: Debian on WD My Cloud Home single-bay (MCH) - part 1 (loetzimmer.de) 24"
I was able to install Debian 11 and OMV 6.
For your storage problem, I do not have a real good solution. I opened the MCH and put the HD into my computer. I first deleted all partitions starting from sataa20 and created bigger partitions instead.
Hi Alex-N,
Can this be used to modify the partitions? E.g. for changing the partition size?
If you do not open the case and manually repartition the /, /usr and /var partitions you may run into storage problems. It would be good to have a larger / partition instead.
@Alex-N With Debian 11 disk doesn’t stay in sleep mode, it immediately turns on when it goes to sleep. When checking forlder2ram status it shows “/var/log is NOT mounted”. Any idea?
Yeah, it’s already been bugging me…
This is probably due to some systemd change in Bullseye. I am also looking into it. Maybe someone is quicker to uncover the reason behind this behavior.
The quick fix is to delete /var/log/journal which will make the syslog NON-persistent.
The underlying problem is that folder2ram tries to copy some additional ACL which doesn’t work
Yeah, can confirm that deleting it fix mount error. Another thing, does anyone had any connection problem after sending a reboot via ssh? Sometimes needs to be unplugged physically to get back working
By the way, if someone wants to regain the 256 MB of ram lost because of the transcoder reserved memory, you need to edit rtd-129x-ion-1GB.dtsi from the kernel source, in this file are the exact memory reserved in hexadecimal format followed by the amount in numbers ( like this: (0x0b800000) // 184M) I try to erase the "#include “rtd-129x-ion-1GB.dtsi” argument, but then it doesn’t boot, so I change the reserved memory hexadecimal values of the dtsi file to a value of 1024 (1MB), then you just need to compile the kernel and boot it. And if someone with knowledge of programming language want to help, I’m trying to edit the bootloader so we can boot the kernel 4.9 and use for example openwrt and the rtk wrapper for hw media acceleration, but is a slow process because I go with try and error.
It´s wrote on a script called “boottar_gen_monarch.sh”, for the one disk version, and “boottar_gen_pelican.sh” for the 2 disks version. Both use ddr3 1600 mhz, but with different configuration files
I tried different kernel versions as well.
My biggest problem was the network driver and the SATA interface.
Looks like there is some custom code not found in other rtd-1295 boards
We really need to get a more recent kernel. Bullseye’s c-library uses lots of system calls implemented in 4.12 and later.
Maybe i’m wrong, but i believe that the problem it’s the bootloader, in the banana pi w2 you need to change the bootloader to boot openwrt, and the bootloader for android and for openwrt are radically different. I manage to free the the reserved memory, or change the boot device (emmc, sata, usb) editing the dts files of the kernel source, but i never manage to boot another kernel without a kernel panic. And I looked at the sources of terramaster, asustor, qnap and synology nas with the same chipset (only the kernel, they don’t share the bootloader) and the ones with openwrt or a proprietary linux system had a kernel 4.9.119 (or similar), and there was another nas with android (don’t remember which one) that had a kernel similar to ours, 4.1.14 (or something like that). Realtek make the boards and then gives to the manufacturers the software almost complete depending on what they want (android, openwrt or both). So maybe the key for booting a newer kernel is the bootloader. The sources of openwrt for the banana pi w2 had the configuration files (both the kernel and the bootloader) for Monarch, but i own the pelican, so I’m trying to adapt the sources in my free time.
Since we’re using uBoot, it’s the bootloader’s job to locate kernel, dts, rootfs (initrd) and write those into RAM. Then executing the kernel at a given memory address.
I don’t think you’d have to fiddle with the bootloader.
If the kernel crashes either the dts didn’t initialize the hardware correctly or some driver could not be loaded.
I paused my efforts since 4.9 was the latest kernel to be found in OpenWRT. QNAP uses the same as WD. And the syscalls I am looking for are only implement in 4,11+
Maybe the wakeup from RTC would work in 4.9 but that would be a lot of work for little gain.
Great find about the memory btw., I tried but ended up with no change at all or the system not booting.
