Hi!
I have a bricked DS218j due to bad CRC issue when loading the Ramdisk:
I have tried some guides and tricks to load via tftpboot and have succeed to boot with the following sequence with changed memory order. I use a dtb-file from this post: https://forum.doozan.com/read.php?2,76314,76604#msg-76604
It starts the kernel, beeps and after a while brings up the web page telling the unit is possible to migrate. However, when trying to update the DSM it always fails with corrupted file message (see atached file).
The printouts from serial port during the process hints there are some disk issues and I guess the dtbdump_3.dtb is not compatible with the DS218j:
After a reset the CRC error persists.
Somone with any sugesstions how to solve this?
Is it possible to create a *.dtb for the synology_armada38x_ds218j in some way (can't find it anywhere)?
Thanks in advance!
I have a bricked DS218j due to bad CRC issue when loading the Ramdisk:
SF: Detected MX25L6405D with page size 64 KiB, total 8 MiB ## Booting kernel from Legacy Image at 02000000 ... Image Name: Linux-3.10.108 Created: 2022-09-21 2:56:09 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2251616 Bytes = 2.1 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 03000000 ... Image Name: synology_armada38x_ds218j 42962 Created: 2022-09-22 10:07:49 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 3528278 Bytes = 3.4 MiB Load Address: 08000000 Entry Point: 08000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid
I have tried some guides and tricks to load via tftpboot and have succeed to boot with the following sequence with changed memory order. I use a dtb-file from this post: https://forum.doozan.com/read.php?2,76314,76604#msg-76604
tftpboot 0xd00000 zImage tftpboot 0x800000 rd.bin tftpboot 0x1000000 dtbdump_3.dtb bootm 0xd00000 0x800000 0x01000000
It starts the kernel, beeps and after a while brings up the web page telling the unit is possible to migrate. However, when trying to update the DSM it always fails with corrupted file message (see atached file).
The printouts from serial port during the process hints there are some disk issues and I guess the dtbdump_3.dtb is not compatible with the DS218j:
[ 80.392700] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 80.429350] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 80.635687] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 80.644712] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 80.658999] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 80.876455] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 80.885469] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 80.899067] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 80.927836] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 80.936922] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 80.955376] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 94.165287] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 94.174319] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 94.222775] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 101.736994] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 101.746035] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 101.790411] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 107.333767] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 107.342806] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 107.391144] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 108.349215] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 108.358195] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 108.407940] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 108.630192] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 108.639216] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 108.659044] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 108.684257] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 108.693412] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 108.709395] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 108.957516] md0: detected capacity change from 2549940224 to 0 [ 108.963415] md: md0: set sda1 to auto_remap [0] [ 108.967963] md: md0: set sdb1 to auto_remap [0] [ 108.972520] md: md0 stopped. [ 108.975420] md: unbind<sda1> [ 109.008612] md: export_rdev(sda1) [ 109.011953] md: unbind<sdb1> [ 109.048614] md: export_rdev(sdb1) [ 109.418006] md1: detected capacity change from 2147418112 to 0 [ 109.423884] md: md1: set sda2 to auto_remap [0] [ 109.428432] md: md1: set sdb2 to auto_remap [0] [ 109.432990] md: md1 stopped. [ 109.435890] md: unbind<sda2> [ 109.488605] md: export_rdev(sda2) [ 109.492028] md: unbind<sdb2> [ 109.538604] md: export_rdev(sdb2) [ 112.903174] md: bind<sda1> [ 112.906085] md: bind<sdb1> [ 112.909413] md/raid1:md0: active with 2 out of 2 mirrors [ 112.941354] md0: detected capacity change from 0 to 2549940224 [ 116.040632] md: bind<sda2> [ 116.043537] md: bind<sdb2> [ 116.046628] md/raid1:md1: active with 2 out of 2 mirrors [ 116.073773] md1: detected capacity change from 0 to 2147418112 [ 116.134531] md1: unknown partition table [ 116.202130] md0: unknown partition table [ 117.293176] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 117.302209] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 117.330858] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 117.590008] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 117.599036] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 117.620652] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 117.645489] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 117.654511] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (240) [ 117.669151] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
After a reset the CRC error persists.
Somone with any sugesstions how to solve this?
Is it possible to create a *.dtb for the synology_armada38x_ds218j in some way (can't find it anywhere)?
Thanks in advance!