Hi Bodhi, I'll try by myself to not disturb you. My problem was that i didn't have the prompt, i had my nas reboot everytime without possibility to stop it with ctrl+c or anything. today, i have a Marvell>> prompt My goal is to go on DSM and then we will discuss to find everything we need to detect all disks and redo our debian with all informations.by BillyIT - Debian
Hi Bodhi, Thanks for your answer I would like to try to reboot on DSM to find all informations that we need to detect disks for example. But can't boot normally. i'll try what you said if i can't manage to boot on DSM.by BillyIT - Debian
Hi, Im back to unbrick my nas... I tried to boot it from long time without doing anything and bad news, it reboot in loop : __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | _by BillyIT - Debian
Hi Bodhi, No problem, take care about you. I have lots to do too :)by BillyIT - Debian
Hi Bodhi, I couldn't boot on DSM for now. Sorry.by BillyIT - Debian
Hi Bodhi, Good news, i succeed in put back DSM with this : Marvell>> setenv ipaddr 192.168.10.200 Marvell>> setenv serverip 192.168.10.244 Marvell>> setenv netmask 255.255.255.0 Marvell>> tftpboot 0xd00000 zImage Using egiga0 device TFTP from server 192.168.10.244; our IP address is 192.168.10.200 Filename 'zImage'. Load address: 0xd00000 Loadingby BillyIT - Debian
I put a new disk and no raid array. Maybe i need to upload another file with tftp to make the new disk bootable... Like when you buy the nas, you put disk and it ask you to install DSM on the disk.by BillyIT - Debian
Hi Bodhi, I didn't suceed in booting in DSM. I don't know how i did last time maybe it was easy because of some previous raid partition with dsm and i just boot with zImage before mouting the raid DSM stuff... Marvell>> tftpboot 0x800000 zImage Using egiga0 device TFTP from server 192.168.10.244; our IP address is 192.168.10.200 Filename 'zImage'. Load addresby BillyIT - Debian
Bodhi, I went a bit further with a new disk... it complained about no ext2,3,4 partition. So i hope that i could make a ext4 on the new disk and maybe it will copy DSM on it to boot... i hope so... Let me try tomorrow. too tired to go back one more time in my "office room". Go to bed :) Thanks for your help.by BillyIT - Debian
Hi Bodhi I'll try again till you give me another dtb or other thing. When we bought synology there is nothing that we put on the disks before. Thanks:)by BillyIT - Debian
Hi Bodhi, Sorry, i didn't succeed to boot on DSM for now, maybe you can spot my error : Hit any key to stop autoboot: 0 ## Booting image at f8090000 ... Bad Magic Number Marvell>> setenv ipaddr 192.168.10.200 Marvell>> setenv serverip 192.168.10.244 Marvell>> setenv netmask 255.255.255.0 Marvell>> ping 192.168.10.244 Using egiga0 device host 192.168.1by BillyIT - Debian
Hi bodhi OK Maybe we can find informations if I boot again on DSM ? I can try that to dig inside filesystem ?by BillyIT - Debian
Hi Bodhi, New try with the dtb from 9th april : root@Arc-170:~/tools# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p Sending boot message. Please reboot the target.../ Sending boot image... 0 % [......................................................................] 1 % [......................................................................] 3 % [..by BillyIT - Debian
Hi Bodhi, OK too with sata_rootfs and DTB from 6th march : root@Arc-170:~/tools# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p Sending boot message. Please reboot the target...- Sending boot image... 0 % [......................................................................] 99 % [....................................] U-Boot 2017.07-tld-1 (Seby BillyIT - Debian
Hi Bodhi, Sorry i didn't do the test before. With the DTB from 2023 06 march, we have a boot : root@Arc-170:~/tools# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p Sending boot message. Please reboot the target.../ Sending boot image... 0 % [......................................................................] 99 % [...........................by BillyIT - Debian
Hi Bodhi, i'll do that again. Redo the usb key, maybe there is a corruption because of lots of shutdown (the instability when i boot on debian but later the box reboots and i'm stucked in stock u-boot) Thanksby BillyIT - Debian
Hi Bodhi, I had no success to boot successfully from several days. Today i tried with the last DTB to boot on usb (not hdd). So i modified the uEnv.txt to boot en LABEL=rootfs and not sata_rootfs. Not working. I'll try to boot with the previous DTB (but it didn't work last time i tried) root@Arc-170:~/tools# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mby BillyIT - Debian
bodhi Wrote: ------------------------------------------------------- > Billy, > > > I tried the last DTB but the box crashed again > (i > > think it's a crash) > > I don't understand why it crashed either if i > > didn't change anything before this try with new > > DTB. > > Perhaps saving the DTB with a datetime stamp wouldby BillyIT - Debian
root@Arc-170:~/tools# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p Sending boot message. Please reboot the target...| Sending boot image... 0 % [......................................................................] <stripped> 99 % [....................................] U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700) ZyXEL NSA325 2-Bay Pby BillyIT - Debian
Hi Bodhi, I can't boot anymore without changing anything. Can you spot why ? I would like to do it remotely but if i can't remote, i'll need to do it manually, took the usb key, change the dtb, etc...by BillyIT - Debian
Just poweroff the nas and redo kwboot... I went farest but it stopped again. root@Arc-170:~/tools# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p Sending boot message. Please reboot the target.../ Sending boot image... 0 % [......................................................................] 1 % [......................................................by BillyIT - Debian
I tried just booting with the one that was working. I don't touch anything and i have the boot to stock u-boot... root@Arc-170:~/tools# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p Sending boot message. Please reboot the target...- Sending boot image... 0 % [......................................................................] 1 % [.............by BillyIT - Debian
ok, i'll wait for the changes i'm on it to test the last one and post logsby BillyIT - Debian
i'll try tomorrow, the laptop connected to the serial console of my nas is off.by BillyIT - Debian
It's not the dtb file for now... i try to binwalk against the DSM and try to find information about DS413J and GPIO with strings. I have extracted all untill i have this output_file that contains some interesting output but can't go further binwalk dsm dd if=dsm of=kernel.zImage bs=1 skip=64 binwalk -e kernel.zImage cd _kernel.zImage.extracted/ binwalk 4244 281 stby BillyIT - Debian
Hi Bodhi, i'm trying to reverse engineering the dtb... i'm close to it but can't find how to extract the information : strings output_file2 | grep 413j Apply DS 413j GPIO i have a file output_file2 that contains "data" and inside date i have some interesting informations that i want :) like : strings output_file2 | grep gpio arch/arm/mby BillyIT - Debian
I can't the box "crashed" either if I put fans at 4600 rpm. I put it in "manual" to try cool down. 56 -> 47 but crashed / reboot to stock uboot I'll try the "newest dtb"by BillyIT - Debian
I watch every 10 seconds the sensors, the last message was : root@faucon:~# watch -n 10 sensors Every 10.0s: sensors faucon: Fri Apr 7 03:41:29 2023 gpio_fan-isa-0000 Adapter: ISA adapter fan1: 4600 RPM (min = 0 RPM, max = 5000 RPM) kirkwood_thermal-virtual-0 Adapter: Virtual device temp1: +47.0 C The box was up for about 1:30 hourby BillyIT - Debian