I guess our journey ends here.. :'( But many thanks again for your patience and explanations. I've learned quite a lot, especially the last days with erasing and writing to NAND as well as partitioning ubi or the expressions of loading adresses... well, now the search begins for a cheap but reliable alternative storage, that provides my music collection to my network as well (Linuby alexinc - Rescue System
$ printenv bootargs bootargs=console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 earlyprintk=serial mem=128M poweroutage=yes Stage-1 Bootloader Tue Aug 9 16:44:00 CST 2011 Attempting to set PLLA to 750MHz ... plla_ctrl0 : 0x0000000A plla_ctrl1 : 0x000F0000 plla_ctrl2 : 0x001D01A0 plla_ctrl3 : 0x00000017 PLLA Set Setup memory, testing Reading NAND, Imageby alexinc - Rescue System
just took it apart as good as possible, but they soldered a heat shield over the whole area of cpu and ram... would need to desolder like 12 pins first to get access to ram chip(s)... hell yeah, time to give up on this project, i guess. it's not reachable via ssh or browser through 192.168.1.1 or 192.168.50.100 - so i guess it's stuck at booting kernel again.by alexinc - Rescue System
last step i took (instead of flashing stock mtd4)... OX820> ext2load ide 0:3 61000000 /19.07.5/openwrt-19.07.5-oxnas-ox820-mitrastar_stg-212-initramfs-uImage 5698471 bytes read in 729 ms (7.5 MiB/s) OX820> nand write 61000000 440000 56F3A7 NAND write: device 0 offset 0x440000, size 0x56f3a7 5698471 bytes written: OK Stage-1 Bootloader Tue Aug 9 16:44:00 CST 2011 Attempting toby alexinc - Rescue System
thanks for clearing that too. in the end it means, no matter what i do, as long as RAM may be broken, nothing will fix that error... i now wrote stock mdt1, mtd2 and mtd3 again. as mtd4 i used "openwrt-15.05-oxnas-stg212-u-boot-initramfs.bin". then i extended stock envs with second stage bootloader (as it was back then and in earlier openwrt days) and everything starts at least to thby alexinc - Rescue System
Once more i tried a different approach by unsquashing rootfs of openwrt-15.05.1 to (rescue) SSD root "rootfs" and loading belonging zImage and openwrt-oxnas-stg212.dtb into ram. booting results in the usual decompressing failure. i referred to http://blog.qnology.com/p/openwrt-on-pogoplug-v3oxnas-proclassic.html . Did i miss something in the envs to refer to right rootfs? shouldn'tby alexinc - Rescue System
> And the kernel is at mtd3. > > So that GitHub has a different MTD layout. It > probaly stock MTD. The DTS is OpenWrt flavor. Stock MTD is definitely different. MTD7 is sysdisk on stock. Then i would somehow need mtd1, mtd2 and mtd3 from openwrt as backup for flashing directly to NAND? But where to get that from? :-?by alexinc - Rescue System
bodhi Wrote: ------------------------------------------------------- > mtd7 is irrelevant while kernel booting. Break the > boot command into individual steps. Good to know. > Double check the syntax of this > > help nboot > > And > > nboot 61000000 0 440000 > bootm 61000000 > You mean after tftp Debian uImage? I guess so... Need some sleep firby alexinc - Rescue System
I already did that yesterday... ( https://forum.doozan.com/read.php?4,54044,134611#msg-134611 )by alexinc - Rescue System
daviddyer Wrote: ------------------------------------------------------- > Or put a heavy item on the ram / cpu and try to > boot it again. :P last of all options, just before being on my way to the window... ;-) guess it's not me jumping!by alexinc - Rescue System
Yes, i tried "mtest" without any given values is stuck at "Pattern 0000000". When running mtest 60000000 7FE0000 it is reading and writing circulation pattern non stop until i ^C. I didn't find anything explaining on the net, how it should work - which behaviour to expect, when it's finished and so on. So not very helpful to me to this point. I then tried mteby alexinc - Rescue System
$ tftp 0x61000000 uImage Wait GMAC to reset Wait for PHY reset. PHY is Realtek RTL8211E Wait for link to come up..........Link up Wait for auto-negotiation to complete Link is 1000M TFTP from server 192.168.50.59; our IP address is 192.168.50.100 Filename 'uImage'. Load address: 0x61000000 Loading: ################################################################# #by alexinc - Rescue System
Stage-1 Bootloader Tue Aug 9 16:44:00 CST 2011 Attempting to set PLLA to 750MHz ... plla_ctrl0 : 0x0000000A plla_ctrl1 : 0x000F0000 plla_ctrl2 : 0x001D01A0 plla_ctrl3 : 0x00000017 PLLA Set Setup memory, testing Reading NAND, Image 0 Hdr len: 0x0001A94C Hdr CRC: 0xF0019DAC OK U-Boot 1.1.2 (Jun 24 2011 - 09:41:57) U-Boot code: 60D00000 -> 60D1A94C BSS: ->by alexinc - Rescue System
another way failing: Stage-1 Bootloader Tue Aug 9 16:44:00 CST 2011 Attempting to set PLLA to 750MHz ... plla_ctrl0 : 0x0000000A plla_ctrl1 : 0x000F0000 plla_ctrl2 : 0x001D01A0 plla_ctrl3 : 0x00000017 PLLA Set Setup memory, testing Reading NAND, Image 0 Hdr len: 0x0001A94C Hdr CRC: 0xF0019DAC OK U-Boot 1.1.2 (Jun 24 2011 - 09:41:57) U-Boot code: 60D00000 ->by alexinc - Rescue System
no success for now Stage-1 Bootloader Tue Aug 9 16:44:00 CST 2011 Attempting to set PLLA to 750MHz ... plla_ctrl0 : 0x0000000A plla_ctrl1 : 0x000F0000 plla_ctrl2 : 0x001D01A0 plla_ctrl3 : 0x00000017 PLLA Set Setup memory, testing Reading NAND, Image 0 Hdr len: 0x0001A94C Hdr CRC: 0xF0019DAC OK U-Boot 1.1.2 (Jun 24 2011 - 09:41:57) U-Boot code: 60D0000by alexinc - Rescue System
bodhi Wrote: ------------------------------------------------------- > help no matter how often i post it, it's still the same limited stock u-Boot without any load possibility, besides tftp... ;-) $ help ? - alias for 'help' base - print or set address offset bdinfo - print Board Info structure bootm - boot application image from memory bootp - bootby alexinc - Rescue System
just a short summary before heading to bed... booting various openwrt initramfs from tftp always stuck at "Starting kernel..." - as i can't connect via browser or ssh to 192.168.1.1 nor 192.168.50.100 on subnet 255.255.255.0 or 255.255.0.0 then, i guess it's failing in uncompressing Linux again!? USB boot isn't working with having one ext2 partition called rootfs, sby alexinc - Rescue System
but with stock u-boot i can't boot from usb...by alexinc - Rescue System
Which way would you recommend? TFTP i have to try later at home... just tried starting schnee's rescue disk again, which leads to uncompression error once more. i fear, as stock linux from NAND doesn't uncompress either, i'm going to have the same results on everything i'll try again. at least with stock u-boot i only can TFTP images... we'll see later today. U-Boot SPby alexinc - Rescue System
What happens between E40000 and 1840000 (mtd5)? Why there is no backup (needed)? Ok, it's /etc. mtd ~ # cat /proc/mtd dev: size erasesize name mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit" mtd1: 00040000 00020000 "stage1" mtd2: 00380000 00020000 "uboot" mtd3: 00080000 00020000 "uboot_env" mtd4: 00a00000 00020000 "kernel"by alexinc - Rescue System
ok, it took a while of thinking about it, but at least it's writing now... sektor to start writing from in hex is 2240000 and complete ram is 7FE0000 that means there is just space left for writing filesize of 5DA0000 (not sure if there is a typo in build.sh which wants to write 5DC0000, but all documentations n the net say size of mtd7 is 5DC0000). OX820> nand write 61000000 224000by alexinc - Rescue System
hey schnee, thanks for getting back! unfortunately seems so: OX820> ext2load ide 0:2 61000000 /flash-recovery-hdd/MedionNAS/mtd7.backup 98304000 bytes read in 12499 ms (7.5 MiB/s) OX820> nand write 61000000 2240000 5dbffff NAND write: device 0 offset 0x2240000, size 0x5dbffff Attempt to write outside the flash area 0 bytes written: ERRORby alexinc - Rescue System
time for some really good news! as always you've brought me on the right track and are a big help and inspiration, solving this puzzle. starting your ways and getting the right adresses and information from build.sh script i'm on stock u-boot and environment again... lets keep the pace! i'm trying to flash the other stock mtds now too: OX820> nand erase.part 0 NAND erase.pby alexinc - Rescue System
bodhi Wrote: ------------------------------------------------------- > I begin to think perhaps we are seeing a faulty > RAM. Any chance to check that on the box? On the one hand it would be pretty annoying, but on the other it would mean I'm not that stupid at all understanding all those different options to boot Debian/OpenWRT from hdd, usb or NAND and still failing at someby alexinc - Rescue System
I'll try from scratch tomorrow again. It's almost 3am over here, need to catch some sleep. Thanks again for your patience! If you've got any other ideas or hints i can try tomorrow, let me know. It seems very promising, if that data gets written correctly. I could try recreating that rescue disk once again, without erasing the files that gets created by build.sh during the processby alexinc - Rescue System
bodhi Wrote: ------------------------------------------------------- > > nand erase 0x00040000 0x00380000 > ext2load ide 0:2 0x800000 mtd2.backup > nand write 0x800000 0x00040000 0x00380000 > still hangs here. shouldn't take ages writing 3,5M to NAND!? :-( fyi OX820> nand erase.chip NAND erase.chip: device 0 whole chip Skipping bad block at 0x07b20000by alexinc - Rescue System
so OX820> ext2load ide 0:2 0x800000 /boot/mtd/mtd1.backup 262144 bytes read in 46 ms (5.4 MiB/s) OX820> nand write 0x800000 0x00000000 0x00040000 OX820> ext2load ide 0:2 0x800000 /boot/mtd/mtd2.backup 262144 bytes read in 46 ms (5.4 MiB/s) OX820> nand write 0x800000 0x00040000 0x00380000 OX820> ext2load ide 0:2 0x800000 /boot/mtd/mtd3.data 262144 bytes read in 46 ms (by alexinc - Rescue System
bodhi Wrote: ------------------------------------------------------- > OK, so flash these. > > > -rw-r--r-- 1 root root 256K Apr 6 01:28 > mtd1.backup > -rw-r--r-- 1 root root 3,5M Apr 6 01:28 > mtd2.backup > -rw-r--r-- 1 root root 8,0K Apr 6 01:28 > mtd3.data > > > > But hard to see where they should be on NAND. > Let's check thby alexinc - Rescue System
bodhi Wrote: ------------------------------------------------------- > So follow the Wiki and flash my u-boot images to > NAND. See what'll happen. U-Boot SPL 2013.10-ga72eb8f-dirty (Feb 19 2014 - 15:21:12) Boot device: SATA Attempting to set PLLA to 800 MHz ... plla_ctrl0 : 0000030a plla_ctrl1 : 00400000 plla_ctrl2 : 007f0068 plla_ctrl3 : 00000193 PLLA Set Buby alexinc - Rescue System
bodhi Wrote: ------------------------------------------------------- > But it looks like they are not usable, because > they were built for SATA boot. Not stock MTD. If i got it right, those should be the stock mtd backups, at least that was the intension from it's creators (over here at a german forum called mikrocontroller.net) - creating a rescue disk, that rebuilds everythingby alexinc - Rescue System