So where can I investigate next if its not the image?by saschbaer - Debian
so it has nothing to do with the nsa320.dts file? i thought maybe changing it to the pogo v4 as you said it could only be a 310s 320s or pogov4.by saschbaer - Debian
Nada... __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/by saschbaer - Debian
Here it is root@SaschSamsung:/media/saschbaer/rootfs/boot# cd /mnt/sdd1/boot root@SaschSamsung:/mnt/sdd1/boot# ls config-4.12.1-kirkwood-tld-1 System.map-4.12.1-kirkwood-tld-1 vmlinuz-4.12.1-kirkwood-tld-1 dts uImage zImage-4.12.1-kirkwood-tld-1 initrd.img-4.12.1-kirkwood-tld-1by saschbaer - Debian
I'm sorry... still the same setenv mainlineLinux yes Marvell>> setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' Marvell>> setenv usb_load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage' Marvell>> run set_bootargs Marvell>> printenv bootargs bootargs=console=ttyS0,115200 root=LABEby saschbaer - Debian
the files are ok: insgesamt 192032 drwxr-xr-x 2 root root 4096 Jul 24 02:12 bin drwxr-xr-x 3 root root 4096 Nov 18 14:59 boot -rw-r--r-- 1 root root 196352036 Nov 12 12:25 Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 drwxr-xr-x 5 root root 4096 Feb 24 2012 dev drwxr-xr-x 57 root root 4096 Nov 18 14:54 etc drwxr-xr-x 2 root root 4096 Jan 22 2012 homeby saschbaer - Debian
here it goes... Marvell>> setenv mainlineLinux yes Marvell>> setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=' Marvell>> setenv usb_load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage' Marvell>> setenv usb_load_uinitrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'by saschbaer - Debian
Here it goes... __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_|by saschbaer - Debian
did it, but same as before...by saschbaer - Debian
okay... Marvell>> setenv mainlineLinux yes Marvell>> setenv set_bootargs 'setenv bootargs console=ttyS0,115200' Marvell>> setenv usb_load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage' Marvell>> setenv usb_load_uinitrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd' Marvelby saschbaer - Debian
OK. formatted with ext2, created rootfs, made the dts with kirkwoodnsa320s uBoot recognized the stick and shows USB: scanning bus for devices... 2 USB Device(s) found Waiting for storage device(s) to settle before scanning... 1 Storage Device(s) found usb part print_part of 0by saschbaer - Debian
Hi, after a few try and errors (and reflashing) I noticed something in another forum: if you gpart an usb stick with ext2 name it boot and another ext4 name it rootfs the stick will be recognized correctly. also I found out that maybe the NAS NSA325 seems to have the same config as my Medion P89654. Maybe i should try to get the boot parts onto boot partition and the rest in rootfs? Doby saschbaer - Debian
Well I created the USB Stick (Intenso 32 GB) as root with ext3, extracted the tar... i choosed kirkwood320s, did the build on my Ubuntu x64 laptop, root@SaschSamsung:/media/sdd1/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.12.1-kirkwood-tld-1 -d zImage.fdt uImage Image Name: Linux-4.12.1-kirkwood-tld-1 Created: Sun Nov 12 12:43:05 2017 Imagby saschbaer - Debian
Happy News bodhi... with the help of helge i managed to set the NAS back to factory setting, reflashing the origin sys AND kept my data *bigsighofrelief* So, we may can start to manage Debian on the NAS. So ..what do we need at first now? It would be very nice if you can assist :-D and many many thanks for your help up to this point. Regards Saschbaerby saschbaer - Debian
bodhi, may you have a look here https://forum.doozan.com/read.php?2,32877,33022,quote=1 helge seems to have nanddumped the original md0,1,2 from a Medion Nas. May it be an idea testing if those uboot dumps can be flashed on my nas? seems the same confuguration just that he has a 2x2 TB and me 2x4 TB. What do you think, and if you agree, how do I get the dumps flashed then?by saschbaer - Debian
Hello again... I closed minicom, started your command (with and without -p) But theres only the fast spinning character, no feedback from the nas... I also checked TXD/RXD, and if i changed and started the spinning character went really slow then. as i changed back TXD/RXD its running fast again... any idea?by saschbaer - Debian
Morning... I got kwboot from my ubuntu distrib and downloaded the file. But if I start to use kwboot, I get special characters like this: Execute kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa310s.mtd0.kwb Output of Minicom: * MARVLL BARD: DB702A-GMtech LEby saschbaer - Debian
We have to do Option 3. Nobody has hacked the box before, and Medion hasn't a recovery Firmware. The autorecovery function doesnt work anymore because of the bricked fw. :-( So what to prepare?by saschbaer - Debian
What I meant by listing and log: normally, the first thing we want to do after we connect serial console or boot into stock OS, is to list the envs, and then keep a log of that for recovery purpose. Without that log, you can't restore a good set of envs to boot into stock OS, now that the current envs NAND area is bad. As I wrote, I have to admit I haven't saved the originalby saschbaer - Debian
Look back to the printenv you did in serial console when you first boot up this box with it (before the corruption). Did you list the envs and keep the log of that? Im not sure what you mean with list and log... I just did the printenv which is listed in here. I have to admit that I didn't save the original env list and log :-( I remember that in the fw_env.conf file there was justby saschbaer - Debian
Sorry for answering so late, but it seems that i bricked or damaged the uboot... i get this: __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | |by saschbaer - Debian
__ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** MARVELL Bby saschbaer - Debian
Hello, I own a Medion NAS with 2x4TB WD Harddisk Model WDC WD40EZRX-22SPEB0. I studied the forum about flashing several NAS to use Debian on it, but I'm unsure if my NAS has the possibility to do it. I have root access to my box and was able to install ipkg and other (so it can be used like an open stora.) The kernel is based on HipServ Axentra, version 2.6.31.8 (so very old...:-/)by saschbaer - Debian
Hello, I own a Medion NAS with 2x4TB WD Harddisk Model WDC WD40EZRX-22SPEB0. I studied the forum about flashing several NAS to use Debian on it, but I'm unsure if my NAS has the possibility to do it. I have root access to my box and was able to install ipkg and other (so it can be used like an open stora.) The kernel is based on HipServ Axentra, version 2.6.31.8 (so very old...:-/)by saschbaer - uBoot