Debian on WD MyCloud EX2 Ultra

dtd,

Quote

Flashing by using "dd" in linux or "nand write" in u-boot doesn't matter. The key is you need to overwrite "bootcmd", because with stock uboot it always boots at 0xa00000 0xf00000 <<< and kernel 5.5.3 doesn't work with these 2 addresses.

Don't use dd to flash binary to NAND flash. nand write should be used whether in u-boot or in Debian. For NAND, dd most the time it is OK, but use nand write any way to be foolproof. For SPI flash, never to use dd in Linux, must use flashcp.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Quote
bodhi
Don't use dd to flash binary to NAND flash. nand write should be used whether in u-boot or in Debian. For NAND, dd most the time it is OK, but use nand write any way to be foolproof. For SPI flash, never to use dd in Linux, must use flashcp.

Thanks for your useful information.

Thank you very much, @dtd, I understood it now. I flashed the u-boot and I can now boot fine. Great.

So now I have Kernel v5.5.3 in NAND and Busybox 1.31 in NAND too. WIth a simple init script lke:

#!/bin/busybox ash
# init-script for WD Mycloud Mirror gen2 & Ex2 ultra
# Boots from partition labeled "rootfs"

/bin/busybox mkdir -p /dev /mnt/root /mnt/key /mnt/config /mnt/config/initrd /proc /root /usr/sbin /usr/bin /sbin /bin /sys /run
/bin/busybox --install -s

export PATH=/bin:/sbin:/usr/bin:/usr/sbin

# Mount the /proc and /sys filesystems.
mount -t proc none /proc
mount -t sysfs none /sys
mount -t devtmpfs none /dev

# Adding mdev support
echo /sbin/mdev >/proc/sys/kernel/hotplug
mdev -s

exec 0</dev/console
exec 1>/dev/console
exec 2>/dev/console
exec setsid cttyhack /bin/ash

I can boot and get to the console.

My final target is to add cryptsetup to the Ramdisk so I can decrypt HDD raid and then switch over to boot debian from HDD:

cryptsetup luksOpen $cryptdev cryptroot --key-file luks.key

umount /mnt/config 2> /dev/null
umount /sys 2> /dev/null
umount /proc 2> /dev/null
umount /dev/pts 2> /dev/null
umount /dev 2> /dev/null
exec switch_root -c /dev/console /mnt/root /sbin/init

But I got stuck on getting the network up with DHCP. Does anyone has an init file with network properly working?

I saw this at @CyberPK post to get the mac address:

hexdump  -C -s 0x02000000 -n 18 -v /dev/mem

But I didn't get any far than that.

Ok, I have compiled cryptsetup and Glibc for it and got over 15 Mb, So I will have to put Initrd to USB and boot from USB. So I would like to ask a question. Is it possible to boot kernel from nand and Initrd from USB?

At the end of Initrd I'm going to use switch_root to Debian on HDD. So after booting Debian I will be able to remove my USB drive from NAS and still have rootfs running.

I have now made Initrd less than 5Mb to fit it to NAND. It is Busybox + Cryptsetup binaries and libraries it depends on.

I'm now really thinking on advice of CyberPK to get rid of LVM and Ext4

Quote
About using BTRFS:
It should be BTRFS over LUKS directly, managing both volumes and raid instead of EXT4 over LUKS over RAID.
Also take a moment to understand what is better between LUKS over RAID or RAID over LUKS.

I see that btrfs is better plus I can get rid of mdadm and lvm packages to reduce the size of my Initrd.

I understood I need to create Raid1, mount btrfs filestystem, open my LUKS container on HDD. Then I need to part it (40Gb for root, 512Mb for swap and the rest for home/data). Is that something like this?

mkfs.btrfs /dev/sda /dev/sdb -d raid1 -m raid1 -L raid1_drive
cryptsetup luksFormat /dev/sda
cryptsetup open /dev/sda cryptlvm
btrfs device add /dev/mapper/cryptlvm /mnt/root
btrfs device remove /dev/sda /mnt/tmp

Edited 1 time(s). Last edit at 04/13/2020 07:03AM by vzhilov.

encrypt drive 1
encrypt drive 2

open both drive

create brtfs partition in raid mode on the opened device.

Or, if you can't initialize both drive at once, create brtfs on one drive, then convert to raid.

Cant you share your initrd?

Quote
Cant you share your initrd?

Hello! Yes, sure. Couldn't upload 5Mb, but here is the link

