bodhi Wrote: ------------------------------------------------------- > I think we need to adjust the mtds backup > procedure a bit. > > In summary, instead of dumping in stock OS. We > should do this > > - kwboot the good box with NSA325 u-boot > and adjust envs to boot with USB. > - And do the dd dumping in Debian. > > And then restore them on theby itangoii - uBoot
I took another look inside he Synology update package and see that rd.bin is in there along with VERSIONby itangoii - uBoot
For the heck of it I tried to boot it and Uboot is functional again and I can get to the Marvel prompt. It however is back to the same bootloop that it had before. If I'm inturpreting the startup correctly, Uboot would be mtd0 the image would be mtd1 and its failing at mtd2 which would be due to the mtd2 and up not flashing. __ __ _ _ | \/ | __by itangoii - uBoot
mtd0 and mtd1 went ok but others did not. root@debian:/boot# flash_unlock /dev/mtd0 root@debian:/boot# flashcp -v ds213.mtd0 /dev/mtd0 Erasing blocks: 144/144 (100%) Writing data: 576k/576k (100%) Verifying data: 576k/576k (100%) root@debian:/boot# flash_unlock /dev/mtd0 root@debian:/boot# flashcp -v ds213.mtd0 /dev/mtd0 Erasing blocks: 144/144 (100%) Writing data: 576k/576k (100%)by itangoii - uBoot
You have a typo in the flashunlock above and repeated mtd0. Just in case you were going to add that to the instructions. I also get this on any mtd after mtd0 mtd0 worked, but others result in root@debian:/boot# flash_unlock /dev/mtd1 flash_unlock: error!: could not unlock device: /dev/mtd1 error 22 (Invalid argument)by itangoii - uBoot
I'll go ahead but would like to ask a question. You said they are the same, are the displays in your message above showing hex in one view and decimal in the other (or something like that)? And do I need to do any setenv before the flash or just escape out of uboot and start on the usb?by itangoii - uBoot
Done. 94 % [......................................................................] 95 % [......................................................................] 97 % [......................................................................] 99 % [....................................] U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700) ZyXEL NSA325 2-Bay Power Media Server Soby itangoii - uBoot
Bohdi: I do apologize for the confusion, it seems from reading the last few messages I was thinking one thing and doing something else. Here is the full boot to the response of the cat command. root@ubuntu20:~# picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0 picocom v3.1 port is : /dev/ttyUSB0 flowcontrol : none baudrate is : 115200 parity is : none databits aby itangoii - uBoot
output of help from the Marvell prompt. Marvell>> help ? - alias for 'help' WOLTest - Wake On Lan u-boot testing base - print or set address offset bootm - boot application image from memory bootp - boot image via network using BootP/TFTP protocol bubt - Burn an image on the Boot Flash. cmp - memory compare cp - memory copy cpumap - Display CPU meby itangoii - uBoot
bodhi Wrote: ------------------------------------------------------- > Insead of boot, run the bootcmd directly: > > > run bootcmd > There is no setenvs command so I did setenv. run bootcmd is also command unknown.by itangoii - uBoot
Issuing the boot command after the setenv results in 'unknown command'by itangoii - uBoot
Well, i got it booted and checked the file sizes and it does not look as expected. Debian GNU/Linux 10 debian ttyS0 debian login: root Password: Last login: Wed Dec 31 16:10:00 PST 1969 on ttyS0 Linux debian 5.2.9-kirkwood-tld-1 #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019 armv5tel The programs included with the Debian GNU/Linux system are free software; the exact distribution terms foby itangoii - uBoot
Bodhi: I am setup to do tftpboot, and have all the *mtd? on a usb already in the bricked machine if you feel that may go easier.by itangoii - uBoot
bodhi Wrote: ------------------------------------------------------- > Ok, so no USB recovery implemented :)) Someone could make a fortune manufacturing two and four bay nas boxes that would be blank out of the box and you could install your own os. This is already a reality, but not at the same physical size. Raspberry could make a killing.by itangoii - uBoot
bodhi Wrote: ------------------------------------------------------- > Another test. > > Power down the box. Plug in either the USB rootfs > or any USB formatted as Ext3. > > Kwboot again, and observe to console log to see if > any auto recovery procedure starts. True to form Synology want's you to buy another one ;-) 95 % [...........................by itangoii - uBoot
bodhi Wrote: ------------------------------------------------------- > itangoii, > > On the bricked box, at kwboot serial console > prompt, > > > sflash info > sflash protect off > Looks to be working. Marvell>> sflash protect off Marvell>> sflash info Flash Base Address : 0xf8000000 Flash Model : ST N25Q064 Manufacturerby itangoii - uBoot
bodhi Wrote: > This command seems to be usable. If it is the same > as the sf command in typical u-boot, then we are > almost there. > > Now I need to look at the addresses of the mtds to > see how we can flash them. > > Please get the out put of > > > help sflash > > > I'll be back tomorrow to continue. I'm having to worby itangoii - uBoot
Well, aint this a kick in the head? I setup another computer with Ubuntu so that I would not have to deal with the comport being wanted by both the Win 10 host and Ubunto client. As mentioned above, neither picocom or kwboot was responding. This lead to making sure the usb com port was being seen with setserial. It wasn't. I plugged in another usb/com cable and there it was. So it seemby itangoii - uBoot
bodhi Wrote: ------------------------------------------------------- > Ok. > > When that spinning bar freezes, control-c right > away and recall the kwboot command, execute it > again. Do this several times, e.g 10 times, until > the box loads the image. > > If it still behaves the same way. Try the reverse: > power on the box and execute kwboot right awaby itangoii - uBoot
bodhi Wrote: ------------------------------------------------------- > > Well, I booted the good box and copied all the > > *mtd? over. I then tried kwboot with the mtd0 > on > > the bricked one and as soon as > > I plugged in the power it locked up the > software. > > Please post the log of kwboot session. I'm not sure how. I start kwbootby itangoii - uBoot
bodhi Wrote: ------------------------------------------------------- > > On the bricked box, you must load ds213.mtd0 with > kwboot (it is the correct size of 576K). > > Once you can start the bricked box with ds213.mtd0 > image, it will run and count down, interrupt the > count down and, > Well, I booted the good box and copied all the *mtd? over. I thenby itangoii - uBoot
bodhi Wrote: ------------------------------------------------------- > The back up was successful. Each was verified the > be the size we expected. > > > root@Diskstation1:~# ls -lh ds213.mtd? > -rw-r--r-- 1 root root 576K Oct 11 09:47 > ds213.mtd0 > -rw-r--r-- 1 root root 3.0M Oct 11 09:47 > ds213.mtd1 > -rw-r--r-- 1 root root 4.3M Oct 11 09:48 > dsby itangoii - uBoot
I went to the file listing to check size, but still seeing a discrepancy on file size so stopped there. 97 % [......................................................................] 99 % [....................................] U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700) ZyXEL NSA325 2-Bay Power Media Server SoC: Kirkwood 88F6282_A1 DRAM: 512 MiB WARNING: Caches notby itangoii - uBoot
Everything went well with a couple of notes for the instructions. Did you want the console log showing the results of your instructions, or the results for the hep and printenv commands? 1. You may want to advise where the files are saved as the user may not assume that they are in the current working directory. 2. The user will need to know how to mount the USB for file copy atby itangoii - uBoot
You were right, the last command would not work from an ssh session so I had to crack the case and hook up the serial connection. The information you asked for is below. Part from the ssh session and printenv from serial termninal. root@Diskstation1:~# dmesg [ 0.000000] Linux version 2.6.32.12 (root@build4) (gcc version 4.6.4 (Marvell GCC release 20150204-c4af733b 64K MAXPAGESIZE ALIby itangoii - uBoot
bodhi Wrote: ------------------------------------------------------- > itangoii, > > > Should I be able to acquire a working DS213 is > > there a procedure somewhere to extracting the > > necessary files from it? > Now this DS213 box MTDs definition is quite > different, so we need a set of dd and flashcp > commands specific to the DS213. I will heby itangoii - uBoot
Should I be able to acquire a working DS213 is there a procedure somewhere to extracting the necessary files from it? Is there anything else I can do with this one at this time? Thanksby itangoii - uBoot
bodhi Wrote: ------------------------------------------------------- > itangoii, > > To filter out the network driver activity and > compare to the previous boot with NSA325 kernel. > > Please post both output (just to summarize the > situation so we don't need to scroll back and > forth): > > dmesg | grep mv643xx_eth > > Straight boot.by itangoii - uBoot
bodhi Wrote: - > Try: > > At serial console, log into Debian as root, see if > the network link can be brought up this way. > > > ifdown eth0 > ifup eth0 > results root@debian:~# ifdown eth0 ifdown: interface eth0 not configured root@debian:~# ifup eth0 Internet Systems Consortium DHCP Client 4.4.1 Copyright 2004-2018 Internet Systems Consortium.by itangoii - uBoot
Digging further I find that my ubuntu box picks up enp0s3 for the net interface, but the u-boot is picking up the traditional eth0. From my research this may be an issue with the boot USB using an older version of the OS? Edit: This may explain it. https://superuser.com/questions/1345623/network-adapter-missing-in-ubuntu-18-04-after-migration-from-virtualbox-to-hyperby itangoii - uBoot