Hi again! A lot has come in between, but I thought I'd look further into this now. Unfortunately, I can't find any rescue files that are needed, so I'm unfortunately a bit stuck. Hmm.by elexidor - Debian
radium Wrote: ------------------------------------------------------- > https://www.synology-forum.de/threads/ds218j-blinkt-blau-nach-gescheitertem-fw-update-full-unbrick-user-story.124187/ > > You can try this Ok, I'll check it out and mess with the German language a bit :)by elexidor - Debian
bodhi Wrote: ------------------------------------------------------- > > Ok, I have found a package from Synology which > is > > not encrypted and will try to create an uImage > > using the RS816 DTB. I assume that is the best. > > Not really. You need the kernel images from DSM, > similar to ones you used before. > > > tftpboot 0xd00000 zImageby elexidor - Debian
Quotebodhi You should look for DSM firmware kernel image and initrd and then write them to flash. Ok, I have found a package from Synology which is not encrypted and will try to create an uImage using the RS816 DTB. I assume that is the best.by elexidor - Debian
Quotebodhi Congrats! you're almost done. I love that sentence! :)) QuoteThe reason the reboot does not work because you have not set up the u-boot envs to boot automatically and save them to flash. Aha! QuoteBut in the mean time, you should be OK to explore and install Debian packages that you want to use I have no clue what I want or need. :) At this point I just want to bringby elexidor - Debian
I have now created a new USB disk entirely from a Linux system. Attached is a log file from start to finish at the debian login, then a lsblk -f command to show the file system and finally a reboot command.by elexidor - Debian
Quotebodhi That was wrong. You want to format the partition (sda is the whole disk). Should be Ahh, of course! Quotebodhi It should be able to boot all the way to the Debian login prompt if the disk was correctly formatted. So redo it one more time with my correction above. I must have used the wrong expression. It does boot all the way to the login promt. From synology_ds218j_boot_5_2_9_by elexidor - Debian
I can smell the taste of a working DC218j NAS ! I apologise for my poor Linux skills but I'm happy to learn. :) The file system thing is little bit strange. I do not have an Ubuntu/Linux machine so I used DiskGenius on Winows for creation of the USB disk partion/filesystem (ext3). I did it once more to verify and notised that the file system was ext3 but after inserting the USB diskby elexidor - Debian
I did a new try with the same envars and this time the file system check procedure completed and an automatic restart was performed. After that the CRC error was back. Attached log file: synology_ds218j_boot_5_2_9_filesys_check_compl.txt Then I did the same again, and this time the boot was ... completed (!) Attached log file: synology_ds218j_boot_5_2_9_boot_complete.txt and I can SSH inby elexidor - Debian
bodhi Wrote: ------------------------------------------------------- > What do you mean by a maintenance shell? > What we call a "maintenance shell" is when it > stopped booting at initrd. because of some error. > When you see the prompt "debian:" then it was done > booting. It seems that was the case here. And you > are golden :) > That was theby elexidor - Debian
In this thread salahuddin66 seemed to have exactly the same problem with CRC error in initrdramfs: https://forum.doozan.com/read.php?2,76314,122829#msg-122829 He mentioned that the root cause was the address range: https://forum.doozan.com/read.php?2,76314,122869#msg-122869 I have a strong feeling thats the same on my box. Hm. The positive side is I'm learning some more Linux stuff.by elexidor - Debian
Thank you bodhi! I have a feeling we're getting closer with 5.2.9 :) I created a new USB stick with Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 and think I did all the steps correctly. QuoteYou 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_by elexidor - Debian
bodhi Wrote: ------------------------------------------------------- > This test is better: > > synology_ds218j_boot_uimage116_k607_only.txt > > But it seems you did not have the USB rootfs > attached to the port. Also if you could, remove > the HDD from the slot. > > Reason: the USB rootfs is going to be /dev/sda1 if > it is the only storage drive atby elexidor - Debian
bodhi Wrote: ------------------------------------------------------- > elexidor, > > This uimage2350_k607 was created incorrectly. It > is showing the RS816 being used in the log > synology_ds218j_boot_uimage2350_k607.txt > > ======================= > > Here is another set of 3 tests (replace uImage > with each flavor). > > > setenv fdt_skby elexidor - Debian
Hi again! I have now tried to build three new versions based on zImage-6.0.7-mvebu-tld-1. Unfortunately I did not succeed to boot with any of them. I get stack exceptions after a while during boot and the 816-version did not worked at all (I may have done something wrong when build?) It is really pity because I dont think there are any hardware faults and it boots ok according to my firstby elexidor - Debian
bodhi Wrote: ------------------------------------------------------- > > Either try a few boots like Martin did. > > Or we can just use the latest kernel > 6.0.7-mvebu-tld-1 zImage. Download this kernel > tarball from the release thread: Ok, I've tried repeated boots but it just gets "stall on CPU". I'll test Kernel 6.0.7 when I get back from aby elexidor - Debian
Great! The box has two SATA but I'm not 100% sure about the status of the disks. Attached two new consol logs. Its midnight local time here so I will take a break and continue next morning. Thanks, so far. :)by elexidor - Debian
Quotebodhi Please post the entire serial console log (from u-boot banner until the last line on your terminal). Here is my console log. For some reason I can't interrupt at the count down but due to the CRC error it stops anyway just after.by elexidor - Debian
Mijzelf Wrote: ------------------------------------------------------- > In that case mkimage will be dependent on other > files which cannot be found due to the different > path. You can try to chroot it: > > chroot /volumeUSB1/usbshare/ /bin/sh > > That creates a new root in /volumeUSB1/usbshare/, > and executes /bin/sh from there. So > /volumeUSB1/usbsharby elexidor - Debian
Mijzelf Wrote: ------------------------------------------------------- > Use the full path: > /volumeUSB1/usbshare/usr/bin/mkimage Thanks, but no difference?!?: 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/usbshaby elexidor - Debian
Thank you for the help bodhi! I have tried to follow your recommended steps but as a Windows guy I'm struggling a bit with Linux basics. I have a second Synology box (DS220j) I can use and the creation of a Ext3 USB drive was no problem. Neither extract the tar. However, at the third step when creating the uImage the mkimage command cant be found: -rw-r--r-- 1 root root 205052by elexidor - Debian
Thank's for the reply bodhi! Quotebodhi In the rootfs folder /boot/dts: I tried all three files but non worked. It comes to the "Uncompressing Linux... done, booting the kernel." and hangs there. 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 Typby elexidor - Debian
This is a log with the entire procedure from manual boot until the DSM update fails via web browser:by elexidor - Debian
Hi! 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 Entby elexidor - Debian