This Initrd is a kind of a layer that add cryptsetup before the main rootfs will be loaded. It is still on LVM though. It takes partition from /dev/md0, unencrypts its and boots from there. Can be ajusted for unencrypted partitions too. For example we could put bodhi rootfs on HDD and boot this through Kernel (NAND) -> Initrd (NAND) -> bodhi rootfs (HDD).

Hi vzhilov,

your work is interesting. Could you tell me the average Read/Write speed when LUKS is used (e.g. with scp, ftp). Many thanks.

CyberPK,

Quote
In order to offload disk encryption on the CESA unit, you will need to specify to cryptsetup the following cipher: aes-cbc-essiv:sha256. Therefore the command to create your encrypted disk should looked as follow:
sudo cryptsetup -v -y -c aes-cbc-essiv:sha256 luksFormat /dev/sda1

You can verify running
cryptsetup benchmark

I had to re-build the kernel as it was missing crypto modules. And now I can finally do the benchmark. Here is what I got:

user # cryptsetup benchmark
• Tests are approximate using memory only (no storage I0). 
PBKDF2—shal        215224  iterations  per second  for 256—bit key 
PBKDF2—sha256      317365  iterations  per second  for 256—bit key 
PBKDF2—sha512      150311  iterations  per second  for 256—bit key 
PBKDF2—ripemd160   161022  iterations  per second  for 256—bit key 
PBKDF2—whirlpool    23744  iterations  per second  for 256—bit key 
argon2i        4 iterations, 83132 memory, 4 parallel threads (CPUs) for 256—bit key (requested 2000 ms time)
argon2id      4 iterations, 87954 memory, 4 parallel threads (CPUs) for 256—bit key (requested 2000 ms time)
•     Algorithm  1        Key  1      Encryption   1      Decryption 
        aes—cbc          128b         83.1 MiB/s          85.1 MiB/s 
    serpent—cbc          128b                N/A                 N/A 
    twofish—cbc          128b                N/A                 N/A 
        aes—cbc          256b         76.4 MiB/s          78.2 MiB/s 
    serpent—cbc          256b                N/A                 N/A 
    twofish—cbc          256b                N/A                 N/A 
        aes—xts          256b         62.2 MiB/s          63.3 MiB/s 
    serpent—xts          256b                N/A                 N/A 
    twofish—xts          256b                N/A                 N/A 
        aes—xts          512b         58.4 MiB/s          59.5 MiB/s 
    serpent—xts          512b                N/A                 N/A 
    twofish—xts          512b                N/A                 N/A

I wanted to use sha512. I guess I will not lose a lot of security by switching to sha256 but I will gain some speed.

And you are right, aes-cbc is about 10% faster than xts. So instead of that:

cryptsetup -v --type luks --cipher aes-xts-plain64 --key-size 512 --hash sha512 \ 
--iter-time 2000 --use-random --verify-passphrase luksFormat /dev/md0

I probably should do:

cryptsetup -v --type luks --cipher aes-cbc-essiv --key-size 256 --hash sha256 \
--iter-time 2000 --use-random --verify-passphrase luksFormat /dev/md0

Edited 2 time(s). Last edit at 04/15/2020 02:55PM by vzhilov.

Quote
Could you tell me the average Read/Write speed when LUKS is used (e.g. with scp, ftp).

Before I settled on encryption algorythm I have tftp. Once I settled I was thinking to use samba to transfer all files from my old storage.

For now I'm a bit stuck on making rootfs.

When I do:

debbootstrap --arm=armhf --include=net-tools buster rootfs
chroot rootfs
passwd

I get "Cannot determine your user name. On whoami I get "Cannot find name for user ID 0"

vzhilov,

> For now I'm a bit stuck on making rootfs.

You can just use the rootfs Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 here:

https://forum.doozan.com/read.php?2,32146

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

Quote
linux-image-5.5.3-mvebu-tld-1_1.0_armhf.deb
linux-headers-5.5.3-mvebu-tld-1_1.0_armhf.deb
zImage-5.5.3-mvebu-tld-1
config-5.5.3-mvebu-tld-1
linux-dtb-5.5.3-mvebu-tld-1.tar
linux-5.5.3-mvebu-tld-1.patch

Which one of these is the rootfs? I checked all of them, I see config and DTS files, patch for U-Boot, Kernel, Kernel modules in libs but I can't find the actuall rootfs structure. With my setup I have to have it unpacked (as usual linux folders like /bin, /var /proc /etc) on HDD or USB drive

