INSTALL ENTWARE ON WD MY CLOUD HOME (SSH ACCESS, NFS SERVER, OPKG install packages)


#21

Hello dr3rmo,

The problem comes from the file: services
the copied text is formatted on the forum.

Like, I can not post the text file.

After each word press the Tab key twice

/opt/etc # cat services

sunrpc (TAB,TAB) 111/tcp (TAB,TAB) portmapper (TAB,TAB) # RPC 4.0 portmapper
sunrpc (TAB,TAB) 111/udp (TAB,TAB) portmapper

restart rcpbind :
/opt/etc/init.d/S19rpcbind restart


#22

UPDATE PART 3

Install an SFTP server with ENTWARE


#23

Thanks It works now


#24

Hello,
It looks like big step forward to make this brick useable, but I haven’t done anything like this before…
So before I start I would like to know if there are any tricky parts?
Are there any risks or disadvantages of this installation?
Pc with Ubuntu is must or it can be done without it somehow? (I have only pc with windows 10)


#25

Linux is a must to mount the volumes even I had OSX and Windows both didn’t work except I used fedora live cd
and it will void your warranty
finally if any problems we here to help
I did it because poor battery with WD Discovery app
now I use It with NAS and no battery drain on OSX
Also I installed torrent client and Rsync Server to create custom backups


#26

