Bricked Synology DS218j January 02, 2023 12:41PM |
Registered: 1 year ago Posts: 24 |
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
tftpboot 0xd00000 zImage tftpboot 0x800000 rd.bin tftpboot 0x1000000 dtbdump_3.dtb bootm 0xd00000 0x800000 0x01000000
[ 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)
Re: Bricked Synology DS218j January 02, 2023 03:41PM |
Registered: 1 year ago Posts: 24 |
Re: Bricked Synology DS218j January 02, 2023 03:51PM |
Admin Registered: 13 years ago Posts: 18,821 |
armada-385-synology-ds116.dtb armada-385-synology-rs816.dtb armada-385-thecus-n2350.dtb
Re: Bricked Synology DS218j January 02, 2023 04:39PM |
Registered: 1 year ago Posts: 24 |
Quote
bodhi
In the rootfs folder /boot/dts:
bootm 0xd00000 0x800000 0x01000000 ## Booting kernel from Legacy Image at 00d00000 ... Image Name: Linux-3.10.108 Created: 2021-10-18 11:15:28 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2247000 Bytes = 2.1 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 00800000 ... Image Name: synology_armada38x_ds218j 42218 Created: 2021-10-18 13:15:33 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 3463856 Bytes = 3.3 MiB Load Address: 08000000 Entry Point: 08000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01000000 Booting using the fdt blob at 0x01000000 Loading Kernel Image ... OK OK Loading Ramdisk to 1f6d9000, end 1fa26ab0 ... OK Loading Device Tree to 00ff8000, end 00fffea1 ... OK Skipping Device Tree update ('fdt_skip_update' = yes) Limit DDR size at 3GB due to power of 2 requirement of Address decoding Starting kernel ... Uncompressing Linux... done, booting the kernel.
Re: Bricked Synology DS218j January 02, 2023 04:52PM |
Admin Registered: 13 years ago Posts: 18,821 |
Quote
3. Create uImage with DTB appended. I am using the Zyxel NAS326 as an example here. Please replace armada-380-zyxel-nas326.dtb below with the appropriate DTB name for your box.
cd /media/sdb1/boot cp -a zImage-5.13.8-mvebu-tld-1 zImage.fdt cat dts/armada-380-zyxel-nas326.dtb >> zImage.fdt mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.13.8-mvebu-tld-1 -d zImage.fdt uImage
armada-385-synology-ds116.dtb armada-385-synology-rs816.dtb armada-385-thecus-n2350.dtb
Re: Bricked Synology DS218j January 03, 2023 07:07AM |
Registered: 1 year ago Posts: 24 |
-rw-r--r-- 1 root root 205052 Aug 7 2021 config-5.13.8-mvebu-tld-1 drwxr-xr-x 2 root root 4096 Aug 8 2021 dts -rw-r--r-- 1 root root 9649821 Sep 24 2021 initrd.img-5.13.8-mvebu-tld-1 -rw-r--r-- 1 root root 7785524 Aug 8 2021 linux-headers-5.13.8-mvebu-tld-1_1.0_armhf.deb -rw-r--r-- 1 root root 4461631 Aug 7 2021 System.map-5.13.8-mvebu-tld-1 -rw-r--r-- 1 root root 9649885 Sep 24 2021 uInitrd -rwxr-xr-x 1 root root 5218232 Aug 7 2021 vmlinuz-5.13.8-mvebu-tld-1 -rwxr-xr-x 1 root root 5218232 Aug 8 2021 zImage-5.13.8-mvebu-tld-1 root@SYNOLOGYNAS:/volumeUSB1/usbshare/boot# cp -a zImage-5.13.8-mvebu-tld-1 zImage116.fdt root@SYNOLOGYNAS:/volumeUSB1/usbshare/boot# cat dts/armada-385-synology-ds116.dtb >> zImage116.fdt root@SYNOLOGYNAS:/volumeUSB1/usbshare/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.13.8-mvebu-tld-1 -d zImage116.fdt uImage116 -ash: mkimage: command not found
root@SYNOLOGYNAS:/volumeUSB1/usbshare/usr/bin# ls -l mk* -rwxr-xr-x 1 root root 9928 May 23 2021 mkenvimage -rwxr-xr-x 1 root root 43172 Sep 22 2020 mkfifo -rwxr-xr-x 1 root root 177684 May 23 2021 mkimage -rwxr-xr-x 1 root root 5796 May 23 2021 mksunxiboot root@SYNOLOGYNAS:/volumeUSB1/usbshare/usr/bin# mkimage -ash: mkimage: command not found
Re: Bricked Synology DS218j January 03, 2023 07:23AM |
Registered: 2 years ago Posts: 82 |
Re: Bricked Synology DS218j January 03, 2023 07:38AM |
Registered: 1 year ago Posts: 24 |
root@SYNOLOGYNAS:/volumeUSB1/usbshare/boot# /volumeUSB1/usbshare/usr/bin/mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.13.8-mvebu-tld-1 -d zImage116.fdt uImage116 -ash: /volumeUSB1/usbshare/usr/bin/mkimage: No such file or directory root@SYNOLOGYNAS:/volumeUSB1/usbshare/boot# /volumeUSB1/usbshare/usr/bin/mkimage -ash: /volumeUSB1/usbshare/usr/bin/mkimage: No such file or directory
Re: Bricked Synology DS218j January 03, 2023 07:55AM |
Registered: 2 years ago Posts: 82 |
Re: Bricked Synology DS218j January 03, 2023 10:53AM |
Registered: 1 year ago Posts: 24 |
-rw-r--r-- 1 root root 205052 Aug 7 2021 config-5.13.8-mvebu-tld-1 drwxr-xr-x 2 root root 4096 Aug 8 2021 dts -rw-r--r-- 1 root root 9649821 Sep 24 2021 initrd.img-5.13.8-mvebu-tld-1 -rw-r--r-- 1 root root 7785524 Aug 8 2021 linux-headers-5.13.8-mvebu-tld-1_1.0_armhf.deb -rw-r--r-- 1 root root 4461631 Aug 7 2021 System.map-5.13.8-mvebu-tld-1 -rw------- 1 root root 5236162 Jan 3 17:32 uImage116 -rw------- 1 root root 5238426 Jan 3 17:40 uImage2350 -rw------- 1 root root 5236933 Jan 3 17:37 uImage816 -rw-r--r-- 1 root root 9649885 Sep 24 2021 uInitrd -rwxr-xr-x 1 root root 5218232 Aug 7 2021 vmlinuz-5.13.8-mvebu-tld-1 -rwxr-xr-x 1 root root 5236098 Jan 3 13:45 zImage116.fdt -rwxr-xr-x 1 root root 5238362 Jan 3 17:39 zImage2350.fdt -rwxr-xr-x 1 root root 5218232 Aug 8 2021 zImage-5.13.8-mvebu-tld-1 -rwxr-xr-x 1 root root 5236869 Jan 3 17:36 zImage816.fdt root@SYNOLOGYNAS:/volumeUSB1/usbshare/boot#
Quote
bodhi
If it looks ok I'm ready for the next magic step to bring the DS218j to live igain... :)
Re: Bricked Synology DS218j January 03, 2023 02:56PM |
Admin Registered: 13 years ago Posts: 18,821 |
printenv
setenv fdt_skip_update yes setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial" tftpboot 0x800000 uImage116 tftpboot 0x2100000 uInitrd bootm 0x800000 0x2100000
Re: Bricked Synology DS218j January 03, 2023 04:05PM |
Registered: 1 year ago Posts: 24 |
Quote
bodhi
Please post the entire serial console log (from u-boot banner until the last line on your terminal).
Re: Bricked Synology DS218j January 03, 2023 04:24PM |
Admin Registered: 13 years ago Posts: 18,821 |
[ 3.203342][ T1] spi-nor spi0.0: mx25l6405d (8192 Kbytes) [ 3.209084][ T1] 6 fixed-partitions partitions found on MTD device spi0.0
[ 3.361467][ T1] armada38x-rtc f10a3800.rtc: registered as rtc0 [ 3.367783][ T1] armada38x-rtc f10a3800.rtc: setting system clock to 2023-01-03T21:58:25 UTC (1672783105)
[ 4.709932][ T1244] usb-storage 3-1:1.0: USB Mass Storage device detected [ 4.717082][ T1244] scsi host2: usb-storage 3-1:1.0 [ 5.782380][ T1504] scsi 2:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 4 [ 5.792564][ T23] sd 2:0:0:0: [sda] 30310400 512-byte logical blocks: (15.5 GB/14.5 GiB)
[ 10.082011][ T543] scsi 0:0:0:0: Direct-Access ATA ST1000DM010-2DM1 CC46 PQ: 0 ANSI: 5 [ 10.091573][ T1504] sd 0:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
setenv fdt_skip_update yes setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial" tftpboot 0x800000 uImage816 tftpboot 0x2100000 uInitrd bootm 0x800000 0x2100000
setenv fdt_skip_update yes setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial" tftpboot 0x800000 uImage2350 tftpboot 0x2100000 uInitrd bootm 0x800000 0x2100000
Re: Bricked Synology DS218j January 03, 2023 04:48PM |
Registered: 1 year ago Posts: 24 |
Re: Bricked Synology DS218j January 03, 2023 06:04PM |
Admin Registered: 13 years ago Posts: 18,821 |
Quote
https://forum.doozan.com/read.php?2,133377,133377#msg-133377
- the 5.13.8 kernel was not very stable, but just enough to get install the 6.0.7 kernel, which works very well. Took a few reboots. So if you see problems like a kernel dump about cpu stalls, just try again.
Quote
https://forum.doozan.com/read.php?2,32146
Updated 09 Nov 2022:
Kernel 6.0.7-mvebu-tld-1 package has been uploaded.
New/Updated in this release:
- General kernel upgrade.
Latest Linux kernel 6.x general release information can be found at:
LinuxChanges log
Download at Dropbox
linux-6.0.7-mvebu-tld-1-bodhi.tar.bz2
md5:
bfb1d7cf103f501b991e21b9886db4f6
sha256:
dcf50e17352f7d84ab606abdef374ec0d3db1c39b242c6ae7924b7283edc3ead
mkdir -p /volumeUSB1/boot/linux-6.0.7 cd /volumeUSB1/boot/linux-6.0.7 tar xjf linux-6.0.7-mvebu-tld-1-bodhi.tar.bz2
uImage116-k6 uImage2350-k6 uImage816-k6
Re: Bricked Synology DS218j January 04, 2023 02:42AM |
Registered: 1 year ago Posts: 24 |
Re: Bricked Synology DS218j January 09, 2023 09:15AM |
Registered: 1 year ago Posts: 24 |
tftpboot 0xd00000 zImage tftpboot 0x800000 rd.bin tftpboot 0x1000000 dtbdump_3.dtb bootm 0xd00000 0x800000 0x01000000
Re: Bricked Synology DS218j January 09, 2023 03:36PM |
Admin Registered: 13 years ago Posts: 18,821 |
setenv fdt_skip_update yes setenv bootargs "console=ttyS0,115200 root=/dev/sda1 rootdelay=10 earlyprintk=serial" tftpboot 0x800000 uImage bootm 0x800000
Re: Bricked Synology DS218j January 09, 2023 04:55PM |
Registered: 1 year ago Posts: 24 |
> setenv fdt_skip_update yes > setenv bootargs "console=ttyS0,115200 > root=/dev/sda1 rootdelay=10 earlyprintk=serial" > tftpboot 0x800000 uImage > bootm 0x800000 >>
Re: Bricked Synology DS218j January 09, 2023 05:40PM |
Admin Registered: 13 years ago Posts: 18,821 |
setenv fdt_skip_update yes setenv bootargs "console=ttyS0,115200 root=/dev/sda1 rootdelay=10 earlyprintk=serial" tftpboot 0x800000 uImage bootm 0x800000
Re: Bricked Synology DS218j January 09, 2023 10:31PM |
Admin Registered: 13 years ago Posts: 18,821 |
Quote
- Thanks salahuddin for bring up the Synology DS218j.
Re: Bricked Synology DS218j January 10, 2023 06:16AM |
Registered: 1 year ago Posts: 24 |
Re: Bricked Synology DS218j January 10, 2023 04:40PM |
Admin Registered: 13 years ago Posts: 18,821 |
Quote
setenv load_image_addr 0x02000000
setenv load_initrd_addr 0x3000000
setenv load_image 'echo loading uImage from raw HDD ...; scsi device 0; scsi read $load_image_addr 0x5000 0x2F00'
setenv load_initrd 'echo loading uInitrd from raw HDD ...; scsi device 0; scsi read $load_initrd_addr 0xA000 0xAF00'
setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"'
setenv bootcmd_exec 'echo Booting Debian ...; run set_bootargs; setenv fdt_skip_update yes; setenv initrd_high 0xffffffff; run load_image; run load_initrd; bootm $load_image_addr $load_initrd_addr'
setenv bootcmd 'scsi init; run bootcmd_exec; echo Booting Stock OS ...; run bootspi'
setenv load_image_addr 0x02000000 setenv load_initrd_addr 0x3000000 setenv fdt_skip_update yes setenv initrd_high 0xffffffff setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial" tftpboot $load_image_addr uImage tftpboot $load_initrd_addr uInitrd bootm $load_image_addr $load_initrd_addr
Quote
Updated 10 Sep 2019:
Rootfs Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 has been uploaded.
Basic Debian buster armhf rootfs for most MVEBU Armada NAS:
- tarball size: 258M
- install size: 680M
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below.
- Installed packages: openssh-server, nano, avahi, libnss-mdns, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, locales, dialog, bzip2, nfs-kernel-server, nfs-common, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils, mtd-utils, u-boot-tools, rsync, pmount, i2c-tools, qemu-arm-static (x86 version).
- see LED controls in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root
Download at Dropbox:
Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2
md5:
ffa864878dd797241c0bea05d563239a
sha256:
15d111a119aa1b1909b33178056c5d11d310a16f84d66f741f4dfd7c7e5d1b59
Re: Bricked Synology DS218j January 11, 2023 04:56AM |
Registered: 1 year ago Posts: 24 |
Quote
You are still trying to boot with tftp and USB rootfs, so the envs should be
setenv load_image_addr 0x02000000 setenv load_initrd_addr 0x3000000 setenv fdt_skip_update yes setenv initrd_high 0xffffffff setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial" tftpboot $load_image_addr uImage tftpboot $load_initrd_addr uInitrd bootm $load_image_addr $load_initrd_addr
Marvell>> setenv load_image_addr 0x02000000 setenv load_image_addr 0x02000000 Marvell>> setenv load_initrd_addr 0x3000000 setenv load_initrd_addr 0x3000000 Marvell>> setenv fdt_skip_update yes setenv fdt_skip_update yes Marvell>> setenv initrd_high 0xffffffff setenv initrd_high 0xffffffff Marvell>> setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial" setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial" Marvell>> tftpboot $load_image_addr uImage tftpboot $load_image_addr uImage Using egiga0 device TFTP from server 192.168.1.137; our IP address is 192.168.1.102 Filename 'uImage'. Load address: 0x2000000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ##################### 727.5 KiB/s done Bytes transferred = 5076212 (4d74f4 hex) Marvell>> tftpboot $load_initrd_addr uInitrd tftpboot $load_initrd_addr uInitrd Using egiga0 device TFTP from server 192.168.1.137; our IP address is 192.168.1.102 Filename 'uInitrd'. Load address: 0x3000000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ############################################################## 781.3 KiB/s done Bytes transferred = 9488618 (90c8ea hex) Marvell>> bootm $load_image_addr $load_initrd_addr bootm $load_image_addr $load_initrd_addr ## Booting kernel from Legacy Image at 02000000 ... Image Name: Linux-5.2.9-mvebu-tld-1 Created: 2023-01-11 8:05:54 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5076148 Bytes = 4.8 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 03000000 ... Image Name: initramfs-5.2.9-mvebu-tld-1 Created: 2019-08-26 11:03:27 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 9488554 Bytes = 9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid Marvell>>
setenv fdt_skip_update yes setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial" tftpboot 0x800000 uImage tftpboot 0x2100000 uInitrd bootm 0x800000 0x2100000
root@debian:/# ls -l ls -l total 263916 drwxrwxrwx 3 root root 4096 Jan 10 23:43 @eaDir drwxrwxrwt 2 root root 4096 Jan 10 23:42 @tmp -rwxrwxrwx 1 1026 users 269907402 Jan 10 23:33 Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 drwxr-xr-x 2 root root 4096 Aug 26 2019 bin drwxr-xr-x 3 root root 4096 Jan 11 00:05 boot drwxr-xr-x 13 root root 13240 Jan 11 01:53 dev drwxr-xr-x 70 root root 4096 Sep 5 2019 etc drwxr-xr-x 2 root root 4096 Sep 11 2016 home drwxr-xr-x 13 root root 4096 Aug 26 2019 lib drwx------ 2 root root 4096 Jan 9 2017 lost+found drwxr-xr-x 2 root root 4096 Jan 20 2017 media drwxr-xr-x 2 root root 4096 Jan 2 2017 mnt drwxr-xr-x 2 root root 4096 Jan 2 2017 opt dr-xr-xr-x 80 root root 0 Dec 31 1969 proc drwx------ 5 root root 4096 Sep 9 2019 root drwxr-xr-x 6 root root 200 Jan 11 01:53 run drwxr-xr-x 2 root root 4096 Aug 26 2019 sbin drwxr-xr-x 2 root root 4096 Jan 2 2017 srv dr-xr-xr-x 12 root root 0 Jan 11 01:53 sys drwxrwxrwt 2 root root 4096 Sep 5 2019 tmp -rw------- 1 root root 0 Jan 11 00:05 uImage drwxr-xr-x 10 root root 4096 Jan 2 2017 usr drwxr-xr-x 11 root root 4096 Jan 2 2017 var root@debian:/# cd boot cd boot root@debian:/boot# ls -l ls -l total 56220 -rw------- 1 root root 3266081 Aug 19 2019 System.map-5.2.9-mvebu-tld-1 -rw-r--r-- 1 root root 183639 Aug 19 2019 config-5.2.9-mvebu-tld-1 drwxr-xr-x 2 root root 4096 Aug 19 2019 dts -rw-r--r-- 1 root root 9488554 Aug 26 2019 initrd.img-5.2.9-mvebu-tld-1 -rw-r--r-- 1 root root 9676808 Aug 19 2019 linux-headers-5.2.9-mvebu-tld-1_1.0_armhf.deb -rw------- 1 root root 5076212 Jan 11 00:05 uImage -rw-r--r-- 1 root root 9488618 Aug 26 2019 uInitrd -rw------- 1 root root 5057632 Aug 19 2019 vmlinuz-5.2.9-mvebu-tld-1 -rwxr-xr-x 1 root root 5057632 Aug 19 2019 zImage -rwxr-xr-x 1 root root 5057632 Aug 19 2019 zImage-5.2.9-mvebu-tld-1 -rwxr-xr-x 1 root root 5076148 Jan 10 23:57 zImage.fdt root@debian:/boot#
Re: Bricked Synology DS218j January 11, 2023 08:26AM |
Registered: 1 year ago Posts: 24 |
Re: Bricked Synology DS218j January 11, 2023 03:52PM |
Admin Registered: 13 years ago Posts: 18,821 |
ifconfig -aAnd then open another terminal and try SSH in. The same credential is root/root.
ssh root@<the DS218j IP address>
Re: Bricked Synology DS218j January 11, 2023 04:09PM |
Registered: 1 year ago Posts: 24 |
Re: Bricked Synology DS218j January 11, 2023 04:41PM |
Registered: 1 year ago Posts: 24 |
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Wed Jan 11 14:28:07 2023 debian 192.168.1.138 Synology RS816 Linux version 5.2.9-mvebu-tld-1 (root@tldDebianVM) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #1 SMP PREEMPT Mon Aug 19 12:47:39 PDT 2019 Debian 10.0 Wed Jan 11 14:29:31 PST 2023 up 2 minutes root@debian:~#
Re: Bricked Synology DS218j January 11, 2023 05:10PM |
Admin Registered: 13 years ago Posts: 18,821 |
Quote
Make sure you follow the instruction verbatim. Being root user (not sudo), create a single partition, format it using Ext3 (not Ext4) file system, and label it as rootfs.
su - whoami
fdisk /dev/sdx
mkfs.ext3 -L rootfs /dev/sdx1
Re: Bricked Synology DS218j January 11, 2023 05:12PM |
Admin Registered: 13 years ago Posts: 18,821 |