vzhilov,

>

Quote
linux-image-5.5.3-mvebu-tld-1_1.0_armhf.deb
> linux-headers-5.5.3-mvebu-tld-1_1.0_armhf.deb
> zImage-5.5.3-mvebu-tld-1
> config-5.5.3-mvebu-tld-1
> linux-dtb-5.5.3-mvebu-tld-1.tar
> linux-5.5.3-mvebu-tld-1.patch
>
>

>
> Which one of these is the rootfs?

None of them is. They are kernel files, config, and patch.

The rootfs is mentioned in the release thread:

https://forum.doozan.com/read.php?2,32146

Quote

Latest released rootfs: Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 (10 Sep 2019)

Quote

Note: If this is your first time installation, then you need rootfs Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 (this has kernel 5.2.9-mvebu-tld-1 already installed). Please scroll down to the 10 Sep 2019 section to install this rootfs. After you've booted the box with this rootfs, you can proceed to install the latest kernel.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 04/16/2020 04:34AM by bodhi.

dtd,

I compiled the kernel without marvell_cesa module (option M) just to compare software encrytption vs builtin harware encryption. First I run benchmark without this module, then I add this and run benchmark again. The difference is actually 100%. Here are the results:

/ # cryptsetup benchmark
  # Tests are approximate using memory only (no storage I0).
PBKDF2—shal       215578  iterations per  second for 256—bit key 
PBKDF2—sha256     316217  iterations per  second for 256—bit key 
PBKDF2—sha512     150657  iterations per  second for 256—bit key 
PBKDF2—ripemd160  161022  iterations per  second for 256—bit key 
PBKDF2—whirlpool    23710 iterations per  second for 256—bit key
argon2i       4 iterations,  84084 memory, 4 parallel threads (CPUs) for 256—bit key (requested 2000 ms time) 
argon2id      4 iterations,  89275 memory, 4 parallel threads (CPUs) for 256—bit key (requested 2000 ms time) 
#     Algorithm  1       Key 1      Encryption   1     Decryption
        aes—cbc         128b        31.8 MiB/s         33.4 MiB/s
    serpent—cbc         128b                N/A               N/A
    twofish—cbc         128b                N/A               N/A
        aes—cbc         256b        25.3 MiB/s         26.6 MiB/s
    serpent—cbc         256b                N/A               N/A
    twofish—cbc         256b                N/A               N/A
        aes—xts         256b        31.5 MiB/s         31.7 MiB/s
    serpent—xts         256b                N/A               N/A
    twofish—xts         256b                N/A               N/A
        aes—xts         512b        25.8 MiB/s         25.5 MiB/s
    serpent—xts         512b                N/A               N/A
    twofish—xts         512b                N/A               N/A
/ # modprobe marvell_cesa
[ 440.149497][ T6276] marvell—cesa f1090000.crypto: CESA device successfully registered
/ # cryptsetup benchmark
  # Tests are approximate using memory only (no storage I0).
PBKDF2—shal       217727  iterations per  second for 256—bit key 
PBKDF2—sha256     313569  iterations per  second for 256—bit key 
PBKDF2—sha512     151004  iterations per  second for 256—bit key 
PBKDF2—ripemd160  161418  iterations per  second for 256—bit key 
PBKDF2—whirlpool    23744 iterations per  second for 256—bit key
argon2i       4 iterations, 85714 memory, 4 parallel threads (CPUs) for 256—bit key (requested 2000 ms time)
argon2id      4 iterations, 88399 memory, 4 parallel threads (CPUs) for 256—bit key (requested 2000 ms time)
#     Algorithm  1       Key 1      Encryption   1     Decryption 
        aes—cbc         128b        83.3 MiB/s         85.1 MiB/s 
    serpent—cbc         128b                N/A               N/A 
    twofish—cbc         128b                N/A               N/A 
        aes—cbc         256b        76.6 MiB/s         78.3 MiB/s 
    serpent—cbc         256b                N/A               N/A 
    twofish—cbc         256b                N/A               N/A 
        aes—xts         256b        59.5 MiB/s         63.4 MiB/s 
    serpent—xts         256b                N/A               N/A 
    twofish—xts         256b                N/A               N/A 
        aes—xts         512b        58.4 MiB/s         59.3 MiB/s 
    serpent—xts         512b                N/A               N/A 
    twofish—xts         512b                N/A               N/A