Hello, why do I have these problems and how to solve them? Thank you.!
root@monarch32_mini:/ # /system/bin/mount -o rw,remount /
/system/bin/mount -o rw,remount /
root@monarch32_mini:/ # mkdir /opt
mkdir /opt
root@monarch32_mini:/ # /system/bin/mount -o ro,remount /
/system/bin/mount -o ro,remount /
root@monarch32_mini:/ # mkdir /data/entware.arm
mkdir /data/entware.arm
mkdir: ‘/data/entware.arm’: File exists
1|root@monarch32_mini:/ # mount -o bind /data/entware.arm / opt
mount -o bind /data/entware.arm / opt
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|root@monarch32_mini:/ # /system/bin/mount -o bind /data/entware.arm / opt
/system/bin/mount -o bind /data/entware.arm / opt
Usage: /system/bin/mount [-r] [-w] [-o options] [-t type] device directory
1|root@monarch32_mini:/ # ./sbin/busybox -install
./sbin/busybox -install
-install: applet not found
1|root@monarch32_mini:/ # ./sbin/busybox --install /system/xbin
./sbin/busybox --install /system/xbin
busybox: /system/xbin/[: Read-only file system
busybox: /system/xbin/[[: Read-only file system
busybox: /system/xbin/acpid: Read-only file system
busybox: /system/xbin/add-shell: Read-only file system
busybox: /system/xbin/addgroup: Read-only file system
busybox: /system/xbin/adduser: Read-only file system
busybox: /system/xbin/adjtimex: Read-only file system


#27

Hello ansir,

you must remove the space between the slash and opt command:

mount -o bind /data/entware.arm /opt

to install busybox, you have to mount the system partition in RW:

system/bin/mount -o rw,remount /system
./sbin/busybox --install
system/bin/mount -o ro,remount /system

The syntax problem copy paste google translation
Sorry


#28

Thank you for your reply. My command line uses manual input, but there are still the following errors. btw,I wonder if MCH can install resilio sync?


#29

My problem has been solved. The subfolder permissions involved have been changed to read and write. The MCH synchronized folder is located in the /data/data/com. transmissionbt.WD/auth0|xxxxxxx folder. Thank you again.


#30

hi juju thank you for your help, your tutorial will be handy to me for sure, with this done, is there a way for the plex server to be moded to be able to use the folders we want?


#31

Hi ansir,

I have the same problem running the “./sbin/busybox --install”.

C:\Share\platform-tools_r28.0.1-windows\platform-tools>adb connect 192.168.1.99
connected to 192.168.1.99:5555
C:\Share\platform-tools_r28.0.1-windows\platform-tools>adb root
C:\Share\platform-tools_r28.0.1-windows\platform-tools>adb shell
root@monarch32_mini:/ # /system/bin/mount -o rw,remount /
root@monarch32_mini:/ # mkdir /opt
root@monarch32_mini:/ # /system/bin/mount -o ro,remount /
root@monarch32_mini:/ # mkdir /data/entware.arm
mkdir: ‘/data/entware.arm’: File exists
1|root@monarch32_mini:/ # mount -o bind /data/entware.arm /opt
root@monarch32_mini:/ # /system/bin/mount -o rw,remount /system
root@monarch32_mini:/ # ./sbin/busybox --install
busybox: /usr/bin/[: No such file or directory
busybox: /usr/bin/[[: No such file or directory
busybox: /sbin/acpid: Read-only file system
busybox: /usr/sbin/add-shell: No such file or directory
busybox: /usr/sbin/addgroup: No such file or directory
busybox: /usr/sbin/adduser: No such file or directory
busybox: /sbin/adjtimex: Read-only file system
busybox: /sbin/arp: Read-only file system
busybox: /usr/sbin/arping: No such file or directory
busybox: /bin/ash: Read-only file system
busybox: /usr/bin/awk: No such file or directory
busybox: /bin/base64: Read-only file system
busybox: /usr/bin/basename: No such file or directory
busybox: /usr/bin/beep: No such file or directory
busybox: /sbin/blkid: Read-only file system
busybox: /sbin/blockdev: Read-only file system
busybox: /sbin/bootchartd: Read-only file system
busybox: /usr/sbin/brctl: No such file or directory
busybox: /usr/bin/bunzip2: No such file or directory
busybox: /usr/bin/bzcat: No such file or directory
busybox: /usr/bin/bzip2: No such file or directory
busybox: /usr/bin/cal: No such file or directory
busybox: /bin/cat: Read-only file system
busybox: /bin/catv: Read-only file system
busybox: /usr/sbin/chat: No such file or directory
busybox: /bin/chattr: Read-only file system
busybox: /bin/chgrp: Read-only file system
busybox: /bin/chmod: Read-only file system
busybox: /bin/chown: Read-only file system

Could you please advise how to fix it with commands? Or anyone who know please advise.

Thanks.


#32

Hi,
I found several key issues

  1. The system directory is still read-only although root is available
  2. The built-in busybox version of MCH does not seem to work
    So I try.
  3. Download the latest version of busybox
  4. Use the ADB disable-very command
  5. Modified the read-only property of the system directory
    Fortunately, I succeeded. Here are my steps.You can have a try:
  6. Download busybox: https://busybox.net/downloads/binaries/1.28.1-defconfig-multiarch/busybox-armv7l
    And save it as busybox
  7. The order I executed:

adb connect 192.168.2.100
adb root
adb disable-verity
adb reboot
adb connect 192.168.2.100
adb root
adb shell

/system/bin/mount -o rw,remount /
/system/bin/mount -o rw,remount /system
mkdir /opt
mkdir /data/entware.arm
mount -o bind /data/entware.arm /opt

adb push d:/busybox /system/bin

/system/bin/busybox --install /system/bin

unset LD_LIBRARY_PATH
unset LD_PRELOAD
/opt/bin/opkg install dropbear
/opt/sbin/dropbear -p 22 -a

/system/bin/mount -o ro,remount /system
/system/bin/mount -o ro,remount /


#33

Nice job. Do you know by any chance where is the config file for the network? (I’m trying to change some settings for port mapping)


#34

Thanks ansir!

The problem is fixed. Now I am doing the last part of NFS server installation.

Do you know where to mkdir admsysfile02? and what is the IP 10.10.11.156 for?

mkdir admsysfile02
sudo mount -t nfs 10.10.11.156:/data/wd/diskVolume0/samba/share /home/sysadmin/admsysfile02

If I am using Windows, how to test the mount point?


#35

Is this stable ?
Are ppl installing successfully?

It appear OP has stopped responding to posts… Which makes me think there may be issues!?


#36

Yes it’s working. Check ansir post on how to upload new version of busybox.


#37

What would be the best way to take an image/ backup of the disk before we start messing with it.
I assume this would done at the step when it’s connect to Linux before adjusting the build.prop.

I am an Arch Linux user have Windows10 setup too.

Thanks


#38

DD / Acronis Clone Disk should do the job

But you don’t need to worry about that. You can restore the system partition as there is a separate restore partition with the system files. You can restore the system by pressing the reset button for 60 seconds.


#39

Hey guys,

Please help me. I did the first few steps and enabled ADB. I can connect, but when I try to remount the / partition I get:

/system/bin/mount -o rw,remount /
mount: Operation not permitted

I really need this :slight_smile: what am I doing wrong? I double checked that I followed all the steps. I also opened the adb_enable.sh script to see what it’s doing…and it does the same that I did already.

[edit]
I fixed it! I was mounting the wrong partition. There are 2 partitions that have the build.props file. Be sure to have the one that already has ro.debuggable=0 in it! I thought I had to add it :slight_smile:
Thanks for an amazing tutorial.


#40

Yes I said on my post the other partition (sda19 for me) is for system restore. Do not modify that partition.