Dear Community,

I installed latest Debian Bullseye with OMV on my WD My Cloud Ex2 device.

I compiled kernel v5.10.109 and tested working fine.

I prepared a guide with the steps to update your Linux Kernel for WD My Cloud Ex2

The guide explain you how to update your WD MyCloud Ex2 Device to be able to install any modern OS.
I tested this procedure with WD MyCloud Ex2, but can be adapted also for MyCloud Ex2 Ultra and (whith some abstraction guideline) to any WD Nas device.

The repository contain the image file for kernel v5.10.109.

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 https://github.com/gisab/WDMC-Ex2
The procedure works with armada-370 and armada-385 chip.
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
April 12, 2022 10:16AM
Nice!
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
April 12, 2022 04:29PM
Thanks gisab!

But I don't see where is the OMV part mentioned at your GitHub?

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
June 24, 2022 03:29PM
Hi Gisab,

I have a question about the guide you have written to install Debian on a WD EX2 Ultra. I am stuck at the uboot section, the 'ice reset' command does not show SATA devices. I have attached a SSD to the board but the device cannot be found. Any clues on this?
BootROM - 1.73
Booting from NAND flash

General initialization - Version: 1.0.0
Detected Device ID 6820
High speed PHY - Version: 2.0

Load WD GrandTeton Serdes Config:
board SerDes lanes topology details:
 | Lane #  | Speed |  Type       |
 --------------------------------
 |   0    |  06   |  SATA0      |
 |   1    |  05   |  PCIe0      |
 |   2    |  06   |  SATA1      |
 |   3    |  05   |  USB3 HOST1 |
 |   4    |  05   |  USB3 HOST0 |
 |   5    |  00   |  SGMII2     |
 --------------------------------
PCIe, Idx 0: detected no link
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver TIP-1.26.0
mvSysEnvGetTopologyUpdateInfo: TWSI Read failed
DDR3 Training Sequence - Switching XBAR Window to FastPath Window 
DDR3 Training Sequence - Ended Successfully
BootROM: Image checksum verification PASSED

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 
        | | | |___|  _ \ / _ \ / _ \| __| 
        | |_| |___| |_) | (_) | (_) | |_ 
         \___/    |____/ \___/ \___/ \__| 
 ** LOADER **


U-Boot 2013.01-g7c1da33-dirty_v1.04 (Jul 17 2017 - 18:43:06) Marvell version: 2014_T3.0p6

mvBoardIdIndexGet(boardId) = 1
Board: GrandTeton DB6820
SoC:   MV88F6820 Rev A0
       running 2 CPUs
CPU:   ARM Cortex A9 MPCore (Rev 1) LE
       CPU 0
       CPU    @ 1332 [MHz]
       L2     @ 666 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 666 [MHz]
       DDR 32 Bit Width, FastPath Memory Access, DLB Enabled, ECC Disabled
DRAM:  512 MiB

Map:   Code:                    0x1fece000:0x1ff96010
       BSS:                     0x1ffef654
       Stack:                   0x1f9cdf20
       Heap:                    0x1f9ce000:0x1fece000
raise: Signal # 8 caught
raise: Signal # 8 caught
       U-Boot Environment:      0x00000000:0x00080000 (NAND)