bodhi,

I love your rootfs. Thank you for the great work! It also works perfectly with my setup!

I guess I have completed my work and can write a repot.

I use bodhi kernel. It is in /dev/mtdblock1. I changed it slightly so it fits 5Mb lilmit. I took some media, TV, radio modules out. This is my kernel config and my final uImage based on bodhi kernel.

Then my Initrd is Busybox + updated version of cryptsetup. At the end of boot process I made a little dialog where user can choose futher boot options.

1. If you are like me having /dev/md0 LUKS-encrypted logical volume /dev/MyVolGroup/root with bodhi rootfs inside, then press (1). The system will check for avaliable key file on attached USB drive or in the local network and boot bodi rootfs from that encrypted device.
2. If you have your system unencrypted and simply copied bodhi rootfs on ext3/ext4 HDD or flash drive, just press (2) and specify path to the rootfs device (i.e. /dev/md0, /dev/sdb1 etc).

If something goes wrong it drops to Busybox shell.

You need to have access to shell through UART. There is no other option. By default it boots fron encrypted drive (option 1).

My Initrd with the above is less than 5Mb so it fits to /dev/mtdblock2.

So my booting sequence is: Kernel booting (NAND) -> BusyBox booting (NAND) -> bodhi rootfs. That helps me to add additional encryption layer or do any other operations with devices and volumes before I boot the rootfs.



Edited 2 time(s). Last edit at 04/17/2020 06:01AM by vzhilov.

...message deleted...



Edited 3 time(s). Last edit at 04/19/2020 03:34PM by vzhilov.

vzhilov,

Cool! thanks for the report! glad it finally works well for you. Especially the LUKS-encrypted volume, it will be a good example for others looking for this.

If you could, edit your post to list the u-boot envs changes (permanently or on the fly during booting). Please make it a more detailed procedure so I can add to the Wiki.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

Quote
If you could, edit your post to list the u-boot envs changes (permanently or on the fly during booting). Please make it a more detailed procedure so I can add to the Wiki.

yes, I will do that.


CyperPK,

I think I use your .DTS file #2, the one that handles blue and red led lights with rc.local. But I get:

~ # echo gpio       > /sys/class/leds/wdmcex2u\:blue\:hdd1/trigger
~ # echo gpio       > /sys/class/leds/wdmcex2u\:blue\:hdd2/trigger
~ # echo 1       > /sys/class/leds/wdmcex2u\:blue\:hdd1/inverted  //Here 1st blue ligh goes off
~ # echo 1       > /sys/class/leds/wdmcex2u\:blue\:hdd2/inverted  //Here 2nd blue ligh goes off
~ # echo ide-disk1       > /sys/class/leds/wdmcex2u\:red\:hdd1/trigger
sh: write error: Invalid argument
~ # echo ide-disk1       > /sys/class/leds/wdmcex2u\:red\:hdd1/trigger
sh: write error: Invalid argument

You are missing the kernel patch from bodhi to handle the additional ide-disk1 & ide-disk2
Read my post, there you will find also the relevant patches to manage the poweroff and reboot

CyberPK,

Quote
1) done with the attached patch and "1 -" DTSs. Tested working;
2) done with the attached "2 -" DTSs and rc.local. Tested Working;\

is that gpio_trigger.patch? I thought it only works with DTS file #2 (the one I have). And then I see bodhi later says - use point 2, it is better.

Quote
2nd is a better approach than 1st . Because while 1st is easier, but adding 2 more triggers just for this seems too "cookie cutter" and overkill.

The patch from point 1 still needed for that?

I didn't find patch for poweroff, or is that the same one?

To apply:

cd linux-stable
patch -p1 < gpio_trigger.patch

?



Edited 2 time(s). Last edit at 04/20/2020 12:22PM by vzhilov.

And just another question. When I turn NAS on, the fan keeps running loudly. When I boot it does not go away. Where it is controlled?

Ok, I have handled the LEDs and fan speed with scripts I got from fox-exe. Compile mcu_ctl from the attached file:

apt install build-essential
cc mcu_test.c -o mcu_ctl
cp mcu_ctl usr/sbin/

Then put below to your rc.local file:

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.

# Available triggers:
# none bluetooth-power usb-gadget usb-host timer oneshot disk-activity ide-disk mtd nand-disk heartbeat gpio cpu cpu0 cpu1 default-on panic

