Like I said this is the setting I already have.
hey there, I installed on my my cloud home single bay the OMV and I forgot to move my data before to another disk. So do you guys have any instruction how I can get back to the old file system or any other solution so that I can get my data off this nas ?
But I don´t see instructions how to get back to my original firmware
I don’t had the my cloud home so I can’t help you, as I said in the post that you answered. The autor of the link I posted remove their files, as you can also read. You can use a translator and look into this instructions WD My Live\Book\Cloud\Cloud Mirror - 4PDA or ask someone that has your device.
I spend the last days translating all this. As far as I understand it I need to mount this drive into a linux system and use some of the given commands. But at some point they talk about doing this via usb stick but then the files are no longer there and I don´t really get it… 
Has someone managed to install nginx proxy service or any similar reverse proxy on the mycloud home debian or not
jc21/nginx-proxy-manager - Docker Image | Docker Hub
Docker-Compose\Portainer Stack:
version: '3'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '80:80'
- '81:81'
- '443:443'
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
New GPL Source Code 8.6.1-100 / kernel 4.9.266
https://downloads.wdc.com/gpl/GPL_MCH_Monarch_8.6.1-100_20220608.tar.xz
*** Novice Warning ***
I’ve compiled and installed the new kernel (Linux version 4.9.266) on the My Cloud Home single drive. It hangs on boot with the new kernel right after the hard drive is found. Instead of SATA it uses SDA. How do I set this for SATA?
- Serial output no boot, system hangs *
[ 6.218594] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 6.226467] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 6.231957] sd 0:0:0:0: [sda] Write Protect is off
[ 6.236935] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[ 6.298052] sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15 sda16 sda17 sda18 sda19 sda20 sda21 sda22 sda23 sda24
[ 6.315755] sd 0:0:0:0: [sda] Attached SCSI disk
- Serial output works *
[ 3.768841] sd 0:0:0:0: [sataa] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 3.776872] sd 0:0:0:0: [sataa] 4096-byte physical blocks
[ 3.782515] sd 0:0:0:0: [sataa] Write Protect is off
[ 3.787661] sd 0:0:0:0: [sataa] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[ 3.844247] sataa: sataa1 sataa2 sataa3 sataa4 sataa5 sataa6 sataa7 sataa8 sataa9 sataa10 sataa11 sataa12 sataa13 sataa14 sataa15 sataa16 sataa17 sataa18 sataa19 sataa20 sataa21 sataa22 sataa23 sataa24
[ 3.862690] rescan_partitions: add_partition 1
[ 3.867340] add_partition partition name = sataap1
SATAA* is no longer supported in the sources, need change in:
- In parted (default) /dev/sataa4 (ROOT_FS): /dev/sataa20 → /dev/sda20 e.t.c
- Debian fstab: /dev/sataa* → /dev/sda*
- if installed OMV check settings too
Are there many red errors when loading your kernel version? Post your kernel.
Thanks for the info.
- I ran the “parted” utility, I didn’t see anywhere to change the actual device name from sataa to sda.
- fstab - easy to change
During boot around 25 lines like below. I think that is another issue.
rsvmem_remap 143, rmem->name common@0
[ 0.059794] rsvmem_remap 151, type rsvmem-remap
[ 0.065872] rsvmem_remap 163, ioremap(1f000,1000)
[ 0.072153] rsvmem_remap 175, remap addr ffffff800800c000
[ 0.079208] rsvmem_remap 184, save_remap_name common
[ 0.085778] rsvmem_remap 203, save rpc_common_base
[ 0.092150] rsvmem_remap 216, init common@0/common done
dd if=/dev/sataa4 of=/%your path%/04-ROOTFS_B.bin
unzip 04-ROOTFS_B.bin via 7-zip
see rootfs.cpio
this is a modified one, thanks to which Debian is launched.
Look at the original example - /dev/sataa3 (ROOTFS_A) - also extracted as first (2 times 7-Zip ).
The problem is that it is not known what they (WD/Realtek) changed in these sections. Until someone shares a copy of the original firmware of partitions 1-18…
It may be easier to stick with the awful sataa naming for now. Otherwise the initrd has to be changed (and the fstab of course).
Modify linux-4.9.266/drivers/scsi/sd.c line 3160:
error = sd_format_disk_name("sata", index, gd->disk_name, DISK_NAME_LEN);
1 Like
Alex-N - Awesome! Thanks for the info.
RAH-66 - Great background info also.
As for the memory remapping those lines should be expected.
Did you already modify the Kernel config or are you testing with stock?
I keep getting some errors trying to compile a netfilter module.
The only change I made to the config was to remove Watchdog Timer Support - nice catch by the way.
The new kernel boots and appears to run just fine.
I used the latest GPL and compiled the 4.9.266 kernel on the same My Cloud Home that was running RAH-66 Debian 11 install. The kernel need to be refined so it doesn’t use so much memory, now on boot only 736 mb free.
Try to add the following lines to arch/arm64/boot/dts/realtek/rtd129x/rtd-1295-monarch-1GB.dts
/dts-v1/;
#include <dt-bindings/soc/rtd129x,memory.h>
#define ION_AUDIO_HEAP_SIZE (0x00000400) // 1M
#define ION_MEDIA_HEAP_SIZE1 (0x00000400) // 1M
#define ION_MEDIA_HEAP_SIZE2 (0x00000400) // 1M
It should be enough to run make dtbs DTC_FLAGS=“-p 8192” after the change.
I’m actually using xbuild.sh (From the GPL) to build the kernel. I added the lines to rtd-1295-monarch-1GB.dts and ran xbuild.sh again. I’m getting a console full of “systemd-journald[1300]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system” along with “ata1: COMRESET failed (errno=-16) [ 617.798440] ata1: hard resetting link”.
It’s not happy - Changing back for now.
it’s 1 KByte 
HEX 400=1024 Byte DEC
(0x00000400) // 1K
but it’s just a comment that doesn’t matter
I compiled the kernel version 4.9.266, everything works, but there is some kind of catch - Docker works, but Porteiner does not start, as if its standard ports 9000/9433 are blocked in the kernel itself.