NAND:  ID: daad ,256 MiB
MMC:   mv_sdh: 0
PCI-e 0: Detected No Link.
USB2.0 0: Host Mode
USB3.0 0: Host Mode
USB3.0 1: Host Mode
Board configuration detected:
Creating 1 MTD partitions on "nand0":
0x00000f500000-0x00000ff00000 : "mtd=7"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=7"
UBI: MTD device size:            10 MiB                       
UBI: number of good PEBs:        80                        
UBI: number of bad PEBs:         0                            
UBI: max. allowed volumes:       128                          
UBI: wear-leveling threshold:    4096                         
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             32
UBI: total number of reserved PEBs: 48
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 4/1
UBIFS: mounted UBI device 0, volume 0, name "reserve2"
UBIFS: mounted read-only
UBIFS: file system size:   4063232 bytes (3968 KiB, 3 MiB, 32 LEBs)
UBIFS: journal size:       1015809 bytes (992 KiB, 0 MiB, 6 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: LZO
UBIFS: reserved for root:  200807 bytes (196 KiB)
Loading file '/mac_addr' to addr 0x02000000 with size 18 (0x00000012)...
Done
Set lan 2 WakeOnLan ok
Enable HD1
Enable HD2
Net:   
|  port  | Interface | PHY address  |
|--------|-----------|--------------|
| egiga0 |   RGMII   |   In-Band    |
| egiga1 |   RGMII   |   In-Band    |
| egiga2 |   SGMII   |     0x00     |
egiga0, egiga1, egiga2 [PRIME]
Hit any key to stop autoboot:  0 
Marvell>> ide reset

Reset IDE: 
Marvell Serial ATA Adapter
no device found 

Marvell>> ide reset

no IDE devices available



Edited 1 time(s). Last edit at 06/24/2022 03:34PM by Storm.
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
June 24, 2022 03:38PM
Hi Storm,

Try

scsi reset

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
June 25, 2022 05:55AM
No success either, it hangs after the 'scanning bus for devices' message. I will try the USB route for now.
Marvell>> scsi reset

Reset SCSI
AHCI init for unit0
Target spinup took 0 ms.
SATA link 1 timeout.

Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not found
scanning bus for devices...

Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
June 25, 2022 03:00PM
> No success either, it hangs after the 'scanning
> bus for devices' message.


So the scsi reset command is the correct one to use. But similarly to other WD MyCloud boxes, the SATA ports are not powered up. In other WD boxes and few others that use similar Marvell u-boots, the mw command must be used to poke the GPIO.

> I will try the USB route
> for now.

Yes, USB needs to work first anyway, so you'll have a rescue system.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
June 28, 2022 01:38PM
Short update. I managed to get it working by changing the partition table on the SSD from GPT to MBR. A similar issue is described in this post. Instructions to do the conversion with gdisk can be found here. Using the expert options i zapped the GPT table, only MBR remaining => SSD can be found in u-boot after 'scsi reset'.
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
June 28, 2022 05:58PM
Storm Wrote:
-------------------------------------------------------
> Short update. I managed to get it working by
> changing the partition table on the SSD from GPT
> to MBR. A similar issue is described in this
> post.
> Instructions to do the conversion with gdisk can
> be found
> here.
> Using the expert options i zapped the GPT table,
> only MBR remaining => SSD can be found in u-boot
> after 'scsi reset'.

Cool!

I wonder if the 3.5" HDD works. If you have one, you might want to try in u-boot to see if it is powered up OK.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 06/28/2022 06:00PM by bodhi.
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
June 29, 2022 02:51AM
I checked with a 3.5” WD Blue. It is found during ‘scsi reset’. Files are shown by ext2ls.
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
June 29, 2022 03:51PM
Okay, it only works if the HDD has a MBR partition table, not with GPT. I added a 4TB WD Blue with GPT partition table and the scsi reset commands hangs when trying to find the WD Blue. I am digging through the Marvell github to see if there are updates to GPT, ext2/4 or AHCI that can be patched to the u-boot code distributed by WD. No luck so far.
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
June 29, 2022 04:14PM
Storm Wrote:
-------------------------------------------------------
> Okay, it only works if the HDD has a MBR partition
> table, not with GPT. I added a 4TB WD Blue with
> GPT partition table and the scsi reset commands
> hangs when trying to find the WD Blue. I am
> digging through the Marvell github to see if there
> are updates to GPT, ext2/4 or AHCI that can be
> patched to the u-boot code distributed by WD. No
> luck so far.

OK, thanks!

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
July 01, 2022 12:11AM
Added Storm's finding to the kernel credits so others can find it easier.

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

Quote

- Thanks vzhilov, dtd.2512, CyberPK, mcmg2 for the works in testing to finalize the DTS for the WD MyCloud Ex2 Ultra. And Storm for the finding about MBR vs GPT for the WD MyCloud Ex2 here.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
July 05, 2022 02:49PM
You're welcome :-)
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 04:37AM
Hello all,

Sorry for bumping this topic, but I am run out ideas:

I have an EX2 ultra working fine, with the kernel 4.x working and all the old stuff

Quick summary:

cd /mnt/root
wget http://fox-exe.ru/WDMyCloud/WDMyCloud-Ex2-Ultra/Dev/Linux-4.15.0-rc6/libs-4.15.0-rc6.tar.gz
wget http://fox-exe.ru/WDMyCloud/WDMyCloud-Ex2-Ultra/Dev/Linux-4.15.0-rc6/uImage
wget http://fox-exe.ru/WDMyCloud/WDMyCloud-Ex2-Ultra/Dev/Linux-4.15.0-rc6/uRamdisk
tar xvf libs-4.15.0-rc6.tar.gz
dd if=/dev/zero of=/dev/mtdblock1
dd if=uImage of=/dev/mtdblock1
dd if=/dev/zero of=/dev/mtdblock2
dd if=uRamdisk of=/dev/mtdblock2
rm uImage uRamdisk libs-4.15.0-rc6.tar.gz /mnt/root/lib/modules/4.14.4 -r

I found this forum (and another hundred of blogs) with info to upgrade to the kernel 5.x, new uBoot and this cool stuff, so I started with it.

It was hard, but I got the pins soldered to the board, I bought the uart-usb (UART-TTL USB adapter for 3.3V and 5V with CH340G https://www.az-delivery.de/en/products/usb-ttl-adapter-3-3v-oder-5v-mit-ch340g-und-20cm-jumperkabel) but I can't get anything when the WD is booting. I've tried severals combinations, but without any success.

I thought I could modify the uBoot from the command line, when the NAS is up, so I've installed the u-boot tools, but I can't read the environment either. Below you can find my procs partitions:

root@wdmc:~# cat /proc/partitions 
major minor  #blocks  name

   1        0       4096 ram0
   1        1       4096 ram1
   1        2       4096 ram2
   1        3       4096 ram3
   1        4       4096 ram4
   1        5       4096 ram5
   1        6       4096 ram6
   1        7       4096 ram7
  31        0       5120 mtdblock0
  31        1       5120 mtdblock1
  31        2       5120 mtdblock2
  31        3     189440 mtdblock3
  31        4      15360 mtdblock4
  31        5      20480 mtdblock5
  31        6      10240 mtdblock6
  31        7      10240 mtdblock7
   8       16 3907018584 sdb
   8       17     204800 sdb1
   8       18 3906682672 sdb2
   8       19     131072 sdb3
   8        0  732574584 sda
   8        1     498688 sda1
   8        2    3500032 sda2
   8        3  728573952 sda3
   9        2  728442880 md2
   9        1    3497984 md1
   9        0     498368 md0

root@wdmc:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00500000 00020000 "u-boot"
mtd1: 00500000 00020000 "uImage"
mtd2: 00500000 00020000 "uRamdisk"
mtd3: 0b900000 00020000 "image.cfs"
mtd4: 00f00000 00020000 "Recovery"
mtd5: 01400000 00020000 "config"
mtd6: 00a00000 00020000 "reserve1"
mtd7: 00a00000 00020000 "reserve2"

I've tried with the all combinations I found here for the fw_env.config, but none of them work:

Cannot read environment, using default
Cannot read default environment from file

Could you please give me some light here?

I would really appreciate any idea, suggestion or help here.

Thanks in advanced

Best

i5Js



Edited 2 time(s). Last edit at 11/01/2022 08:35AM by i5Js.
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 01:01PM
i5Js,

Quote

I've tried with the all combinations I found here for the fw_env.config, but none of them work:

cat /proc/mtd might not give you the real mtd partition layout. It is best to see it in stock u-boot log, and also while in stock OS to confirm.

However, according to the Ex2 Ultra stock u-boot log, the env location is at 0x00080000. This Ex2 might be the same.

Try using this in fw_env.config

/dev/mtd0 0x00080000 0x20000 0x20000

==============

By the way, don't flash the kernel files with dd.

Quote

dd if=/dev/zero of=/dev/mtdblock1
dd if=uImage of=/dev/mtdblock1
dd if=/dev/zero of=/dev/mtdblock2
dd if=uRamdisk of=/dev/mtdblock2

Use nandwrite to flash to mtd1 and mtd2. For example,
flash_erase /dev/mtd1
nandwrite /dev/mtd1 uImage

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 01:59PM
Hey bodhi,

Many thanks for your answer. I've changed the file, but it didn't work either :(

root@wdmc:~# cat /etc/fw_env.config 
/dev/mtd0 0x00080000 0x20000 0x20000
root@wdmc:~# fw_printenv 
Cannot read environment, using default
Cannot read default environment from file
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 02:30PM
i5Js,

I've not seen serial boot log for this Ex2 box. Perhaps I did in this forum and did not pay attention to it.

The WD My Cloud series seem to use the same u-boot source, and it prints out the info about the envs.

Like in Storm's post in this thread

https://forum.doozan.com/read.php?2,132015,132426#msg-132426

Quote

U-Boot Environment: 0x00000000:0x00080000 (NAND)

So if you can get the serial console to work, it might show the info.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 02:32PM
Hi,

I've bought another UART cable and arrives tomorrow, let's see if It works this time,

Thanks,



Edited 1 time(s). Last edit at 11/01/2022 02:34PM by i5Js.
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 03:25PM
This is from the dmesg, when the WD boots, I don't know if it helps:

[    4.933398] Creating 8 MTD partitions on "pxa3xx_nand-0":
[    4.937518] 0x000000000000-0x000000500000 : "u-boot"
[    4.941648] 0x000000500000-0x000000a00000 : "uImage"
[    4.945666] 0x000000a00000-0x000000f00000 : "uRamdisk"
[    4.949853] 0x000000f00000-0x00000c800000 : "image.cfs"
[    4.954613] 0x00000c800000-0x00000d700000 : "Recovery"
[    4.958832] 0x00000d700000-0x00000eb00000 : "config"
[    4.962895] 0x00000eb00000-0x00000f500000 : "reserve1"
[    4.967092] 0x00000f500000-0x00000ff00000 : "reserve2"



Edited 1 time(s). Last edit at 11/01/2022 03:28PM by i5Js.
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 03:29PM
ah, one last thing, my mistake, my model is an EX2 Ultra too.
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 03:32PM
Try

echo “/dev/mtd0 0x100000 0x80000 0x20000 4” > /etc/fw_env.config
fw_printenv

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 03:34PM
root@wdmc:~# cat /etc/fw_env.config 
/dev/mtd0 0x100000 0x80000 0x20000 4
root@wdmc:~# fw_printenv 
Cannot read environment, using default
Cannot read default environment from file
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 03:43PM
i5Js,

Now I remember, from the working thread for WD Ex2 Ultra

https://forum.doozan.com/read.php?2,99079,105704#msg-105704

/dev/mtd0 0x100000 0x80000 0x20000 4

I guess you should also post the dmesg here, perhaps I can find something wrong from that. Let's capture the whole set of info in 1 post.

dmesg
cat /proc/mtd
cat /etc/fw_env.config
fw_printenv

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 03:46PM
Hold on. CyperPK said this

https://forum.doozan.com/read.php?2,99079,106494#msg-106494

Quote

Please, note that this address is valid only for the patched uboot.
As explained in my post, the stock address is overlapping with the uImage partition, so it isn't usable

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 03:52PM
And read CyberPK installation post for more details.

https://forum.doozan.com/read.php?2,28939,98649#msg-98649

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 03:56PM
dimes
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.4 (root@build-server) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4)) #14 SMP Wed Dec 20 01:09:34 +05 2017
[    0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: WD MyCloud Mirror gen2: Marvell Armada 385
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 262144
[    0.000000] free_area_init_node: node 0, pgdat c0b46280, node_mem_map ef6f8000
[    0.000000]   Normal zone: 1728 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 196608 pages, LIFO batch:31
[    0.000000]   HighMem zone: 65536 pages, LIFO batch:15
[    0.000000] percpu: Embedded 16 pages/cpu @ef6c9000 s32780 r8192 d24564 u65536
[    0.000000] pcpu-alloc: s32780 r8192 d24564 u65536 alloc=16*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 260416
[    0.000000] Kernel command line: root=/dev/ram console=ttyS0,115200
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1024944K/1048576K available (7031K kernel code, 285K rwdata, 1748K rodata, 1024K init, 227K bss, 23632K reserved, 0K cma-reserved, 262144K highmem)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
                   lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
                   pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
                   modules : 0xbf000000 - 0xbfe00000   (  14 MB)
                     .text : 0xc0008000 - 0xc07ddf58   (8024 kB)
                     .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
                     .data : 0xc0b00000 - 0xc0b47780   ( 286 kB)
                      .bss : 0xc0b49000 - 0xc0b81e24   ( 228 kB)
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 D prefetch enabled, offset 1 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB
[    0.000000] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001
[    0.000006] sched_clock: 64 bits at 666MHz, resolution 1ns, wraps every 4398046511103ns
[    0.000015] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x999999d70a, max_idle_ns: 440795225152 ns
[    0.000029] Switching to timer-based delay loop, resolution 1ns
[    0.000148] Ignoring duplicate/late registration of read_current_timer delay
[    0.000155] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[    0.000389] Console: colour dummy device 80x30
[    0.000403] Calibrating delay loop (skipped), value calculated using timer frequency.. 1332.00 BogoMIPS (lpj=6660000)
[    0.000410] pid_max: default: 32768 minimum: 301
[    0.000496] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000502] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000796] CPU: Testing write buffer coherency: ok
[    0.000912] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.001047] Setting up static identity map for 0x100000 - 0x100060
[    0.001121] mvebu-soc-id: MVEBU SoC ID=0x6820, Rev=0x4
[    0.001194] mvebu-pmsu: Initializing Power Management Service Unit
[    0.001248] Hierarchical SRCU implementation.
[    0.001454] smp: Bringing up secondary CPUs ...
[    0.001614] Booting CPU 1
[    0.001788] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.001835] smp: Brought up 1 node, 2 CPUs
[    0.001840] SMP: Total of 2 processors activated (2664.00 BogoMIPS).
[    0.001842] CPU: All CPU(s) started in SVC mode.
[    0.002324] devtmpfs: initialized
[    0.003837] random: get_random_u32 called from bucket_table_alloc+0xf4/0x240 with crng_init=0
[    0.003938] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.004031] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.004038] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.004106] xor: measuring software checksum speed
[    0.100067]    arm4regs  :  2082.400 MB/sec
[    0.200066]    8regs     :  1601.200 MB/sec
[    0.300067]    32regs    :  1662.800 MB/sec
[    0.400065]    neon      :  1517.600 MB/sec
[    0.400068] xor: using function: arm4regs (2082.400 MB/sec)
[    0.400073] pinctrl core: initialized pinctrl subsystem
[    0.400224] regulator-dummy: no parameters
[    0.400227] random: fast init done
[    0.400512] NET: Registered protocol family 16
[    0.401090] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.401666] cpuidle: using governor ladder
[    0.401815] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling
[    0.401821] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling
[    0.404577] sram soc:sa-sram0: found no memory resource
[    0.404589] sram: probe of soc:sa-sram0 failed with error -22
[    0.404650] sram soc:sa-sram1: found no memory resource
[    0.404656] sram: probe of soc:sa-sram1 failed with error -22
[    0.580253] raid6: int32x1  gen()   175 MB/s
[    0.750145] raid6: int32x1  xor()   243 MB/s
[    0.920176] raid6: int32x2  gen()   278 MB/s
[    1.090092] raid6: int32x2  xor()   284 MB/s
[    1.260067] raid6: int32x4  gen()   303 MB/s
[    1.430092] raid6: int32x4  xor()   284 MB/s
[    1.600166] raid6: int32x8  gen()   345 MB/s
[    1.770105] raid6: int32x8  xor()   256 MB/s
[    1.940111] raid6: neonx1   gen()  1010 MB/s
[    2.110091] raid6: neonx1   xor()   958 MB/s
[    2.280066] raid6: neonx2   gen()  1078 MB/s
[    2.450090] raid6: neonx2   xor()  1116 MB/s
[    2.620116] raid6: neonx4   gen()  1133 MB/s
[    2.790081] raid6: neonx4   xor()  1156 MB/s
[    2.960095] raid6: neonx8   gen()   923 MB/s
[    3.130082] raid6: neonx8   xor()   886 MB/s
[    3.130085] raid6: using algorithm neonx4 gen() 1133 MB/s
[    3.130087] raid6: .... xor() 1156 MB/s, rmw enabled
[    3.130090] raid6: using neon recovery algorithm
[    3.130194] reg-fixed-voltage usb3-vbus0: could not find pctldev for node /soc/internal-regs/pinctrl@18000/xhci0_vbus_pins, deferring probe
[    3.130214] reg-fixed-voltage usb3-vbus1: could not find pctldev for node /soc/internal-regs/pinctrl@18000/xhci1_vbus_pins, deferring probe
[    3.130468] SCSI subsystem initialized
[    3.130590] libata version 3.00 loaded.
[    3.130702] usbcore: registered new interface driver usbfs
[    3.130725] usbcore: registered new interface driver hub
[    3.130754] usbcore: registered new device driver usb
[    3.130800] pps_core: LinuxPPS API ver. 1 registered
[    3.130803] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    3.130812] PTP clock support registered
[    3.131359] Bluetooth: Core ver 2.22
[    3.131384] NET: Registered protocol family 31
[    3.131388] Bluetooth: HCI device and connection manager initialized
[    3.131393] Bluetooth: HCI socket layer initialized
[    3.131398] Bluetooth: L2CAP socket layer initialized
[    3.131416] Bluetooth: SCO socket layer initialized
[    3.131487] clocksource: Switched to clocksource arm_global_timer
[    3.131554] VFS: Disk quotas dquot_6.6.0
[    3.131586] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    3.131631] FS-Cache: Loaded
[    3.131710] CacheFiles: Loaded
[    3.135567] NET: Registered protocol family 2
[    3.135860] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    3.135904] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    3.135976] TCP: Hash tables configured (established 8192 bind 8192)
[    3.136027] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    3.136054] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    3.136143] NET: Registered protocol family 1
[    3.136309] RPC: Registered named UNIX socket transport module.
[    3.136313] RPC: Registered udp transport module.
[    3.136315] RPC: Registered tcp transport module.
[    3.136317] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    3.136323] PCI: CLS 0 bytes, default 64
[    3.136407] Trying to unpack rootfs image as initramfs...
[    3.972768] Freeing initrd memory: 2620K
[    3.973915] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    3.974251] NFS: Registering the id_resolver key type
[    3.974265] Key type id_resolver registered
[    3.974268] Key type id_legacy registered
[    3.974275] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    3.974474] FS-Cache: Netfs 'cifs' registered for caching
[    3.976479] async_tx: api initialized (async)
[    3.976505] bounce: pool size: 64 pages
[    3.976535] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    3.976540] io scheduler noop registered
[    3.976542] io scheduler deadline registered
[    3.976572] io scheduler cfq registered (default)
[    3.976575] io scheduler kyber registered
[    3.977114] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver
[    3.977505] gpio gpiochip0: (f1018100.gpio): added GPIO chardev (254:0)
[    3.977544] gpiochip_setup_dev: registered GPIOs 0 to 31 on device: gpiochip0 (f1018100.gpio)
[    3.977743] gpio gpiochip1: (f1018140.gpio): added GPIO chardev (254:1)
[    3.977787] gpiochip_setup_dev: registered GPIOs 32 to 59 on device: gpiochip1 (f1018140.gpio)
[    3.978190] mv_xor f1060800.xor: Marvell shared XOR driver
[    4.031861] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[    4.032726] mv_xor f1060900.xor: Marvell shared XOR driver
[    4.101846] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[    4.126219] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    4.127060] console [ttyS0] disabled
[    4.147260] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 23, base_baud = 12500000) is a 16550A
[    4.819591] console [ttyS0] enabled
[    4.842333] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 24, base_baud = 12500000) is a 16550A
[    4.852032] brd: module loaded
[    4.855661] loop: module loaded
[    4.857721] ahci-mvebu f10a8000.sata: Looking up target-supply from device tree
[    4.857730] ahci-mvebu f10a8000.sata: Looking up target-supply property in node /soc/internal-regs/sata@a8000 failed
[    4.857791] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode
[    4.865642] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs 
[    4.873634] scsi host0: ahci-mvebu
[    4.875915] scsi host1: ahci-mvebu
[    4.878110] ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 43
[    4.884841] ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x180 irq 43
[    4.891936] pxa3xx-nand f10d0000.flash: This platform can't do DMA on this device
[    4.898498] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
[    4.903623] nand: Hynix H27U2G8F2CTR-BC
[    4.906167] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    4.912473] pxa3xx-nand f10d0000.flash: ECC strength 16, ECC step size 2048
[    4.918361] Bad block table found at page 131008, version 0x01
[    4.923258] Bad block table found at page 130944, version 0x01
[    4.928020] 8 ofpart partitions found on MTD device pxa3xx_nand-0
[    4.932844] Creating 8 MTD partitions on "pxa3xx_nand-0":
[    4.936963] 0x000000000000-0x000000500000 : "u-boot"
[    4.941071] 0x000000500000-0x000000a00000 : "uImage"
[    4.945138] 0x000000a00000-0x000000f00000 : "uRamdisk"
[    4.949349] 0x000000f00000-0x00000c800000 : "image.cfs"
[    4.954106] 0x00000c800000-0x00000d700000 : "Recovery"
[    4.958342] 0x00000d700000-0x00000eb00000 : "config"
[    4.962429] 0x00000eb00000-0x00000f500000 : "reserve1"
[    4.966644] 0x00000f500000-0x00000ff00000 : "reserve2"
[    4.971062] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
[    4.976990] mdio_bus fixed-0: GPIO lookup for consumer reset
[    4.976995] mdio_bus fixed-0: using lookup tables for GPIO lookup
[    4.976999] mdio_bus fixed-0: lookup for GPIO reset failed
[    4.977009] libphy: Fixed MDIO Bus: probed
[    4.980165] mdio_bus f1072004.mdio-mii: GPIO lookup for consumer reset
[    4.980169] mdio_bus f1072004.mdio-mii: using device tree for GPIO lookup
[    4.980176] of_get_named_gpiod_flags: can't parse 'reset-gpios' property of node '/soc/internal-regs/mdio@72004[0]'
[    4.980180] of_get_named_gpiod_flags: can't parse 'reset-gpio' property of node '/soc/internal-regs/mdio@72004[0]'
[    4.980183] mdio_bus f1072004.mdio-mii: using lookup tables for GPIO lookup
[    4.980186] mdio_bus f1072004.mdio-mii: lookup for GPIO reset failed
[    4.980189] libphy: orion_mdio_bus: probed
[    4.985133] mvneta_bm f10c8000.bm: failed to allocate internal memory
[    4.990311] mvneta_bm: probe of f10c8000.bm failed with error -12
[    4.995993] mvneta f1034000.ethernet eth0: Using random mac address 36:a4:2e:d2:e0:df
[    5.002749] usbcore: registered new interface driver lan78xx
[    5.007127] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    5.012385] ehci-orion: EHCI orion driver
[    5.015190] orion-ehci f1058000.usb: EHCI Host Controller
[    5.019316] orion-ehci f1058000.usb: new USB bus registered, assigned bus number 1
[    5.025668] orion-ehci f1058000.usb: irq 39, io mem 0xf1058000
[    5.051494] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00
[    5.056238] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    5.061764] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.067713] usb usb1: Product: EHCI Host Controller
[    5.071305] usb usb1: Manufacturer: Linux 4.14.4 ehci_hcd
[    5.075433] usb usb1: SerialNumber: f1058000.usb
[    5.079021] hub 1-0:1.0: USB hub found
[    5.081506] hub 1-0:1.0: 1 port detected
[    5.084549] xhci-hcd f10f0000.usb3: xHCI Host Controller
[    5.088587] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 2
[    5.094876] xhci-hcd f10f0000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x00010010
[    5.102162] xhci-hcd f10f0000.usb3: irq 45, io mem 0xf10f0000
[    5.106721] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    5.112256] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.118206] usb usb2: Product: xHCI Host Controller
[    5.121804] usb usb2: Manufacturer: Linux 4.14.4 xhci-hcd
[    5.125919] usb usb2: SerialNumber: f10f0000.usb3
[    5.129574] hub 2-0:1.0: USB hub found
[    5.132063] hub 2-0:1.0: 1 port detected
[    5.134852] xhci-hcd f10f0000.usb3: xHCI Host Controller
[    5.138887] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 3
[    5.145155] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[    5.152061] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
[    5.157574] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.163543] usb usb3: Product: xHCI Host Controller
[    5.167135] usb usb3: Manufacturer: Linux 4.14.4 xhci-hcd
[    5.171250] usb usb3: SerialNumber: f10f0000.usb3
[    5.174883] hub 3-0:1.0: USB hub found
[    5.177357] hub 3-0:1.0: 1 port detected
[    5.180219] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    5.184272] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 4
[    5.190542] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x00010010
[    5.197827] xhci-hcd f10f8000.usb3: irq 46, io mem 0xf10f8000
[    5.202387] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[    5.207910] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.213874] usb usb4: Product: xHCI Host Controller
[    5.217466] usb usb4: Manufacturer: Linux 4.14.4 xhci-hcd
[    5.221587] usb usb4: SerialNumber: f10f8000.usb3
[    5.225221] hub 4-0:1.0: USB hub found
[    5.227696] hub 4-0:1.0: 1 port detected
[    5.230488] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    5.234531] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 5
[    5.240790] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM.
[    5.247688] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
[    5.253212] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.259161] usb usb5: Product: xHCI Host Controller
[    5.262771] usb usb5: Manufacturer: Linux 4.14.4 xhci-hcd
[    5.266886] usb usb5: SerialNumber: f10f8000.usb3
[    5.270504] hub 5-0:1.0: USB hub found
[    5.272989] hub 5-0:1.0: 1 port detected
[    5.275904] usbcore: registered new interface driver usb-storage
[    5.280800] i2c /dev entries driver
[    5.293678] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[    5.304899] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
[    5.312293] sdhci: Secure Digital Host Controller Interface driver
[    5.317194] sdhci: Copyright(c) Pierre Ossman
[    5.320364] sdhci-pltfm: SDHCI platform and OF driver helper
[    5.324845] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio-leds/hdd1-red[0]' - status (0)
[    5.324853] no flags found for gpios
[    5.324912] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio-leds/hdd2-red[0]' - status (0)
[    5.324920] no flags found for gpios
[    5.324962] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio-leds/hdd1-blue[0]' - status (0)
[    5.324967] no flags found for gpios
[    5.325011] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio-leds/hdd2-blue[0]' - status (0)
[    5.325016] no flags found for gpios
[    5.325160] ledtrig-cpu: registered to indicate activity on CPUs
[    5.330121] marvell-cesa: probe of f1090000.crypto failed with error -22
[    5.335642] hidraw: raw HID events driver (C) Jiri Kosina
[    5.339820] usbcore: registered new interface driver usbhid
[    5.344124] usbhid: USB HID core driver
[    5.346769] Netfilter messages via NETLINK v0.30.
[    5.350190] nfnl_acct: registering with nfnetlink.
[    5.353781] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[    5.358783] arp_tables: arp_tables: (C) 2002 David S. Miller
[    5.363291] NET: Registered protocol family 10
[    5.366897] Segment Routing with IPv6
[    5.369296] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    5.374250] NET: Registered protocol family 17
[    5.377429] Bridge firewalling registered
[    5.380168] 8021q: 802.1Q VLAN Support v1.8
[    5.383084] Key type dns_resolver registered
[    5.386106] Registering SWP/SWPB emulation handler
[    5.390840] of_get_named_gpiod_flags: parsed 'gpio' property of node '/usb3-vbus0[0]' - status (0)
[    5.390869] usb3-vbus0: 5000 mV 
[    5.390944] reg-fixed-voltage usb3-vbus0: usb3-vbus0 supplying 5000000uV
[    5.391017] of_get_named_gpiod_flags: parsed 'gpio' property of node '/usb3-vbus1[0]' - status (0)
[    5.391035] usb3-vbus1: 5000 mV 
[    5.391089] reg-fixed-voltage usb3-vbus1: usb3-vbus1 supplying 5000000uV
[    5.391314] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio-keys/btn-reset[0]' - status (0)
[    5.391326] gpio-50 (Reset): gpiod_set_debounce: missing set() or set_config() operations
[    5.391467] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[    5.391522] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    5.397424] ata1.00: ATA-7: HITACHI HUA721075KLA330, GK8OA90A, max UDMA/133
[    5.397428] ata1.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    5.398254] ata1.00: configured for UDMA/133
[    5.398437] scsi 0:0:0:0: Direct-Access     ATA      HITACHI HUA72107 A90A PQ: 0 ANSI: 5
[    5.398961] sd 0:0:0:0: [sda] 1465149168 512-byte logical blocks: (750 GB/699 GiB)
[    5.398985] sd 0:0:0:0: [sda] Write Protect is off
[    5.398989] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    5.399026] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    5.435930]  sda: sda1 sda2 sda3
[    5.436588] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    5.446762] hctosys: unable to open rtc device (rtc0)
[    9.951492] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   10.229522] ata2.00: ATA-9: HGST HUS726040ALA614, A5DEKN03, max UDMA/133
[   10.234955] ata2.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   10.393681] ata2.00: configured for UDMA/133
[   10.396834] scsi 1:0:0:0: Direct-Access     ATA      HGST HUS726040AL KN03 PQ: 0 ANSI: 5
[   10.404037] sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[   10.410536] sd 1:0:0:0: [sdb] Write Protect is off
[   10.414056] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[   10.414106] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   10.490226]  sdb: sdb1 sdb2 sdb3
[   10.492754] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[   10.497523] Freeing unused kernel memory: 1024K
[   12.693434] md: md2 stopped.
[   12.696932] md/raid1:md2: active with 1 out of 2 mirrors
[   12.714131] md2: detected capacity change from 0 to 745925509120
[   12.733291] md: md1 stopped.
[   12.736498] md/raid1:md1: active with 1 out of 2 mirrors
[   12.740563] md1: detected capacity change from 0 to 3581935616
[   12.750053] md: md0 stopped.
[   12.754570] md/raid1:md0: active with 1 out of 2 mirrors
[   12.758635] md0: detected capacity change from 0 to 510328832
[   12.805104] EXT4-fs (md1): couldn't mount as ext3 due to feature incompatibilities
[   12.811566] EXT4-fs (md1): couldn't mount as ext2 due to feature incompatibilities
[   13.514575] EXT4-fs (md1): recovery complete
[   13.526402] EXT4-fs (md1): mounted filesystem with ordered data mode. Opts: (null)
[   16.384022] systemd[1]: System time before build time, advancing clock.
[   16.465623] cgroup: cgroup2: unknown option "memory_recursiveprot"
[   16.480316] systemd[1]: systemd 247.3-7+deb11u1 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[   16.502353] systemd[1]: Detected architecture arm.
[   16.561769] systemd[1]: Set hostname to <wdmc>.
[   19.653543] systemd[1]: Queued start job for default target Graphical Interface.
[   19.660618] systemd[1]: system-getty.slice: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling.
[   19.671753] systemd[1]: (This warning is only shown for the first unit using IP firewalling.)
[   19.680081] systemd[1]: Created slice system-getty.slice.
[   19.712085] systemd[1]: Created slice system-modprobe.slice.
[   19.752112] systemd[1]: Created slice system-serial\x2dgetty.slice.
[   19.791900] systemd[1]: Created slice User and Session Slice.
[   19.831738] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[   19.871657] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[   19.911777] systemd[1]: Condition check resulted in Arbitrary Executable File Formats File System Automount Point being skipped.
[   19.922277] systemd[1]: Reached target Local Encrypted Volumes.
[   19.971787] systemd[1]: Reached target Paths.
[   20.001661] systemd[1]: Reached target Slices.
[   20.031654] systemd[1]: Reached target System Time Set.
[   20.061786] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[   20.101897] systemd[1]: Listening on LVM2 poll daemon socket.
[   20.151867] systemd[1]: Listening on RPCbind Server Activation Socket.
[   20.194575] systemd[1]: Listening on Syslog Socket.
[   20.231785] systemd[1]: Listening on fsck to fsckd communication Socket.
[   20.271699] systemd[1]: Listening on initctl Compatibility Named Pipe.
[   20.332057] systemd[1]: Condition check resulted in Journal Audit Socket being skipped.
[   20.339182] systemd[1]: Listening on Journal Socket (/dev/log).
[   20.371903] systemd[1]: Listening on Journal Socket.
[   20.401977] systemd[1]: Listening on Network Service Netlink Socket.
[   20.441842] systemd[1]: Listening on udev Control Socket.
[   20.481766] systemd[1]: Listening on udev Kernel Socket.
[   20.531867] systemd[1]: Condition check resulted in Huge Pages File System being skipped.
[   20.539026] systemd[1]: Condition check resulted in POSIX Message Queue File System being skipped.
[   20.548372] systemd[1]: Mounting NFSD configuration filesystem...
[   20.583223] systemd[1]: Mounting RPC Pipe File System...
[   20.623346] systemd[1]: Mounting Kernel Debug File System...
[   20.661828] systemd[1]: Condition check resulted in Kernel Trace File System being skipped.
[   20.669155] systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped.
[   20.677486] systemd[1]: Finished Availability of block devices.
[   20.738298] systemd[1]: Starting Restore / save the current clock...
[   20.771750] systemd[1]: Condition check resulted in Create list of static device nodes for the current kernel being skipped.
[   20.784232] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
[   20.823708] systemd[1]: Starting Load Kernel Module configfs...
[   20.863815] systemd[1]: Starting Load Kernel Module drm...
[   20.868227] random: crng init done
[   20.903659] systemd[1]: Starting Load Kernel Module fuse...
[   20.960447] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[   20.968418] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[   20.978153] systemd[1]: Starting Journal Service...
[   21.021407] systemd[1]: Starting Load Kernel Modules...
[   21.053317] systemd[1]: Starting Remount Root and Kernel File Systems...
[   21.093609] systemd[1]: Starting Coldplug All udev Devices...
[   21.093862] EXT4-fs (md1): re-mounted. Opts: errors=remount-ro
[   21.136135] systemd[1]: Started Journal Service.
[   21.546811] systemd-journald[1418]: Received client request to flush runtime journal.
[   21.717178] systemd-journald[1418]: File /var/log/journal/c163733b868f4d2c84b3f6b8f68b78b2/system.journal corrupted or uncleanly shut down, renaming and replacing.
[   23.281554] ata2.00: exception Emask 0x10 SAct 0x1 SErr 0x190002 action 0xe frozen
[   23.287861] ata2.00: irq_stat 0x80400000, PHY RDY changed
[   23.292001] ata2: SError: { RecovComm PHYRdyChg 10B8B Dispar }
[   23.296556] ata2.00: failed command: READ FPDMA QUEUED
[   23.300416] ata2.00: cmd 60/08:00:28:50:06/00:00:00:00:00/40 tag 0 ncq dma 4096 in
                        res 40/00:00:28:50:06/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   23.313450] ata2.00: status: { DRDY }