if [ -e /usr/sbin/mcu_ctl ]; then
    /usr/sbin/mcu_ctl sys_ready 2>&1 >/dev/null
fi
if [ -e /sys/class/leds/wdmcex2u\:blue\:hdd1/trigger ]; then
    echo gpio > /sys/class/leds/wdmcex2u\:blue\:hdd1/trigger
    echo 48 >  /sys/class/leds/wdmcex2u\:blue\:hdd1/gpio
fi
if [ -e /sys/class/leds/wdmcex2u\:blue\:hdd2/trigger ]; then
    echo gpio > /sys/class/leds/wdmcex2u\:blue\:hdd2/trigger
    echo 58 > /sys/class/leds/wdmcex2u\:blue\:hdd2/gpio
fi
if [ -e /sys/class/leds/wdmcex2u\:red\:hdd1/trigger ]; then
    echo disk-activity > /sys/class/leds/wdmcex2u\:red\:hdd1/trigger
fi
if [ -e /sys/class/leds/wdmcex2u\:red\:hdd2/trigger ]; then
    echo panic > /sys/class/leds/wdmcex2u\:red\:hdd2/trigger
fi
exit 0

It seems like with the fan turned off the temperature lower, look like the fat creates more heat than cold :)

If you would like to monitor your temperature run simple script:

#/bin/bash

echo -en "TIME\t\tCPU\tSYS\tHDD\n"
while true; do
        echo -en `date +'%H:%M:%S'` "\t"
        echo -en $((`cat /sys/class/thermal/thermal_zone0/temp` / 1000)) "\t"
        echo -en `mcu_ctl tmp_get_c | awk '{print $2}'` "\t"
        echo -en `smartctl -A /dev/sda | awk '/Temperature_Celsius/{print $10}'` "\n"
        sleep 2
done

Edited 2 time(s). Last edit at 04/21/2020 08:15AM by vzhilov.

Maybe someone can help me on LEDs. WIth the above settings the power led stops flashing when rootfs boots. And Frist HDD led blinking red showing disk activity. This is good enough.

When I run `poweroff` command on rootfs all proccesses get stopped and I get "System halted" in the console. But LEDs does not reflect this anyhow, all of them stay blue. The only difference that red light stop blinking. So without the console I can not clearly say when the system is halted.

I would like second HDD led to indicate that system is halted. RIght now I have that LED set to indicate panic.

Here are the options I have:

root@localhost:~# cat /sys/class/leds/wdmcex2u\:blue\:hdd2/trigger
none usb-gadget usb-host rc-feedback kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport timer oneshot disk-activity disk-read disk-write ide-disk mtd nand-disk heartbeat [gpio] default-on flash torch panic f1072004.mdio-mii:00:link f1072004.mdio-mii:00:1Gbps f1072004.mdio-mii:00:100Mbps f1072004.mdio-mii:00:10Mbps

Is there any of those I need to `echo` to second LED to have that?

vzhilov,

> Is there any of those I need to `echo` to second
> LED to have that?

See which one is used from this list,

ls -l /sys/class/leds/wdmcex2u*

And, turn off in /etc/init.d/halt. For example,

echo none > /sys/class/leds/wdmcex2u\:blue\:hdd2/trigger

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thank you very much, bodhi! Great solution.

Just another question. I'm putting my Ex2 Ultra device onto work now. WIth syncing raid to second HDD and in the same time `rsync` data from old disk storage I get CPU temerature up to 70-75 celcius. I can manually set fan to 75% of speed with my `mcu_ctl fan_set_75` but that doesn't seem to help a lot, maybe it gets 1-2 degrees lower. Is that normat CPU temperature for such a device?

root@localhost:~# ./temperatures.sh
TIME            CPU     SYS     HDD
20:08:41        73      20      56
20:08:43        71      20      56
20:08:45        74      20      56
20:08:48        71      20      56
20:08:50        71      20      56
20:08:52        71      20      56

top - 20:13:47 up  2:22,  1 user,  load average: 2.08, 2.18, 1.87
Tasks:  97 total,   1 running,  96 sleeping,   0 stopped,   0 zombie
%Cpu(s):  2.7 us, 33.2 sy,  0.0 ni, 56.4 id,  3.2 wa,  0.0 hi,  4.4 si,  0.0 st
MiB Mem :    999.8 total,    699.9 free,     51.1 used,    248.8 buff/cache
MiB Swap:   2048.0 total,   2048.0 free,      0.0 used.    909.7 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
 3971 zhilov    20   0   79944  14684  11896 S  19.5   1.4   5:58.01 smbd
 3913 root      20   0       0      0      0 I  14.6   0.0   0:25.37 kworker/u+
 1522 root      20   0       0      0      0 D  10.6   0.0  22:44.74 md0_resync
 1370 root     -51   0       0      0      0 S   8.9   0.0   0:50.40 irq/39-f1+
 1371 root     -51   0       0      0      0 S   7.6   0.0   0:44.95 irq/40-f1+
 4147 root      20   0       0      0      0 I   5.0   0.0   0:23.10 kworker/u+
 1512 root      20   0       0      0      0 S   2.3   0.0   4:27.77 md0_raid1
  613 root      20   0       0      0      0 S   1.7   0.0   0:07.62 kswapd0
 1517 root       0 -20       0      0      0 I   1.0   0.0   1:11.73 kworker/0+
 6019 root      20   0       0      0      0 I   1.0   0.0   0:10.81 kworker/u+
 6441 root      20   0    8452   2488   2136 R   1.0   0.2   0:00.22 top
    9 root      20   0       0      0      0 S   0.3   0.0   0:21.25 ksoftirqd+
 1513 root       0 -20       0      0      0 I   0.3   0.0   1:15.27 kworker/1+
 1608 root      20   0       0      0      0 S   0.3   0.0   0:02.32 dmcrypt_w+
 3914 root      20   0   10292   5180   4400 S   0.3   0.5   0:00.49 sshd
 5800 root      20   0       0      0      0 I   0.3   0.0   0:00.10 kworker/1+

Total DISK READ:         0.00 B/s | Total DISK WRITE:         8.26 M/s
Current DISK READ:       0.00 B/s | Current DISK WRITE:      33.56 K/s
  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND
 3117 be/3 root        0.00 B/s    0.00 B/s  0.00 % 12.24 % [jbd2/dm-3-8]
 6512 be/4 root        0.00 B/s    0.00 B/s  0.00 %  1.56 % [kworker/~efficient]
 6467 be/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [kworker/~le_power_]
 6565 be/4 zhilov      0.00 B/s    8.26 M/s  0.00 %  0.00 % smbd --fo~cess-group
    1 be/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % init
    2 be/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [kthreadd]
    3 be/0 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [rcu_gp]
    4 be/0 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [rcu_par_gp]
    6 be/0 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [kworker/~H-kblockd]
    8 be/0 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [mm_percpu_wq]
    9 be/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [ksoftirqd/0]
   10 be/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [rcu_preempt]
   11 rt/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [migration/0]
   12 be/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [cpuhp/0]
   13 be/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [cpuhp/1]
   14 rt/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [migration/1]

Edited 3 time(s). Last edit at 04/25/2020 12:24PM by vzhilov.

vzhilov,

If you run CPU intensive task, and it gets to 70-80 C, it is OK. If you are idle, it should be around 40 C. This box seems to have a small fan, so there is only so much you can do. To get it cooler, the fan speed should be max when it gets to 80 C and slow down again when it is down. But small fan is quite noisy during that time.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello everyone,

I need little help, i have some problem to fix the issue with random MAC address.

I have read that the tool "set_persistent_mac_address" should fix my problem, but It doesn't!

After reboot my wd mycloud ex2 ultra I got always a new Mac.
Ok, I can fix this with static IP and change interface config..but i will leave this on DHCP.

I run my WD with this files:
Latest released kernel: linux-5.6.9-mvebu-tld-1-bodhi.tar.bz2 (05 May 2020)
Latest released rootfs: Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 (10 Sep 2019)

If you need more informations let me know.

regards, wood



Edited 1 time(s). Last edit at 05/09/2020 05:33AM by w00dp3ck3r.

wood,

> I have read that the tool
> "set_persistent_mac_address" should fix my
> problem, but It doesn't!

In Debian, see if you can list u-boot envs:

fw_printenv

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

dtd and vzhilov,

I lost track of this thread. When I released kernel 5.6.9, I forgot all about this box!

Are you guys using the same DTS now?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> > I have read that the tool
> > "set_persistent_mac_address" should fix my
> > problem, but It doesn't!
>
> In Debian, see if you can list u-boot envs:
>

> fw_printenv
>

here is my output:

fw_printenv
Cannot open /dev/mtd1: No such file or directory

wood