[   23.315826] ata2: hard resetting link
[   24.409177] Adding 498364k swap on /dev/md0.  Priority:-2 extents:1 across:498364k 
[   31.921497] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   32.480996] ata2.00: configured for UDMA/133
[   32.484010] ata2: EH complete
[   33.732640] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   34.556983] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
[   34.561667] 8021q: adding VLAN 0 to HW filter on device bond0
[   37.991864] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   37.998616] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   44.409303] NFSD: starting 90-second grace period (net c0b3e1c0)

root@wdmc:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00500000 00020000 "u-boot"
mtd1: 00500000 00020000 "uImage"
mtd2: 00500000 00020000 "uRamdisk"
mtd3: 0b900000 00020000 "image.cfs"
mtd4: 00f00000 00020000 "Recovery"
mtd5: 01400000 00020000 "config"
mtd6: 00a00000 00020000 "reserve1"
mtd7: 00a00000 00020000 "reserve2"

root@wdmc:~# cat /etc/fw_env.config
/dev/mtd0 0x100000 0x80000 0x20000 4

root@wdmc:~# fw_printenv 
Cannot read environment, using default
Cannot read default environment from file

Thanks for your time!
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 01, 2022 04:30PM
i5Js,

I recalled the issue now that I've reread CyberPK's post.

The problem is the env locations in these WD NAS series actually overlaps the kernel uImage location. So you cannot save the env. If you do save them in serial console, the stock kernel on NAND will be corrupted.

So now you have to make a choice. Either

- Booting Debian permanently with the rootfs Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 and later install new kernels as they are available. This option allows you to update the envs.

- Boot with stock kernel. And you cannot access or update the envs.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV
November 02, 2022 01:20PM
Well, my box is officially dead or bricked. I've tried to follow the tutorials and I flashed the nand and recreated the filesystem, but now it doesn't boot. Blinking blue all the time.

I also get another uart interface, but it don't know why it doesn't work. I don't have anything the screen. I'm trying to use my Mac, or a windows machine with puttt, but nothing works. Just two questions before giving up:

** should I need a raspberry to connect to the box using the uart?
** the cables, do I need to cross it? Rx-Tx and viceversa?

Thanks
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: